mirrors/arti.git/crates/tor-error/src/lib.rs, branch arti-v0.4.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.02022-05-09T18:40:29ZAdd new FsPermissions ErrorKind.2022-05-09T18:40:29ZNick Mathewsonnickm@torproject.org2022-05-03T15:54:41Zurn:sha1:8509ffff7af468c32873d278e2bca4fecfd59a17Fix grammar and typos2022-04-27T12:52:13ZSamanta Navarroferivoz@riseup.net2022-04-23T11:51:44Zurn:sha1:c53818d496c910de4dfc4bc8d1f53e419fbf7408tor-error: Add a new RetryTime type and related trait.2022-04-04T15:09:25ZNick Mathewsonnickm@torproject.org2022-03-31T14:43:46Zurn:sha1:3676826d0332912f6fdfd4f5b55f7d93ce671c62tor-proto: better errors when handshake fails due to untimely certs2022-03-23T12:24:36ZNick Mathewsonnickm@torproject.org2022-03-14T18:33:11Zurn: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.
Provide ErrorKind::Other2022-03-04T17:35:34ZIan Jacksonijackson@chiark.greenend.org.uk2022-03-04T17:31:03Zurn:sha1:055b7399f2acba4dd71777ad7d08deaec9e2a271Merge branch 'clippy-allow-arc-clone' into 'main'2022-03-01T20:38:05ZNick Mathewsonnickm@torproject.org2022-03-01T20:38:05Zurn:sha1:83c8b11c2c08a05928bdb0390922391d13261ef2
Disable clippy::clone_on_ref_ptr
See merge request tpo/core/arti!352Fix typo in message2022-02-28T14:47:25ZNick Mathewsonnickm@torproject.org2022-02-28T14:47:25Zurn:sha1:ec25f68b9bf002034886256b18e6247b13a0018bEK::RemoteProtocolFailed replaces OtherRemote2022-02-28T13:27:44ZIan Jacksonijackson@chiark.greenend.org.uk2022-02-28T13:27:44Zurn:sha1:8898bbb4218b4858aabe80d5b049a8a025c1c7a9
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/355#note_2781816
Introduce ErrorKind::OtherRemote2022-02-28T13:07:44ZIan Jacksonijackson@chiark.greenend.org.uk2022-02-24T18:10:08Zurn:sha1:c08a3170937c64d8cf699584867e5fe3fcc51fb6
arti-hyper wants to be able to have a kind for TLS failure.
Given that arti-hyper is above arti-client, this shows that callers
above arti-client might need to invent kinds for their own errors.
Possibly this means we need other Other errors for other locations.
If we have pluggable components we might even want OtherTorError.
Merge branch 'proto_handshake_err' into 'main'2022-02-24T19:44:34ZNick Mathewsonnickm@torproject.org2022-02-24T19:44:34Zurn:sha1:7f3ea03e58dfe7a7dcc051aeb015b432cab876df
tor-proto: Split up a couple of handshake-based errors
Closes #359 and #358
See merge request tpo/core/arti!344