gpg2 --version Wed Apr 6 12:25:33 2016
gpg (GnuPG) 2.1.11
libgcrypt 1.6.5
Copyright (C) 2016 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, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2`
keybase login Wed Apr 6 12:19:53 2016
How would you like to sign this install of Keybase?
(1) Use an existing device
(2) Use a paper key
(3) Use my Keybase passphrase
(4) Use GPG
Choose a signing option: 4
In order to authorize this installation, keybase needs to sign this installation
with your GPG secret key.
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?: 1
# Algo Key Id Created UserId
= ==== ====== ======= ======
1 E BLABLABLA 2016-04-06 snipped <snipped>
Choose a key: 1
▶ NOTICE Failed to parse public key at position 3
▶ ERROR Bad key family: No key found for 011377353389862d5fa72ec530de170f078c39d6f295c27ff7b67d08137efda629ec0a
I thought it was probably related to my gpg version, so tried to login directly:
keybase login Wed Apr 6 12:27:34 2016
How would you like to sign this install of Keybase?
(1) Use an existing device
(2) Use a paper key
(3) Use my Keybase passphrase
(4) Use GPG
Choose a signing option: 3
Your keybase username or email address: qzhou
▶ NOTICE Failed to parse public key at position 3
▶ ERROR Bad key family: No key found for 011377353389862d5fa72ec530de170f078c39d6f295c27ff7b67d08137efda629ec0a
I thought it might be related to issue#1984, but it seems to be fixed.
I tried to login with gpg first, but failed:
I thought it was probably related to my gpg version, so tried to login directly:
I thought it might be related to issue#1984, but it seems to be fixed.
here's debug output for login: