mirrors/arti.git/crates/tor-proto/src, branch arti-v0.3.0 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.3.0 2022-05-04T18:41:50Z Fix typos (using the typos-cli tool). 2022-05-04T18:41:50Z Nick Mathewson nickm@torproject.org 2022-05-04T18:36:27Z urn:sha1:fc33fc3efbfabd6d7d38334caedbea51ad6c8064 Upgrade to AES 0.8 2022-04-26T16:16:22Z Nick Mathewson nickm@torproject.org 2022-04-25T19:39:26Z urn:sha1:aaab6f38122261f7527e9a04b24972d09b775689 Now that we require Rust 1.56, we can upgrade to AES 0.8. This forces us to have some slight API changes. We require cipher 0.4.1, not cipher 0.4.0, since 0.4.0 has compatibility issues with Rust 1.56. squash! Bump every crate's edition to 2021. 2022-04-25T17:06:26Z Nick Mathewson nickm@torproject.org 2022-04-25T16:40:33Z urn:sha1:2f6bc6bdc431fa36de70a167eea777dcf3f60bf2 Remove all `use` statements for `TryFrom` and `TryInto`. These are now redundant in Rust 2021. handshake.rs: Document the time for clock skew authentication. 2022-04-11T16:34:16Z Nick Mathewson nickm@torproject.org 2022-04-11T16:31:05Z urn:sha1:4efe45ce6e14672625dea392b93da9cf43c72ec1 Implement a better clock skew estimator. 2022-04-11T16:34:16Z Nick Mathewson nickm@torproject.org 2022-04-07T20:03:25Z urn:sha1:cf362fac9f7288ddeddff447f9db23b0a27690b6 This time, our estimator discards outliers, takes the mean of what's left, and uses the standard deviation to try to figure out how seriously to take our report of skew/not-skew. These estimates are still not actually used. Initial functions to determine and expose a clock skew estimate. 2022-04-07T20:01:46Z Nick Mathewson nickm@torproject.org 2022-04-07T16:16:13Z urn:sha1:eedee51899eb3365a21c37be3803846373265284 (This is just a placeholder; I'm going to make the functions smarter in the next commit.) chanmgr: bubble ClockSkew up through the Error object. 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. Channel: Expose our view of whether the clock is skewed, and the age 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. Merge branch 'netinfo-clock-skew' into 'main' 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 tor-proto: better errors when handshake fails due to untimely certs 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.