-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
67108933 Not implemented <GPG Agent> #146
Comments
Looking at the log and the related code it seems it fails retrieving the keygrip. https://github.com/crazy-max/ghaction-import-gpg/blob/master/src/main.ts#L77 In the logs you will see there is no keygrip printed, meaning https://github.com/crazy-max/ghaction-import-gpg/blob/master/src/main.ts#L76 probably failed getting the keygrip. |
I finally figured it out. I was using the subkey id as opposed to the subkey fingerprint. Now I'm using the subkey fingerprint all works perfect. I figured it out when reading this code. ghaction-import-gpg/src/gpg.ts Lines 184 to 193 in c8bb57c
Probably would be good to document how to get the I did this via following command. gpg --batch --with-colons --with-keygrip --list-secret-keys | awk -F: "/^fpr:.*AE0B37D819AFABE6:/ { print $10 }" The keyid |
I am running into the same issue but adding the full fingerprint still does not make it work. You can get the fingerprint of subkeys like that: gpg -K --with-subkey-fingerprint <[email protected]> |
Behaviour
Steps to reproduce this issue
gpg --armor --export-secret-keys KEYID | pbcopy
In this workflow I am selecting the RSA subkey for signing.
Expected behaviour
The key should successfully load into the gpg-agent.
Actual behaviour
Running this workflow fails with following log
Configuration
Logs
See attached build URL.
The text was updated successfully, but these errors were encountered: