[Feature Request] Set a default PGP key, other than the most recent
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Just a quick request - is there any chance we could gain the ability to set a default PGP key, other than 'the most recent'?
At the moment to get this behaviour I have to:
keybase pgp export -s -q $KEYID | gpg --import
keybase pgp drop $KEYID
gpg --export-secret-key -a "$KEY_NAME" | keybase pgp import --push-secret
gpg --delete-secret-keys -a "$KEY_NAME"
Which amongst other things signs a statement that a key shouldn't be associated with my account and then re-associates it. Which is /hopefully/ acceptable, given Keybase's model, but is still somewhat sketchy. 👀
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 tracing the existing keybase pgp command handling and how it selects the most recent key. Define how a user-selected default should be stored and used, then verify that the supported key-management flow avoids the export, drop, and re-import workaround described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cryptography
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100