-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble Finding GPG Key #107
Comments
Another thing to point out: if you are using the latest version of keychain, you can specify gpg2 with |
And my gpg keygrip needed to follow directly:
|
I'm having the same issue on my laptop, but I have the newest version of Keychain. Can't yet figure out if the problem is a bug or my config. Ubuntu 19.04 Command in my .zprofile is: I've tried This is the output of my key which I'm using to grab the key ID (from
|
The Keychain documentation on Funtoo wiki now has the relevant documentation on configuring the correct key ID format on e.g. Ubuntu 18.04 LTS: |
If problems getting |
To whom it may concert, try specifying |
hello @bmccary - if you'd like to report a bug kindly use https://bugs.funtoo.org/ you can also reach us on Discord - for more info check https://www.funtoo.org/Welcome |
Ubuntu 18.04 appears to use an unfortunate combination of keychain and GPG versions.
Specifically, keychain could not find my GPG keys and repeatedly responded:
Apparently, keychain 2.8.2 was written against a gpg version which printed stuff a little differently
than gpg 2.2.4. Looking through the git blame for the part of the keychain script which looks for GPG keys, this problem appears to have been fixed around keychain 2.8.4.
To be clear: this issue applies to a historic version of keychain still in widespread use, not the current version of keychain.
A workaround to get keychain 2.8.2 and gpg 2.2.4 to play nice is to add the following line to
~/.gnupg/gpg.conf
:In my view, the solution to this issue has two parts:
keyid-format
workaround.At least now a google search might lead to this issue.
The text was updated successfully, but these errors were encountered: