Repository navigation
feat: detect staged OpenSSH Ed25519 keys in Rust safety preview - #5
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
1 participant
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.
The Rust pre-commit preview previously checked sensitive paths and verified Git object bytes but did not inspect content. It now reports a structurally complete unencrypted OpenSSH Ed25519 private key from the verified staged blob, including managed .codeguard records, without reading worktree replacements or exposing key bytes. The preview remains exit 3/incomplete/not_evaluated; schema 0.3.0 adds the rule ID and preserves 0.2.0. Local core 2/2 and Git/CLI 15/15 passed; a real ssh-keygen sample exposed and then verified the zero-padding fix. Full workspace local testing was interrupted before disk exhaustion and is left to CI.