keybase / keybase/keybase-issues
keybase push of existing PGP key shouldn't make me@keybase.io primary
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
## Steps to Reproduce
- have an existing PGP key with an email (different than user@keybase.io), e.g. "user@example.dev"
- `keybase login`
- `keybase push`
- Choose _option (2)_, having keybase CLI add the email "keybase.io/user <user@keybase.io>"
- Observe that "user@example.dev" is no longer the primary email for the key; instead "user@keybase.io" is primary
Presumably `keybase push --add-email` has an equivalent result, but I didn't test that.
## Expected Behavior
The original primary email (user@example.dev) should remain as the primary email.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the issue with an existing PGP key, then run `keybase push` and choose option (2) while recording the original primary email. Check the equivalent `keybase push --add-email` path if relevant. Done means adding the keybase.io email without changing the existing primary email.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100