mirrors/arti.git/crates/tor-proto/src/relay, branch arti-v1.7.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.7.02025-10-27T16:48:23Zproto: Avoid identifying relay circuits using TunnelId2025-10-27T16:48:23ZGabriela Moldovangabi@torproject.org2025-10-23T15:21:09Zurn:sha1:2c67f190e8c491b77eb7b1941a2548d49e3c985a
We replaced TunnelId with UniqId in the relay code a while ago.
proto: Remove relay ChannelAuthenticationData builder2025-10-23T17:47:06ZDavid Gouletdgoulet@torproject.org2025-10-23T16:54:04Zurn:sha1:c6d2e8ca9bcad5d5259dc5aee7bfa9a67b8c96db
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Use Arc for relay identities object2025-10-23T17:47:05ZDavid Gouletdgoulet@torproject.org2025-10-23T14:33:16Zurn:sha1:3407ff852c667df663309df65ecbb71a5824ae30
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Remove LOG_PREFIX in relay handshake2025-10-23T17:46:24ZDavid Gouletdgoulet@torproject.org2025-10-23T14:01:38Zurn:sha1:488b4c2ac86902841e8b7de381d4f489953284e5
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>
proto: Add a relay channel builder2025-10-23T17:45:41ZDavid Gouletdgoulet@torproject.org2025-10-22T15:19:45Zurn:sha1:2d41498ffb84b25f42d2137fd871e1cca8db9c11
The client and relay channel builder don't share anything and return
different objects hence the seperation.
Furthermore, this seperation avoids having the client ChanMgr ability to
launch relay channels.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Add RelayIdentities object holding our keys2025-10-23T17:45:41ZDavid Gouletdgoulet@torproject.org2025-10-22T15:03:51Zurn:sha1:d8c63706f566f9043270f669cd1654d3502ae5a0
This is a intermediary object between tor-chanmgr and tor-proto that is
when building a relay channel, those keys/certs need to be set in the
ChannelBuilder so the tor-proto can use them to authenticate.
We avoid that way making tor-proto depending on tor-keymgr for the
ultimate goal to avoid tor-proto to have access to all the keys in the
KeyMgr.
Future commits will introduce a relay channel builder which will use
that object to set the keys.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Add the channel authentication data2025-10-23T17:45:36ZDavid Gouletdgoulet@torproject.org2025-10-22T14:39:02Zurn:sha1:6db57d6696a2cb289768326e24ecb9c20f6f69c1
This commit only adds a struct holding all the authentication data that
needs to be built during the verification process after all handshake
cells needed for authentication have been sent.
It lives in the VerifiedChannel struct so it can be used to build the
AUTHENTICATE cell and be sent before the NETINFO.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Add RelayInitiatorHandshake2025-10-23T17:44:42ZDavid Gouletdgoulet@torproject.org2025-10-22T14:25:16Zurn:sha1:fa78ad3aa8a47e579b55ed0025cc730bd0b159fe
This implements the relay initiator side of the handshake up to the
creation of an unverified channel.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Replace select! with select_biased!2025-10-22T12:40:18ZGabriela Moldovangabi@torproject.org2025-10-22T12:40:18Zurn:sha1:66b69bff855f7236cf1f3ca32b6cf95fd7de2d8b
We need to give the control channels higher priority here.