mirrors/arti.git/crates/tor-proto/src/channel.rs, branch arti-v1.8.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.02025-11-24T16:28:07Zopentelemetry: Instrument a bunch of functions.2025-11-24T16:28:07ZWesley Aptekar-Casselsme@wesleyac.com2025-11-24T16:28:07Zurn:sha1:a4db6a7495b13dd7b00416dd1660a5ad82b60919
These are all aimed at figuring out in more detail what's going on
in #2079 and related issues.
proto: Add a TODO relay for ChannelBuilder2025-11-19T19:42:47ZDavid Gouletdgoulet@torproject.org2025-11-19T18:43:05Zurn:sha1:156c564030755d2fa7feeaf313474be8aa9ad69e
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Make cargo doc happy2025-11-19T19:42:47ZDavid Gouletdgoulet@torproject.org2025-10-28T18:40:44Zurn:sha1:ce838fbdcea7b313f7b58b5a5c59328d3cc03bca
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Add client specific handshake channel structs2025-11-19T19:42:47ZDavid Gouletdgoulet@torproject.org2025-10-28T16:33:43Zurn:sha1:a16d8c28952685e18ed4223707c119a25945bf23
This adds the UnverifiedClientChannel and VerifiedClientChannel
mirroring the relay API for channels.
It plainly uses the generic object underneath as for now those objects
are client only.
Followup commits will make things more client specific.
No behavior change.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Move client handshake into client channel module2025-11-19T19:42:47ZDavid Gouletdgoulet@torproject.org2025-10-28T15:36:09Zurn:sha1:16d73b136b639f0f1a0ec6e128fa9e1e08260cdf
This only moves code from src/channel to src/client/channel.
It introduces a ClientChanBuilder that is used to launch client specific
channel by the public ChanBuilder.
The followup commits will add a VerifiedClientChannel and
UnverifiedClientChannel in order to again decouple client and relay code
from the generic objects.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Add VerifiedRelayChannel implementation2025-11-19T19:42:47ZDavid Gouletdgoulet@torproject.org2025-10-28T15:12:51Zurn:sha1:3281ca08ec1184ed7bee2f4deca1046ad68dbb6b
Add the finish() function that for now simply calls the generic
finish(). There is a bunch of TODO in the code in this commit explaining
why we haven't made the implementation relay specific just yet.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Add UnverifiedRelayChannel implementation2025-11-19T19:42:47ZDavid Gouletdgoulet@torproject.org2025-10-28T14:57:58Zurn:sha1:23b300c46d2c5a32392b88c5f99a1d26870ba882
This commits takes out the relay specific code out of UnverifiedChannel
and puts it in UnverifiedRelayChannel.
In order to pull this off, we added some fiels to the VerifiedChannel
struct so the relay code get back generated data from the
UnverifiedChannel::check() in order to do its validation work and yield
a VerifiedRelayChannel.
This also lead to a cleanup of expect() and ChannelType::is_initiator().
Signed-off-by: David Goulet <dgoulet@torproject.org>
tor-proto: Reduce `high_water_mark` of ChannelFrame2025-11-05T23:53:47Znieldcontact@ndvibes.com2025-11-05T23:53:47Zurn:sha1:1bf62c63ac58fb822c193bc96d8bea1473791528proto: Feature flag some relay specific code2025-10-23T17:47:06ZDavid Gouletdgoulet@torproject.org2025-10-23T14:44:26Zurn:sha1:0fb991e2369ea80e2c1d1e70b566eb7bd4b38968
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Compute authenticate data after validating certificates2025-10-23T17:46:24ZDavid Gouletdgoulet@torproject.org2025-10-22T15:58:33Zurn:sha1:95d256e0828b8a00f7af67a3a1cda5822136c51c
This is only done if we kept the AUTH_CHALLENGE cell and we have relay
identities. In other words, this is only when the UnverifiedChannel was
created from a RelayInitiatorHandshake.
Note: The check_internal() function is too large and should be
refactored in smaller pieces.
Note: It is also likely that we need to split UnverifiedChannel and
VerifiedChannel as it is getting client or relay members. Not great.
Signed-off-by: David Goulet <dgoulet@torproject.org>