Try running gpg when secret key not available?
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 subkeys stored on a smartcard for use with gpg -- this works wonderfully for me. I tried using the keybase client for the first time today and found that, after configuring keybase to use the correct executable, gpg is called and works great for login.
My problem? If I try to use keybase as a helper, i.e. keybase pgp sign <x>, I receive an error indicating that no secret key is available. It would be really nice if, at least upon encountering that error, keybase would attempt to perform the action by calling gpg for me.
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 keybase pgp sign <x> with secret subkeys available only on a smartcard, using the configured GPG executable. Trace the existing PGP signing path and its handling of the no-secret-key error. Done means the command falls back to GPG for this case without breaking normal Keybase signing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100