mirrors/arti.git/crates/tor-netdoc/src/doc/hsdesc, 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. tor-checkable: TimeBound: Make dangerously_into_parts return TimeRange 2026-07-23T10:13:34Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-07-20T10:38:50Z urn:sha1:632e87a5355305d6200fb3d3f78555f244139c37 It is better to return a more cooked type. `TimeRange` aka `TimeRangeBound<()>` is perfect for this. tor-checkable: TimeRangeBound: Rename bounds to bounds_start_end 2026-07-23T10:13:34Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-07-20T08:49:42Z urn:sha1:4c86579d470fbd4d5e71619f24bd1bc35c073776 This just returns a tuple. We're going to introduce a new method that returns a `TimeRagne` and will want to be called `bounds`. That method will want to be in the `TimeBound` trait, but for now we add it here. Various call sites will be added in forthcoming commits. Use new TimeRangeBound name throughout the tree 2026-07-16T15:47:50Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-07-16T14:35:45Z urn:sha1:92c26c4c07be73c91890ed3d7d4e53a06f26d0a1 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 Merge branch 'upgrade-cipher' into 'main' 2026-07-13T09:44:20Z gabi-250 gabi@torproject.org 2026-07-13T09:44:20Z urn:sha1:edbccf96e5245b5ec9e6df28806d52d3f3401145 Upgrade cipher, aes, and ctr. See merge request tpo/core/arti!4195 Upgrade cipher, aes, and ctr. 2026-07-13T09:44:19Z Nick Mathewson nickm@torproject.org 2026-07-13T09:44:19Z urn:sha1:295a9f1547886f3556b49d2329cc63c076429897 Change HS descriptor sendme_inc into a NonZeroU8 2026-07-02T14:37:16Z Nick Mathewson nickm@torproject.org 2026-07-02T14:17:20Z urn:sha1:31b0293b3356ef3d7d99c2780419e0048a07c211 This saves us from having to check whether it is 0, and better represents what the type is allowed to be. netdoc: Add new capability negotiation pieces to hsdesc. 2026-07-02T14:37:13Z Nick Mathewson nickm@torproject.org 2026-06-08T18:27:55Z urn:sha1:3b818d01e5d6c8d8432c82c952fe0b0fbf0a7004 The "flow-control" item is documented in proposal 324 section 9.1; there's a ticket (torspec#418) to document it. The "proto" item is documented at https://spec.torproject.org/rend-spec/hsdesc-encrypt.html#item:proto 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.