Repository navigation
Validate persisted proxy certificate caches before reuse - #23
Closed
Bikebrainz wants to merge 2 commits into
Closed
Bikebrainz wants to merge 2 commits into
Bikebrainz wants to merge 2 commits 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.
Included in merged #22, which adds the final DNS/IP SAN checks and passed all eight CI jobs on its reviewed integration head. This draft is closed as superseded; no separate merge is needed.
Persisted proxy leaves were reused when their subject and dates looked valid even if the CA had changed or the private key no longer matched. That left HTTPS interception failing after restart.
Disk-cache reuse now verifies the certificate against the current CA and compares its public key with the private key's public component. Damaged keys, invalid signatures and stale issuers trigger regeneration. Valid cached leaves remain unchanged. Checks run once per host on disk load; later connections use the in-memory cache.
The public changelog, developer changelog and certificate-cache roadmap entry describe the recovery behavior and remaining limits. Live CA replacement and cache-management controls remain unfinished.
Validation:
This builds on #21. Cross-platform CI is required before merge.