"openpgp: invalid argument no valid signing keys" when logging in
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I am running Keybase GUI Version 1.0.28-20170815141344+c36e316 on Windows 10.
Trying to log in through the GUI gives this error after naming my computer:
There was an error provisioning
Unknown error: openpgp: invalid argument no valid signing keys
Here are some logs from keybase -d login:
2017-08-31T21:18:34.303635-07:00 - [DEBU keybase log.go:30] 1a6 | Failure in SignJson()
2017-08-31T21:18:34.303635-07:00 - [DEBU keybase log.go:30] 1a7 - Delegator.Run() -> ERROR: openpgp: invalid argument: no valid signing keys
2017-08-31T21:18:34.304134-07:00 - [DEBU keybase log.go:30] 1a8 - RunEngine(DeviceWrap) -> ERROR: openpgp: invalid argument: no valid signing keys
2017-08-31T21:18:34.304635-07:00 - [DEBU keybase log.go:30] 1a9 * LoginState login request complete: loginReq loginWithPromptHelper [VMAJI5j8]
2017-08-31T21:18:34.304635-07:00 - [DEBU keybase log.go:30] 1aa - loginHandle done: loginReq loginWithPromptHelper [VMAJI5j8] (1m14.8786472s) [ERROR: openpgp: invalid argument: no valid signing keys]
2017-08-31T21:18:34.305135-07:00 - [DEBU keybase log.go:30] 1ab - LoginWithPrompt -> ERROR: openpgp: invalid argument: no valid signing keys
2017-08-31T21:18:34.305635-07:00 - [DEBU keybase log.go:30] 1ac an error occurred during provisioning, logging out
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 Windows 10 login failure with keybase -d login and trace the provisioning path from SignJson() through Delegator.Run() and DeviceWrap. Use the reported openpgp: invalid argument: no valid signing keys message to locate the relevant login and signing code; done means GUI provisioning completes without this error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100