mirrors/arti.git/crates/tor-proto/src/relay/reactor, branch arti-v2.3.0 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.3.0 2026-04-23T14:45:29Z proto: Wrap PeerInfo in Arc<> 2026-04-23T14:45:29Z Gabriela Moldovan gabi@torproject.org 2026-04-23T09:32:18Z urn:sha1:0211b9058f4b1adabcc7953c6055bd40fac08664 To avoid copying the same information for every circuit, as suggested by @opara in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3906#note_3399497 proto: Avoid collecting the chan identities in RelayIdSet 2026-04-23T14:44:06Z Gabriela Moldovan gabi@torproject.org 2026-04-22T09:25:55Z urn:sha1:c25258d8a46962bd64e00abd03f3d787b2206f18 It doesn't make sense to do so, as pointed out by @opara in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3906#note_3398956 proto: Use PeerInfo in the extend handler 2026-04-23T14:43:58Z Gabriela Moldovan gabi@torproject.org 2026-04-21T10:28:13Z urn:sha1:99ae1ef7985f312730fa4cca3e476177169a4c70 Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3906#note_3397922 proto: Reject EXTEND2 targeting the previous hop in the circuit 2026-04-23T14:43:58Z Gabriela Moldovan gabi@torproject.org 2026-04-20T16:01:07Z urn:sha1:8bada0b12dfcac69956be6e1752012611c43341d The relay reactor will now reject any EXTEND2 that tries to extend the circuit to a hop that shares any identities with our previous hop. Closes #2415 proto: Give the ExtendRequestHandler a copy of the inbound peer info 2026-04-23T14:43:58Z Gabriela Moldovan gabi@torproject.org 2026-04-20T15:30:47Z urn:sha1:da241d1b3a604fc85981e9cabc29b7effd6dca9c This will soon be used for preventing the circuit from being extended to the previous hop (#2415). proto: Fix broken doc link in extend handler 2026-04-23T14:43:58Z Gabriela Moldovan gabi@torproject.org 2026-04-20T16:46:46Z urn:sha1:ce5d093b4f5c72f748067c3ce7fa6a01619d826c proto: Extract EXTEND2 handling into a new module 2026-04-23T14:43:58Z Gabriela Moldovan gabi@torproject.org 2026-04-20T15:22:12Z urn:sha1:ef8934dbc58ffc0fdcb518bb43be51e713324414 The EXTEND2 handling logic is fairly self-contained, so I'm moving it outside of the `Forward` handler. This refactoring enables us to add more context to the handler (i.e. the inbound channel identities needed for #2415) without cluttering the `Forward` implementation. I recommend reviewing this commit with `git diff --color-moved`. proto: Remove unnecessary clippy allow 2026-04-20T10:30:28Z Gabriela Moldovan gabi@torproject.org 2026-04-20T10:29:06Z urn:sha1:e84ba46b4a1628b0f539f975d1d7993f3eb103b9 I'm removing this so that we don't accidentally suppress new instances of this warning. proto: Use the inbound CircuitAccount when extending circuit (fmt) 2026-03-26T16:54:26Z Gabriela Moldovan gabi@torproject.org 2026-03-26T16:49:25Z urn:sha1:e002813eebf94372922990dcbca993d12e55a872 proto: Use the inbound CircuitAccount when extending circuit 2026-03-26T16:54:16Z Gabriela Moldovan gabi@torproject.org 2026-03-25T18:10:27Z urn:sha1:097a6ae733e3dc6a58f34877550f13457bee0c36 This was previously creating a new CircuitAccount in `new_outbound_circ()`, and then immediately dropping it.