mirrors/arti.git/crates/tor-proto/src/circuit.rs, branch arti-v1.1.12mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.122023-12-14T16:56:58ZRename {Any}RelayCell to {Any}RelayMsgOuter2023-12-14T16:56:58ZNick Mathewsonnickm@torproject.org2023-12-14T16:43:44Zurn:sha1:8c0b166de3057e0ddb0d7771e50ad5a366bdd7c8
This commit is pure renaming, done automatically with rust-analyzer.
Comment fixes and other cleanups will be in the subsequent commits.
We're doing this renaming because we need a name for
the combination of a `RelayMsg` and an `Option<StreamId>`
that we use when we have a `RelayMsg`
we intend to route to a given stream or circuit internally.
Previously we called this a `RelayCell`,
but that name was already somewhat inaccurate,
and will become _very_ inaccurate with the arrival of prop340,
which breaksthe 1:1 relationship between relay cells
and relay messages.
(If we didn't do this renaming now, we'd soon be making
the relationship between `UnparsedRelayCell`and `RelayCell`
many-to-many, which would be ridiculous and confusing.)
The `RelayMsgOuter` name is a placeholder:
We expect that we'll want to rename this type,
and may also want to rename `RelayMsg`,
and unify our vocabulary in other areas too.
But such a renaming will have to wait
for a larger discussion affecting the specifications,
so that we can use the same vocabulary everywhere.
Test extend_ntor_v32023-11-27T16:48:04ZJim Newsomejnewsome@torproject.org2023-11-15T21:13:59Zurn:sha1:9f9dc604153322637301a1df988cccb740c79f44Parameterize circuit-extension test by handshake type2023-11-27T16:48:04ZJim Newsomejnewsome@torproject.org2023-11-02T15:27:31Zurn:sha1:678619384ade5c1c1904469bbe012eea0ab7ba79Add `ClientCirc::extend_ntor_v3`2023-11-27T16:48:04ZJim Newsomejnewsome@torproject.org2023-11-15T21:12:41Zurn:sha1:6149409574b57e919d9fc76cf0c0aa9a33d447acCircuit reactor: test ntor-v3 "create"2023-11-27T16:48:04ZJim Newsomejnewsome@torproject.org2023-10-30T22:49:50Zurn:sha1:e24f20e2c6c427c91b4220dd79d3ee67f152f6ecAdd PendingClientCirc::create_firsthop_ntor_v32023-11-27T16:48:04ZJim Newsomejnewsome@torproject.org2023-10-30T22:14:54Zurn:sha1:00094c759a06bbf7cc7243339cf6b7b70c4ad867Merge remote-tracking branch 'public/hs_begin'2023-11-16T15:46:49ZNick Mathewsonnickm@torproject.org2023-11-16T15:46:49Zurn:sha1:e54893693021ab443fcf462365d3ba8e9b8644c6Send less information in onion service BEGIN messages2023-11-15T18:21:11ZNick Mathewsonnickm@torproject.org2023-11-15T18:19:47Zurn:sha1:23492cc2423f2ab0611a390cfa2ad49a3bd81d6d
While looking for differences, we found that C tor always
omits the flags and the hostname from a BEGIN message sent on an
onion service circuit. In torspec!179, we specified that behavior.
This patch brings arti into conformance.
Closes #1077.
tor-proto: make ClientHandShake and ServerHandshake generic over aux data2023-11-15T14:56:34ZJim Newsomejnewsome@torproject.org2023-11-02T20:37:48Zurn:sha1:f25d9335ed68b3562593e8167c15682ff1f4c2a4ServerHandshake: extend to support ntorv3 extensions2023-11-15T14:56:34ZJim Newsomejnewsome@torproject.org2023-11-01T00:43:13Zurn:sha1:73d3615e39fc59dee51ebdd94cca221d7a0e655c