mirrors/arti.git/crates/tor-netdir/src, branch arti-v1.4.5mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.52025-07-07T15:50:04ZTemporarily suppress mismatched_lifetime_syntaxes.2025-07-07T15:50:04ZGabriela Moldovangabi@torproject.org2025-07-07T15:50:04Zurn:sha1:a11b611466a5a73f5e06a0aabd17284a57d12fe3
See #2060.
NetParameters::saturating_update: log when a value is out of range2025-06-23T17:11:01ZJim Newsomejnewsome@torproject.org2025-06-10T22:01:15Zurn:sha1:2d79634258326e7f86471fe2b2720f83d215c2cc
On one hand, this can be quite noisy when something *is* out of range.
On the other hand, a clamped value shouldn't normally happen, and is
likely to result in surprising and otherwise difficult-to-debug
behavior.
Log unrecognized net params2025-06-23T17:11:01ZJim Newsomejnewsome@torproject.org2025-06-10T21:24:03Zurn:sha1:00fbefa2a70a72bd3193e098790219c6cb879858Merge branch 'hs-interval-min' into 'main'2025-06-11T01:04:54ZNick Mathewsonnickm@torproject.org2025-06-11T01:04:54Zurn:sha1:0a677a9b42558f23ceb1d46e6ee1d4251bd8acd7
tor-netdir: decrease minimum hsdir_interval from 30 to 5
See merge request tpo/core/arti!3042tor-netdir: decrease minimum hsdir_interval from 30 to 52025-06-10T21:00:11ZJim Newsomejnewsome@torproject.org2025-06-10T21:00:11Zurn:sha1:ba2247dfa42a6230c044ac23e631f5750b6f847b
This matches the spec change:
<https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/406>
Progress on:
<https://gitlab.torproject.org/tpo/core/chutney/-/issues/40038>
proto: Move NegotiatedHopSettings to a higher level2025-06-10T15:52:28ZNick Mathewsonnickm@torproject.org2025-06-05T16:11:30Zurn:sha1:e07000a2ea86f1205ed9dc44228c0b2c69f1a36b
We will construct this object based on the circuit parameters _and_
on the target's supported protocol versions, so we need to do so
when we have both pieces of info.
NetDir::pick_n_relays: avoid some unwarranted warnings2025-06-05T21:42:23ZJim Newsomejnewsome@torproject.org2025-06-05T21:17:10Zurn:sha1:044011474d5613e1ab314659f373ac852a31d221
Previously we logged a warning whenever `choose_multiple_weighted`
returns `Ok(iter)`, whenever `iter` contains fewer relays than
requested.
However, this is expected behavior of `choose_multiple_weighted` if the
filtered list of relays doesn't have the requested number of relays, in
which case it should return all of the relays in the filtered list.
In particular, this condition occurs regularly in test networks when
looking for candidate relays to add to the potential guard set while
excluding those already in the potential guard set.
We still warn if the returned list is fewer than requested, *and* fewer
than available in the filtered list.
netdir, relay-selection: require Fast and Stable for rendpoints.2025-05-20T19:22:08ZNick Mathewsonnickm@torproject.org2025-05-20T13:07:29Zurn:sha1:c51745d1d0cdfb3363d8b505c7c749f70276ab57
Since we don't know what kind of traffic we'll use a rendezvous
point for, we don't want to use it if it isn't "Fast" (reasonably
high bw) and "Stable" (unlikely to crash soon).
hs: Prevent a client from using a `MiddleOnly` relay for onion services2025-05-20T19:22:08ZNeel Chauhanneel@neelc.org2025-04-03T00:38:04Zurn:sha1:94baab29f330fd17269e6b44958896b3f9ca794a
> The actual impact of this patch is to prevent usage of MiddleOnly
> relays as Introduction Points. The Rendezvous Point logic isn't
> hooked up yet - nick
netdir: fix warning about an opportunity to use saturating_sub2025-05-16T01:31:14ZNick Mathewsonnickm@torproject.org2025-05-16T01:31:14Zurn:sha1:4aa98c7e3c462a4c83e303c9b52c8bebc4e44c9d