mirrors/arti.git/crates/tor-proto/src, branch arti-v1.5.0

proto: Move TunnelId to a separate, shared module (fmt).

2025-08-28T10:54:49Z

proto: Move TunnelId to a separate, shared module.

2025-08-28T10:54:48Z

The `TunnelId*` types will be reused in the relay reactor (exit relays need to have the concept of a "tunnel ID" because of conflux). Now the `relay::reactor` module only has a single import from `client` (for the `unwrap_or_shutdown` helper, which we should be able to remove soon). From now, we will avoid importing anything from `client` in the `relay` module, and instead prefer refactoring the code as needed (to pull the implementation-agnostic parts outside of `client`). This commit has no functional changes, just code motion.

proto: Add a circuit module shared between client and relay impls.

2025-08-28T10:54:48Z

This is just code motion (I suggest reviewing with `--color-moved`). This also moves the implementation-agnostic parts from `tor_proto::client::circuit` to a new `tor_proto::circuit` module.

Merge branch 'relay-chan-msg' into 'main'

2025-08-28T09:53:17Z

proto: Add a new RelayCircChanMsg message subclass. See merge request tpo/core/arti!3198

proto: Avoid referring to restricted ChanMsgs as "subclasses".

2025-08-28T09:08:17Z

proto: Add a new RelayCircChanMsg message subclass.

2025-08-28T09:08:17Z

This will be used to restrict the types of messages that can be sent on the relay-specific channels.

proto: Derive ChanMsgSubclass for CreateResponse, ClientCircChanMsg.

2025-08-27T18:08:57Z

This enables us to remove the open-coded implementations in favor of the derived version.

proto: Add d-d macro for creating AnyChanMsg subclasses.

2025-08-27T18:08:57Z

The code for generating these is repetitive (see `CreateResponse` and `ClientChanMsg`), and we will soon need a `RelayChanMsg` type too, so now is a good time to introduce a helper for generating the boilerplate.

tor-proto: don't allow consecutive XOFF messages

2025-08-27T18:07:12Z

proto: Only allow VERSIONS cell for the new handshake state

2025-08-27T15:04:24Z

Due to this, it is not possible to get a VPADDING before because it requires a link protocol version to decideon the encoding: https://gitlab.torproject.org/tpo/core/torspec/-/issues/366 Signed-off-by: David Goulet