mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.4 2022-01-21T11:07:15Z 2022-01-21T11:07:15Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-01-20T18:05:10Z urn:sha1:aa4d8de16e99de41b384e77fb2fc265a4c750430 The docs even say this is about stream. As @nickm writes in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/252#note_2771289 we generally call end-to-end connections that are tunneled over Tor "Streams" to distinguish them from everything else in the Tor protocols that could possibly be called a "Connection". That seems to apply here too. 2021-12-07T15:04:41Z Neel Chauhan neel@neelc.org 2021-12-07T15:04:41Z urn:sha1:0e9c2d274ef5a1f3a21579d43ced512f17656797 2021-11-30T19:12:08Z Nick Mathewson nickm@torproject.org 2021-11-30T19:12:08Z urn:sha1:c733374693b67c4d577828af7511ededd252f0eb 2021-11-30T16:58:08Z eta tor@eta.st 2021-11-30T16:09:38Z urn:sha1:9a94f72e42ecfb7032de06784533aba6a5c8b61b 2021-11-29T14:47:09Z eta tor@eta.st 2021-11-29T14:47:09Z urn:sha1:ca42139944ca7c4e6bc9a69c1639c2e89d417419 The new CircMgr::build_circuits_preemptively function actually causes preemptive circuits to be built; it gets called from arti-client, like the other daemon tasks the CircMgr has. 2021-11-29T14:08:32Z Neel Chauhan neel@neelc.org 2021-11-29T00:30:54Z urn:sha1:2461bd86b1a04d14e4b190c2f90b8357294f65e5 2021-11-23T16:37:52Z eta tor@eta.st 2021-11-23T16:37:52Z urn:sha1:8a5a9575c6319f42f638e5bcdbc1ff2a4a186fe5 In preparation for making Arti build circuits preemptively, this commit introduces `TargetCircUsage::Preemptive`, a circuit usage that works somewhat differently from other ones: it requires at least 2 circuits to exist that can exit the port it contains in order for an existing circuit to match against it (path-spec.txt § 2.1.1); if that's not the case, that usage will require building new circuits (in order that we build enough to have 2 available). This required refactoring how circuit reuse worked; now, `CircList::find_open` uses the new `AbstractSpec::find_supported` trait method, which we customize to implement the above check in the case of `Preemptive` circuit usages. To make that work, `OpenEntry` now takes two type parameters (the spec and circuit types), instead of taking a builder type parameter and using its associated types. (We also got rid of type constraints on that struct, yay!) A WIP implementation of a preemptive circuit predictor that implements path-spec.txt § 2.1.1 is also included, but this will require additional effort to wire it up with the `CircMgr` properly. 2021-11-12T11:54:50Z Dimitris Apostolou dimitris.apostolou@icloud.com 2021-11-12T11:35:28Z urn:sha1:ad3c18a456b469d4ccacbadd806aa45d6de4b517 2021-11-02T17:30:04Z Nick Mathewson nickm@torproject.org 2021-11-02T17:30:04Z urn:sha1:ad132602aec55c894f614e0c8f69ab7927afb9ce This doesn't add much to coverage, but it's important. 2021-11-02T14:58:28Z Nick Mathewson nickm@torproject.org 2021-11-02T14:58:28Z urn:sha1:5b1b87c89650722df39d259a09b8140d92803d71