[web] cannot proof http nor https altough keybase.txt is there
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Following up on your web (stefan.stoelzle.me) proof has failed.
The proof is available via https://stefan.stoelzle.me/keybase.txt, but keybase doesn't seem to be able to reach it. It will also not work for http://stefan.stoelzle.me
The URL is hosted via GitHub Pages and the repo is https://github.com/stoe/stefan.stoelzle.me, there is nothing else there but the keybase.txtfile, a google site verification file and the README.
Any ideas what I can do?
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's access to both the HTTP and HTTPS URLs, using the linked GitHub Pages repository and its keybase.txt file as the fixture. Trace the web-proof verification entry point to determine why the proof is unreachable; done means the hosted keybase.txt proof is fetched and accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100