Note GPG bug when creating NIST auth/sign subkeys #45
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
Users who wish to create NIST auth or sign subkeys using the
`--quick-add-key` command are likely to trip over a long-standing GPG
bug¹ which results in the following error:
$ gpg --expert --quick-add-key [fpr] nistp256 sign
gpg: Key generation failed: Wrong key usage
gpg: Key not changed so no update needed.
Help readers by noting the documented workaround. The GPG bug has been
open since July 2018. Unfortunately, it seems unlikely to be fixed
anytime soon.
¹ https://dev.gnupg.org/T4052
Signed-off-by: Todd Zullinger <tmz@pobox.com>
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.
Users who wish to create NIST auth or sign subkeys using the
--quick-add-keycommand are likely to trip over a long-standing GPG bug¹ which results in the following error:Help readers by noting the documented workaround. The GPG bug has been open since July 2018. Unfortunately, it seems unlikely to be fixed anytime soon.
¹ https://dev.gnupg.org/T4052
Signed-off-by: Todd Zullinger tmz@pobox.com