mirrors/arti.git/crates/tor-rtcompat, branch arti-v1.4.2mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.22025-04-01T10:13:21Ztor-rtcompat: Avoid wildcard dependency requirements.2025-04-01T10:13:21ZGabriela Moldovangabi@torproject.org2025-04-01T10:13:21Zurn:sha1:3ce3c2f4aeea2515db6473c6fe30ab90eeb197d8
This is preventing us from publishing `tor-rtcompat`:
> error: failed to publish to registry at https://crates.io
>
> Caused by:
> the remote server responded with an error (status 400 Bad Request): wildcard (`*`) dependency constraints are not allowed on crates.io. Crate with this problem: `hex` See https://doc.rust-lang.org/cargo/faq.html#can-libraries-use--as-a-version-for-their-dependencies for more information
Bump all the unstable tor- and arti- crates to 0.29.0.2025-03-31T17:59:51ZGabriela Moldovangabi@torproject.org2025-03-31T17:34:50Zurn:sha1:1be579f99a7c0784bd7710f9ee6ee9a6b10c85df
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.29.0
done
```
Upgrade rustls-wekpki dependency to 0.103.1.2025-03-27T14:32:25ZGabriela Moldovangabi@torproject.org2025-03-27T11:56:32Zurn:sha1:0cee4a47625c5840003bbd81164adf4f004cb7c8
We aren't affected by any of the breaking changes from [0.103.0].
[0.103.0]: https://github.com/rustls/webpki/releases/tag/v%2F0.103.0
AF_UNIX terminology: Rename two error structs2025-03-24T13:58:54ZIan Jacksonijackson@chiark.greenend.org.uk2025-03-06T15:52:03Zurn:sha1:73157920ffa84d6f1580170a0e40e5fbe3106a67
We change `NoUnixAddressSupport` to `NoAfUnixSocketSupport` because it
doesn't make much sense to talk about support for the addresses
separately from support for the sockets.
Fix AF_UNIX terminology in docs, comments, and error messages2025-03-24T13:58:54ZIan Jacksonijackson@chiark.greenend.org.uk2025-03-06T15:16:03Zurn:sha1:a60165c11c66c579d628a670de56bfcff494c1cdMerge branch 'x509-signature-yeet' into 'main'2025-03-05T13:50:08ZNick Mathewsonnickm@torproject.org2025-03-05T13:50:08Zurn:sha1:f880d8c4bea2cd82aba325b82bb68878bb769e97
Switch from x509-signature to rustls-webpki when using rustls.
Closes #1824 and #1854
See merge request tpo/core/arti!2816rustls: move provider-installer to its own function.2025-03-04T19:45:18ZNick Mathewsonnickm@torproject.org2025-03-03T15:17:33Zurn:sha1:d206e9b70ddfce0083546d4f1836129985b9abfc
We do this so that we can make sure there's a provider installed
when we run the tests.
Require rustls 0.23.202025-03-04T19:45:18ZNick Mathewsonnickm@torproject.org2025-03-03T15:15:14Zurn:sha1:3931f216ec23991653b196596c9758eff61b68e5
This is the version that introduces `root_hint_subjects()`,
which we want our ServerCertVerifier to override.
Require rustls-pki-types 1.8 for CertificateDer::from_slice2025-03-04T19:45:18ZNick Mathewsonnickm@torproject.org2025-02-27T21:49:33Zurn:sha1:e07f893b93e5503c56d7ff875a11e7afe7ff0d91rustls.rs: Replace x509-signature with rustls-webpki2025-03-04T19:45:18ZNick Mathewsonnickm@torproject.org2025-02-26T22:02:48Zurn:sha1:ede6d75567c1ee81812478e6137032dd568ddb91
The x509-signature crate is archived, and won't see any more
releases. Using it is tying us to ring 0.16 internally,
which means we depend on two ring versions.
Fortunately, rustls-webpki relaxes some of the earlier restrictions
from the vanilla webpki crate, which means that its certificate parser
now accepts C tor's oddball x509 certificates as valid.
With this change, we can delegate to rustls's built-in
signature-checking code, and we only have to override its
certificate validation. (We still override it with a pile of
comments about how we don't validate link certificates much.)
I've had to include a few certificates: two are for tests,
but one is needed as a placeholder, since we can't construct
a rustls certificate validator without a root cert,
even if we'll never use it.
Closes #1824.
Closes #1854.