Optionally filter key usage in frontend#14
Merged
Conversation
This was referenced Jul 14, 2026
Owner
Author
|
Supersedes #13. |
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.
alternative solution to #13 using optional frontend filtering when editing the encrypted key file. Filtering can be bypassed if needed by ticking the newly added checkbox "Ignore key usage restrictions (show all)". Key usage extension is ignored when selecting smart cards / certificates to decrypt the key file. Therefore any permitted cert / card can be used to decrypt the key file, independent of the key usage extension.
Should solve #12. @TickoSpy: please confirm.