mirrors/arti.git/crates/tor-proto/src/circuit/msghandler.rs, branch ios-sqlite-hacks mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=ios-sqlite-hacks 2023-08-04T12:08:31Z tor-proto: Add ClientCirc::start_conversation(). 2023-08-04T12:08:31Z Gabriela Moldovan gabi@torproject.org 2023-07-31T18:53:30Z urn:sha1:ed5a051ebe94a8cf4e5e9f33c000a9bd2fddfd8f This will enable hidden services to send `RENDEZVOUS1` messages to the `N`th hop of the circuit rather than the `N + 1`th virtual one (which can only used after the client and service have completed the introduction handshake). This also deprecates `start_conversation_last_hop`. Closes #959 tor-proto: run rustfmt 2023-06-30T17:43:20Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-06-30T17:34:04Z urn:sha1:27ad9ca249858e8e6e896da7f91106ae44a56ce4 tor-proto conversation API: Provide ConversationInHandler 2023-06-30T17:43:20Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-06-30T16:44:15Z urn:sha1:226bca984b6a65466da1b4517cc2a16fa762d591 tor-proto circuit: Plumb async Context through 2023-06-30T17:28:41Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-06-30T14:46:10Z urn:sha1:800f390a9d514b5270a2038bc87f30c222fb813d handle_msg is going to want this in a moment. tor-proto conversation API: Soften a warning 2023-06-30T17:28:41Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-06-30T17:11:57Z urn:sha1:c599258b85423873613a432dbf8c30aa53709c97 If the circuit is just being used by us (which is likely, if we're using this API) then the only reactor we're blocking is our own. tor-proto conversation API: Rename to start_conversation_last_hop 2023-06-30T17:02:56Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-06-30T16:51:02Z urn:sha1:2882e3a93e22a4acdfb93da8a2ca1e62a50141b2 Was send_control_message. proto: Convert MsgHandler API to expect a message, not a cell. 2023-06-12T18:55:26Z Nick Mathewson nickm@torproject.org 2023-06-12T18:55:26Z urn:sha1:beecf3c92c95fd1e0fdddfcc32703abd4cdeadfc Closes #887. tor-circmgr: send_control_message: Fix reference to circuit 2023-06-05T12:50:51Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-06-05T12:50:51Z urn:sha1:9b366972824465a0631bcf572ae9cc3f87ee4fbe tor-circmgr: send_control_message: Clarify some corner cases 2023-06-05T12:19:58Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-06-05T11:28:32Z urn:sha1:a9ff778ba5ec536240a237ee1bceae0213c18327 Also, no longer talk about handlers being "installed". That's not something that's exposed by this API. And, say that `send_control_message` can be called again only after *`send_control_message`* returns, not when `handle_msg` has returned `UinstallHandler`. IMO this makes more sense. Explain that we can't maintain a continuous watch while holding a conversation with the peer. (This is surely an API bug.) 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.)