Switch back to ssh-agent from gpg-agent with setting $SSH_ASKPASS which internally uses gpg#852
Merged
Switch back to ssh-agent from gpg-agent with setting $SSH_ASKPASS which internally uses gpg#852
$SSH_ASKPASS which internally uses gpg#852Conversation
This partially reverts GH-814 However ssh passphrase will be kept by the SSH_ASKPASS and gpg encrypted command
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.
goldwardenwithpassfor the secret/password manager #817 directionSince using gpg-agent, it does not remain and hard to handle SSH passphrase.
Instead of that, pass command internally uses gpg. It looks enough to me.