<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-chanmgr/src/builder.rs, branch tor-dirmgr-v0.5.1</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-dirmgr-v0.5.1</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-dirmgr-v0.5.1'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-07-06T15:51:28Z</updated>
<entry>
<title>ChanMgr: errors: attribute errors to correct address.</title>
<updated>2022-07-06T15:51:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-05T15:47:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=dd491931c8841f2eaed7fea19d6b0777e990a254'/>
<id>urn:sha1:dd491931c8841f2eaed7fea19d6b0777e990a254</id>
<content type='text'>
Even when keys are relevant, we still don't want to attribute errors
to a set of addresses when we have a single address that we're
connected with.
</content>
</entry>
<entry>
<title>ChanMgr: Add more contextual info to error types.</title>
<updated>2022-07-06T15:51:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-05T15:37:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bc9db9b84cc11861b9d7f1ffa7def24e6abca8af'/>
<id>urn:sha1:bc9db9b84cc11861b9d7f1ffa7def24e6abca8af</id>
<content type='text'>
Now each type has a peer.  In some cases this peer is just an
address, whereas in others (where key is relevant or address isn't
yet narrowed down) it's a full OwnedChanTarget.
</content>
</entry>
<entry>
<title>channel padding: Rename ChannelsParams from ChannelsConfig</title>
<updated>2022-06-21T18:19:28Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-06-17T13:16:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7d676cde02c692f3800f05ff8195a500e974677c'/>
<id>urn:sha1:7d676cde02c692f3800f05ff8195a500e974677c</id>
<content type='text'>
As per
  https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/586#note_2814276

Change names and comments and docs everywhere.
</content>
</entry>
<entry>
<title>channel padding: Plumb settings from chanmgr</title>
<updated>2022-06-21T18:19:22Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-06-14T14:42:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7f3f42673816be8924395c9db26e55bee5c9c412'/>
<id>urn:sha1:7f3f42673816be8924395c9db26e55bee5c9c412</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Plumb a SleepProvider into the channel reactor</title>
<updated>2022-06-08T10:24:26Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-06-06T15:39:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e8fc1036d3d8de0da72329071b63a64e8f5d98eb'/>
<id>urn:sha1:e8fc1036d3d8de0da72329071b63a64e8f5d98eb</id>
<content type='text'>
The channel reactor is going to want to be able to sleep so that it
can do padding, so it needs a SleepProvider.
</content>
</entry>
<entry>
<title>chanmgr: expose whether we are failing because of expired certs.</title>
<updated>2022-04-12T12:03:49Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-04-11T20:29:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5f946b8d4589bf68e1e9d58f18b484c32cfb6f5f'/>
<id>urn:sha1:5f946b8d4589bf68e1e9d58f18b484c32cfb6f5f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>chanmgr: bubble ClockSkew up through the Error object.</title>
<updated>2022-04-07T14:15:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-04-07T14:01:19Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9160b55c57e9b2d68b82059139a2be0dd7954b8a'/>
<id>urn:sha1:9160b55c57e9b2d68b82059139a2be0dd7954b8a</id>
<content type='text'>
Fortunately, we don't need a separate type here: authenticated
clock skew can only come attached to a `tor_proto::Error`.

We also remove skew from `tor_proto::Error::HandshakeCertsExpired`,
since it would now be redundant.
</content>
</entry>
<entry>
<title>chanmgr: add a test for AbstractChannel::duration_unused</title>
<updated>2022-04-02T20:05:00Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-04-02T20:01:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f59f68d32de287af40201c9936675b104fb16797'/>
<id>urn:sha1:f59f68d32de287af40201c9936675b104fb16797</id>
<content type='text'>
</content>
</entry>
<entry>
<title>chanmgr: add tests for connect_one.</title>
<updated>2022-04-02T19:50:56Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-04-02T19:50:56Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8d823dd2e5f2f33db7b1d10ce4028898b1dbcfc0'/>
<id>urn:sha1:8d823dd2e5f2f33db7b1d10ce4028898b1dbcfc0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-proto: add a backend to detect reported clock skew.</title>
<updated>2022-03-23T12:24:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-03-14T15:51:06Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3885a2c05b64e6d071adfabdf5eb957fab001a5d'/>
<id>urn:sha1:3885a2c05b64e6d071adfabdf5eb957fab001a5d</id>
<content type='text'>
NETINFO cells, which are sent in every handshake, may contain
timestamps.  This patch adds an accessor for the timestamp in the
Netinfo messages, and teaches the tor-proto code how to compute the
minimum clock skew in the code.

The computation isn't terribly precise, but it doesn't need to be:
Tor should work fine if your clock is accurate to within a few
hours.

This patch also notes a Y2038 problem in the protocol: see
torspec#80.

Part of #405.
</content>
</entry>
</feed>
