mirrors/arti.git/crates/tor-dirserver, branch arti-v2.5.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.02026-06-30T15:30:57ZMerge branch 'version-bumps'2026-06-30T15:30:57ZNick Mathewsonnickm@torproject.org2026-06-30T15:30:57Zurn:sha1:e1f077b83d9a815afd01c546842d087be1debf2dVersion bumps for 2.5.02026-06-30T13:42:13ZNick Mathewsonnickm@torproject.org2026-06-30T13:42:13Zurn:sha1:245b03f5a48b4e58f8c84f072920160fc87be500
Closes #2617.
We've lucked out this time, and it turns out that every one of our
published crates gets a minor bump. So this was generated with:
```
for cr in $(./maint/list-crates); do
cargo set-version -p $cr --bump minor
done
```
Run "fixup-features".2026-06-30T12:03:01ZNick Mathewsonnickm@torproject.org2026-06-30T12:03:01Zurn:sha1:b9c7db0e3a3d3008a9413edd59cde3d805719ac9tor-dirserver: Change "categories" in Cargo.toml2026-06-22T14:23:21ZIan Jacksonijackson@chiark.greenend.org.uk2026-06-17T11:09:45Zurn:sha1:ce0c9a6c24df79749b3e43de31fd255d1fb1422f
We already seem to use "network-programming", which kind of fits.
Bump MSRV to 1.912026-06-15T13:18:11ZClara Englercve@cve.cx2026-06-15T12:59:25Zurn:sha1:e93e0e2f9f42f526a8e1aa64e6ea659ef31dd800
This commit bumps the MSRV to 1.91 which was released on 2025-10-30.
The Cargo.toml files were updated as follows:
```sh
git ls-files | \
grep ".*Cargo\.toml$" | \
xargs sed -i '' 's/^rust-version = "1\.89"$/rust-version = "1\.91"/g'
```
The following files were updated manually:
```
modified: .gitlab-ci.yml
modified: README.md
modified: flake.nix
modified: maint/docker-android/Dockerfile
```
tor-netdoc: authcert: use TimerangeBound for UnverifiedAuthCert::verify (fmt)2026-06-10T14:42:10ZIan Jacksonijackson@chiark.greenend.org.uk2026-06-04T12:13:00Zurn:sha1:b6e5b60f02eb6c523a42ee3bc726b8dc6a8b94b0
Precisely the result of rustfmt.
tor-netdoc: authcert: use TimerangeBound for UnverifiedAuthCert::verify2026-06-10T14:42:10ZIan Jacksonijackson@chiark.greenend.org.uk2026-06-04T12:10:18Zurn:sha1:ccac99474f98ef197a7dfc48930c2c67662e7991
TimerangeBound is reasonably nice and this will fit in better when we
want to verify votes.
Adjust the one non-test call site (in tor-dirserver) using .and_then.
In the tests:
* Where we expected success, call .check_valid_at and add another .unwrap().
* Where we expected signature verification failure, delete the time parameters.
* Where we expected timeliness failure, call .check_valid_at and map the error.
* With nontrivial tolerance, add calls to `extend_[pre_]tolerance`.
tor-dirserver: Promote tor-checkable dep2026-06-10T14:41:46ZIan Jacksonijackson@chiark.greenend.org.uk2026-06-04T13:27:28Zurn:sha1:b1992f30caaecff2f16073ef369687dc8f27a523
We're going to need to talk about Timebound in the non-test code.
everywhere: Add #[allow(clippy::string_slice)]2026-06-09T16:02:36ZClara Englercve@cve.cx2026-06-09T16:00:38Zurn:sha1:d0af4abbd7b371f1eade609202a730cd9a1c21d3
This commit adds #[allow(clippy::string_slice)] to all functions in the
code where string slices are used, alongside a TODO comment.
We do this add the function header to have it consistent, as things like
expression based allow's are still experimental.
maint: 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.