search

keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
899 stars 37 forks source link

ERROR ImportKey error: GPG error: exit status 2 #2132

Open aleininger opened 8 years ago

aleininger commented 8 years ago

prompt ~ $ keybase login

prompt ~ $ keybase pgp select

\# Algo Key Id Created UserId

\= ==== ====== ======= ======

1 4096R CFB251E356B27251 my e-mail addresses associated with the key

Choose a key: 1

▶ ERROR ImportKey error: GPG error: exit status 2

Anyone got any idea what is going wrong here?

I have the most recent version of keybase.

arndt@arndt-ThinkPad-X1-Carbon ~ $ keybase version

Client: 1.0.14-1

Service: 1.0.14-1

I am running Linux Mint 17.3. and am using PGP successfully with Enigmail and Thunderbird.

pserrano commented 5 years ago

I have the same error in MacOSX, and now they haven't --no-import solution 

keybase pgp select --no-import
Incorrect Usage.

NAME:
   keybase pgp select - Select a key from GnuPG as your own and register the public half with Keybase

USAGE:
   keybase pgp select [command options] [key query]

DESCRIPTION:
   "keybase pgp select" looks at the local GnuPG keychain for all
   available secret keys. It then makes those keys available for use with keybase.
   The steps involved are: (1a) sign a signature chain link with the selected PGP
   key and the existing device key; (1b) push this signature and the public PGP
   key to the server; and if "--import" flag is passed: (2a) copy the PGP secret half
   into your local Keybase keyring; and (2b) encrypt this secret key with Keybase's
   local key security mechanism.

   By default, Keybase suggests only one PGP public key, but if you want to,
   you can supply the "--multi" flag to override this restriction. If you
   want your secret key imported into the local Keybase keyring, then use
   the "--import" flag. Importing your secret key to Keybase keyring makes
   it possible to use Keybase PGP commands like "pgp decrypt" or "pgp sign".

   If you don't want to publish signature chain link to Keybase servers, use
   "--no-publish" flag. It's only valid when both "--no-publish" and "--import"
   flags are used.

   This operation will never push your secret key, encrypted or otherwise,
   to the Keybase server.

OPTIONS:
   --multi  Allow multiple PGP keys.
   --import Import private key to the local Keybase keyring.
   --no-publish Only import to Keybase keyring, do not publish on user profile.

Error parsing command line arguments: flag provided but not defined: -no-import
maxtaco commented 5 years ago

This error just means that GPG failed. You might have misconfigured it in many many ways that we can't detect. You should check the logs and see what made it fail

keybase status tells you where the logs are.

garyemiller commented 5 years ago

"This error just means that GPG failed".

I use GPS hundreds of times a day. Not a GPS failure. I'm not gonna debug, I removed keybase due to the many issues.

zommuter commented 5 years ago

Sorry for not reading everything, but I thought I should mention I encountered this error on Git for Windows' Bash and could circumvent it using cmd instead. @maxtaco's comment about pinentry was helpful here 👍

zot24 commented 4 years ago

Just in case it worth for someone else in my particular case to make this work on Mac (Mojave) I had to do the following:

brew install gnupg pinentry-mac
add pinentry-program /usr/local/bin/pinentry-mac in ~/.gnupg/gpg-agent.conf
restart the laptop

After that I manage to introduce the require passphrase and push-export the needed keys to then pull-export in other device

The problem as mentioned before it's with your gpg configuration I'm not even sure if the version affects anything anymore I'm in gpg 2.2.18