mirrors/arti.git/crates/tor-chanmgr/src/builder.rs, branch arti-v2.0.0

proto: Remove async for VerifiableChannel::check()

2026-01-22T16:16:44Z

Signed-off-by: David Goulet

proto: Send relay channel NETINFO in check()

2026-01-22T16:16:44Z

Once channel is verified and authenticate if need be, send the NETINFO. We require our advertised IP addresses for this so pass them to launch() as well to the UnverifiedRelayChannel. A cargo fmt change slipped in here, sorry about that. Signed-off-by: David Goulet

proto: Make VerifiableChannel::check() async

2026-01-22T16:16:44Z

Relay initiator needs to send CERTS and AUTHENTICATE in that function after verifiying the channel. And thus require to be async. Signed-off-by: David Goulet

relay: Pass advertised addresses to the channel handler

2026-01-22T16:16:44Z

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

chanmgr: Get rid of the builder outbound_chan_type

2026-01-13T18:46:18Z

Instead, we'll simply use `RelayInitiator` if the identity keys (identities) struct is set. This avoids the problem where someone could call outbound_chan_type() of the ChanMgrConfig and get the wrong channel type if with_identities() is set after. This way, a single call, `with_identities()` is what will define the outbound channel type so no chance of errors. This also removes the cfg_if {} around the builder creation in a much more simplified version. Related to #1599 Signed-off-by: David Goulet

chanmgr: Use the new tor-proto channel traits in builder

2026-01-13T18:46:18Z

Remove code duplication and simplifies the code by using the new VerifiableChannel and FinalizableChannel traits. Signed-off-by: David Goulet

proto: Add traits for public channel views

2026-01-13T18:46:18Z

Add traits that will be returned outside tor-proto allowing us to not expose client and relay specific channels. The goal is for the tor-chanmgr to get those objects implementing those traits and can build and run the reactor without knowing the specific underlying type. This allows us to have less code duplication and less client/relay distinction in the chanmgr. Signed-off-by: David Goulet

chanmgr: Add a relay channel connect to ChanBuilder

2026-01-13T18:46:18Z

First, this is not great. Lots of duplicated code but it is a starting point that we can build on top to remove code duplication. Future commit will address this but for now, the client and relay mechanics are implemented. Signed-off-by: David Goulet

chanmgr: Rename the connect_no_timeout() to be client specific

2026-01-13T18:46:18Z

Heavy refactoring coming up for the ChanBuilder. This renames connect_no_timeout() to be client specific and uses the client channel builder directly instead of the generic one. Previous commit added the outbound ChannelType to the ChanBuilder which means that we'll soon have a relay specific function to connect using the relay channel builder. Refactoring will then happen for shared code in those two functions. Signed-off-by: David Goulet

chanmgr: Add RelayIdentities to ChanBuilder

2026-01-13T18:46:18Z

Signed-off-by: David Goulet