book
                                
                                 book copied to clipboard
                                
                                    book copied to clipboard
                            
                            
                            
                        Bump ring from 0.17.8 to 0.17.14 in /listings/ch17-async-await/listing-17-01
Bumps ring from 0.17.8 to 0.17.14.
Changelog
Sourced from ring's changelog.
Version 0.17.14 (2025-03-11)
Fixed a performance bug in the AVX2-based AES-GCM implementation added in ring 0.17.13. This will be another notable performance improvement for most newish x86-64 systems. The performance issue impacted not just AES-GCM.
Compatibility with GNU binutils 2.29 (used on Amazon Linux 2), and probably even earlier versions, was restored. It is expected that ring 0.17.14 will build on all the systems that 0.17.12 would build on.
Version 0.17.13 (2025-03-06)
Increased MSRV to 1.66.0 to avoid bugs in earlier versions so that we can safely use
core::arch::x86_64::__cpuidandcore::arch::x86::__cpuidfrom Rust in future releases.AVX2-based VAES-CLMUL implementation. This will be a notable performance improvement for most newish x86-64 systems. This will likely raise the minimum binutils version supported for very old Linux distros.
Version 0.17.12 (2025-03-05)
Bug fix: briansmith/ring#2447 for denial of service (DoS).
Fixes a panic in
ring::aead::quic::HeaderProtectionKey::new_mask()when integer overflow checking is enabled. In the QUIC protocol, an attacker can induce this panic by sending a specially-crafted packet. Even unintentionally it is likely to occur in 1 out of every 2**32 packets sent and/or received.
Fixes a panic on 64-bit targets in
ring::aead::{AES_128_GCM, AES_256_GCM}when overflow checking is enabled, when encrypting/decrypting approximately 68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols like TLS and SSH are not affected by this because those protocols break large amounts of data into small chunks. Similarly, most applications will not attempt to encrypt/decrypt 64GB of data in one chunk.Overflow checking is not enabled in release mode by default, but
RUSTFLAGS="-C overflow-checks"oroverflow-checks = truein the Cargo.toml profile can override this. Overflow checking is usually enabled by default in debug mode.
Commits
- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- @dependabot rebasewill rebase this PR
- @dependabot recreatewill recreate this PR, overwriting any edits that have been made to it
- @dependabot mergewill merge this PR after your CI passes on it
- @dependabot squash and mergewill squash and merge this PR after your CI passes on it
- @dependabot cancel mergewill cancel a previously requested merge and block automerging
- @dependabot reopenwill reopen this PR if it is closed
- @dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- @dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency
- @dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- @dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- @dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.