keybase / keybase/keybase-issues
Bad remote_host given for a perfectly fine name
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
keybase prove https www.proper.com
You will be asked to post a file to:
/.well-known/keybase.txt
OR /keybase.txt
Proceed? [y/N] y
▶ ERROR Bad remote_host given (error 100)
keybase version
Client: 1.0.16
Service: 1.0.16
The same error happens for "http" and "web" as well.
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
Reproduce the issue with keybase prove https www.proper.com, then compare the behavior for http and web mentioned in the report. Trace the prove command's handling of remote_host; done means a valid name such as www.proper.com no longer produces error 100 and the proof flow proceeds to its documented prompt.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100