Repository navigation
feat: add reversible emergency trust repair for macOS and Linux - #3
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.
Adds embarass fix to turn confirmed exposure into an actionable emergency repair on macOS and supported Linux distributions.
Batch results now explain why some tools remain exposed after repair. Press d to explore per-tool trust sources, repair coverage, and remediation, or use --details for headless output. Guidance distinguishes system stores, bundled CA data, runtime updates, gcloud configuration, .NET native macOS trust, and container trust. Welcome, help, and exposed results include repair calls to action.
Also fixes a runner completion race that could miss final TLS observations and makes certificate-preservation tests independent of Windows checkout line endings.
Scope: repair covers the selected system store. Private application bundles, Keychain trust, and containers require separate remediation. Legitimate chains relying solely on the removed roots also lose trust.
Validation