mirrors/arti.git/crates/tor-rtcompat/src, branch arti-v1.4.3mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.32025-04-14T14:06:59ZMerge branch 'fork' into 'main'2025-04-14T14:06:59ZDavid Gouletdgoulet@torproject.org2025-04-14T14:06:59Zurn:sha1:e165048b205ec98f8d1a06d3b8c2bc30eeb7fad9
Forbid fork, except very carefully before exec
Closes #1897
See merge request tpo/core/arti!2925Merge branch 'rtmock-unsend' into 'main'2025-04-14T13:22:34ZDavid Gouletdgoulet@torproject.org2025-04-14T13:22:34Zurn:sha1:603cd07c65c5d8cbaa2cf277a7102514c7d8e5c1
Relax bounds on BlockOn::reenter_block_on
Closes #1933
See merge request tpo/core/arti!2934tor-rtcompat: BlockOn: relax bounds on reenter_block_on2025-04-09T16:52:03ZIan Jacksonijackson@chiark.greenend.org.uk2025-04-07T16:58:45Zurn:sha1:2a7dc6c46274e0d96e773c031cabd5373483429e
The future no longer needs to be `Send + 'static`.
Allow StreamOps import to be unused2025-04-09T16:25:51ZNick Mathewsonnickm@torproject.org2025-04-09T16:25:51Zurn:sha1:f79bb13bbd55957a8e67725455cc8460f5064ee0
This comes up on OSX; I hadn't seen it before, so I assume it is new
with Rust 1.86.
tor-rtcompat: xref to fork policy from PreferredRuntime2025-04-07T15:24:53ZIan Jacksonijackson@chiark.greenend.org.uk2025-04-07T15:00:35Zurn:sha1:8a413f8a047d603cd2187ab0cbcc2a487b9cc41aAF_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.
rustls.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.