commit: 81c2a56d3e0cc097041e840c95a645e92cf9a684
parent d59254f5046581e7cab75fa646e0c2bfc15f46b8
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date: Sun, 20 Jul 2025 03:07:33 +0200
notes/rust-issues: ring got releases in 2023-10-02
Few months after I added the ring section in my notes.
Diffstat:
1 file changed, 0 insertions(+), 8 deletions(-)
diff --git a/notes/rust-issues.xhtml b/notes/rust-issues.xhtml
@@ -34,14 +34,6 @@
This is what intentionally throwing distros away gets you into.
</p>
- <h2><code>ring</code> crypto library</h2>
- <ul>
- <li><a href="https://lib.rs/crates/ring/versions">No release, stable or alpha, since 2021</a></li>
- <li>Used by virtually everything in Rust, it's a dependency of <code>rustls</code> <a href="https://lib.rs/crates/ring/rev">among other things</a></li>
- <li>Grabs some C and Assembly code from BoringSSL, which no one except Google should be using as it doesn't have versions nor security notices</li>
- <li><code>x86_{32,64}</code> and <code>arm{32,64}</code> only due to it using assembly and released versions not supporting a fallback to portable code. So for other architectures like ppc64, riscv, … you need to mangle the dependency tree to use patches / forks or the latest git.</li>
- </ul>
-
<h2>Extra: Crates.io outage due to bad URL mangling</h2>
<p>
<a href="https://blog.rust-lang.org/inside-rust/2023/07/21/crates-io-postmortem.html">crates.io Postmortem: Broken Crate Downloads</a>
