mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.0 2022-04-11T16:34:16Z 2022-04-11T16:34:16Z Nick Mathewson nickm@torproject.org 2022-04-11T16:31:05Z urn:sha1:4efe45ce6e14672625dea392b93da9cf43c72ec1 2022-04-07T14:15:28Z Nick Mathewson nickm@torproject.org 2022-04-07T14:01:19Z urn:sha1:9160b55c57e9b2d68b82059139a2be0dd7954b8a 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. 2022-04-07T14:07:35Z Nick Mathewson nickm@torproject.org 2022-04-06T19:29:24Z urn:sha1:7656ab09319aacbc8ef0e89e34a7dd5ce0ba1d85 of a channel. At first I wanted to have this information not be a part of channels at all, but it is a fairly tiny amount of data, and the alternatives are pretty crufty. 2022-03-23T12:49:36Z Nick Mathewson nickm@torproject.org 2022-03-23T12:49:36Z urn:sha1:791394cd2b455646c5e8938e7592d73b28c7977b tor-proto: add the ability to learn clock skew from NETINFO cells See merge request tpo/core/arti!410 2022-03-23T12:24:36Z Nick Mathewson nickm@torproject.org 2022-03-14T18:33:11Z urn:sha1:0b2cf533ee5771fdb16255652837af69c316642e We now check the handshake certificates unconditionally, and only report them as _expired_ as a last resort. (Rationale: if somebody is presenting the wrong identity from a year ago, it is more interesting that they are presenting the wrong ID than it is that they are doing so with an expired cert. We also now report a different error if the certificate is expired, but its expiration is within the range of reported clock skew. (Rationale: it's helpful to distinguish this case, so that we can blame the failure on possible clock skew rather than definitely attributing it to a misbehaving relay.) Part of #405. 2022-03-23T12:24:36Z Nick Mathewson nickm@torproject.org 2022-03-14T15:51:06Z urn:sha1:3885a2c05b64e6d071adfabdf5eb957fab001a5d 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. 2022-03-17T16:03:34Z Nick Mathewson nickm@torproject.org 2022-03-17T15:52:15Z urn:sha1:764930b9cd8c63a4dd59229ad6298e6b27fb375c Each channel now remembers an OwnedChanTarget. Each circuit now remembers a vector of OwnedChanTarget to represent the path that it was constructed for. Part of #415. 2022-02-24T18:23:42Z Nick Mathewson nickm@torproject.org 2022-02-24T18:23:42Z urn:sha1:d8120e1649e4e8f039666ff1c3aedff5f1310154 Remove default conversion; instead use a specific conversion in each of the two modules that need to do it. 2022-02-23T15:39:08Z Nick Mathewson nickm@torproject.org 2022-02-23T15:35:09Z urn:sha1:74a5ce863553780fadc1afb926a14cfb8426f367 This helps the user distinguish between protocol violations that happen when connecting to the tor network from those that happen while connected. Closes #358. 2022-02-23T15:38:48Z Nick Mathewson nickm@torproject.org 2022-02-23T15:01:28Z urn:sha1:afa49eac8f45ea34a419e7a8cef7bb03026b5c75 We want to distinguish handshake failures from errors later on in the channel's lifetime. Closes #359.