Skip to content
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

No useable private keys found #960

Closed
sevenmaxis opened this issue Oct 15, 2018 · 6 comments
Closed

No useable private keys found #960

sevenmaxis opened this issue Oct 15, 2018 · 6 comments

Comments

@sevenmaxis
Copy link

sevenmaxis commented Oct 15, 2018

$ gpg -K
/home/megas/.gnupg/pubring.kbx
------------------------------
sec   rsa4096 2018-10-15 [SC] [expires: 2023-10-14]
      5A5E5D9XXXX4B5F93F01XXXX8CE297B6C1854
uid           [ unknown] MyName <email>
ssb   rsa4096 2018-10-15 [E] [expires: 2023-10-14]
$ gopass
It seems you are new to gopass. Do you want to run the onboarding wizard? [Y/n/q]: Y
[init] [local] Initializing your local store ...

Error: failed to run onboarding wizard: failed to init local store: failed to read user input: no useable private keys found

The gpg key was imported from another computer.

@martinhoefling
Copy link
Contributor

I suspect that the trust is not set correctly for the key. Trust levels full or ultimate should work afair.

@sevenmaxis
Copy link
Author

You're right, I changed the trust level to ultimate and gopass accepted this key

@Kraymer
Copy link

Kraymer commented Jun 24, 2019

Just had same problem, it fixed it.

Would be nice if the error message in the CLI pointed to that direction

@espoelstra
Copy link

For those arriving here and still running into this issue, maybe with a Keybase account and/or a Yubikey, if you have several public keys that have been uploaded to Keybase or another keyserver using the same email address but some of them have expired, if you do gpg --edit-key yourEmail@domain gpg>trust 5 (for ultimate) you are probably NOT editing the correct key. After you run gpg --card-edit gpg> fetch (if you have a Yubkey and uploaded to Keybase), you need to run gpg --list-secret-keys and using the portion after the 0x of the UNEXPIRED/currently valid key (sec# if using a Yubikey or in gpg --list-keys after the 0x in the pub line), then run gpg --edit-key 0123456789ABCDEF and run gpg> trust 5 on this specific key, and you shouldn't get the error anymore.

Oddly enough I was able to use the GPG key for SSH and Git cloning by just trusting the email address, but in order to get gopass to like it I had to specify the correct key and trust it specifically.

@stale
Copy link

stale bot commented Nov 4, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Nov 4, 2019
@stale stale bot closed this as completed Dec 4, 2019
@pmyjavec
Copy link

Just hit this issue. It's a very confusing error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants