Connecting computer, verifying via DNS, verifying via Twitter, and keybase passphrase recover
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I installed Keybase on my Android phone, tried to verify with DNS. It showed UNREACHABLE. Perhaps I tried with WiFi and the ipconfig was incorrect, but then I attempted it via cell (by turning off WiFi) and it still didn't work. A web-based DNS check showed the correct TXT setting.
Then I installed Keybase on my Windows 7 VAIO computer and attempted to connect it to my mobile via QR code. I tried several times over a couple minutes to no avail, until I pressed "Type text code instead" at which point my computer appeared as a connected device on my mobile.
I then attempted to add my Twitter account via my mobile, but it appeared as unconnected. Oddly, on my computer it showed as connected. And my computer shows my DNS as connected! Cool! But my DNS connection status still shows UNREACHABLE on my mobile.
So I went to the website to report a bug. By this time I had forgotten my password. Ha! So I clicked "Recover account" and saw that I should enter "keybase passphrase recover" on my computer. Where on my computer? I guess the command line, which the majority of people are unaware of. So I entered the command and got the error: "'keybase' is not recognized as an internal or external command,
operable program or batch file."
Hopefully my debt is paid. ;)
Thanks for the work on making the world more secure. Good luck!
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 Android DNS verification and QR-code connection behavior, then compare the mobile and Windows account-status displays. Also check the Windows keybase passphrase recover entry point; done means the reported recovery command is discoverable or works as documented and the connection statuses are consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- cli, mobile, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100