keybase does not work nicely with gpg-agent for pgp select command (linux)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Following instructions to verify my key, and I'm told to do 'keybase pgp select hash' which prompts me for my PGP key passphrase.
I do not have a PGP key passphrase, it should be using gpg-agent to interface with my smartcard and pinentry, instead. Rather, the secret key is stripped and doesn't live on this machine, and instead there are signed subkeys that live on my smartcard.
I only have gpg2 installed (though there's a link so gpg works). I have gpg 2.1.11 and keybase client 1.0.17-20161025160021+77565f4
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 with the keybase pgp select _hash_ command path and inspect how it interacts with gpg2, gpg-agent, and pinentry; the issue names no source file or test. Reproduce with the stated gpg 2.1.11 and Keybase 1.0.17 setup using a smartcard-backed key, then confirm selection no longer requests a local PGP passphrase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100