keybase / keybase/keybase-issues
Generating new web proof fails with "live proof exists" on 404
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I'd like to reinstate my web proof. But when I run keybase prove -f web http://paschmidt.de I get the following error:
error: A live proof for http://paschmidt.de already exists (error #230)
My webserver returns 404 or 403 for both possible URLs, respectively.
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 keybase prove -f web http://paschmidt.de and checking how the proof lookup handles the two possible URLs when they return 404 or 403. Done means a user can reinstate the web proof without the client incorrectly reporting that a live proof already exists.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100