Keybase upload secret key after generation.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Hi,
Although I understand the security concerns with doing this I would still like to know if it is possible. I have a previously generated gpg key and should not need to regenerate in order to use in browser decryption.
Perhaps I have missed something and if that is so, just provide me with a link or instructions in order to accomplish this.
Thanks,
Chris
my log id: 36dfd1f6175f9b65bb58e31c
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 reviewing the existing browser decryption flow and how it handles a previously generated GPG secret key. Determine whether importing or uploading that key is supported without regeneration. Done means providing documented instructions for a supported path, or clearly documenting that the requested workflow is not possible.
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