Repository navigation
update bundled CA certificates to 2026-10-20 - #98
Merged
AlexisT-CM merged 1 commit intoOct 27, 2026
Merged
Conversation
Contributor
Author
|
Hi @AlexisT-CM, you seem to be the one who has approved the latest PRs for this repo. Could you please take a look at this one? 🙂 It's important for the security of everyone using this library. |
AlexisT-CM
approved these changes
Oct 27, 2026
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.
What?
Update the outdated CA certificate bundle, similar to #92
Why?
This is mostly motivated by the recent eMudhra Intermediate CA Compromise (aka
emSign).The library uses the outdated bundle in the
VerifiedHTTPSConnectionclass for SSL/TLS verification, which may unnecessarily expose library consumers to security risks.