agent: Allow password-caching in pinentry #11
Merged
Conversation
This file contains 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
stigtsp
temporarily deployed
to
Build, sign, release binaries
GitHub Actions
Inactive
stigtsp
temporarily deployed
to
Build, sign, release binaries
GitHub Actions
Inactive
stigtsp
temporarily deployed
to
Build, sign, release binaries
GitHub Actions
Inactive
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.
Note: This PR might need some more work
This allows pinentry-gtk2 (and maybe other pinentries) to cache PIN using libsecret/gnome-keychain
OPTION allow-external-password-cacheSETINFOto"ssh-tpm-agent/" + sha256(publicKey)(this should prob be something else)One problem is that cached passwords names are prefixed with "GnuPG: ", not yet figured out how to fix that.