mirrors/arti.git/crates/tor-proto/src/relay/channel/responder.rs, branch arti-v2.1.0

proto: Pass PeerAddr at the channel handshake finish for initiators

2026-02-19T20:57:29Z

Responder relay handshake requires the peer address at the very start as it sends its NETINFO right away. For initiators, we only need it during the finalization process which is when the NETINFO is sent and the Channel is created. Signed-off-by: David Goulet

proto: Use the PeerAddr accross channel handshake

2026-02-19T20:57:29Z

This is a large change but it is basically using PeerAddr in the channel builder through the channel handshake code and into the Channel itself. Signed-off-by: David Goulet

relay: Pass our TLS cert to the responder verify process

2026-02-12T16:48:14Z

For the responder to build the authentication data, it needs its own certificate of the TLS handshake that it is responding to (as a TLS server). This resolves an important TODO(relay) in the code. Signed-off-by: David Goulet

proto: Enforce that channel method as unique SocketAddr

2026-02-12T16:11:07Z

During the channel handshake, we require the peer IP address for the canonicity check which requires the exact peer IP we are connected to. This commit adds a function that enforces this requirement on a ChannelMethod so anything else results in an error. It is to basically have stronger guarantee on the channel method we use in the handshake. Signed-off-by: David Goulet

proto: Channel finish() now handles canonicity

2026-02-12T16:11:07Z

All handshake pass the NETINFO cell, the advertised addresses (if any) and the peer address in order to build the Canonicity and build the channel with it. In order to pull this off, the "my_addrs" were added to several object along the NETINFO cell. We also pass the channel method when connecting (initiator) to a relay as we need this for this canonicity build. Signed-off-by: David Goulet

proto: Relay responder channel allow to be non_exhaustive

2026-02-09T20:49:37Z

Signed-off-by: David Goulet

proto: Publicly re-export MaybeVerifiableRelayResponderChannel

2026-02-09T20:49:37Z

This type is needed in the tor-chanmgr crate in order to decide to verify or not the underlying relay channel.

proto: Add missing clock_skew() to unverified channels

2026-02-04T18:22:17Z

Signed-off-by: David Goulet

proto: Introduce new relay responder channel types

2026-02-04T18:22:17Z

Add the unverified, verified, non verifiable flavor types of a responder channel. This follow on the previous commit to use the type system for stronger guarantees. Signed-off-by: David Goulet