Cannot import existing GPG4Win PGP cert
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
When trying to import my existing PGP keys, I received an error the key pair was missing an MBS something... I didn't get to take a screen cap of the message. The key pair was created using GPG4Win and then exported in .gpg format. I had to create a new key pair within the Keybase app, which worked fine, but I would love to be able to sign messages with my existing key pair.
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 reproducing the import of the GPG4Win-exported .gpg key in the Keybase app and capture the reported error. Compare the failing existing-key import with the working key-pair creation flow. Done means an existing GPG4Win key pair can be imported and used to sign messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100