<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-guardmgr/src/bridge/descs.rs, branch arti-v2.3.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.3.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.3.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-03-26T19:20:17Z</updated>
<entry>
<title>tor-guardmgr: Port to web_time_compat.</title>
<updated>2026-03-26T19:20:17Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-03-26T15:06:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=02421eae87ee34653960046c25b6239b01f557c9'/>
<id>urn:sha1:02421eae87ee34653960046c25b6239b01f557c9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>squash! Upgrade rand dependency to 0.9.</title>
<updated>2025-03-18T16:09:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-18T13:01:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2f8993c22c2b86010e4fd8b5169ef0ab83f8c754'/>
<id>urn:sha1:2f8993c22c2b86010e4fd8b5169ef0ab83f8c754</id>
<content type='text'>
- `rand::thread_rng()` has been deprecated and renamed to `rand::rng()`
</content>
</entry>
<entry>
<title>GuardMgr: Treat Guards as sensitive and Bridges as redacted.</title>
<updated>2022-11-28T13:01:53Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-23T18:19:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cf9f29158f2958a7e8bfe19789289bec3de2dd8d'/>
<id>urn:sha1:cf9f29158f2958a7e8bfe19789289bec3de2dd8d</id>
<content type='text'>
This machinery is a bit inelegant, but it is all confined to
be within the GuardMgr crate, so IMO it should be fine for now.
</content>
</entry>
<entry>
<title>BridgeConfig: Replace all Arc&lt;BridgeConfig&gt; with BridgeConfig</title>
<updated>2022-11-22T15:33:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-11-22T15:28:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ee87097dc17650637e546a9833673fd2a5174033'/>
<id>urn:sha1:ee87097dc17650637e546a9833673fd2a5174033</id>
<content type='text'>
BridgeConfig is itself an Arc now, so these are redundant.
</content>
</entry>
<entry>
<title>Allow a subset-only ChanMethod match when looking up a BridgeConfig</title>
<updated>2022-11-15T18:53:14Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-15T18:18:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d78cde7dea34e4e9178050915d248a71d25338a1'/>
<id>urn:sha1:d78cde7dea34e4e9178050915d248a71d25338a1</id>
<content type='text'>
If we have a bridge guard that is using Direct connection and it
knows multiple addresses, our code to match it with a BridgeConfig
is wrong, because the BridgeConfig has only one address, and our
code looks for an exact match.

Fixes #642.
</content>
</entry>
<entry>
<title>GuardMgr: Update desired bridge descs from 'update' function.</title>
<updated>2022-11-14T18:36:10Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-10T18:47:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=92115aa366e81ec297ea16f347b1dc02965eb2d7'/>
<id>urn:sha1:92115aa366e81ec297ea16f347b1dc02965eb2d7</id>
<content type='text'>
There are some new TODOs here for us to think about, but I think
this will give us something to test.
</content>
</entry>
<entry>
<title>GuardMgr: Explain why we timestamp BridgeSets as we do.</title>
<updated>2022-11-10T17:11:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-08T15:15:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b91f7d61b30ed3d83769f217b6f44e8d9f1d2a63'/>
<id>urn:sha1:b91f7d61b30ed3d83769f217b6f44e8d9f1d2a63</id>
<content type='text'>
</content>
</entry>
<entry>
<title>GuardMgr Document why a BridgeSet has trivial weight thresholds.</title>
<updated>2022-11-10T17:11:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-08T17:34:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8cf04d2a3825f3f77ca7e167247471f0dd622586'/>
<id>urn:sha1:8cf04d2a3825f3f77ca7e167247471f0dd622586</id>
<content type='text'>
This is the only way I could find in which parameter interpretation
differs between bridge guards and relay guards; with it documented,
I can remove a TODO about identifying such ways.
</content>
</entry>
<entry>
<title>GuardMgr: Docs for BridgeDescProvider</title>
<updated>2022-11-08T16:35:35Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-08T14:43:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9dcfc2bb650527e012a59f938b6007ae40b2ae7d'/>
<id>urn:sha1:9dcfc2bb650527e012a59f938b6007ae40b2ae7d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>GuardMgr: Remove a TODO pt-client comment.</title>
<updated>2022-11-08T16:35:35Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-08T14:21:48Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=91cfd7ea4a43339fb6a3f72dac754c43b3c95099'/>
<id>urn:sha1:91cfd7ea4a43339fb6a3f72dac754c43b3c95099</id>
<content type='text'>
The BridgeSet type does not necessarily need further changes... and
if it gets them, it won't be because of this comment.
</content>
</entry>
</feed>
