Repository navigation
Security: remediate eMudhra certificate trust - #134
Merged
Merged
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.
Refreshes OS CA packages and independently bundled pip/certifi stores in build and runtime image stages, and adds a TLS trust regression workflow. The dependency-free core remains unchanged. Full application tests are being checked; image/host rollout requires deployment inventory and positive/negative TLS validation.
Incident: https://emudhra.we-have-a-problem.com/
Roll out from patched administration tooling, canary legitimate upstream access, and verify affected-chain rejection in the actual running process. Rollback images must retain the patched trust layer.