mirrors/arti.git/crates/tor-rtcompat/src/impls, branch arti-v1.2.3mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.32024-04-22T15:25:45ZAdd a note about CryptoProvicder.2024-04-22T15:25:45ZNick Mathewsonnickm@torproject.org2024-04-22T14:51:27Zurn:sha1:8009b323e192ed380ada8b7da2fc52974b942331Upgrade to futures-rustls 0.26.0, rustls 0.23.5.2024-04-22T15:25:45ZNick Mathewsonnickm@torproject.org2024-04-22T14:00:46Zurn:sha1:5f035cb5cbcb11bcdf0467667ad51a53bcdbce85
The rustls upgrade will solve #1377 and CVE-2024-32650.
Note that we've had to patch our RustlsProvider impl a bit in order
to keep the tests passing. See comments.
Closes #1377.
Run maint/add_warning.2024-03-13T16:30:53ZNick Mathewsonnickm@torproject.org2024-03-13T16:30:53Zurn:sha1:c0c9bd15d42897825dd0ab3d3b8dd1c17bd6320crtcompat: Fix a rustdoc link.2024-01-30T18:17:49ZNick Mathewsonnickm@torproject.org2024-01-30T18:17:49Zurn:sha1:8942fecd037a1d6c7c377043d379afda598881e7Upgrade to futures-rustls and rustls 0.22.2024-01-25T14:12:43ZNick Mathewsonnickm@torproject.org2024-01-23T19:37:00Zurn:sha1:91735540559d35bb272d0a5e26e61053d38ebd82
The futures-rustls crate has supplanted the async-rustls crate,
and it requires/embeds rustls 0.22.
Closes #1179.
clippy: consequential rustfmt2024-01-02T15:04:18ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-02T12:49:55Zurn:sha1:1ba7e8a78f21b5e1c26c87d12e7a77ebb3a8949dclippy: Use infallible calls2024-01-02T13:56:22ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-02T12:48:56Zurn:sha1:0ce386a24bd5b0490aee28345f90c7ac956a844d
Resolves clippy complaints about needless fallible conversions.
clippy: Replace many calls to .get(0) with .first()2024-01-02T13:56:08ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-02T12:48:44Zurn:sha1:b9da8cf60618b16c021d3ecf1ec24e2dce56aff5
FTR I don't think agree with clippy on this question, but then I often
don't.
tor-rtcompat: use track-caller for thin wrappers2023-12-18T17:02:12ZJim Newsomejnewsome@torproject.org2023-12-18T17:02:12Zurn:sha1:30c07a6c0b544a55795985ff6451f72818fda1c8
In particular, when the (unstable) tokio tracing feature is enabled,
every tracing line includes the name of where the current task was
created. Without this change, that ends up being the name of
intermediate trait methods like TokioRuntimeHandle::block_on, which is
not very helpful.
Adding the `track_caller` attribute causes the name of the caller of
these methods to be used instead, which is typically more helpful.
IIUC this change is not breaking in terms of semver
https://rustc-dev-guide.rust-lang.org/backend/implicit-caller-location.html.
Upgrade async_executors dependency to 0.7.02023-09-28T13:47:31ZNick Mathewsonnickm@torproject.org2023-09-28T13:47:31Zurn:sha1:1be1b1616349749988a6483b357e6f017a13c03c