keybase / keybase/keybase-issues
Adding gpg public key fails with TypeError
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I just got an invite tonight, and I am trying to setup my Keybase account. I already have a 4096-bit cert generated and stubs stored on a Yubikey NEO.
When adding my private key either stored in the web-browser or using the command line (I tried both ways) I get the following:
TypeError: ("unknown s2k gnu protection mode: " + gnu_ext_type) is not a constructor
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
Reproduce the failure when adding the private key through the web browser and command line, using the reported Yubikey setup. Start with the TypeError about the unknown GNU protection mode; done means the key can be added successfully through the affected path.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100