keybase / keybase/keybase-issues
Verification failing when no SSL certificate
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
on my keybase (linked to my Github) I have claimed a site via DNS. The DNS proof for that site is still there. However, Keybase is claiming it is not there because it is attempting to access the HTTPS version of the site. The site does not have an SSL certificate and therefore this will never exist. But that doesn't mean I don't own the site and that my proof is notcorrect. The system should be checking both versions to verify the proof and not simply rejecting if one of them fails. Especially if that one uses extra components that do not actually define ownership.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the site-claim DNS proof verification flow and how it handles HTTP versus HTTPS requests. The fix is done when a valid DNS proof is accepted for a site without an SSL certificate, rather than being rejected solely because the HTTPS check fails.
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