mirrors/arti.git/crates/tor-proto/src/crypto/bench_utils.rs, 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-04-29T16:31:09Zproto: Make crypt layers take a ChanCmd argument2025-04-29T16:31:09ZNick Mathewsonnickm@torproject.org2025-04-15T01:14:25Zurn:sha1:1998aa7b6a837bc33d372de22566447f477bf01f
CGO will need this argument so that it can authenticate
the command as part of its crypto operations.
(Trying to meddle with RELAY vs RELAY_EARLY will no longer work!)
proto: refactor RelayCrypt trait into separate traits2025-04-29T16:31:09ZNick Mathewsonnickm@torproject.org2025-04-15T00:01:22Zurn:sha1:3bd64c9308a7f3c7772acc2a42f5349ad0534e17
It seems very likely that, as with client crypto,
we'll want relay crypto to separable into "forward" and "reverse"
objects, so that the two can be used more or less independently.
proto: Tweak semantics of RelayCrypt::originate.2025-04-29T16:31:09ZNick Mathewsonnickm@torproject.org2025-04-14T22:54:28Zurn:sha1:955440b3c54621233fae23e7a3ddfa1e21d130df
This makes the behavior of "originate" match the behavior of
OutboundClientLayer::originate_for, which creates the message
_and_ encrypts it. This will be necessary for CGO, where
"originate" and "encrypt" are not easily separated operations.
(Nothing uses this trait yet, since relay circuits aren't yet a thing,
so it's a good time to get it right.)
tor-proto: put every bench_utils mod behind the bench feature2024-11-06T18:36:19ZLionel Goffauxlionel.goffaux@unamur.be2024-11-06T18:36:19Zurn:sha1:375f63cd7aff14cc288141a749ee8b4342d45ba3tor-proto: remove inlines attributes2024-11-06T12:03:05ZLionel Goffauxlionel.goffaux@unamur.be2024-11-06T12:03:05Zurn:sha1:8e7239d65a3da8b78e4497825d1f116195ba79c9tor-proto: Add benchmarks for cell encryption and decryption2024-11-04T12:05:10ZLionel Goffauxlionel.goffaux@unamur.be2024-11-04T12:05:10Zurn:sha1:10607de5023ce98c82237186654b0f87e9466931