mirrors/arti.git/crates/tor-proto/Cargo.toml, branch arti-v1.4.3mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.32025-05-01T16:22:28Zrelease: 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
```
chore: Run fixup-features.2025-04-30T15:49:52ZWesley Aptekar-Casselsme@wesleyac.com2025-04-30T14:26:40Zurn:sha1:da4308744bf59b50dfcc28a438fda047a115812d
cargo run -p fixup-features -- --exclude examples/ --exclude maint/ Cargo.toml
The following features in arti-ureq were manually added to full or
marked non-additive:
* rustls
* native-tls
* tokio
* async-std
Update rand requirement to 0.9.12025-04-29T22:52:26ZNick Mathewsonnickm@torproject.org2025-04-29T19:04:27Zurn:sha1:fc0810c1091b2ec606111ae94e726cf5f7b10b38
(This is going to be a _requirement_,
since rand 0.9.1 has a behavioral change from 0.9.0)
Run cargo update.2025-04-29T21:35:34ZWesley Aptekar-Casselsme@wesleyac.com2025-04-29T17:30:17Zurn:sha1:54e3933f577548f10e01ae9e979ffb110481f9b4
I updated everything except rand, because the new version of rand
interacts with #1903, thus requiring more care.
Rename feature cgo => counter-galois-onion.2025-04-29T16:35:19ZNick Mathewsonnickm@torproject.org2025-04-24T13:49:40Zurn:sha1:65974c8ab586c6d3b92374071ab0c1e4950c3c99proto: Implement CGO functions ET and PRF2025-04-29T16:34:57ZNick Mathewsonnickm@torproject.org2025-04-14T20:44:30Zurn:sha1:bc04d424c95174e8fb1b849a970a37d8445e8664
These are a tweakable block cipher, and a pseudorandom byte stream.
This commit includes test vectors, which were generated from the
Python reference implementation and confirmed with a less optimized
Rust implementation.
New empty CGO module.2025-04-29T16:34:56ZNick Mathewsonnickm@torproject.org2025-04-14T16:35:15Zurn:sha1:dfa6e308275795c106ee38b2d5cac45ecd40f6eator-proto: only use congestion control if "flowctl-cc" feature is enabled2025-04-23T18:39:16ZSteven Engleropara@torproject.org2025-04-17T03:39:44Zurn:sha1:ccb65961cc5a25c304b240a8cfa40d08c4569713
Congestion control is not completely working correctly, and is not fully
implemented (XON/XOFF). This commit adds a new experimental "flowctl-cc"
feature to enable the congestion control extension during the ntor-v3
handshake.
New functions to report supported subprotocols2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-02T18:00:00Zurn:sha1:efe36d15de88ec5b7f39db99f9d2a58e4e5db7ac
Part of #1849.
Note that these functions are distributed across crates,
so that if (in the future) we stop doing API breaks
with every release, we will get the right outputs.
Note also that these functions build the list of protocols
out of specific symbolic features, rather than numbers:
this makes it easier to avoid errors about "which feature was
Relay=4 again", and easier to avoid accidentally referring to a
protocol that doesn't exist, like "Consensus" (should be "Cons")
or "HsDir" (case is wrong).
tor-proto: removed "ntor_v3" feature flag2025-04-01T14:16:33ZSteven Engleropara@torproject.org2025-04-01T00:54:57Zurn:sha1:a4c610b60d6bb0e269435f4f0995e20d8f2f70e4
ntor v3 is now always enabled.