keybase / keybase/client

can't make proof of HTTPS and DNS for the website verification

Open
#25,204 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
PR merge metrics
PR metrics pending

Description

Says unreachable for both pelagico.uz@https and pelagico.uz@dns
For some strange reasons, for https the link /keybase.txt apears as /keybasetxt

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing verification for pelagico.uz through both HTTPS and DNS, including the reported /keybase.txt to /keybasetxt change. Trace the website-verification entry point that processes these checks; done means both proofs are reachable and the HTTPS path remains /keybase.txt.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking, security, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.