Can't import with multiple identities

blackxored commented 8 years ago

I can't import my key, it has multiple identities on it, which I can only make a guess could be related to the issue since generating a key works.

Here's the output of both keys (first is existing, second is generated by keybase):

/Users/blackxored/.gnupg/secring.gpg
------------------------------------
sec   4096R/D6421CDC 2014-11-08 [expires: 2017-11-09]
uid                  Adrian Perez <adrianperez.deb@gmail.com>
uid                  Adrian Perez <adrian@adrianperez.org>
uid                  Adrian Perez <blackxored@debian.org>
uid                  Adrian Perez <adrianperez-deb@ubuntu.com>
uid                  Adrian Perez <adrian@elasticdev.io>
ssb   4096R/F21D093B 2014-11-08

sec   4096R/85A6E344 2016-04-12 [expires: 2032-04-08]
uid                  Adrian Perez <adrian@adrianperez.org>
ssb   4096R/51E79A8D 2016-04-12

EDIT: the error, can't believe I forgot: ERROR openpgp: invalid data: entity without any identities

maxtaco commented 8 years ago

The feature you described works, you're likely hitting a different bug. Can you send logs or error messages?

blackxored commented 8 years ago

@maxtaco Thanks for the quick reply, I was editing the post just now.

blackxored commented 8 years ago

If it helps, I recently changed my expiry date but I don't think it'd be related.

maxtaco commented 8 years ago

Have you tried keybase pgp update?

blackxored commented 8 years ago

I did just now, it (re)uploaded the generated key, but I can't still select my existing key: same error.

Best Regards,

Adrian Perez http://adrianperez.org

On April 12, 2016 at 6:32:27 PM, Maxwell Krohn (notifications@github.com) wrote:

Have you tried keybase pgp update?

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub

maxtaco commented 8 years ago

Oh, these are two different PGP keys.

If you want to associate the second with your account, then run:

keybase pgp select --multi

Or if you don't want to import the corresponding secret key into your local keybase keyring, then:

keybase pgp select --multi --no-import

blackxored commented 8 years ago

Yes I've been using --multi while trying to import in all subsequent attempts. Still no luck.

maxtaco commented 8 years ago

I'm in the dark without a debug log or a dump of error traces or both. keybase log send is one possibility

blackxored commented 8 years ago

It gave me a warning, let me know if it uploaded successfully.

Log ID: 087fa0c83a6ba59a1720411c

Edit: gpg -v

blackxored@adrian-mbp ~ $ gpg --version                                                                                                                      [ruby:2.3.0][🐳 :native]
gpg (GnuPG/MacGPG2) 2.0.28
libgcrypt 1.6.3
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA, RSA, ELG, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

maxtaco commented 8 years ago

Thanks, it's, as usual, a limitation of the Go OpenPGP libraries:

ImportKey error: openpgp: invalid data: entity without any identities

Can you try with the --no-import flag? Does that still fail?

Can you do a gpg --export -a a598a2cc77e92d7cabb529fc7e1c9515d6421cdc, which exports your public key, and then, if you don't mind, post your public key here?

Thanks!

blackxored commented 8 years ago

Nope, --no-import also fails, I tried:

keybase gpg --multi --no-import

and after selecting that key, fails.

Pubkey:

maxtaco commented 8 years ago

Ok, yeah, there's likely something slightly weird about your key that the OpenPGP libraries in Go can't handle. We'll have to put in a fix, but I can't promise when we'd get to it. It seems like there's a UID in your Key that doesn't have any associated signatures. The code is just conservatively bailing out but it ought to ignore that UID and keep going (as gpg no doubt does). We've hit about half-dozen of these cases so far, but they keep coming in....

blackxored commented 8 years ago

How can I verify/workaround this? All my UIDs seem fine 😕

blackxored commented 8 years ago

I've regenerated all of my user IDs and apparently I was able to import it successfully.

maxtaco commented 8 years ago

it was some weirdness in your key that gpg was papering over....

blackxored commented 8 years ago

Well, after a small hickup with "no secret key" error which I solved by --only-import I've been able to go through the examples and verify that at least signing, encryption/decryption towards my user work.

Thanks so much for being so responsive and helpful!

I've made backup of my original key, in case you need it when you decide to tackle the root cause of this. Although you already have the public key, I thought it wouldn't hurt. Thanks again.

maxtaco commented 8 years ago

Thank you! We have an ticket in our JIRA open.

jeffreycentex commented 8 years ago

I have the same issue. I can't import my existing keys into Keybase - i get the "entity without any identity" error. I generated the keys with the Chocolately version of gpg.

gpg (GnuPG) 1.4.20 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg Supported algorithms: Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compression: Uncompressed, ZIP, ZLIB, BZIP2

Public Key: https://pgp.mit.edu/pks/lookup?op=get&search=0x15454A618557A9AB

zQueal commented 8 years ago

@jeffreycentex #2047 seems to be related.

zapu commented 7 years ago

@jeffreycentex would you mind trying this again? I checked your key against our PGP library and it seems to be parsed fine now.

keybase / keybase-issues

Can't import with multiple identities #2202