<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-guardmgr/src/bridge.rs, branch arti-v1.1.9</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.9</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.9'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-11-21T14:58:24Z</updated>
<entry>
<title>BridgeConfigBuilder: Introduce the struct with the dictionary repr</title>
<updated>2022-11-21T14:58:24Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-11-18T16:32:11Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=589f74a78f05f0d9fbdc9844d6686b0cbb60878d'/>
<id>urn:sha1:589f74a78f05f0d9fbdc9844d6686b0cbb60878d</id>
<content type='text'>
This struct is going to be the principal "dictionary-style" serde
representation for a bridge, and the builder, making this all in
keeping with our usual approach.

In this commit:
 * Introduce the struct (defining the serialisation)
 * Provide the setters (defining the Rust API)
 * Add success test cases (not all of the data in which is used yet)
</content>
</entry>
<entry>
<title>GuardMgr: Remove TODO to move `mod bridge` to another crate</title>
<updated>2022-11-10T17:11:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-08T16:28:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b8792307acf386177e393d5dbf79c50b152a83f2'/>
<id>urn:sha1:b8792307acf386177e393d5dbf79c50b152a83f2</id>
<content type='text'>
The code seems happy enough here for now.
</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>tor-guardmgr: bridges: export BridgeDescError at toplevel</title>
<updated>2022-10-27T14:57:54Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-10-21T13:30:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a89daba1c8bdbd329877edb5535a8bfdd0416f7b'/>
<id>urn:sha1:a89daba1c8bdbd329877edb5535a8bfdd0416f7b</id>
<content type='text'>
</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>tor-guardmgr: Export BridgeParseError from toplevel</title>
<updated>2022-10-12T12:50:29Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-10-05T17:33:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f9e841841a1ed17e9d2c167aafc9da58ec3acbdc'/>
<id>urn:sha1:f9e841841a1ed17e9d2c167aafc9da58ec3acbdc</id>
<content type='text'>
Callers could `use` it as `tor_guardmgr::config::BridgeParseError` but
it seems unecessary to force them to.
</content>
</entry>
<entry>
<title>Start on a new BridgeRelay type.</title>
<updated>2022-10-04T21:49:32Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-10-04T17:13:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d9e3d38bd642015132a4e523825bb987970e2bef'/>
<id>urn:sha1:d9e3d38bd642015132a4e523825bb987970e2bef</id>
<content type='text'>
This is the one we'll actually use to connect to bridges. It
has a `Bridge` line, and an optional `BridgeDesc`.

Maybe this will turn into a `BridgeRelay&lt;'a&gt;` by analogy to `Relay`
some time; I'm not sure.
</content>
</entry>
<entry>
<title>GuardMgr/DirMgr: Add APIs for bridge descriptor lists</title>
<updated>2022-09-26T15:23:21Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-09-26T13:28:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1196e1b6800273680a4c893d50ea31e77fd7746c'/>
<id>urn:sha1:1196e1b6800273680a4c893d50ea31e77fd7746c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>A basic configuration type for a bridge.</title>
<updated>2022-09-26T15:23:21Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-09-23T19:42:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e097d644172ccbf4377eaf3b5ee082034e02329b'/>
<id>urn:sha1:e097d644172ccbf4377eaf3b5ee082034e02329b</id>
<content type='text'>
This type goes in tor-guardmgr, since that's where decisions about
circuits' first hops are made.

There are a lot of "todo"s here for us to resolve.
</content>
</entry>
</feed>
