mirrors/arti.git/crates/tor-proto/src/client/circuit/padding, branch mainmirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=main2026-07-01T18:15:46ZUpgrade to itertools 0.15.02026-07-01T18:15:46ZNick Mathewsonnickm@torproject.org2026-07-01T13:56:10Zurn:sha1:6094d35e1a770aa6c1417697336d7d454991ac9e
Additionally, fix itertools usage in maybenot_padding.rs
The definition of `Position` changed in 0.15.0.
Upgrade rand crates to 0.10.2026-05-12T20:55:43ZWesley Aptekar-Casselsme@wesleyac.com2026-05-07T20:06:21Zurn:sha1:a18167928901d8c88cd1cdd87346de8ad1ee42a2
When the circ-padding feature is enabled, we use maybenot, which does
not yet support rand 0.10. In the meantime, enabling this feature pulls
in rand 0.9. This is not ideal, but should be okay as a temporary
situation.
This also replaces the use of ReseedingRng (which was removed in 0.10)
with the reseeding_rng crate. This is somewhat less performant, but it
should be okay.
proto: Take current time as an argument when constructing padder.2026-03-31T19:49:57ZNick Mathewsonnickm@torproject.org2026-03-31T19:49:57Zurn:sha1:e58b7f9890144b6cf0d149cd04a9ec143052e501
Previously we'd get the time by calling Instant::now, but that would
lead to a mismatch with the runtime if we were mocking.
Part of #2428.
tor-proto: Port to web-time-compat2026-03-26T19:20:16ZNick Mathewsonnickm@torproject.org2026-03-26T14:33:04Zurn:sha1:11f365738ade6ba75eedee83d7d19f8877da7d65proto; Factor HOPS constant out of maybenot_padding2026-01-29T16:33:21ZGabriela Moldovangabi@torproject.org2026-01-14T11:40:35Zurn:sha1:0189413e0581ea7c852c87663fe4a24511e3158b
I am about to use this in other places too.
proto: Implement channel padding with maybenot padders.2025-10-02T16:04:40ZNick Mathewsonnickm@torproject.org2025-10-02T14:09:15Zurn:sha1:9a6d37141a09bc24581d0a872ef53f141595a042
With this commit we now actually generate padding when we're told to.
proto: Trigger maybenot events for channel-level padding.2025-10-02T16:04:40ZNick Mathewsonnickm@torproject.org2025-10-01T15:43:34Zurn:sha1:ebf9e3e09217b19f9c1b6217874d4ca4e1525f7fproto: Use a VecDeque for padding events; avoid reversing.2025-09-17T15:11:59ZNick Mathewsonnickm@torproject.org2025-09-17T15:11:59Zurn:sha1:a22a1234f3955238f1472933da201bebcd16aefcproto: Rename PaddingEventVec => PaddingEventQueue2025-09-17T15:09:06ZNick Mathewsonnickm@torproject.org2025-09-17T15:09:06Zurn:sha1:c41e0611676e42a091e210c8b2900716f05d4459proto: Fix a pair of padding setup TODOs.2025-09-17T15:08:12ZNick Mathewsonnickm@torproject.org2025-09-17T15:00:03Zurn:sha1:31d7c35bf8e943c328bfce368af1ea0bb6b0d525
When we install a new padder, we should check whether we have become
unblocked, and we should wake up the PaddingEventStream in case
the new padder has something to say.
This has required us to move a couple of fields around, but not in a
very complicated way.