<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-chanmgr/src/factory.rs, branch main</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=main</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-02-24T21:02:35Z</updated>
<entry>
<title>chanmgr: Responder relay channel now use the builder my_addrs</title>
<updated>2026-02-24T21:02:35Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2026-02-24T18:10:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cf30a925f51cab7672b894f28c72f4fccd7716cc'/>
<id>urn:sha1:cf30a925f51cab7672b894f28c72f4fccd7716cc</id>
<content type='text'>
No need to pass from the arti relay binary our addresses when handling
an incoming channel, use the one in the channel builder that an
initiator channel uses.
</content>
</entry>
<entry>
<title>chanmgr: Add a set_relay_identities() to update the RelayIdentities</title>
<updated>2026-02-24T17:34:18Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2026-02-24T15:28:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=393a0624d7fa20bdb6d3faa856346475860158ce'/>
<id>urn:sha1:393a0624d7fa20bdb6d3faa856346475860158ce</id>
<content type='text'>
The arti-relay crate rotates the keys at regular interval which we need
to give to the ChanMgr to update its builder.

This function boldly replace the default factory with the new identities
including the TLS acceptor can pick up the new key.

Signed-off-by: David Goulet &lt;dgoulet@torproject.org&gt;
</content>
</entry>
<entry>
<title>relay: Pass advertised addresses to the channel handler</title>
<updated>2026-01-22T16:16:44Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2026-01-14T19:17:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=05c703d7b510f7356be1ec9f0cd62735d7fcee78'/>
<id>urn:sha1:05c703d7b510f7356be1ec9f0cd62735d7fcee78</id>
<content type='text'>
We need the advertised addresses for the NETINFO cell when opening a
relay channel. Keep them in the TorRelay object so we can pass them to
the ChanMgr channel handler.

This will also help with config reload where only the local values in
TorRelay will need to be updated.

Signed-off-by: David Goulet &lt;dgoulet@torproject.org&gt;
</content>
</entry>
<entry>
<title>tor-chanmgr: wrap the peer address in `Sensitive`</title>
<updated>2025-11-05T19:31:01Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-10-28T05:06:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=de760f8049b901e0d99c345a700523b8e8b3cc25'/>
<id>urn:sha1:de760f8049b901e0d99c345a700523b8e8b3cc25</id>
<content type='text'>
For incoming connections, wrap the peer address in `Sensitive` as it
could be a client.
</content>
</entry>
<entry>
<title>opentelemetry: Add some instrument macros.</title>
<updated>2025-09-24T19:23:32Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2025-09-16T13:25:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e21ebd3793d497429ba7c8c437b346a9a2833407'/>
<id>urn:sha1:e21ebd3793d497429ba7c8c437b346a9a2833407</id>
<content type='text'>
I've added these in places that are useful for the debugging that I've
been doing.
</content>
</entry>
<entry>
<title>Switch Cargo.toml files to edition 2024.</title>
<updated>2025-08-07T15:28:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-06T01:19:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=77b0de43b8c67cdb81befe0680a3df43b6ad37bc'/>
<id>urn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc</id>
<content type='text'>
First, run

```
git grep -l "^edition =" |
    xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```

Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.

Third, run cargo fmt again.
</content>
</entry>
<entry>
<title>tor-proto: Plumb the ChannelAccount through to queue creation site</title>
<updated>2024-10-03T14:10:47Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-10-02T16:24:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=939d291ed3792a5fd1392f4e2816de254ac1bc12'/>
<id>urn:sha1:939d291ed3792a5fd1392f4e2816de254ac1bc12</id>
<content type='text'>
This gets it as far as the outbound circuit-&gt;channel mpsc queue creation.
Also, we provide an accessor for it.
</content>
</entry>
<entry>
<title>tor-proto: Plumb the ChannelAccount through to queue creation site (pre-fmt)</title>
<updated>2024-10-03T14:10:35Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-10-02T15:32:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=17f55b3302cb254506f0ce2a3421211b55eb5bc4'/>
<id>urn:sha1:17f55b3302cb254506f0ce2a3421211b55eb5bc4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-chanmgr: Make a memquota::ChannelAcocunt per channel</title>
<updated>2024-10-03T14:10:35Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-10-02T15:01:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2d685fb537dd8d43c1c873910c662c8283009fec'/>
<id>urn:sha1:2d685fb537dd8d43c1c873910c662c8283009fec</id>
<content type='text'>
This delivers a fresh account per channel to the places where channels
are actually made, but doesn't pass them to tor-proto yet.
</content>
</entry>
<entry>
<title>tor-chanmgr: add experimental `ChanMgr::handle_incoming`</title>
<updated>2024-09-11T18:15:16Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2024-09-04T14:38:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6dda7fc80834962d9485b8d92f63feacbcad4be8'/>
<id>urn:sha1:6dda7fc80834962d9485b8d92f63feacbcad4be8</id>
<content type='text'>
The channel manager in the future will need to be able to receive
incoming streams. The type of the stream depends on an associated type
within `ChannelFactory`, so this commit exposes this associated type
through several other types, eventually to the `ChanMgr`.

The new methods are behind the experimental "relay" feature flag.
</content>
</entry>
</feed>
