mirrors/arti.git/crates/tor-relay-selection/src/restriction.rs, branch mainmirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=main2026-06-09T15:36:01Zmaint: 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.
Fix name of clippy lint to unchecked_time_subtraction (2)2025-11-06T11:28:22ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-06T11:23:25Zurn:sha1:a5fd5c48ea059a80cc1f6c50e248654b5ff3aaff
Run maint/add_warning
tor-linkspec: Change HasAddrs::addrs to return an Iterator2025-10-06T18:52:44ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-01T11:56:57Zurn:sha1:dc9ff7b72e6a5f6746c5b6a6a6c50673d1c46688
This will let us model the actual structure of routerstatus entries in
netdocs more closely. They don't have the addresses in a single list.
When this code was written this would have been much more awkward,
but now we have RPITIT.
Switch Cargo.toml files to edition 2024.2025-08-07T15:28:36ZNick Mathewsonnickm@torproject.org2025-08-06T01:19:58Zurn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc
First, run
```
git grep -l "^edition =" |
xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```
Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.
Third, run cargo fmt again.
netdir: Consider RelayFamilyIds based on family rules2025-02-25T14:29:50ZNick Mathewsonnickm@torproject.org2025-02-10T21:10:15Zurn:sha1:9650d0b75d6a5ce5c554cb0ac04077374a889538
This implements the client side of proposal 321.
It's a breaking change in netdir, since in_same_family now takes an
extra argument.
relay-selection: Add FamilyRules to exclude_relays_in_same_family.2025-02-25T14:29:50ZNick Mathewsonnickm@torproject.org2025-02-10T20:51:36Zurn:sha1:5ce84e59b6031416a7d404d20c3a2efce0ec5f2a
When we're trying to exclude relays by family,
we need to know which lists to look at.
This information ultimately comes from the network parameters.
We could avoid this change if we just told clients
"look at all family information all the time",
but that's not what the proposal says.
This is a breaking change.
Rename `Relay::same_relay` and make it private.2024-03-28T12:21:14ZNick Mathewsonnickm@torproject.org2024-03-27T18:37:04Zurn:sha1:909afb6977f2e186b3af18cccf430d5d0f0b2aa1
Everybody outside of tor-netdir should use
HasRelayIds::same_relay_ids, whose intent is clearer.
Remove temporary functions in CheckedRelay.2024-03-28T12:21:14ZNick Mathewsonnickm@torproject.org2024-03-27T18:09:37Zurn:sha1:dd53eca3a35d5918e13cac50a13f2bb91ce622daRun maint/add_warning.2024-03-13T16:30:53ZNick Mathewsonnickm@torproject.org2024-03-13T16:30:53Zurn:sha1:c0c9bd15d42897825dd0ab3d3b8dd1c17bd6320cFix some rustdoc warnings.2024-03-12T14:50:11ZNick Mathewsonnickm@torproject.org2024-03-12T14:48:46Zurn:sha1:fc7221d286dd2f8b8d731d38a05da4a89fe78fb3
These are mostly about explicitly linking to things that were
already in scope.