mirrors/arti.git/crates/tor-proto/src/circuit, branch arti-v1.1.5 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.5 2023-05-23T14:59:37Z proto: Make PathEntry::Virtual feature-conditional. 2023-05-23T14:59:37Z Nick Mathewson nickm@torproject.org 2023-05-23T14:59:37Z urn:sha1:03c81ae5aa5dea6012a79365427d27721114c9e5 This fixes a warning when building tor-proto without the `rpc-common` feature. Merge branch 'virtual_hop' into 'main' 2023-05-18T17:14:01Z Nick Mathewson nickm@torproject.org 2023-05-18T17:14:01Z urn:sha1:f333c9029a7d89529ef9dd14c1a5f0506ad4f848 tor-proto: Add support for extending circuits through virtual hops. Closes #726 See merge request tpo/core/arti!1191 proto: Allow circuit Paths to represent virtual hops. 2023-05-18T16:40:02Z Nick Mathewson nickm@torproject.org 2023-05-18T13:58:27Z urn:sha1:3b7a20ef4cd8eb2752f36dfcbd3e6ef8f65c78e4 Sadly, this adds a few more `TODO HS` entries, but I think we can clean them up later after a bit of discussion. proto: Implement Circuit::extend_virtual. 2023-05-18T16:40:02Z Nick Mathewson nickm@torproject.org 2023-05-18T13:47:22Z urn:sha1:663f25d44c19ecfc1e24a5ae71debbf53f5bbb1d There are a few new TODO hs comments, though, and an XXXX I'll need to fix up in the next commit. Implements #726. tor-proto: Code to construct crypto layers for virtual hops. 2023-05-18T16:40:02Z Nick Mathewson nickm@torproject.org 2023-05-17T21:04:46Z urn:sha1:b9a848a7acb1761a19764f4058f3924f55d04a90 This is fairly straightforward, thanks to our existing design work on this code. tor-guardmgr, tor-proto: minor logging tweaks 2023-05-18T15:04:11Z eta tor@eta.st 2023-05-18T13:55:50Z urn:sha1:4665835ee8879bf4d11ccf56420b899909cf32ff - We make the tor-guardmgr "We have found that {} is usable" line include the word "guard", otherwise it doesn't appear very useful to a user in safe logging mode, since the guard gets replaced with [scrubbed]. - The "Actually got an end cell..." message is downgraded to DEBUG. Change CircTarget::linkspecs() to return an encoded list. 2023-05-10T16:30:32Z Nick Mathewson nickm@torproject.org 2023-05-10T16:25:57Z urn:sha1:7ce808b75bb500f27ce7837d4f76cbf7fc1ee705 If we didn't do this, we would need to transfrom `EncodedLinkSpec`s into a `LinkSpec::Unrecognized`, which is not semantically right. What's more, every user of this API wants to consume encoded link specifiers, so encoding them early saves a little effort. tor-proto: Feature-conditionalise some enum variants 2023-03-23T11:50:18Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-22T12:11:59Z urn:sha1:b8345353474094bd8c6f4dd3f442e867ad0fc537 This avoids some dead code warnings when building without send-control-msg. tor-proto: Split off send-control-msg feature 2023-03-23T11:50:18Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-22T12:06:59Z urn:sha1:93809cc5941e7ddaa5ac3f5691a986033a4a9244 tor-proto: Say "control message" a little more consistently 2023-03-08T19:21:33Z Nick Mathewson nickm@torproject.org 2023-03-08T15:26:14Z urn:sha1:c1b45e1be45774e50beac8cfa52e78f9d7ba7ae7 (I found "user request" in one place, and fixed that. I am not currently going to try to unify "control message" and "meta message" since both terms are misleading and we already have TODOs to try to merge them into a third better term.)