client: Unable to use Keybase app on MacOS X Sierra 10.12.4

Had the same issue, and the same results when I ran keybase login on the command line, but my GPG version is 2.0.x. See Log ID cbd2c25d2b54c04cee67ca1c.

I’m just starting to use Keybase again, now that the iOS app exists. What specifically am I missing out on by not being able to import my GPG key into Keybase’s keychain? If I export my secret key using gpg -a --export-secret-key 0xdadadadadadadada, is there a way to import that into the Keybase app’s keychain by hand?

my log id: 21228ca8e82ca21cf22b1f1c

Ran into the same problem today. Had keybase on my computer in the past but reinstalled. Trying to login I get this in the GUI:

unknown error unknown incoming rpc 138 keybase.1.provisionui.switchtogpgsignok

On the command line it get what others are getting:

There was a problem importing your GPG secret key: GPG error: exit status 2

Using gpg (GnuPG) 2.1.21 on macOS.

I choose the fallback and still get:

Enter a public name for this device: MacBookPro ▶ ERROR GPG error: exit status 2

---

Update 1: I just installed the iOS app and got better error notes. It told me “Sorry, your account is already established with a PGP public key, but we can’t access the corresponding key.” My options are:

- Use keybase login on the command line to log in (not working)
- Go back and provision with another device or paper key (how?)
- Or, reset your account and start fresh (looks like this is my own option)

In my keybase.io account page it tells me:

You chose to manage your PGP private key yourself (nice!), and you don't have any Keybase devices yet. To prove your first install is really yours, you must use a computer (1) that has GPG installed, and (2) has access to your private key. Keybase will ask GPG to sign its first device key.

I definitely have GPG installed, step 1 complete. Not sure exactly what step 2 is saying. I have access to my private key. What else do I need to do? What command is keybase trying to run against GPG that is getting the exit status 2? Perhaps if I knew the command I could try running it manually.

---

Update 2: After a bit of mucking about in the keybase code I decided to try using gpg to sign something. This is what I saw:

$ gpg -s test.txt
gpg: signing failed: No pinentry

So I looked in the conf file:

$ cat ~/.gnupg/gpg-agent.conf
pinentry-program /usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac

I looked for the pinentry-mac program and it did not exist. So I did which pinentry and got /usr/local/bin/pinentry which I then put into the gpg-agent.conf file in place of the previous one.

Then I did a killall gpg-agent and ran keybase login again and it worked.

Conclusion: Apparently my GnuPG config was messed up.

@portante you can try keybase login on the command line, but I believe it will tell you the same thing that @maxtaco said: that it needs that key to provision.