mirrors/arti.git/crates/tor-chanmgr/src/transport, branch arti-v2.4.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.4.02026-05-27T04:05:49Ztor-chanmgr: fix `unused_imports` warning2026-05-27T04:05:49ZSteven Engleropara@torproject.org2026-05-26T19:35:49Zurn:sha1:c68513ad796f06937ce924f49587e822b088ea35Merge branch 'socket-buf-size' into 'main'2026-05-21T18:29:42Zoparaopara@torproject.org2026-05-21T18:29:42Zurn:sha1:7f27830adb14823cb1d27a5d55265e69eb2cc313
Set socket buffer sizes (`SO_SNDBUF` and `SO_RCVBUF`) for proxy sockets
Closes #2500
See merge request tpo/core/arti!3957tor-rtcompat+misc: add `NetStreamProvider::ListenOptions`2026-05-07T15:05:57ZSteven Engleropara@torproject.org2026-05-06T23:05:12Zurn:sha1:89790050b66f4eed80b9215b18c893ab7adba298
This adds the trait type `ListenOptions` to `NetStreamProvider` and adds
this `ListenOptions` as an argument to `NetStreamProvider::listen()`.
You probably want to look at the changes in tor-rtcompat first, then the
rest of this commit is updating the various places we use
`NetStreamProvider`.
chanmgr: report target address, not proxy address, in error2026-05-07T12:22:31ZNick Mathewsonnickm@torproject.org2026-05-07T12:22:31Zurn:sha1:fdd0c264bd9523bf36eb34da398d8862f52aa4bd
Also, change the address type in the error to String for now.
In reality we need a better representation of this error,
but that shouldn't block this.
chanmgr: refactor error types2026-05-07T12:15:06ZNick Mathewsonnickm@torproject.org2026-04-28T17:48:35Zurn:sha1:4c0f60c68fbc4c1e480d144ab81d5c972315e4eb
Proxy belonged as a subcase of ChannelBuild. And ChannelBuild
was only about making an initial connection.
chanmgr: Do not turn connect errors into proxy errors.2026-05-07T12:15:06ZNick Mathewsonnickm@torproject.org2026-04-28T16:17:20Zurn:sha1:59b8b12e46b5a42883d3e74db03661b9ff4d3ddc
This fixes the problem where we'd report all connect failures as
proxy failures.
Closes #2459.
tor-chanmgr: don't `warn_report!` for failed connections2026-03-24T22:51:19ZSteven Engleropara@torproject.org2026-03-24T22:51:14Zurn:sha1:c7c376c60d77edd4d2324dc9f7e4a23620203f42
`warn_report!` is useful when there's an error that we need to ignore
and can't propagate up the call stack. But here we're using
`warn_report!` while also returning the error in a
`Error::ChannelBuild`.
This is not great because:
1. The caller should warn if it wants to, since it will have the error
message and the proper context.
2. This code is doing something like happy eyeballs, which means we only
care that one connection succeeds, not if any fail.
One instance where this is problematic is when running Arti on a machine
without IPv6 support. If connecting to a relay with both an IPv4 and
IPv6 address, the IPv6 attempt will always fail. We don't want to warn
about every outgoing IPv6 connection failure when the IPv4 connection
succeeds.
tor-chanmgr: add loopback validation, startup warning and httparse2026-03-18T15:03:45ZNihal4218-nihalxkumar@gitlab.torproject.org2026-03-10T15:51:47Zurn:sha1:0149e5b710f15a66648d2c0a31e2eb90fadb49e7tor-chanmgr: split handshake into helper functions2026-03-18T15:00:46ZNihalnihalxkumar@protonmail.com2026-02-17T13:37:00Zurn:sha1:5f5d106a30f3ce4f0caeb08ad13c7e67560b7afctor-chanmgr: fix type inference in handshake2026-03-18T15:00:46ZNihalnihalxkumar@protonmail.com2026-02-17T13:13:09Zurn:sha1:e8e6195ed94acb18a67e48712c873d64a18092d9