mirrors/arti.git/crates/tor-proto/src/channel.rs, branch arti-v2.0.0

proto: Move TimeoutEstimator to util

2026-01-29T16:33:21Z

This will be used in the stream reactor too (and the stream reactor will eventually replace the corresponding client impl).

proto: Improve some comments in relay module

2026-01-22T16:16:44Z

Signed-off-by: David Goulet

proto: Remove async for VerifiableChannel::check()

2026-01-22T16:16:44Z

Signed-off-by: David Goulet

proto: Move cell sending out of check() and into finish()

2026-01-22T16:16:44Z

This is so check() only authenticate a channel. The finish() function now only sends back the missing cells and build the final Channel. To pull this off, the AUTHENTICATE cell and our IP addresses need to be copied into the VerifiedRelayChannel. This allows us to remove complexity into the check() function as well and future commit will remove the async. Signed-off-by: David Goulet

proto: Authenticate a relay channel

2026-01-22T16:16:44Z

This commit is a bit loaded but it is coherent. First, we set Eq and PartialEq to the channel message Authenticate so we can compare it with the one we expected. Second, the AuthenticationCell enum is introduced to store either an AUTH_CHALLENGE or an AUTHENTICATE since one side of the handshake can only have one. This allows us to store one or the other in UnverifiedRelayChannel. Depending on what we have, the authentication process is different as it dictates which side we are on (initiator vs responder). Keep in mind that the handshake code enforces receiving a AUTH_CHALLENGE along side CERTS. And same goes for AUTHENTICATE which means that if we have an AUTH_CHALLENGE in the UnverifiedRelayChannel, it is certain that the other side wants to authenticate and we are the initiator. Finally, the sending of CERTS and AUTHENTICATE by the initiator is now in UnverifiedRelayChannel::check() done right after verifying the channel CERTS and holding a "VerifiedChannel" object. This means that the last piece, sending the `NETINFO` by the initiator will be done in the check() but in a future commit. This leaves the VerifiableChannel::finish() to send nothing and only finalize the channel with the NETINFO (canonicity). 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

proto: Make CERTS cell optionnable for UnverifiedChannel

2026-01-22T16:16:44Z

This requires to make a series of cert and digest also optionnable in the VerifiedChannel. This change is needed because as a relay responder, you might get the CERTS or not depending on if the other side wants to authenticate. Client and bridges do not authenticate and thus it is expected to not have a CERTS cell. This leads to the UnverifiedChannel::check() function to return early with a VerifiedChannel without any identity attached to it. Signed-off-by: David Goulet

proto: Fix comments documentation

2026-01-13T18:46:18Z

proto: Seal the VerifiableChannel and FinalizableChannel traits

2026-01-13T18:46:18Z

They are public but avoid anyone outside implementing them. Signed-off-by: David Goulet

proto: Improve channel trait comments

2026-01-13T18:46:18Z

Signed-off-by: David Goulet