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

[portante]

I installed the new app from today, and was unable to sign in from the app. Password works on the web site. The error shown is "Unknown RPC Error".

Keybase GUI Version: 1.0.22-20170502110012+a3c4856
my log id: 206e71c1b929e598be63811c

[maxtaco]

@chrisnojima / @patrickxb , seems like an issue we saw yesterday, with the root cause being:

73823 2017-05-13T08:32:47.881434-04:00 ▶ [DEBU keybase engine.go:67] 371 - RunEngine(loginProvision) -> ERROR: No private GPG keys found on this device that match account PGP keys E76C 2560 32D5 311D 5E68 BCD4 213D 5E2F BA81 C413

Which isn't propagated to the UI, and the unknown RPC error having to do with FSSyncStatus

[maxtaco]

@portante do you have GPG access to the secret key for E76C 2560 32D5 311D 5E68 BCD4 213D 5E2F BA81 C413? It's needed to provision.

[patrickxb]

@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.

[portante]

Thanks folks, I ended up finding my pgp key on another computer, so I was able to complete this.

However, using the UI, I now see, "Unhandled incoming RPC 138 keybase.1.provisionUi.switchToGPGSignOk" asking me for a passphrase. I enter my valid passphrase and nothing else happens in the UI.

[portante]

I restarted the app, and now I see a similar message, but it says "RPC 135"...

[maxtaco]

Wow this path through the electron UI sounds really broken. I would stick
to the CLI until we fix it.

On Sat, May 13, 2017 at 12:24 PM Peter Portante [e-mail]
wrote:

I restarted the app, and now I see a similar message, but it says "RPC
135"...

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/6986#issuecomment-301258607,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05_yfAuS-GkI_aQXxq3tkNjw8EIJ7Oks5r5dkwgaJpZM4NaDxQ
.

[portante]

Okay, I'll try that then.

[portante]

Well, not much better, @maxtaco :

$ keybase login
Your keybase username or email address: [email protected]
In order to authorize this installation, keybase needs to sign this installation
with your GPG secret key XXXXXX...XXXXXX.

You have two options.

(1) Keybase can use GPG commands to sign the installation.

(2) Keybase can export your secret key from GPG and save it to keybase's local encrypted
    keyring. This way, it can be used in 'keybase pgp sign' and 'keybase pgp decrypt'
    going forward.
Which do you prefer?: 2

There was a problem importing your GPG secret key XXXXXX...XXXXXX.

    GPG error: exit status 2

Would you like to try using GPG commands to sign this installation instead? [Y/n]

Thanks for the help, though.

[maxtaco]

Can you do keybase log send? There is likely a misconfiguration with your
gpg, something like a permission problem. Sadly it happens all the time

On Sat, May 13, 2017 at 12:32 PM Peter Portante [e-mail]
wrote:

Well, not much better, @maxtaco https://github.com/maxtaco :

$ keybase login
Your keybase username or email address: [email protected]
In order to authorize this installation, keybase needs to sign this installation
with your GPG secret key XXXXXX...XXXXXX.

You have two options.

(1) Keybase can use GPG commands to sign the installation.

(2) Keybase can export your secret key from GPG and save it to keybase's local encrypted
keyring. This way, it can be used in 'keybase pgp sign' and 'keybase pgp decrypt'
going forward.
Which do you prefer?: 2

There was a problem importing your GPG secret key XXXXXX...XXXXXX.

GPG error: exit status 2

Would you like to try using GPG commands to sign this installation instead? [Y/n]

Thanks for the help, though.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/6986#issuecomment-301259110,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05_7rf8VWt0LEIUnrGJxHD7VSxygXgks5r5ds5gaJpZM4NaDxQ
.

[portante]

sure, id: 10adc69c40e88119a69e491c

[maxtaco]

Ok, looks like it works. Your version of GPG (2.1.x) is hostile to exporting secret keys, so that's why tactic #2 failed. But it fell back to tactic #1 which worked.

[portante]

So the fall-back was my choosing #1, but it would be nice to give more helpful error messages.

[maxtaco]

Cool, agreed, thanks for your help

[kg4zow]

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?

[SunSparc]

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.

[smsaladi]

I got this error but was able to resolve it by running keybase login from the command line. I think it may have to do with the fact that my pgp key requires a passphrase.

[davidxia]

Not sure if this is the same error. I tried to provision a new Macbook with a fresh install of the Keybase native app. I logged in with my username and password but eventually got the error Unknown incoming RPC 143 keybase.1.provisionUi.switchToGPGSignOK.

Mac OS X HIgh Sierra 10.13.4 (17E202
Keybase Version 1.0.47-20180410052738+f705a9510f (1.0.47-20180410052738+f705a9510f)

[maxtaco]

Different bug @davidxia. But while you're here, can you keybase log send?

[davidxia]

@maxtaco Done. log ID d947cefc61c755e06309e21c. Do you want me to open a new issue or update an existing one?

[hraban]

For people encountering the "GPG error: exit status 2" error on Mac, it might be because your key is password protected. Try this:

gpg --sign --output - -a <(echo foo)

It will cache the key password for a brief moment. You'll see that if you try it again immediately, it won't ask for your passphrase.

Now quickly try the keybase login command from the command line, and see if that helps.