<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-guardmgr/src/bridge/relay.rs, branch arti-v2.5.1</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.1</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.1'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-10-06T18:52:44Z</updated>
<entry>
<title>tor-linkspec: Change HasAddrs::addrs to return an Iterator</title>
<updated>2025-10-06T18:52:44Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-10-01T11:56:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=dc9ff7b72e6a5f6746c5b6a6a6c50673d1c46688'/>
<id>urn:sha1:dc9ff7b72e6a5f6746c5b6a6a6c50673d1c46688</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Bridges: deduplicate addresses.</title>
<updated>2023-07-13T20:58:12Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-13T20:58:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b8334292fb11494f8a9bf768a8c5b606ef3ce79f'/>
<id>urn:sha1:b8334292fb11494f8a9bf768a8c5b606ef3ce79f</id>
<content type='text'>
Currently we list an address for a bridge twice if it is listed both
in the bridge line and the bridge descriptor. That can't be right.
</content>
</entry>
<entry>
<title>Use bool::then_some() as appropriate</title>
<updated>2023-04-11T19:32:32Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-04-11T19:32:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e26445b1b018ee924dd33b6d5eceaa4957da8baf'/>
<id>urn:sha1:e26445b1b018ee924dd33b6d5eceaa4957da8baf</id>
<content type='text'>
Now that we require a version of Rust that allows
`b.then_some(v)`, clippy complains about our use of
`b.then(|| v)`.
</content>
</entry>
<entry>
<title>Rename for_circuit_usage =&gt; as_relay_with_desc</title>
<updated>2022-11-30T18:16:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-30T18:16:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ed08cce1b55a9615c0aa17f14b561b333910d0f8'/>
<id>urn:sha1:ed08cce1b55a9615c0aa17f14b561b333910d0f8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove TODO to rename for_circuit_usage in favor of #623</title>
<updated>2022-11-10T17:11:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-08T16:32:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1ad45f164e1162fd14f571ea6433e1a2d3cf7b3f'/>
<id>urn:sha1:1ad45f164e1162fd14f571ea6433e1a2d3cf7b3f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Resolve todo!()s and TODOs around BridgeRelay::HasAddrs.</title>
<updated>2022-11-10T17:11:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-08T16:10:24Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=942dfc8487cc0e910d1fee7c8201c7d6903fab12'/>
<id>urn:sha1:942dfc8487cc0e910d1fee7c8201c7d6903fab12</id>
<content type='text'>
Also, add a bunch of reminders around these implementations that
`HasAddrs` returns all the address associated with you for GeoIp or
family purposes, even if they are _not_ ones that we should actually
contact you at.
</content>
</entry>
<entry>
<title>GuardMgr: Change BridgeSet, BridgeRelay to use more references</title>
<updated>2022-11-08T13:10:15Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-03T19:43:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f4149cd1331cb758a7ea1b49b3e13d618ec45112'/>
<id>urn:sha1:f4149cd1331cb758a7ea1b49b3e13d618ec45112</id>
<content type='text'>
This will match our needs better and help avoid some `Arc&lt;&gt;`s.

It will be especially helpful for avoiding `Arc`s we don't
actually have.
</content>
</entry>
<entry>
<title>guardmgr: Implement Universe for bridges.</title>
<updated>2022-11-02T12:06:43Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-10-28T15:55:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5867318a3590f2f557b482e832fb4de7c4e85a9d'/>
<id>urn:sha1:5867318a3590f2f557b482e832fb4de7c4e85a9d</id>
<content type='text'>
Now we can use a group of bridges as the basis for a sample of
guards.
</content>
</entry>
<entry>
<title>struct BridgeConfig: Rename from Bridge</title>
<updated>2022-10-12T12:54:25Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-10-12T12:54:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=19de97177552bdd24f2c65c14be9201a2b0586c9'/>
<id>urn:sha1:19de97177552bdd24f2c65c14be9201a2b0586c9</id>
<content type='text'>
Fixes #599
</content>
</entry>
<entry>
<title>Change multiplicity of ChannelMethod and addresses</title>
<updated>2022-10-11T12:53:31Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-10-06T20:35:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=74d4c73d090f28ba5a8dca4fda3f170a36c0fe16'/>
<id>urn:sha1:74d4c73d090f28ba5a8dca4fda3f170a36c0fe16</id>
<content type='text'>
Now each `ChanTarget` has at most one `ChannelMethod`, and only
`Direct` `ChannelMethods` can have multiple addresses.

Closes #600.
</content>
</entry>
</feed>
