keybase / keybase/keybase-issues
Private key proof fails using "hardcore" approach
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
On macOS (El Capitan) I copy-pasted the command line instructions given into Terminal, but it resulted in the following error:
You need a passphrase to unlock the secret key for
user: "..."
4096-bit RSA key, ID ..., created ...
gpg-agent[43177]: command get_passphrase failed: Inappropriate ioctl for device
gpg: problem with the agent: Inappropriate ioctl for device
gpg: skipped "e0060eee169fec9a0758c3f19c5c8c9751e47ba4": Operation cancelled
gpg: signing failed: Operation cancelled
Error in your post
I was able to use the Keybase application with no problem.
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 command-line instructions referenced in the issue and reproduce the signing attempt in macOS Terminal. Compare that path with the Keybase application, then identify why the passphrase prompt returns “Inappropriate ioctl for device”; done means private-key proof succeeds from the documented command line.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100