<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-guardmgr/src, branch arti-v1.0.1</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.0.1</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.0.1'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-09-26T15:23:21Z</updated>
<entry>
<title>Add the necessary APIs for bridge-based circuit construction.</title>
<updated>2022-09-26T15:23:21Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-09-26T13:41:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3272c6fb04ca124908aa3863b9dd39534a1dd134'/>
<id>urn:sha1:3272c6fb04ca124908aa3863b9dd39534a1dd134</id>
<content type='text'>
</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>GuardMgr: Add TODOs for bridge support.</title>
<updated>2022-09-26T15:23:21Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-09-26T12:44:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ab5dd6cbc35162c0a5563b5c01e5f881cafe5f19'/>
<id>urn:sha1:ab5dd6cbc35162c0a5563b5c01e5f881cafe5f19</id>
<content type='text'>
This covers only the most basic notions of working with bridges:
that we need a separate set of guards, and that they have to
come from the list of known bridges.
</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>
<entry>
<title>Downgrade "guard set loaded" messages</title>
<updated>2022-08-25T15:03:19Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-08-25T15:03:19Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0f133de6b90e799d37fdcd9dc75f9f94acb6bb6c'/>
<id>urn:sha1:0f133de6b90e799d37fdcd9dc75f9f94acb6bb6c</id>
<content type='text'>
These aren't interesting to the user.
</content>
</entry>
<entry>
<title>enable doc_auto_cfg feature on every crate when documenting for docs.rs</title>
<updated>2022-08-24T16:22:41Z</updated>
<author>
<name>trinity-1686a</name>
<email>trinity@deuxfleurs.fr</email>
</author>
<published>2022-08-17T19:13:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7f939fa4804b3c934343141b79e8e2ded5fe0b0d'/>
<id>urn:sha1:7f939fa4804b3c934343141b79e8e2ded5fe0b0d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'main' into 'linkspec_refactor_v3'</title>
<updated>2022-08-10T14:48:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-08-10T14:48:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=36a28a8587bbef44daa735c52a0207434989f11b'/>
<id>urn:sha1:36a28a8587bbef44daa735c52a0207434989f11b</id>
<content type='text'>
# Conflicts:
#   crates/tor-netdir/semver.md</content>
</entry>
<entry>
<title>Make sure all HasRelayIds constaints allow ?Sized.</title>
<updated>2022-08-10T14:39:47Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-08-05T16:53:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6dc8b1af20ce25d37fee53ff0ec2997a7d96929c'/>
<id>urn:sha1:6dc8b1af20ce25d37fee53ff0ec2997a7d96929c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdir: Collapse by_id and by_relay_id into a single fn.</title>
<updated>2022-08-10T14:39:46Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-08-05T16:30:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=37b3daa11d7e51abe02a92c3fcabccec267dca28'/>
<id>urn:sha1:37b3daa11d7e51abe02a92c3fcabccec267dca28</id>
<content type='text'>
There are some downstream changes required for this to work, but
they are all just unit tests that could no longer infer the type of
an Ed25519 key.
</content>
</entry>
<entry>
<title>Final (?) API revisions for tor-linkspec</title>
<updated>2022-08-10T14:39:37Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-08-05T15:47:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2d4507ff35f8e8cf874c81d3754804b2c20f31aa'/>
<id>urn:sha1:2d4507ff35f8e8cf874c81d3754804b2c20f31aa</id>
<content type='text'>
With this change, each individual identity type becomes optional.
The functions that expose them unconditionally are now in a "legacy"
trait that only some downstream types are expected to implement.

There are new convenience APIs in HasRelayIds:
  * to return Option&lt;&amp;keytype&gt;,
  * to see if one identity-set contains another.

This commit will break several downstream crates!  For the
reviewer's convenience, I will put the fixes for those crates into a
series of squash! commits on this one.

tor-netdir
----------

Revise tor-netdir to accept optional identities.  This required some
caveats and workarounds about the cases where we have to deal with a
key type that the tor-netdir code does not currently recognize at
all.  If we start to add more identity types in the future, we may
well want more internal indices in this code.

tor-proto
---------

In order to make tor-proto support optional identities, there were
fewer changes than I thought.  Some "check" functions needed to start
looking at "all the ids we want" rather than at "the two known IDs";
they also needed to accommodate that case where we don't have an ID
that we demand.

This change will also help with bridges, since we want to be able to
connect to a bridge without knowing all of its IDs up front.

The protocol currently _requires_ the two current ID types in some
places. To deal with that, I added a new `MissingId` error.

I also removed a couple of unconditional identity accessors for
chanmgr; code should use `target().identity(...)` instead.

tor-chanmgr
-----------

This is an incomplete conversion: it does not at all handle channel
targets without Ed25519 identities yet.  It still uses those
identities to index its internal map from identity to channel; but
it gives a new `MissingId` error type if it's given a channel target
that doesn't have one.

We'll want to revise the map type again down the road when we
implement bridges, but I'd rather not step on the channel-padding
work in progress right now.

tor-guardmgr
------------

This change is mostly a matter of constructing owned identity types
more sensibly, rather than unwrapping them directly.

There are some places marked with TODOs where we still depend on
particular identity types, because of how the directory protocol
works.  This will need revisiting when we add bridge support here.

tor-circmgr
-----------

These changes are just relatively simple API changes in the tests.
</content>
</entry>
</feed>
