Keybase not using User-Agent to scan website proofs; being blocked
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
According to one of my website hosts, Keybase does not send a User-Agent id when re-scanning for domain identities. See the server log below:
--------------------------------------------------------
54.84.133.185 - - [25/Sep/2017:07:21:55 +0100] "GET /keybase.txt HTTP/1.1" 200 2941 "-" "keybase-proofs/2.1.17"
54.84.133.185 - - [25/Sep/2017:08:45:42 +0100] "GET / HTTP/1.1" 404 - "-" "-"
54.84.133.185 - - [25/Sep/2017:09:14:34 +0100] "GET / HTTP/1.1" 404 - "-" "-"
--------------------------------------------------------
As a result, this host - and possibly others - block the Keybase IP as potentially malicious. Should this be fixed?
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 locating the website-proof rescanning request that fetches domain identities, then compare its HTTP headers with the keybase.txt request shown in the server log. Done means rescans identify themselves with a User-Agent so hosts can distinguish Keybase traffic from potentially malicious requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100