mirrors/arti.git/crates/tor-proto/src/crypto/cell, 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:35:04ZCGO: Fix authenticated-sendme tag handling.2025-04-29T16:35:04ZNick Mathewsonnickm@torproject.org2025-04-23T16:20:03Zurn:sha1:5d5599392d514517b3d5fc387694c73388e474dc
See discussion at torspec#328: it's important that our
SENDME authentication tag always be taken based on the
_encrypted_ cell.
CGO: Note another possible performance improvement.2025-04-29T16:35:04ZNick Mathewsonnickm@torproject.org2025-04-23T14:05:12Zurn:sha1:ecd0702a2e662dbd45272ca1424be206db0316aaproto: Implement and test CGO cryptography.2025-04-29T16:35:04ZNick Mathewsonnickm@torproject.org2025-04-15T00:57:32Zurn:sha1:37aba22d180e5817bcb3302e8fb4e55494a382fc
This provides all the operations from proposal 359,
along with the necessary integration and unit tests to make sure
that they are behaving properly.
Closes #1943
proto: Implement UIV+, the wide-block RPRP used for CGO.2025-04-29T16:35:04ZNick Mathewsonnickm@torproject.org2025-04-14T21:39:39Zurn:sha1:f60463a91d404fc12e0929707f1a626d6d2cefbbproto: 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:dfa6e308275795c106ee38b2d5cac45ecd40f6eaproto: Make relay-side cell crypto traits return tags.2025-04-29T16:31:09ZNick Mathewsonnickm@torproject.org2025-04-15T14:41:13Zurn:sha1:8f6d6201c2b61a9a2d40527b3a77143d7b49be5c
(We'll need these tags both to implement authenticated SENDMES
at the relay side, and also to make sure that cgo is generating them
correctly.)
proto: 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.)