<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-chanmgr/src/transport, branch arti-v2.5.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-06-09T15:36:01Z</updated>
<entry>
<title>maint: Run maint/add_warning to deny string slices</title>
<updated>2026-06-09T15:36:01Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-06-09T15:36:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9f5752a77fb57052c06ead0eeae606831f1e8e97'/>
<id>urn:sha1:9f5752a77fb57052c06ead0eeae606831f1e8e97</id>
<content type='text'>
This commit executes maint/add_warning with the just added change to
deny string slices except in tests.

I recommend auditing this by checking out the previous commit followed
by running the script yourself and then verifying that the diff is
identical to this commit.

This commit makes cargo clippy fail.  We will add exceptions in the next
commit.
</content>
</entry>
<entry>
<title>tor-rtcompat+misc: add `NetStreamProvider::ConnectOptions`</title>
<updated>2026-06-08T16:55:27Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2026-05-26T20:57:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=926c7a5449e29e2d652431a2406e7acae59bed50'/>
<id>urn:sha1:926c7a5449e29e2d652431a2406e7acae59bed50</id>
<content type='text'>
This adds the trait type `ConnectOptions` to `NetStreamProvider` and adds
this `ConnectOptions` as an argument to `NetStreamProvider::connect()`.

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`.
</content>
</entry>
<entry>
<title>tor-chanmgr: fix `unused_imports` warning</title>
<updated>2026-05-27T04:05:49Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2026-05-26T19:35:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c68513ad796f06937ce924f49587e822b088ea35'/>
<id>urn:sha1:c68513ad796f06937ce924f49587e822b088ea35</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'socket-buf-size' into 'main'</title>
<updated>2026-05-21T18:29:42Z</updated>
<author>
<name>opara</name>
<email>opara@torproject.org</email>
</author>
<published>2026-05-21T18:29:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7f27830adb14823cb1d27a5d55265e69eb2cc313'/>
<id>urn:sha1:7f27830adb14823cb1d27a5d55265e69eb2cc313</id>
<content type='text'>
Set socket buffer sizes (`SO_SNDBUF` and `SO_RCVBUF`) for proxy sockets

Closes #2500

See merge request tpo/core/arti!3957</content>
</entry>
<entry>
<title>tor-rtcompat+misc: add `NetStreamProvider::ListenOptions`</title>
<updated>2026-05-07T15:05:57Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2026-05-06T23:05:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=89790050b66f4eed80b9215b18c893ab7adba298'/>
<id>urn:sha1:89790050b66f4eed80b9215b18c893ab7adba298</id>
<content type='text'>
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`.
</content>
</entry>
<entry>
<title>chanmgr: report target address, not proxy address, in error</title>
<updated>2026-05-07T12:22:31Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-05-07T12:22:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fdd0c264bd9523bf36eb34da398d8862f52aa4bd'/>
<id>urn:sha1:fdd0c264bd9523bf36eb34da398d8862f52aa4bd</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>chanmgr: refactor error types</title>
<updated>2026-05-07T12:15:06Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-04-28T17:48:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4c0f60c68fbc4c1e480d144ab81d5c972315e4eb'/>
<id>urn:sha1:4c0f60c68fbc4c1e480d144ab81d5c972315e4eb</id>
<content type='text'>
Proxy belonged as a subcase of ChannelBuild.  And ChannelBuild
was only about making an initial connection.
</content>
</entry>
<entry>
<title>chanmgr: Do not turn connect errors into proxy errors.</title>
<updated>2026-05-07T12:15:06Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-04-28T16:17:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=59b8b12e46b5a42883d3e74db03661b9ff4d3ddc'/>
<id>urn:sha1:59b8b12e46b5a42883d3e74db03661b9ff4d3ddc</id>
<content type='text'>
This fixes the problem where we'd report all connect failures as
proxy failures.

Closes #2459.
</content>
</entry>
<entry>
<title>tor-chanmgr: don't `warn_report!` for failed connections</title>
<updated>2026-03-24T22:51:19Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2026-03-24T22:51:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c7c376c60d77edd4d2324dc9f7e4a23620203f42'/>
<id>urn:sha1:c7c376c60d77edd4d2324dc9f7e4a23620203f42</id>
<content type='text'>
`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.
</content>
</entry>
<entry>
<title>tor-chanmgr: add loopback validation, startup warning and httparse</title>
<updated>2026-03-18T15:03:45Z</updated>
<author>
<name>Nihal</name>
<email>4218-nihalxkumar@gitlab.torproject.org</email>
</author>
<published>2026-03-10T15:51:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0149e5b710f15a66648d2c0a31e2eb90fadb49e7'/>
<id>urn:sha1:0149e5b710f15a66648d2c0a31e2eb90fadb49e7</id>
<content type='text'>
</content>
</entry>
</feed>
