Skip to content

deps(deps): bump the crypto-stack group with 4 updates #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

deps(deps): bump the crypto-stack group with 4 updates #41

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
97 changes: 72 additions & 25 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 4 additions & 4 deletions Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ semver = { version = "^1.0.27" } # 2025-11-03 sw: version range evaluation for d
serde = { version = "=1.0.228", features = ["derive"] } # 2025-11-03 sw: canonical serialization; CT reviewed
serde_json = { version = "=1.0.145" } # 2025-11-03 sw: deterministic JSON for protocol surfaces
serde_yaml = { version = "0.9" } # YAML parsing for CLI policies
blake3 = { version = "=1.8.3" } # 2025-11-03 sw: convergent hash, SIMD constant-time per upstream audit
blake3 = { version = "=1.8.5" } # 2025-11-03 sw: convergent hash, SIMD constant-time per upstream audit
bloomfilter = { version = "=1.0.13" } # 2025-11-03 sw: dedupe candidate screening, bounded memory
aya = { version = "=0.11.0" } # 2025-11-09 sw: eBPF loader for zero-trust ingress hooks
tokio-tungstenite = { version = "=0.21.0", default-features = false, features = ["connect", "rustls-tls-webpki-roots"] } # 2025-11-09 sw: mTLS control plane for zero-trust frontends
Expand All @@ -78,14 +78,14 @@ hex = { version = "=0.4.3" } # 2025-11-03 sw: hex encoding for key material, con
lz4 = { version = "=1.28.1" } # 2025-11-03 sw: hot-path compression, SIMD routines audited
zstd = { version = "=0.13.3" } # 2025-11-03 sw: deep compression with wasm off, see audit log entry CRS-132
zeroize = { version = "=1.8.2" } # 2025-11-03 sw: memory clearing policy alignment
aes = { version = "=0.8.4" } # 2025-11-03 sw: AES-NI optimized, matches Phase3 design
cipher = { version = "=0.4.4" } # 2025-11-03 sw: trait glue for AES/Poly1305 stack
aes = { version = "=0.9.0" } # 2025-11-03 sw: AES-NI optimized, matches Phase3 design
cipher = { version = "=0.5.1" } # 2025-11-03 sw: trait glue for AES/Poly1305 stack

@augmentcode augmentcode Bot Apr 27, 2026 •
edited
Loading

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cipher was bumped across a major version; please double-check crates/encryption/src/xts.rs (Xts128::<Aes256> + KeyInit) is still using the same cipher trait version that xts-mode is built against. If xts-mode and aes end up pulling different cipher major versions, Aes256 may no longer satisfy xts-mode’s trait bounds and break encryption/decryption.

Severity: high

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.

xts-mode = { version = "=0.5.1" } # 2025-11-03 sw: XTS primitive, matches patentable_concepts.md guidance
poly1305 = { version = "=0.8.0" } # 2025-11-03 sw: MAC verification, constant-time guarantee
cpufeatures = { version = "=0.2.17" } # 2025-11-03 sw: runtime AES capability detection
subtle = { version = "=2.6.1" } # 2025-11-03 sw: constant-time comparisons for key/tweak handling
hmac = { version = "=0.12.1" } # 2025-11-04 sw: HKDF based on HMAC-SHA256 for key derivation
sha2 = { version = "=0.10.9" } # 2025-11-04 sw: Hash core for HKDF extractor
sha2 = { version = "=0.11.0" } # 2025-11-04 sw: Hash core for HKDF extractor

@augmentcode augmentcode Bot Apr 27, 2026 •
edited
Loading

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bumping sha2 to 0.11 likely moves it onto the digest 0.11 trait stack, while hmac remains pinned to 0.12.1; please verify Hmac<Sha256> in crates/encryption/src/keymanager.rs still typechecks with a single digest version. A digest major-version split in the dependency graph commonly causes hard-to-diagnose trait/type incompatibilities in KDF codepaths.

Severity: high

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.


# Web Interface & Mesh Networking (2025-11-16 sw; Next-gen web interface with gossip)
axum = { version = "^0.7.9", features = ["ws", "macros", "multipart"] } # 2025-11-16 sw: Web server framework
Expand Down
Loading