should not ask for passphrase with GnuPG 2 or above
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Keybase GUI Version: 1.0.18-20170103235713+b2b347b
"keybase pgp select" assumes that it can pass the passphrase for the OpenPGP key to gpg. As of GnuPG 2, this is no longer the case. This results in a confusing second request for a passphrase. Moreover, when using a smartcard-based PGP key, there is no passphrase (instead, there is a PIN code), increasing the confusion.
Because of the above, at first I thought I wouldn't be able to assign my key to keybase, but this is obviously wrong.
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 at the keybase pgp select entry point and inspect how it handles GnuPG 2 or later, including smartcard-based keys. Done means selecting a key no longer causes a confusing second passphrase request, while PIN-based smartcard use remains clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cryptography
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100