keybase / keybase/keybase-issues
Old HTTP proof still broken after available again after downtime
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
My HTTP proofs for 2 domains are broken since the server was offline for a short time. The proofs broke then but didn't went back up after they were available again (with a code 200 response, so no invalid redirection either). My guess it's because the key has been revoked since, but I'm hesitating to just replace the proof since I would loose the time and date of the original proof as well. And the proof should still be valid since it was created when the old key was valid.
Keybase Account: link
Broken proof 1: link
Broken proof 2: link
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 proof status for the linked Keybase account and the two keybase.txt URLs after the reported downtime. Check how the existing proof records handle a revoked key and confirm whether the original proof date can be retained; done means both proofs validate again without requiring replacement.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100