web-based proof started failing
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 https://keybase.io/ennorehling and my web-based proof for https://wiki.eressea.de/ has started failing. The keybase.txt file is in place, and has not changed. I can fetch the file, and get no certificate warnings:
$ wget https://wiki.eressea.de/keybase.txt
--2017-07-12 09:03:11-- https://wiki.eressea.de/keybase.txt
Resolving wiki.eressea.de (wiki.eressea.de)... 185.91.65.54
Connecting to wiki.eressea.de (wiki.eressea.de)|185.91.65.54|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2906 (2.8K) [text/plain]
Saving to: ‘keybase.txt’
keybase.txt 100%[=====================>] 2.84K --.-KB/s in 0.002s
2017-07-12 09:03:11 (1.67 MB/s) - ‘keybase.txt’ saved [2906/2906]
and yet, every time I tell keybase to retry my proof, it sends me an email saying that it broke. Would it be too hard to include some more info to help troubleshoot this?
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 with the Keybase proof retry flow and the provided https://wiki.eressea.de/keybase.txt URL, reproducing the failure described in the issue. Compare the successful fetch with the verification result and make the failure information identify the cause; no source file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100