keybase / keybase/keybase-issues

adding key twice gives error "You need to delete your active key before uploading a new one"

Open
#982 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

Repo:
- click 'a mystery user with no key'
- select to add my own public key
- do not encrypt private key
- cancel before validating public key
- click 'a mystery user with no key' (2nd time)
- select to generate key, follow steps to generate the key
- select 'done post to keybase'
- see error message and attached image:

ERROR {"status":{"code":908,"desc":"You need to delete your active key before uploading a new one","name":"KEY_NEED_REVOKE"},"csrf_token":"lgHZIDdkYTA0YzdiNWY3YWVlOGJhZDNlYjhkZGQ2MzRkNzAwzlP9wDLOAAFRgMDEIKX2nJWs00qTf3feJ4Irr+8SVPs5IESoprMUmJQUJJO5"}

Suggested fix: if home screen refreshes to remove the 'a mystery user with no key' button after key is created (but not verified) this error will not be hit.

![keybase_error](https://cloud.githubusercontent.com/assets/1126871/4059099/167e5860-2de0-11e4-9fa4-8288807b43b9.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the listed key-generation flow, including canceling public-key validation and then generating a key. Start by tracing the home-screen state after key creation but before verification; done means the “a mystery user with no key” action no longer leads to the KEY_NEED_REVOKE error.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.