keybase / keybase/keybase-issues

Device not registered on OS X after upgrade from 0.7.7

Open
#1,894 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

I just received an invite after waiting quite a while. I had installed an old version of the client through Homebrew (0.7.7) and successfully signed in through that client, which didn't appear to have device registration. I even successfully did a Twitter proof through that client.

Then I upgraded to 1.0.3-0 and things started to go wrong. I had to log in again, at which point I had to do the dance with signing the install with PGP, etc. I chose to use GPG commands to sign the installation, which seems to have caused the problem; after choosing the correct key, the following happened:

Choose a key: 3
Enter a public name for this device: Odin
▶ INFO gpg: cannot open `/dev/tty': Device not configured
▶ ERROR GPG error: exit status 2
Odin:~ oscar$ keybase login
Odin:~ oscar$ keybase prove github
Your username on Github: fraveydank
▶ ERROR No device found No device found for device ID 61e0bdd5750ea5fbd3bfd673f8da5d18

My guess is that the MacGPG passphrase dialog doesn't cooperate nicely with something that expects a terminal session. In any case, it seems that my device was never registered and if I list them:

Odin:~ oscar$ keybase device list
Name Type ID
========== ========== ==========

For obvious reasons, I can't generate a paperkey this way either. Any ideas on how I can rectify the situation?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the upgrade path from client version 0.7.7 to 1.0.3-0 on OS X, then run the GPG signing flow and the mentioned keybase login, keybase device list, and keybase prove github commands. Done means the device appears in keybase device list and GitHub proving no longer reports “No device found”; no source files or tests are identified in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, shell
Domain
authentication, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.