Bump rustls to 0.23.45 for RUSTSEC-2026-0285 - #334
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
EnRaiha
added
the
run-ci
EnRaiha
changed the title
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.
Why
cargo deny checkruns in the lint job and fails on the current lockfile:rustls 0.23.43carries RUSTSEC-2026-0285 — TLS 1.3 handshake messages sent at the wrong encryption level were accepted when they followed a key-changing message in the same record. Because that check runs for every pull request, each one opens with a redLint & Checkuntil the lockfile moves. The advisory is the whole task, so it gets its own PR.What changed
Cargo.lock:rustls 0.23.43→0.23.45(the fixed release). No source change, no API change.Steps to test
cargo update -p rustls --precise 0.23.45cargo deny check advisories→advisories okcargo deny check→ clean; licenses and bans are unchanged by the bumpNo issue to close: the advisory is the task.