keybase / keybase/keybase-issues
failing proof w/o explanation && https chained certs
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I saw that my proof for hexmode.com was failing, but the web wouldn't tell me why. After telling keybase.io to retry a couple of times, I gave up and revoked it.
I tried to prove it again, but got nowhere. This time, though, I was given a message:
$ keybase prove https hexmode.com
ERROR Failed to find a connection to hexmode.com: [https: Error: unable to verify the first certificate]
[http: Error: unable to verify the first certificate] (error 229)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported command, `keybase prove https hexmode.com`, and inspect how the proof failure is reported for the chained-certificate error. Done means the client provides an explanation for the failed proof and handles the reported HTTPS certificate case consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100