Bump deps to v0.3.1: security fixes + cargo install fix#18
Merged
Conversation
- russh 0.57 → 0.60: fixes `cargo install` rsa pre-release resolver conflict and closes high-severity DoS GHSA-f5v4-2wr6-hqmg; drops libcrux-ml-kem (high-severity GHSA-q29p-9pfr-j652 in libcrux-sha3) - ratatui 0.29 → 0.30, crossterm 0.28 → 0.29, ssh2-config 0.6 → 0.7: latest - aws-lc-sys 0.37 → 0.40 via cargo update: closes 5 high-severity CVEs - lru 0.12 → 0.16, rand 0.9 → 0.10.1, plus ~60 compatible transitive bumps Adapt authenticate_publickey_with call site for russh 0.60 API change (AgentIdentity now wraps PublicKey; extract via .public_key().into_owned()).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
cargo install sshfwd— russh 0.57 used caret ranges on RustCrypto pre-releases, causing cargo's resolver to land onrsa-0.10.0-rc.12(type-mismatch compile error). russh 0.60 uses exact pins (rsa =0.10.0-rc.16,pkcs8 =0.11.0-rc.11), so the resolver is now deterministic and correct.russhDoS GHSA-f5v4-2wr6-hqmg (fixed in 0.60.1) — russh 0.57 → 0.60aws-lc-sys5× high CVEs (fixed in 0.38–0.39) — 0.37.0 → 0.40.0 viacargo updatelibcrux-sha3high GHSA-q29p-9pfr-j652 — libcrux-ml-kem dropped entirely in russh 0.60lrulow GHSA-rhfx-m35p-ff5j — 0.12.5 → 0.16.4 via ratatui 0.30 transitive bumprandlow GHSA-cq8v-f236-94qc — 0.9.2 → 0.10.1 via cargo update ✅ (fully closed)aws-lc-sys0.37.0 → 0.37.1) — that bump did not satisfy any of the open CVEs (required ≥0.38.0); close it after this merges.authenticate_publickey_withinssh/session.rs— russh 0.60 changedAgentIdentityfrom a plainPublicKeyto an enum; extract via.public_key().into_owned()Test plan
cargo fmt -- --checkpassescargo clippy --all-targets --all-featurespassescargo test --workspacepasses (19 tests)cargo build -p sshfwdsucceedscargo install --path crates/sshfwd --forcesucceeds (verifies resolver fix)v0.3.1and push to trigger GH Actions release; close PR build(deps): Bump aws-lc-sys from 0.37.0 to 0.37.1 in the cargo group across 1 directory #16