keybase / keybase/keybase-issues
Support for transition phase to new key
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
This is a special case of #178
When I signed up to keybase I did so with my rather old 1024-key. Now I created a new key according to https://www.apache.org/dev/key-transition.html
I'd like to now make the new key my default key on keybase.io with a minimum of fuzz (loose people tracking me, have to reverify my accounts). If possible have both keys for the transition phase
It'd be nice if that use-case was at least described in some way. I'm not sure for instance if revoke/push is what I want (whether it revokes my old GPG-key generally. Which I don't want to do for the transition phase)
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 reading issue #178 and the Apache key-transition guidance linked in the report. Determine whether Keybase can support both the old and new keys during transition, and clarify the expected behavior of revoke/push; done would require an agreed implementation scope and documented user workflow.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100