Repository navigation
Fix Python SSL trust after the eMudhra certificate compromise - #322
Open
vortexopenclaw wants to merge 1 commit into
Open
vortexopenclaw wants to merge 1 commit into
vortexopenclaw 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.
BlitzAPI's Python certificate bundle can still trust certificates affected by the eMudhra compromise even after the node's system certificates are updated. This updates certifi in the existing dependency locks so requests and httpx reject those chains while normal HTTPS continues to work. Verified with real affected certificate chains and live HTTPS checks. Pip has a separate certificate bundle, which is being fixed in the RaspiBlitz installer.