mirrors/arti.git/crates/tor-error/src/lib.rs, branch arti-v0.6.0 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.6.0 2022-06-23T18:15:42Z Run maint/add_warning crates/*/src/{lib,main}.rs 2022-06-23T18:15:42Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-06-23T18:15:29Z urn:sha1:589c6e52bb49ccfe6c0ad9d18d6b994978e46c6c Update all lint blocks tor-error: Fix a broken intra-doc link 2022-06-10T12:45:30Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-06-10T12:45:30Z urn:sha1:abea103bb06ba1c047c58540d8057fc0ef5fdc8c I didn't spot this in review amongst the other messages from Nightly. try to differentiate transient from nontransient error 2022-06-08T15:02:01Z trinity-1686a trinity@deuxfleurs.fr 2022-06-02T17:43:47Z urn:sha1:6c6998a65b815ffe5c20b5c1db48d76af55648e9 lints: Make lint blocks consistent 2022-05-31T14:24:11Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-31T13:39:09Z urn:sha1:fec706c2f3525d38f540e986c94a092fa498734b The remaining consequences of running add_warning lints: Add let_unit_value allow to all crates 2022-05-31T14:23:52Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-31T10:46:13Z urn:sha1:4f42101554822c44782c164cac0051e3b4055abd From running add_warning, with manual picking of the right hunks/lines. lints: Add lint block delimiters to every crate 2022-05-31T12:00:31Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-30T17:43:12Z urn:sha1:ba0843da4a7ba1e63846a286b870b893092e0a4f This was the result of: maint/add_warning crates/*/src/{lib,main}.rs and then manually curating the results. Add new FsPermissions ErrorKind. 2022-05-09T18:40:29Z Nick Mathewson nickm@torproject.org 2022-05-03T15:54:41Z urn:sha1:8509ffff7af468c32873d278e2bca4fecfd59a17 Fix grammar and typos 2022-04-27T12:52:13Z Samanta Navarro ferivoz@riseup.net 2022-04-23T11:51:44Z urn:sha1:c53818d496c910de4dfc4bc8d1f53e419fbf7408 tor-error: Add a new RetryTime type and related trait. 2022-04-04T15:09:25Z Nick Mathewson nickm@torproject.org 2022-03-31T14:43:46Z urn:sha1:3676826d0332912f6fdfd4f5b55f7d93ce671c62 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.