mirrors/arti.git/crates/tor-proto/src/circuit.rs, branch arti-v1.2.7 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.7 2024-08-28T14:27:46Z extract tor_async_utils::oneshot into ::oneshot-fused-workaround 2024-08-28T14:27:46Z Jim Newsome jnewsome@torproject.org 2024-08-22T19:20:36Z urn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1 Having this in the `tor-async-utils` crate prevents us from doing both of the following without introducing a circular dependency: * using it in `tor-rtmock` (which we currently do, particularly in tests). * using `tor-rtmock` to test things in `tor-async-utils`. We don't do this yet, but it is generally sensible to do so. In particular we want to move the `stream_peak` module there, which is currently tested with `tor-rtmock`. Moving this into its own crate avoids this circular dependency. `circuit` docs: delete comment about no flow-control etc 2024-08-26T19:53:11Z Jim Newsome jnewsome@torproject.org 2024-08-26T19:44:43Z urn:sha1:508d67054c282e9aedda4e5d1e700b8b9e5f3da1 There is now (sendme-style) flow control, and some fairness (via round robin scheduling of streams). `circuit` docs: delete "one big mutex" limitation 2024-08-26T19:36:01Z Jim Newsome jnewsome@torproject.org 2024-08-26T19:36:01Z urn:sha1:e5918dfdc4f155ab0c973860a9522faa41f2137a There is a mutex for some of the "mutable state", but the reactor only needs to lock it when adding a hop. It's not needed "to process a cell" or when streams send. Probably not worth calling out here. tor-proto circuit: add unit test for fairness 2024-08-22T18:51:03Z Jim Newsome jnewsome@torproject.org 2024-07-31T20:26:05Z urn:sha1:9866eb8f31660052a145d9a52af50434ab1a5ab8 tor-proto::circuit: Move test-only methods into test module 2024-07-29T16:15:06Z Jim Newsome jnewsome@torproject.org 2024-07-29T15:53:58Z urn:sha1:c24866a2eb35447f0eb7da212960bb1dc6cc261d tor-proto circuit tests: dedupe circid magic number 2024-07-29T16:15:06Z Jim Newsome jnewsome@torproject.org 2024-07-25T21:38:26Z urn:sha1:a8245f5ae89eb7429db8e7d23bc0bddc15e9a6ec tor-proto circuit test: Move to tighter scope and shadow outer def 2024-07-29T16:15:06Z Jim Newsome jnewsome@torproject.org 2024-07-25T21:10:16Z urn:sha1:d3be01bb4d6d3d035cd94bece2937687ea0beebe tor-proto circuit tests: delete stale commented-out test 2024-07-29T16:15:06Z Jim Newsome jnewsome@torproject.org 2024-07-25T19:51:37Z urn:sha1:f9a21aca66ea000d1de140ae3713cce2718700c5 tor-proto circuit tests: fix some comment copy-pasta 2024-07-29T16:15:06Z Jim Newsome jnewsome@torproject.org 2024-07-25T19:50:38Z urn:sha1:a5fe81ce174781e2238d5b35c0a306f9e526b3fd tor-proto: Return proper `Error::MissingId` 2024-07-12T11:49:05Z Clara Engler cve@cve.cx 2024-07-12T11:49:05Z urn:sha1:a36d157be23f3498dd351efdadffa8ddfe6dbfad This commit fixes a bug in the `ClientCirc::extend_ntor` function, which currently returns a `Error::MissingId(Ed25519)` in the case that no RSA identity has been found in the accompanying channel target. This behavior is obviously wrong, because a missing RSA identity should yield a `Error::MissingId(Rsa)`.