mirrors/arti.git/crates/tor-cell/src, branch arti-1.2.1mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-1.2.12024-03-20T14:10:32ZAdd and use RelayCellFormatTrait2024-03-20T14:10:32ZJim Newsomejnewsome@torproject.org2024-03-19T00:30:12Zurn:sha1:8a91f277bbb9faa263a33d6b270f652a0da98068
This lets us paramaterize types and functions by a particular relay cell
format. We use this e.g. to statically parameterize the cell crypto
functions, thereby removing some run-time branching in the hot path.
RelayCellBody: generalize over RelayCellFormat2024-03-20T14:07:53ZJim Newsomejnewsome@torproject.org2024-03-14T16:52:13Zurn:sha1:86f38c6d785b0adebcc81878719411b6d4648877
Different formats will use different ranges for the `recognized` and
`digest` fields.
Run maint/add_warning.2024-03-13T16:30:53ZNick Mathewsonnickm@torproject.org2024-03-13T16:30:53Zurn:sha1:c0c9bd15d42897825dd0ab3d3b8dd1c17bd6320cRemove RelayMsgOuter::decode_from_reader2024-03-12T15:58:12ZJim Newsomejnewsome@torproject.org2024-03-11T20:33:14Zurn:sha1:92f12efe7e76a227bcb363c41d792ed5b8a71e4a
The semantics of such a function that supports both the legacy V0 format
and the V1 packing and fragmentation format are a bit tricky. Since it's
not used outside of its module, we can simply remove it.
relay-cell: Update relay cell decoding API for prop3402024-03-12T15:58:12ZJim Newsomejnewsome@torproject.org2024-03-05T20:58:01Zurn:sha1:2d427eb93d699e779c608f71a243d581b1027a73
Prop 340:
https://spec.torproject.org/proposals/340-packed-and-fragmented.html
This updates the decoding API to support multiple versions of the relay
cell encoding, including the new encoding proposed in prop340 that
supports relay message packing and fragmentation.
This commit doesn't actually add support for that new encoding yet.
Rename UnparsedRelayCell -> UnparsedRelayMsg2024-03-12T15:58:12ZJim Newsomejnewsome@torproject.org2024-03-04T17:17:41Zurn:sha1:190d1cba722c1ebe840eca2b06d82a89678847dc
For consistency with the terminology proposed in
https://gitlab.torproject.org/tpo/core/torspec/-/issues/253
Fix typos in doc comments2024-03-06T19:52:42ZTobias Stoeckmanntobias@stoeckmann.org2024-03-06T19:05:17Zurn:sha1:18db641cca83fa707b3a97fa2975f99063f08875deny clippy::unchecked_duration_subtraction2024-02-29T17:16:49Ztrinity-1686atrinity@deuxfleurs.fr2024-02-29T17:06:46Zurn:sha1:ac5b36027ca825d27ef466501c660ce498fd9e3ctor-cell: impl Eq, PartialEq, Hash for est_intro::DosParams2024-02-21T13:46:14ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-21T13:41:54Zurn:sha1:3eada5293f138bc2b53483528918aa815bd65e2a
We only need Eq and PartialEq but given those we should have Hash too.
(We're going to want to be able to compare parameters for equality.)
tor_cell: never construct empty DATA messages.2024-02-13T14:37:11ZNick Mathewsonnickm@torproject.org2024-02-13T14:37:11Zurn:sha1:b5c70dad02124549a13e25f62c8073fef4a063fe
We never actually constructed these before, but now we enforce it at
the API level.
Part of #1269.