Skip to content

fix(deps): update rust crate shadowsocks-crypto to 0.7.0#2129

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/shadowsocks-crypto-0.x
Open

fix(deps): update rust crate shadowsocks-crypto to 0.7.0#2129
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/shadowsocks-crypto-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 1, 2026

This PR contains the following updates:

Package Type Update Change
shadowsocks-crypto dependencies minor 0.6.00.7.0

Release Notes

shadowsocks/shadowsocks-crypto (shadowsocks-crypto)

v0.7.0

Compare Source

Changelog — v0.7.0

Breaking changes

  • MSRV bumped to 1.71 (was 1.63).
  • Faster-crypto backend switched from ring to aws-lc-rs, exposed via the new aws-lc Cargo feature. Platforms not supported by aws-lc-rs (e.g. WASM) must leave the feature off and use the pure-Rust fallback.
  • Windows builds with aws-lc now require NASM at build time.

Features

  • New aws-lc-rs backend for AES-128/256-GCM, ChaCha20-Poly1305, AES-GCM-SIV, and HKDF-SHA1, delivering higher AEAD/HKDF throughput.
  • Pure-Rust implementations remain available as the default fallback.

Improvements

  • Pure-Rust AES-GCM wrappers now heap-box their key schedule, greatly shrinking AeadCipherVariant and the v2 TCP/UDP CipherVariant enums.
  • Updated RustCrypto hash dependencies (md-5, sha1, hkdf).
  • Various clippy-driven cleanups across RC4, Table, SM4-GCM and HKDF code.

v0.6.3

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 1, 2026

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants