Repository navigation
SECURITY: Update rustls-webpki to 0.103.16 to exclude leaked CA certificates - #209
Open
manishearth-agent wants to merge 1 commit into
Conversation
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.
Note
This is a security issue filed automatically after an LLM-driven ecosystem-wide
security audit of the eMudhra certificate issue run by @Manishearth.
No text in this PR body is AI-generated: it is a handwritten template. Any further comments from me will also not be AI-generated.
Hi!
I ran an ecosystemwide security audit of the eMudhra certificate issue and discovered that this crate's dependency requirements prevent upgrading rustls-webpki via
cargo update. This bumps the version to 0.103.16.You may need to perform further fixes to get this to pass CI, unfortunately running
cargo update/cargo checkon third-party code is a security risk so this is the maximum change I can make automatically. This only changes the manifest, does not touch lockfiles, and has not been build-tested. Consider this more like a filed issue that may be possible to be merged directly.I am happy to answer any questions you may have!
Please do feel free to close this PR and make your own, and there is no obligation to fix this quickly.
This is a public PR without private reporting as the eMudhra issue is widely known at this point.