mirrors/arti.git/crates/tor-cert, branch arti-v1.1.2mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.22023-02-28T12:13:27ZPatchlevel bumps for remaining changed crates.2023-02-28T12:13:27ZNick Mathewsonnickm@torproject.org2023-02-28T12:13:27Zurn:sha1:f41449d0bd9a2db5f72dd9941fb897e5cd9b922d
These crates have had small code changes, but no API additions:
tor-config
tor-socksproto
tor-cert
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
arti
tor-hsservice
tor-congestion
These crates have had API extensions:
fs-mistrust
tor-llcrypto
tor-bytes
tor-checkable
tor-linkspec
tor-netdoc
tor-persist
arti-client
Merge branch 'ticket_525_part2' into 'main'2023-02-09T18:06:39ZNick Mathewsonnickm@torproject.org2023-02-09T18:06:39Zurn:sha1:696b9bd2d572b2a6b990c86a3f598c00664bf040
Apply restricted_msg to ChanMsg parts of tor-proto
See merge request tpo/core/arti!1013Change tor_bytes::Error::BadMessage to a Cow.2023-02-09T15:20:31ZNick Mathewsonnickm@torproject.org2023-02-08T13:51:27Zurn:sha1:48ab7b0463aaada172a426ad4b20a63d7f44cb84
Actually, to avoid making a breaking change, I'm deprecating
BadMessage and creating a new InvalidMessage variant that takes a
Cow. This way I don't need to track every crate that re-exposes
tor_bytes::Error and call this a breaking change in those.
Making this change will allow tor_bytes errors to be much more
helpful.
Rename key identifiers that have changed in the spec2023-02-08T16:57:51ZNick Mathewsonnickm@torproject.org2023-02-08T16:57:27Zurn:sha1:18e8ac7cb664067913c04a7091907fad785aaef1
Generated with perl:
s/K([PS])_hs_intro_tid/K$1_hs_ipt_sid/g;
s/K([PS])_onion_ntor/K$1_ntor/g;
s/K([PS])_hs_intro_ntor/K$1_hss_ntor/g;
s/K([PS])_hs_desc_ephem/K$1_hss_desc_enc/g;
tor-cert: document hs-related certificate types.2023-02-07T14:00:19ZNick Mathewsonnickm@torproject.org2023-01-30T14:52:28Zurn:sha1:a751eacd5b6a284186eee3de653980b15658a7cc
Also, explain why a few of these certificates aren't actually useful
as certificates. (This issue is also documented in torspec!110)
tor-cert: Implement Timebound for Ed25519Cert2023-02-07T14:00:19ZNick Mathewsonnickm@torproject.org2023-01-30T14:41:45Zurn:sha1:079002d2837fcf4320cb92d393719f48e5c835a7
This allows us to run `is_valid_at` and friends on the certificate
itself, which we will use soon in hsdesc validity checks.
Bump the patch version of every crate that had API additions2023-02-01T15:36:29ZNick Mathewsonnickm@torproject.org2023-02-01T15:36:29Zurn:sha1:7c1b6a5a81e382be6210c7e2b0aae9695ad0bef4
These crates had API or behavior changes that may affect downstream
crates. Fortunately, they're all version 0.x, and don't need minor
bumps for this.
Bump the patch-level version of crates with _minor_ changes.2023-02-01T15:23:58ZNick Mathewsonnickm@torproject.org2023-02-01T15:23:58Zurn:sha1:66f594a4b6fac81137886be90a7bda3687923d48
These changes influence behavior, but not effect compatibility.
(If I messed up, and any crate except for `arti` has non-breaking
API changes, that's still fine, since they are all version
0.x.)
Allow clippy::unchecked_duration_subtraction in tests2023-01-27T13:28:02ZNick Mathewsonnickm@torproject.org2023-01-27T13:01:45Zurn:sha1:a6dd92843edf2bd4c58de62a0d562921e4191ada
This panics on error, and we're fine with a panic on misbehavior in
tests.
Disable clippy::unlinlined-format-args2023-01-27T13:27:47ZNick Mathewsonnickm@torproject.org2023-01-27T12:49:39Zurn:sha1:bf04641c6818cb2c87c6ed9cf463a5710f8919d2
This warning kind of snuck up on us! (See #748) For now, let's
disable it. (I've cleaned it up in a couple of examples, since
those are meant to be more idiomatic and user-facing.)
Closes #748.