search

keybase / keybase-issues

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

utility cannot find the corresponding private key on this machine #2638

Open janmyszkier opened 7 years ago

janmyszkier commented 7 years ago

OS: Ubuntu 16.04 LTS keybase version 1.0.17-20161024194756+4dcf351

Getting this after keybase login

▶ ERROR Sorry, your account is already established with a PGP public key, but this
utility cannot find the corresponding private key on this machine.
This is the fingerprint of the PGP key in your account:

`#### #### #### #### #### #### #### #### 9FD7 C2C1`

You need to prove you're you. We suggest one of the following:

   - put one of the PGP private keys listed above on this machine and try again
   - reset your account and start fresh: https://keybase.io/#account-reset

but gpg --list-secret-keys yields

sec   4096R/9FD7C2C1 2015-10-08 [expires: 2025-10-05]
uid                  keybase.io/jamysz <jamysz@keybase.io>

How do I point keybase to my keys?

patrickxb commented 7 years ago

Hi, could you please do two things to help us figure out what is going on:

  1. paste the result of gpg -K --with-colons --fingerprint here.
  2. do keybase log send after your failed keybase login and tell us the log ID.

Thanks!

janmyszkier commented 7 years ago

@patrickxb sure Ad1. 

sec::4096:1:DBFD714D9FD7C2C1:2015-10-08:2025-10-05:::keybase.io/jamysz <jamysz@keybase.io>:::
fpr:::::::::414190EAFDA54F5A580D5578DBFD714D9FD7C2C1:
uid:::::::EA9EEB7C4B818848B7D3787EB2EDC20AAEEB6A8C::Jan Myszkier <MY_PRIVATE_EMAIL>:
ssb::4096:1:7A0B617393B27BB6:2015-10-08:::::::

Ad2. Situation changed a bit because I logged in on my old computer, and was able to keybase login from there, now I don't get the same error on the laptop I was having issues on but I get options to provision my device using various options. So most likely keybase log send won't send you the same thing that was there before. HOWEVER I did use the command to send the logs, since it said "recent keybase log entries" so I hope it also contains the ones from yesterday my log id: b1c5d2e3e04b6c4b7b79361c

the issue still stands, because no document defines how to handle add gpg keys to keybase on ubuntu for it to recognize them

alexanderkjeldaas commented 7 years ago

I have the same issue. The problem is that the key has timed out.

Resetting the account because the associated GPG key timed out seems a bit excessive.

sec::2048:17:E016A1B3DCC64FB6:2015-05-27:2016-05-26:::Alexander Kjeldaas (1 year key) <removed@email.address>:::
fpr:::::::::DEA0883091E1EF1989FFF56DE016A1B3DCC64FB6:
ssb::2048:16:A1CE461EFBF8EB4A:2015-05-27:::::::

log id: b24140ed9fd7587ed2d6121c

alexanderkjeldaas commented 7 years ago 

▶ WARNING Error running Bug 3964 repairman: lksec load: no device id set, thus can't fetch server half
▶ WARNING In Bug 3964 repair: lksec load: no device id set, thus can't fetch server half
▶ WARNING Skipping expired primary key DEA0 8830 91E1 EF19 89FF F56D E016 A1B3 DCC6 4FB6
▶ ERROR Sorry, your account is already established with a PGP public key, but this
utility cannot find the corresponding private key on this machine.
This is the fingerprint of the PGP key in your account:

   DEA0 8830 91E1 EF19 89FF F56D E016 A1B3 DCC6 4FB6

You need to prove you're you. We suggest one of the following:

   - put one of the PGP private keys listed above on this machine and try again
   - reset your account and start fresh: https://keybase.io/#account-reset
alexanderkjeldaas commented 7 years ago

So the primary key is expired so it suggests to reset the account.

janmyszkier commented 7 years ago

@alexanderkjeldaas your issue is different, your key expired, mine was still working. you also get different error/output in console, please submit another issue.

theethernaut commented 6 years ago

Same problem here. The key is there, and is valid, but the app will just not find it.

palewire commented 5 years ago

I get this same bug after having made my key on my own on my terminal and pasting the public version into your site.

$ gpg -K --with-colons --fingerprint
sec::4096:1:96D527C46009AA8D:2019-04-19::::Ben Welsh (palewire) <ben.welsh@gmail.com>:::
fpr:::::::::39C7D9D20AC892B5BCA2AE0096D527C46009AA8D:
ssb::4096:1:4207B7E6F76E9C3A:2019-04-19:::::::
ssb::4096:1:3318C3C8C20EC0F6:2019-04-19:::::::
$ keybase login        
Your keybase username or email address: palewire
▶ ERROR Sorry, your account is already established with a PGP public key, but this
utility cannot find the corresponding private key on this machine.
This is the fingerprint of the PGP key in your account:

   39C7 D9D2 0AC8 92B5 BCA2 AE00 96D5 27C4 6009 AA8D

You need to prove you're you. We suggest one of the following:

   - put one of the PGP private keys listed above on this machine and try again
   - reset your account and start fresh: https://keybase.io/#account-reset
$ keybase log send
This command will send recent keybase log entries to keybase.io
for debugging purposes only.

These logs don’t include your private keys or encrypted data,
but they will include filenames and other metadata keybase normally
can’t read, for debugging purposes.

Continue sending logs to keybase.io? (type 'YES' to confirm): YES
Enter feedback (or <Enter> to send): command line tool can't find my key
More feedback (or press <Enter> when done): 
▶ INFO Not sending up a UID for logged in user; none found

------------
Success! Your log ID is:

  2bd335de8ed6fa9548bf061c
zapu commented 5 years ago

Hey @palewire sorry for missing your comment.

Can you try to run gpg -K to see where is the key ring that your keys live in? For me it's 

» gpg -K
/home/zapu/.gnupg/pubring.kbx

Keybase might have issues if it's not in default location because of e.g. GNUPGHOME environment variable.

Also can you check if you use the same gpg that Keybase client tries to shell out? Using which gpg. Keybase runs /usr/bin/gpg2 (according to your log), there used to be issues if someone had multiple versions of gpg installed.

palewire commented 5 years ago

Here you go.

$ gpg -K
/home/palewire/.gnupg/secring.gpg
$ which gpg
/usr/bin/gpg
$ gpg --version
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
zapu commented 5 years ago

Let's see what gpg2 binary says about the keys:

/usr/bin/gpg2 --no-tty --with-colons --fingerprint -K

does the output look similar to just doing gpg -K --with-colons --fingerprint?

To force keybase to use /usr/bin/gpg you can try the following:

# stop keybase service
keybase ctl stop
# use keybase pgp command in standalone mode with GPG overriden
GPG=/usr/bin/gpg keybase --standalone login
palewire commented 5 years ago 
$ /usr/bin/gpg2 --no-tty --with-colons --fingerprint -K

$ gpg -K --with-colons --fingerprint
sec::4096:1:96D527C46009AA8D:2019-04-19::::Ben Welsh (palewire) <ben.welsh@gmail.com>:::
fpr:::::::::39C7D9D20AC892B5BCA2AE0096D527C46009AA8D:
ssb::4096:1:4207B7E6F76E9C3A:2019-04-19:::::::
ssb::4096:1:3318C3C8C20EC0F6:2019-04-19:::::::
zapu commented 5 years ago

OK, can you try the following:

# stop keybase service
keybase ctl stop
# use keybase pgp command in standalone mode with GPG overriden
GPG=/usr/bin/gpg keybase --standalone login

it should let you login using gpg instead of gpg2

maxtaco commented 5 years ago

@zapu another strategy is to set the config file option and then to restart the service. Is the restart even needed?

zapu commented 5 years ago

I was trying that this morning I think in any case restart was needed. Shall we pass GPG and similar env vars from command to the service like we do for gpg_tty? It could simplify supporting this class of problems that users have.

Also I agree that changing config is way to go if someone needs the gpg integration working long term.

Wiadomość napisana przez Maxwell Krohn notifications@github.com w dniu 04.05.2019, o godz. 14:35:

@zapu another strategy is to set the config file option and then to restart the service. Is the restart even needed?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

richkum92 commented 2 years ago

Getting this after keybase login

ERROR Sorry, your account is already established with a PGP public key, but this utility cannot find the corresponding private key on this machine. This is the fingerprint of the PGP key in your account:

3FE9 07C9 A867 7010 F3B2 FB3C 3242 9005 3894 8BBA

You need to prove you're you. We suggest one of the following:

I have already saved private key on my machine at the time of creation of PGP key. Then why its not working? Reset your account says it will take 3 days to reset. Could you please help me here to fix the issue.