mirrors/arti.git/crates/tor-dirserver/src/mirror, branch main mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=main 2026-08-05T18:57:30Z tor-dirserver: fix tests on OpenBSD 2026-08-05T18:57:30Z Andrew Kloet andrew@kloet.net 2026-08-05T18:57:30Z urn:sha1:c40cd3ce49b6cd3774379cef25230b8b6b34ead9 Use an IPv6 loopback address instead of the unspecified address when creating test servers. The address returned by binding to [::]:0 is not valid as a connection target on OpenBSD. 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. Much formatting churn for 2024 edition 2026-07-22T12:25:53Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-07-22T12:25:53Z urn:sha1:e64263b921638ceb9c6adf3967fdde39e0a73db2 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 tor-dirserver: Use "plain" consensus terminology rather than "ns" (fmt) 2026-07-15T12:00:00Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-07-01T13:24:49Z urn:sha1:d4c2fdbf55286b973a46d39d2fd086cb3077332f tor-dirserver: Use "plain" consensus terminology rather than "ns" 2026-07-15T12:00:00Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-06-17T10:59:06Z urn:sha1:06f06ef39269bb4a9b561e4d0a0dd197754419c5 It doesn't make sense to say that a plain consensus is an "ns" consensus, because "ns" stands for "network status" and all consensus flavours, and indeed votes, are network statusus. That's why tor-netdoc now uses "plain". Use that here too. tor-dirserver: Use real consensus types, not poc (fmt) 2026-07-15T12:00:00Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-06-17T11:03:33Z urn:sha1:56961bf0f8cc311fc3f314a81ea42d7718e2dcfb tor-dirserver: Use real consensus types, not poc 2026-07-15T12:00:00Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-06-17T10:56:24Z urn:sha1:48215b4f8afce519c2558791cf30f41dc79ec462 tor-netdoc: authcert: use TimerangeBound for UnverifiedAuthCert::verify (fmt) 2026-06-10T14:42:10Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-06-04T12:13:00Z urn:sha1:b6e5b60f02eb6c523a42ee3bc726b8dc6a8b94b0 Precisely the result of rustfmt. tor-netdoc: authcert: use TimerangeBound for UnverifiedAuthCert::verify 2026-06-10T14:42:10Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-06-04T12:10:18Z urn: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`.