Fix import GPG keys #267
Merged
Fix import GPG keys #267
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
Previously stdin was used for the gpg passphrase, but importing of the private key also happens on stdin. Now it uses a path to a file for the gpg passphrase, which leaves stdin available for the private key. Fixes: c71e787 ("Securely pass the password to GPG")
evgeni
approved these changes
Sep 6, 2023
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.
Previously stdin was used for the gpg passphrase, but importing of the private key also happens on stdin. Now it uses a path to a file for the gpg passphrase, which leaves stdin available for the private key.
Fixes: c71e787 ("Securely pass the password to GPG")