mirrors/arti.git/crates/tor-key-forge/src, branch mainmirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=main2026-07-23T10:13:34Ztor-checkable: TimeBound: Make wrapped type an associated type2026-07-23T10:13:34ZIan Jacksonijackson@chiark.greenend.org.uk2026-07-20T12:00:15Zurn:sha1:b16e7a5ac48daa3e2f94660bdf7c39f54e7c702c
It wouldn't make much sense for one concrete type to be unwrappable
variously as different inner types.
tor-checkable: TimeBound: Make is_valid_at a provided method2026-07-23T10:13:34ZIan Jacksonijackson@chiark.greenend.org.uk2026-07-16T15:30:15Zurn:sha1:9313f79335c2ba15e7e60bc6d97086c4c56ff30a
Now that we have `bounds()`, we can centralise this implementation and
delete the implementations.
I don't think it's necessary to provide an engineered safeguard
against downstreams overriding this method. Any existing implementors
of this trait will break because they must provide `.bounds()` now,
which is an opportunity to notice that the `is_valid_at` can be
deleted. But, if it is not deleted, nothing goes wrong.
tor-checkable: TimeBound: remove Error associated type2026-07-23T10:13:34ZIan Jacksonijackson@chiark.greenend.org.uk2026-07-16T15:19:05Zurn:sha1:726f97b2a2099eea34d804e0132cf742964af8b7
This was always TimeValidityError. And we want to rely on that so we
can do the validity checking more centrally.
tor-checkable: TimeBound: Add bounds accessor2026-07-23T10:13:34ZIan Jacksonijackson@chiark.greenend.org.uk2026-07-20T18:25:52Zurn:sha1:845f56aeedabfd44ec4573f872aeefa77cf72556
This makes a `TimeBound` much more convenient to work with, will allow
more centralisation.
This replaces temporary `bound` inherent method on `TimeRangeBound`.
Use new TimeBound name throughout the tree2026-07-16T15:47:50ZIan Jacksonijackson@chiark.greenend.org.uk2026-07-16T14:32:14Zurn:sha1:5f57903ab4a8c280acf8a5bec274c50d5f544fd6add_warning: add reference to arti#25562026-07-15T17:56:49ZJim Newsomejnewsome@torproject.org2026-07-15T17:56:49Zurn:sha1:6d333d6e6f0bf4d75fdc81e8865e06f6537d5af6Removed unnecessary lint2026-07-15T17:16:51Zpryty26238962075+pryty26@users.noreply.github.com2026-07-15T17:07:59Zurn:sha1:d12e408c1d62f29e58647c91a2714c49e3004cc4
Removed unnecessary lint
tor-key-forge: add a `secret()` accessor to the derived keypair type2026-06-25T02:46:15ZSteven Engleropara@torproject.org2026-06-25T02:45:46Zurn:sha1:c719fe1a49a984b3d4b6362c8f4f7e6b61ab3ac8maint: Run maint/add_warning to deny string slices2026-06-09T15:36:01ZClara Englercve@cve.cx2026-06-09T15:36:01Zurn:sha1:9f5752a77fb57052c06ead0eeae606831f1e8e97
This commit executes maint/add_warning with the just added change to
deny string slices except in tests.
I recommend auditing this by checking out the previous commit followed
by running the script yourself and then verifying that the diff is
identical to this commit.
This commit makes cargo clippy fail. We will add exceptions in the next
commit.
Upgrade rand crates to 0.10.2026-05-12T20:55:43ZWesley Aptekar-Casselsme@wesleyac.com2026-05-07T20:06:21Zurn:sha1:a18167928901d8c88cd1cdd87346de8ad1ee42a2
When the circ-padding feature is enabled, we use maybenot, which does
not yet support rand 0.10. In the meantime, enabling this feature pulls
in rand 0.9. This is not ideal, but should be okay as a temporary
situation.
This also replaces the use of ReseedingRng (which was removed in 0.10)
with the reseeding_rng crate. This is somewhat less performant, but it
should be okay.