<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-guardmgr/src/sample/candidate.rs, branch ios-sqlite-hacks</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=ios-sqlite-hacks</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=ios-sqlite-hacks'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-11-28T13:01:53Z</updated>
<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>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: Spelling fixes and normalizations.</title>
<updated>2022-11-08T13:10:15Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-04T19:34:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3943c6cd1ed3706019a56edbaddd6705587d8203'/>
<id>urn:sha1:3943c6cd1ed3706019a56edbaddd6705587d8203</id>
<content type='text'>
</content>
</entry>
<entry>
<title>GuardMgr: Refactor UniverseRef to contains Arcs.</title>
<updated>2022-11-08T13:10:15Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-04T17:46:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=25d79248324820d06ffa7183743adfaed5699f8c'/>
<id>urn:sha1:25d79248324820d06ffa7183743adfaed5699f8c</id>
<content type='text'>
We already _have_ these Arc&lt;&gt;s whenever we construct a UniverseRef,
so there's no real point in using &amp;refs and making these so
hard to construct.
</content>
</entry>
<entry>
<title>GuardMgr: Pass correct universe to "Bridges" `GuardSet`.</title>
<updated>2022-11-08T13:10:15Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-04T13:45:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=697a355a21968d40c431db5072943fd9a6dc7999'/>
<id>urn:sha1:697a355a21968d40c431db5072943fd9a6dc7999</id>
<content type='text'>
This can probably be done in a simpler way, but for the moment I
would prefer to try to minimize the amount of code I'm changing
here.
</content>
</entry>
<entry>
<title>Refactor CandidateStatus API to simplify code in descs.</title>
<updated>2022-11-02T12:07:32Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-01T21:43:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c2ed381c99ec91b1be0e84a4467f9b1cf30c3cdf'/>
<id>urn:sha1:c2ed381c99ec91b1be0e84a4467f9b1cf30c3cdf</id>
<content type='text'>
This removes some duplication.
</content>
</entry>
<entry>
<title>GuardMgr: Fix and improve comments based on review.</title>
<updated>2022-11-02T12:07:32Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-01T21:14:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fc0c12510adce24d7c16e0b31ed79d65e75b366d'/>
<id>urn:sha1:fc0c12510adce24d7c16e0b31ed79d65e75b366d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>guardmgr: Refactor candidate info; add `full_dir_info`</title>
<updated>2022-11-02T12:07:11Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-10-28T16:28:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=08473872abccf389db261b4631f83a7cf42c7976'/>
<id>urn:sha1:08473872abccf389db261b4631f83a7cf42c7976</id>
<content type='text'>
Previously we always set `dir_info_missing` to `false` for new
guards, since new guards could only be taken from ones that were
present in the NetDir.  But for bridges, we don't download their
info until _after_ we have chosen them as guards.
</content>
</entry>
<entry>
<title>guardmgr: Universe API should look up by ChanTarget</title>
<updated>2022-11-02T12:06:43Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-10-28T15:04:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=79dade342a39e670a6e47849150826372d6351f1'/>
<id>urn:sha1:79dade342a39e670a6e47849150826372d6351f1</id>
<content type='text'>
This will be necessary for bridges.
</content>
</entry>
<entry>
<title>guardmgr: take sampled guards from Universe.</title>
<updated>2022-11-02T12:06:43Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-10-26T17:32:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=82e9a57012ccff3c9a510eb34ff04039e50961aa'/>
<id>urn:sha1:82e9a57012ccff3c9a510eb34ff04039e50961aa</id>
<content type='text'>
This is a trickier case, since we have to deal with weights.
</content>
</entry>
</feed>
