mirrors/arti.git/crates/tor-relay-crypto/src, branch main mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=main 2026-07-23T10:13:34Z tor-checkable: Rename `TimeBound::check_valid_*` to `if_valid_*` 2026-07-23T10:13:34Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-07-20T16:40:18Z urn:sha1:ca37f30a097696ce2ebd4e9945a4bdaebe086b31 I find these names confusing. To my mind "check" implies a function returning `Result<(), _>`. Some other APIs use `unwrap` here but I think `if` is good. Use new TimeBound name throughout the tree 2026-07-16T15:47:50Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-07-16T14:32:14Z urn:sha1:5f57903ab4a8c280acf8a5bec274c50d5f544fd6 add_warning: add reference to arti#2556 2026-07-15T17:56:49Z Jim Newsome jnewsome@torproject.org 2026-07-15T17:56:49Z urn:sha1:6d333d6e6f0bf4d75fdc81e8865e06f6537d5af6 Removed unnecessary lint 2026-07-15T17:16:51Z pryty26 238962075+pryty26@users.noreply.github.com 2026-07-15T17:07:59Z urn:sha1:d12e408c1d62f29e58647c91a2714c49e3004cc4 Removed unnecessary lint maint: Run maint/add_warning to deny string slices 2026-06-09T15:36:01Z Clara Engler cve@cve.cx 2026-06-09T15:36:01Z urn: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. tor-cert: Ed25519CertBuilder: do builder fn rename 2026-04-29T16:49:21Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-04-28T09:58:04Z urn:sha1:d90b703d0c4bc4ffb9068fb5c25fc78e72743961 Change all call sites. This completes the rename. relay: Modify RelayNtorKeys to use a constructor 2026-04-21T18:01:27Z David Goulet dgoulet@torproject.org 2026-04-21T14:27:41Z urn:sha1:e84f73d564b71c386b4e18020da0093839a8874a Because of the sorting requirement and the fact that a `KeyMgr` can have multiple Ntor keys, the caller now explicitly extract the two Ntor keys it wants from the `KeyMgr` and then creates a `RelayNtorKeys` object with them. Future changes (#2495) will move this into a view and warn if there are more than 2 keys. Signed-off-by: David Goulet <dgoulet@torproject.org> relay-crypto: Add RelayNtorKeys struct holding both Ntor keys 2026-04-21T18:01:27Z David Goulet dgoulet@torproject.org 2026-04-16T16:11:13Z urn:sha1:dc114d6c580b9360d241327b36e13f506d1cd529 Signed-off-by: David Goulet <dgoulet@torproject.org> relay-crypto: Add new RelayNtor key wrapper 2026-04-09T17:34:01Z Gabriela Moldovan gabi@torproject.org 2026-04-01T13:05:06Z urn:sha1:a677677e0bcbfd3cebe7c2e31f45bddbb00e2d07 arti-relay: Move all key specifiers to a new keys module 2026-04-01T11:17:50Z Gabriela Moldovan gabi@torproject.org 2026-04-01T10:45:21Z urn:sha1:2cdc938a1bca3aa84eb7317a17d7776e55af5ae4 This extracts the key specifier types out of `tor-relay-crypto`, which * makes the code layout consistent with the hidden service crates (the key specifiers are defined in a `keys` module in `tor-hsservice`, while the key wrapper types live in `tor-hscrypto::pk`) * helps reduce the API surface: the key specifiers are only used in `arti-relay`, so we can move them there and make them `pub(crate)` instead of `pub`