Cannot prove public key is mine: keybase and curl return errors
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
$ keybase pgp select 767625c8354a5f6d2174b70e5843b2a5444674e3
▶ INFO Forking background server with pid=6708
▶ ERROR Login required
If I paste the curl command to the terminal, even substituting the gpg by gpg2, as the key was issued with gpg2 it returns an error.
I've also pasted the curl command to a file, just added the shebang, substituted curl by /usr/bin/curl, gpg by /usr/bin/gpg2 and the script returns the same error as the terminal's command.
$ ./keybase.io
gpg: assinatura falhou: Inappropriate ioctl for device
gpg: signing failed: Inappropriate ioctl for device
Error in your post
-------------------
Code: 218
Name: GENERIC
Description: neither pgp nor kb sig: (Error: Error parsing PGP data: no tailer found, Error: bad base 64 string)
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 keybase pgp select command and the curl-generated signing script, including the reported GPG errors. Trace the CLI entry points for PGP signing and request submission; done means the public-key proof succeeds without the login, ioctl, or signature parsing errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, shell
- Domain
- cli, cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100