mirrors/arti.git/crates/tor-cell/src, branch arti-v2.1.0

Allow clippy::collapsible_if to trigger

2026-02-16T15:22:24Z

`clippy::collapsible_if` started triggering after bumping the MSRV to 1.88. Since this triggers from a lot of places, and since there even are a couple of instances where we explicitly allow `clippy::collapsible_ifs`, I've opened #2342 for deciding what to do about it.

proto: Implement a Canonicity struct

2026-02-12T16:11:07Z

This struct will be put in a Channel and derived from the received NETINFO cell. This follows the C-tor implementation for which we have two indicator of canonicity: 1. Peer is canonical: the address they advertise in the NETINFO cell matches the one we see on the TCP connection. 2. Canonical to peer: the peer sees us as canonical. Those flag will get used to select "the best" channel. Signed-off-by: David Goulet

cell: Add an accessor for the linkspecs of an EXTEND2

2026-02-05T16:00:17Z

maint/add_warning: Run script to add new warning

2026-01-27T18:05:36Z

This adds the lint to all our crates.

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

Remove unnecessary `doc(cfg(...))` attributes

2025-12-05T02:40:50Z

Fixes part of #2193. (Edits from nickm: I selected the cases here that I could verify were correct from immediate context.) Edited-by: Nick Mathewson

cell: Add missing docs to internal macro

2025-12-01T10:48:14Z

Merge branch 'bug2172' into 'main'

2025-11-24T15:09:00Z

tor-llcrypto: Stop deriving Deref in CtByteArray Closes #2172 See merge request tpo/core/arti!3432

tor-llcrypto: Stop deriving Deref in CtByteArray

2025-11-24T15:08:59Z

Fix name of clippy lint to unchecked_time_subtraction (2)

2025-11-06T11:28:22Z

Run maint/add_warning