keybase / keybase/keybase-issues
My PGP key is being rejected?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I have a pre-existing PGP key at: http://virgil.gr/wp-content/uploads/2014/04/PGP.asc
But when I copy/paste the key it is rejected, the error message is:
http://dl.dropbox.com/u/3308162/Screen%20Shot%202015-07-29%20at%2016.33.42.png
However, when I go through the keybase-provided command-line PGP steps everything works fine. It is unclear to me what the hangup here is. For what it's worth the key above was generated by Mailvelope. I would prefer not to create a new PGP key as I'd have to update all of my colleagues using my current one.
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 linked rejection screenshot and the PGP.asc key, then compare the failing paste flow with the keybase-provided command-line PGP steps. Done means identifying why the Mailvelope-generated key is rejected and confirming whether the existing key can be accepted without requiring a replacement.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100