Re: [PR] build(deps): bump ring from 0.17.9 to 0.17.14 [datafusion-python]

2025-05-28 Thread via GitHub


dependabot[bot] commented on PR #1124:
URL: 
https://github.com/apache/datafusion-python/pull/1124#issuecomment-2917263369

   Looks like ring is up-to-date now, so this is no longer needed.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



Re: [PR] build(deps): bump ring from 0.17.9 to 0.17.14 [datafusion-python]

2025-05-28 Thread via GitHub


dependabot[bot] closed pull request #1124: build(deps): bump ring from 0.17.9 
to 0.17.14
URL: https://github.com/apache/datafusion-python/pull/1124


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



[PR] build(deps): bump ring from 0.17.9 to 0.17.14 [datafusion-python]

2025-05-09 Thread via GitHub


dependabot[bot] opened a new pull request, #1124:
URL: https://github.com/apache/datafusion-python/pull/1124

   Bumps [ring](https://github.com/briansmith/ring) from 0.17.9 to 0.17.14.
   
   Changelog
   Sourced from https://github.com/briansmith/ring/blob/main/RELEASES.md";>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::__cpuid and 
core::arch::x86::__cpuid from
   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: https://redirect.github.com/briansmith/ring/pull/2447";>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" or 
overflow-checks = true in the Cargo.toml
   profile can override this. Overflow checking is usually enabled by default in
   debug mode.
   
   
   
   Commits
   
   See full diff in https://github.com/briansmith/ring/commits";>compare view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=ring&package-manager=cargo&previous-version=0.17.9&new-version=0.17.14)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   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-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot show  ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will 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 version` will 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 dependency` will 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](https://github.com/apache/datafusion-python/network/alerts).
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---