mirrors/arti.git/crates/tor-cell/semver.md, branch arti-v1.4.6mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.62025-07-15T06:04:44Ztor-cell: change `UnparsedRelayMsg::data_len`2025-07-15T06:04:44ZSteven Engleropara@torproject.org2025-07-15T03:50:51Zurn:sha1:d499af464198520e0b4115d624b1cf53929d0024
It now performs some validation and can return a `Result`.
We perform validation here since different cell formats may have
different maximum data lengths in the future, and `UnparsedRelayMsg`
doesn't expose the cell format so it's difficult to perform this
validation at a higher layer.
tor-cell: remove `flowctl-cc` feature and make XON/XOFF cells stable2025-07-15T05:33:18ZSteven Engleropara@torproject.org2025-07-15T05:27:21Zurn:sha1:676dbdb43f2a930b7dc89d2a6275338064fd37bf
I don't see any further changes being needed for these types, and it
simplifies a lot of future code in tor-proto that uses these types.
release: Delete semver.md files after release.2025-06-05T13:45:22ZAlexander Hansen Færøyahf@torproject.org2025-06-05T13:45:22Zurn:sha1:a59953da8d68cbf8ffdc8711e3fc5ec3bba77ae4cell,proto: Split request/response extensions into seprate types2025-05-07T12:44:59ZNick Mathewsonnickm@torproject.org2025-04-30T17:27:58Zurn:sha1:ff9c3478d2aac678e4ad27712fd65b1ce296d423
Implements part of proposal 358.
Rename NtorV3Extension to CircRequestExt2025-05-07T12:41:39ZNick Mathewsonnickm@torproject.org2025-04-30T16:05:45Zurn:sha1:70aab0213f42b14ff8dfa02c22a2cf615709ed9c
This type will, because of prop358, be shared by ntorv3,
hs-ntor, and probably other future handshakes.
There will also be a CircResponseExt type.
proto, cell: Remove RelayCellFormatTrait.2025-05-06T22:34:17ZNick Mathewsonnickm@torproject.org2025-04-30T00:59:07Zurn:sha1:297aa8027f7528605fe5bf2097f3474d9ba3eef9
The purpose of the trait was to parameterize the tor1 cell crypto
on the different possible relay cell layouts.
It made sense to have this trait when we thought we would implement
the new cell layout for prop340 (packed-and-fragmented) well before
we implemented CGO.
But it now appears all but certain that CGO will land long before
we make any more headway on prop340. Therefore,
it doesn't make sense to carry the ability to customize `tor1`
for other relay cell layouts.
Removing this trait saves a fair bit of complexity.
proto: Use SendmeTag in place of CircTag2025-05-06T22:34:17ZNick Mathewsonnickm@torproject.org2025-04-29T23:20:06Zurn:sha1:44f4290934140cd8afdc09e03aeeadd88264b23b
This doesn't make much change yet, but does save us an allocation
when handling SENDMEs.
release: Bump all unstable tor/arti crates to 0.30.02025-05-01T16:22:28ZWesley Aptekar-Casselsme@wesleyac.com2025-05-01T15:55:57Zurn:sha1:770aaa9648d42835b2c6b3b29f4051d287ddba88
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.30.0
done
```
cell, proto: Use correct Data sizes for v1 relay cells2025-04-16T14:58:49ZNick Mathewsonnickm@torproject.org2025-04-11T01:57:10Zurn:sha1:497e5f1acd27c2c316c3f5bbf7158c9516fef159
Since v1 cells have a longer tag, they can fit less data into a
single cell. Ah well, that's the cost of improved security.
The code in data.rs is a little wonky, in that it currently requires
its buffer to be exactly the maximum size for a data cell. We have
a TODO about fixing that in the future, but for now I've moved it to
use a boxed slice rather than a boxed array.
Part of #1944.
cell: Remove the deprecated Data::split_from().2025-04-16T14:58:49ZNick Mathewsonnickm@torproject.org2025-04-11T01:53:32Zurn:sha1:01b7c735761d878e68912355d1a16fe50d24e5b3