mirrors/arti.git/crates/tor-cell/tests/testvec_chanmsg.rs, branch main

proto: Remove the AUTHORIZE as a parsable cell

2025-08-21T15:59:37Z

The AUTHORIZE cell command is simply reserved but not defined. The tor specification, at this point in time, is allowing such cell before the handshake starts but it is very unclear on what ordering is allowed nor how many can are allowed. C-tor silents drop them like VPADDING and so clearly unused. Instead of dealing with it, simply remove its support but keeping its reserved number. Signed-off-by: David Goulet

Switch Cargo.toml files to edition 2024.

2025-08-07T15:28:36Z

First, run ``` git grep -l "^edition =" | xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;' ``` Second, manually verify that all Cargo.toml files have changed, and nothing else has changed. Third, run cargo fmt again.

Add a caret_int HandshakeType for HTYPE constants

2023-10-26T15:14:40Z

Change tor_bytes::Error::BadMessage to a Cow.

2023-02-09T15:20:31Z

Actually, to avoid making a breaking change, I'm deprecating BadMessage and creating a new InvalidMessage variant that takes a Cow. This way I don't need to track every crate that re-exposes tor_bytes::Error and call this a breaking change in those. Making this change will allow tor_bytes errors to be much more helpful.

tor-cell: Rename ChanMsg and ChanCell-related types.

2023-02-07T21:03:14Z

tor-cell: Remove ChanMsg methods that are duplicated in ChanMsgClass.

2023-02-07T21:03:14Z

tor-cell: Use macro to generate ChanMsg too.

2023-02-07T21:03:14Z

Disable clippy::unlinlined-format-args

2023-01-27T13:27:47Z

This warning kind of snuck up on us! (See #748) For now, let's disable it. (I've cleaned it up in a couple of examples, since those are meant to be more idiomatic and user-facing.) Closes #748.

msg::{CreateFast/CreatedFast}: Rename accessor to (into_)body()

2022-12-19T05:00:24Z

tor-cell: Rename for_client and for_relay

2022-10-21T11:21:52Z

This commit renames the for_client and for_relay functions to from_client and from_relay respectively, in order to indicate their origin, as the term "for" is more likely to indicate a destination, which is not true in that situation.