GPG decrypt/sign does not play well with OpenPGP cards
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I have all my keys generated on Yubikey or GnuPG cards. I was able to import the public key using "keybase pgp select", but it seems like keybase really wants the private key for any real operations.
:~ $ keybase pgp sign
asdfasdfasdfasdf
▶ ERROR Bad key found: no private key material or GPGKey
I can run the content through gpg itself though. It seems like keybase has control of it's own pgp keystore, and doesn't really support cards.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported keybase pgp select and keybase pgp sign behavior, then trace how the client handles imported public keys and private-key operations. Compare the failing Keybase path with the working GnuPG path. Done means card-backed keys can be used for the reported signing and decryption operations without importing private key material.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100