Repository navigation
fix(deps): close two russh SSH server advisories by moving to 0.64.1 - #658
Conversation
GHSA-4wc5-f2rc-q74m (medium): the agent protocol server allocated without bound on crafted constraint records; fixed in 0.64.1. GHSA-j7h2-66j4-ghjf (low): the server accepted a publickey signature made with a different algorithm than the request named; fixed in 0.64.0. russh stays on ring with the same features, so aws-lc stays out of the graph, and its cargo vet exemption moves to the new version.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Dependabot reports two open russh advisories against
Cargo.lock. russh is only built with thesshfeature, where it runs the Tailscale SSH server.The fix moves the pin from 0.63.2 to 0.64.1, with the same features (
flate2,ring, no defaults), so aws-lc stays out of the graph. Only the russh entry changes inCargo.lock, and thecargo vetexemption moves to 0.64.1. No code change was needed.On MacMini:
cargo clippy --workspace --all-targets --all-features -D warningsis clean,cargo test -p geiserx_tailscale --all-featurespasses (174 tests),cargo deny check allreports advisories ok, andcargo vet --lockedpasses.Summary by CodeRabbit