Primary Key Expiring, how do I rotate?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
When I generated my current master PGP key (ChristopherA@LifeWithAlacrity.com FDFE14A54ECB30FC5D2274EFF8D36C91357405ED 4096-RSA) I set it to expire 2019-04-16. I'd like to start to proactively rotate to a new offline master key & use subkeys for GitHub, etc. It has many strong web-of-trust attestations associated with it, including from some bitcoin-core and other security professionals.
I can't find any advice in the Keybase FAQ on how to Keybase might facilitate this upcoming change, or best practices for generating new keys/subkeys for use with Keybase.
Any advice or tips?
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 with the Keybase FAQ and the issue's question about rotating an expiring offline master PGP key and using subkeys. Define the supported workflow and best practices for Keybase users, including how existing attestations are handled. Done means the FAQ or related documentation gives clear, actionable key-rotation guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100