keybase / keybase/keybase-issues
Website verificative does not work when one of the 2 URLs return a 403
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
## steps to reproduce
- add the proof to /keybase.txt
- return HTTP status code 403 for a request to /.well-known/keybase.txt
## expected result
- verification is working
## actual result
- verification is not working
- the webserver logs a request to /.well-known/keybase.txt and returns a 403 error
- the webserver DOES NOT log a request to /keybase.txt
- after changing the webserver to return a 404 for /.well-known/\* ... it is working fine
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the verification flow with proof content at /keybase.txt while /.well-known/keybase.txt returns 403, then compare it with a 404 response. Inspect the verification entry point that requests these two URLs; done means verification succeeds and the webserver logs requests to both paths when either URL returns 403.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100