<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-circmgr/src, branch arti-v1.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-v1.5.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.5.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-08-28T10:54:48Z</updated>
<entry>
<title>proto: Add a circuit module shared between client and relay impls.</title>
<updated>2025-08-28T10:54:48Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-08-26T17:48:56Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4ee5a4abcee895e79588888f6bc8eaa6963a6ba7'/>
<id>urn:sha1:4ee5a4abcee895e79588888f6bc8eaa6963a6ba7</id>
<content type='text'>
This is just code motion (I suggest reviewing with `--color-moved`).

This also moves the implementation-agnostic parts from
`tor_proto::client::circuit` to a new `tor_proto::circuit` module.
</content>
</entry>
<entry>
<title>Merge branch 'circmgr-timeout-estimator-logging' into 'main'</title>
<updated>2025-08-28T00:04:21Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-28T00:04:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=acca547fd0d08b22a4f7e1773b3a90d07728ae95'/>
<id>urn:sha1:acca547fd0d08b22a4f7e1773b3a90d07728ae95</id>
<content type='text'>
tor-circmgr: Add more logging about timeout estimation.

See merge request tpo/core/arti!3152</content>
</entry>
<entry>
<title>chanmgr: Add KeyMgr to channel builder</title>
<updated>2025-08-20T16:41:03Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2024-09-30T15:32:06Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a187a2fef281d7daae2fb6f503168cf48cfc0b99'/>
<id>urn:sha1:a187a2fef281d7daae2fb6f503168cf48cfc0b99</id>
<content type='text'>
This is so a relay can build authenticated channels. Several keys/cert
are required for this that are within the key manager.

Signed-off-by: David Goulet &lt;dgoulet@torproject.org&gt;
</content>
</entry>
<entry>
<title>proto: Move the `stream` module under `client` (fmt).</title>
<updated>2025-08-18T16:09:04Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-08-18T15:56:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fc10bb4cae16e0b19f39fd206d4d6f0b334f3f82'/>
<id>urn:sha1:fc10bb4cae16e0b19f39fd206d4d6f0b334f3f82</id>
<content type='text'>
</content>
</entry>
<entry>
<title>proto: Move the `stream` module under `client` (breaking).</title>
<updated>2025-08-18T16:09:04Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-08-18T15:52:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=702e7276898d3f31e22033c5b64fea91703f3701'/>
<id>urn:sha1:702e7276898d3f31e22033c5b64fea91703f3701</id>
<content type='text'>
The `stream` module is client-specific, for the most part, so I am
moving it under `client`. Later on, we will factor out the parts that
can be shared with the relay implementation.

Note: this is a breaking change as the deleted `stream` module was
`pub`. We could've kept the module and reexported from it the public
types from `tor_proto::client::stream`, but I think it's better to have
this `client` namespacing, because it makes the separation between the
client and relay parts clearer.
</content>
</entry>
<entry>
<title>tor-circmgr: Make connection failure log at debug level.</title>
<updated>2025-08-13T16:12:28Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2025-08-13T16:12:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a1970a6f64cf6393b0763e529c73194aa484a7fb'/>
<id>urn:sha1:a1970a6f64cf6393b0763e529c73194aa484a7fb</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-circmgr: Add more logging about timeout estimation.</title>
<updated>2025-08-12T15:25:01Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2025-08-11T23:54:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=51b689af344d3f24375c66a05f8feb1449d86f1c'/>
<id>urn:sha1:51b689af344d3f24375c66a05f8feb1449d86f1c</id>
<content type='text'>
We're seeing the logic that resets the timeouts when 18/20 connections
fail not triggering when we're expecting it to, this logging may help
figure out what's going on there.
</content>
</entry>
<entry>
<title>circmgr: Move the body of get_channel_to_guard into its only caller.</title>
<updated>2025-08-07T22:47:46Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-07T22:47:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=194c64bc0cc691457afe7ab1086c60f98269f7d4'/>
<id>urn:sha1:194c64bc0cc691457afe7ab1086c60f98269f7d4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>circmgr: Don't count channel negotiation towards circuit built time.</title>
<updated>2025-08-07T22:05:38Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-07T22:05:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f36b696837a4fe78b5fa6a9df90cb3786ea8b3e1'/>
<id>urn:sha1:f36b696837a4fe78b5fa6a9df90cb3786ea8b3e1</id>
<content type='text'>
This is important, since some circuits require us to negotiate a new
channel, and some don't: by adding this variability, we can easily
learn a timeout based on pre-existing channels to our guards, but
then later time out if it takes a while to open a TLS connection.

This is a possible solution to part of #2079, a bug where we "learn"
a circuit timeout that is too low for us to satisfy.
</content>
</entry>
<entry>
<title>cirmgr: extract code that opens a channel.</title>
<updated>2025-08-07T21:18:40Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-07T21:18:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4697000db5348511ef470f9f9d1a235bb176e3b7'/>
<id>urn:sha1:4697000db5348511ef470f9f9d1a235bb176e3b7</id>
<content type='text'>
</content>
</entry>
</feed>
