keybase / keybase/keybase-issues
"your web proof just broke" is too vague
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I've got alert that my "proof just broke", but keybase isn't telling me what exactly is broken about it.
It'd be good if you could specify exactly where the proof failed for you.
- Do you have trouble validating the certificate? Do you not support my server's cyphersuites or TLS version? Do you not support SNI? (I've recently changed SHA-1 cert to SHA-256 cert.)
- Are you getting 404?
- Maybe my server has firewalled your host?
- Maybe you can download it, but the content is wrong?
It looks fine to me: https://pornel.net/.well-known/keybase.txt so information that it's "just broke" is not enough for me to fix the issue.
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 validation of https://pornel.net/.well-known/keybase.txt and compare the possible failure points listed in the issue: certificate or TLS/SNI support, HTTP status, connectivity, and downloaded content. Done means the “proof just broke” alert identifies the specific validation failure clearly enough for the reporter to act.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100