stage0 - login with username fails

arenzana commented 8 years ago

I get the following when I try to log in with my username.

▶ ERROR failed to get synced secret key (error 901)

I'm pasting the password from my password manager into pinentry, the password contains special characters.

Using kbstage cli 1.0.0-47.

patrickxb commented 8 years ago

What's your keybase username?

arenzana commented 8 years ago

iarenzana

patrickxb commented 8 years ago

This is a bad error message on our part. It will be improved in the next release.

If you select the GPG option, you should be able to login.

Thanks!

arenzana commented 8 years ago

With option 4, I get the following error:

▶ ERROR openpgp: invalid data: user ID self-signature invalid: openpgp: invalid signature: hash tag doesn't match

I'm not creating a new issue since I'm not entirely sure it's a problem with Keybase. My key is DA004171. I can unlock it and use it normally using GPGTools. Is it expecting anything in particular?

maxtaco commented 8 years ago

Grr, this is a new one. Can you paste the output of your public key export from gpg?

gpg --export -a DA004171

Also, which version of GPG are you running? Can you run gpg --version ?

Finally, a keybase -d login debug trace could be useful too. Thank you!

arenzana commented 8 years ago

GPG version:

gpg --version
gpg (GnuPG) 1.4.19
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

Debug trace of kbstage:

Choose a key: 1
13:49:37.560083 ▶ [DEBU keybase log.go:30] 023 SelectKey result: 2B201107DA004171
13:49:37.560172 ▶ [DEBU keybase log.go:30] 024 + API GET request to https://stage0.keybase.io/_/api/1.0/key/basics.json?fingerprint=afb2336f7ea5be5ab9b22ff82b201107da004171
13:49:37.815668 ▶ [DEBU keybase log.go:30] 025 + Resolving username iarenzana
13:49:37.815710 ▶ [DEBU keybase log.go:30] 027 + Account "G - GetMyUID - GetUID"
13:49:37.815679 ▶ [DEBU keybase log.go:30] 026 | resolved to 519e13aa39b79f424c71b3aea2861e19
13:49:37.815747 ▶ [DEBU keybase log.go:30] 028 - Account "G - GetMyUID - GetUID"
13:49:37.815770 ▶ [DEBU keybase log.go:30] 029 + loadUserFromLocalStorage(519e13aa39b79f424c71b3aea2861e19)
13:49:37.815803 ▶ [DEBU keybase log.go:30] 02a + LevelDb.open
13:49:37.815810 ▶ [DEBU keybase log.go:30] 02b + LoadUser(uid=, name=iarenzana)
13:49:37.815820 ▶ [DEBU keybase log.go:30] 02c | Result is: 200 OK
13:49:37.815915 ▶ [DEBU keybase log.go:30] 02d - LevelDb.open -> ok
13:49:37.816343 ▶ [DEBU keybase log.go:30] 02e | Loaded successfully
13:49:37.816533 ▶ [DEBU keybase log.go:30] 02f + ParseKeyFamily
13:49:37.823714 ▶ [DEBU keybase log.go:30] 030 found user (iarenzana, 519e13aa39b79f424c71b3aea2861e19) for key afb2336f7ea5be5ab9b22ff82b201107da004171
13:49:37.823804 ▶ [DEBU keybase log.go:30] 031 LoadUser: {UID: Name:iarenzana PublicKeyOptional:true NoCacheResult:false Self:false ForceReload:false AllKeys:false LoginContext:<nil> Contextified:{g:0xc820088f20}}
13:49:37.826225 ▶ [DEBU keybase log.go:30] 032 | Loaded username iarenzana (uid=519e13aa39b79f424c71b3aea2861e19)
13:49:37.826289 ▶ [DEBU keybase log.go:30] 033 - ParseKeyFamily -> ok
13:49:37.826353 ▶ [DEBU keybase log.go:30] 034 + MerkleClient.LoadRoot()
13:49:37.826396 ▶ [DEBU keybase log.go:30] 035 - LevelDb.open -> ok
13:49:37.826470 ▶ [DEBU keybase log.go:30] 036 - loadUserFromLocalStorage(iarenzana,519e13aa39b79f424c71b3aea2861e19)
13:49:37.826507 ▶ [DEBU keybase log.go:30] 037 + LevelDb.open
13:49:37.826548 ▶ [DEBU keybase log.go:30] 039 + MerkleClient.LookupUser(map[uid:519e13aa39b79f424c71b3aea2861e19])
13:49:37.826543 ▶ [DEBU keybase log.go:30] 038 + LevelDb.open
13:49:37.826619 ▶ [DEBU keybase log.go:30] 03a - LevelDb.open -> ok
13:49:37.826640 ▶ [DEBU keybase log.go:30] 03b - MerkleClient.LoadRoot() -> &{{0xc820088f20} 292598 [165 69 104 91 61 230 200 247 178 95 52 7 251 250 218 73 174 145 93 134] 0xc8204b7260 {"body":{"key":{"fingerprint":"a545685b3de6c8f7b25f3407fbfada49ae915d86","key_id":"FBFADA49AE915D86"},"legacy_uid_root":"d3450288d233fe9125d0b6f8196dbc93447bca2630300898781a637a44752032","prev":"b924abc1093cfd424c0ddc74a5d280dfa90d282e38191d7c9856339ac9bac05400edfe156e6c9081d340faaa37a7a0d512c40c0464eba9af6bc131bc1f7f1c55","root":"cea2542b9efc416a0b376f72cc41392c9a87f4f6accb0a0a566d7f46903aa9f29ff2b6f452a4c1a3bf0d3beef16940960e5f52d552e3f8770225a0a685cc2fc7","seqno":292598,"txid":"d9e054f69b97a4637208bd6316f3ab15","type":"merkle_root","version":1},"ctime":1447757132,"tag":"signature"} 0xc8204b7410 [206 162 84 43 158 252 65 106 11 55 111 114 204 65 57 44 154 135 244 246 172 203 10 10 86 109 127 70 144 58 169 242 159 242 182 244 82 164 193 163 191 13 59 238 241 105 64 150 14 95 82 213 82 227 248 119 2 37 160 166 133 204 47 199] [211 69 2 136 210 51 254 145 37 208 182 248 25 109 188 147 68 123 202 38 48 48 8 152 120 26 99 122 68 117 32 50] 1447757132}
13:49:37.826689 ▶ [DEBU keybase log.go:30] 03c + API GET request to https://stage0.keybase.io/_/api/1.0/merkle/path.json?poll=10&uid=519e13aa39b79f424c71b3aea2861e19
13:49:37.826706 ▶ [DEBU keybase log.go:30] 03d | LookupPath
13:49:37.925135 ▶ [DEBU keybase log.go:30] 03e | Result is: 200 OK
13:49:37.970221 ▶ [DEBU keybase log.go:30] 03f - successful API call
13:49:37.970300 ▶ [DEBU keybase log.go:30] 040 | VerifyRoot
13:49:37.970592 ▶ [DEBU keybase log.go:30] 041 | VerifyUser
13:49:37.971994 ▶ [DEBU keybase log.go:30] 042 | SigChainLoader.Load(519e13aa39b79f424c71b3aea2861e19) GetFingerprint
13:49:37.972007 ▶ [DEBU keybase log.go:30] 043 + ParsingMerkleUserLeaf
13:49:37.972073 ▶ [DEBU keybase log.go:30] 044 - ParsingMerkleUserLeaf -> ok
13:49:37.972076 ▶ [DEBU keybase log.go:30] 045 | VerifyUsername
13:49:37.977626 ▶ [DEBU keybase log.go:30] 046 | Merkle root: got back 292598, >= cached 292598
13:49:37.977755 ▶ [DEBU keybase log.go:30] 047 | Username iarenzana mapped to 519e13aa39b79f424c71b3aea2861e19 via direct hash
13:49:37.977857 ▶ [DEBU keybase log.go:30] 048 + SigChainLoader.LoadFromStorage(519e13aa39b79f424c71b3aea2861e19)
13:49:37.978024 ▶ [DEBU keybase log.go:30] 049 - MerkleClient.LookupUser(map[uid:519e13aa39b79f424c71b3aea2861e19 poll:10]) -> OK
13:49:37.978088 ▶ [DEBU keybase log.go:30] 04a | SigChainLoader.Load(519e13aa39b79f424c71b3aea2861e19) AccessPreload
13:49:37.978123 ▶ [DEBU keybase log.go:30] 04b | Preload failed
13:49:37.978184 ▶ [DEBU keybase log.go:30] 04c | SigChainLoader.Load(519e13aa39b79f424c71b3aea2861e19) LoadLinksFromStorage
13:49:37.978218 ▶ [DEBU keybase log.go:30] 04d | Unpacked Link af8e4508d3740777846d8792431e87efdcb2623d99b84d3fdc23b5cd9000c74f
13:49:37.978272 ▶ [DEBU keybase log.go:30] 04e + LevelDb.open
13:49:37.978314 ▶ [DEBU keybase log.go:30] 04f - LevelDb.open -> ok
13:49:37.978375 ▶ [DEBU keybase log.go:30] 050 | loading link; curr=53505dd83df136ae48918109e60a9650a855ac72b4e0e1b6ce594e867b3e31e3
13:49:37.978408 ▶ [DEBU keybase log.go:30] 051 + LevelDb.open
13:49:37.978462 ▶ [DEBU keybase log.go:30] 052 - LevelDb.open -> ok
13:49:37.978500 ▶ [DEBU keybase log.go:30] 053 | Link is marked as 'sig_verified'
13:49:37.978562 ▶ [DEBU keybase log.go:30] 054 | Unpacked Link 53505dd83df136ae48918109e60a9650a855ac72b4e0e1b6ce594e867b3e31e3
13:49:37.978606 ▶ [DEBU keybase log.go:30] 055 | Setting loadKID=010174db9b4d3e25217b408af9eab4546aff0f66a7f1cf9d8893c081e8f93c3d7aff0a
13:49:37.978660 ▶ [DEBU keybase log.go:30] 056 | loading link; curr=1c9882c65fa88e0f4ef84f0229b1c2a1c29a9729b6c92845a540cf5da1ddb0a2
13:49:37.978693 ▶ [DEBU keybase log.go:30] 057 + LevelDb.open
13:49:37.978748 ▶ [DEBU keybase log.go:30] 058 - LevelDb.open -> ok
13:49:37.978779 ▶ [DEBU keybase log.go:30] 059 | Unpacked Link 1c9882c65fa88e0f4ef84f0229b1c2a1c29a9729b6c92845a540cf5da1ddb0a2
13:49:37.978833 ▶ [DEBU keybase log.go:30] 05a | loading link; curr=93ecf25c3e9d773ef23dcb84109741b88e50a7aba395b7eba7553166b30a4ba5
13:49:37.978877 ▶ [DEBU keybase log.go:30] 05b + LevelDb.open
13:49:37.978937 ▶ [DEBU keybase log.go:30] 05c - LevelDb.open -> ok
13:49:37.978969 ▶ [DEBU keybase log.go:30] 05d | Unpacked Link 93ecf25c3e9d773ef23dcb84109741b88e50a7aba395b7eba7553166b30a4ba5
13:49:37.979029 ▶ [DEBU keybase log.go:30] 05e | loading link; curr=b65473e085d0ce8c577b933c6372747fd0a11678856af8e772aa60136e6ce9da
13:49:37.979060 ▶ [DEBU keybase log.go:30] 05f + LevelDb.open
13:49:37.979114 ▶ [DEBU keybase log.go:30] 060 - LevelDb.open -> ok
13:49:37.979159 ▶ [DEBU keybase log.go:30] 061 | loading link; curr=261ccb7ca3c565be2b5bafda86756018698fcd0ee6ce89074fcc36698ba7f90e
13:49:37.979167 ▶ [DEBU keybase log.go:30] 062 | Unpacked Link b65473e085d0ce8c577b933c6372747fd0a11678856af8e772aa60136e6ce9da
13:49:37.979218 ▶ [DEBU keybase log.go:30] 063 + LevelDb.open
13:49:37.979251 ▶ [DEBU keybase log.go:30] 065 | Unpacked Link 261ccb7ca3c565be2b5bafda86756018698fcd0ee6ce89074fcc36698ba7f90e
13:49:37.979248 ▶ [DEBU keybase log.go:30] 064 - LevelDb.open -> ok
13:49:37.979295 ▶ [DEBU keybase log.go:30] 066 | Local basics version is up-to-date @ version 36
13:49:37.979315 ▶ [DEBU keybase log.go:30] 067 | Freshness: basics=true; for 519e13aa39b79f424c71b3aea2861e19
13:49:37.979349 ▶ [DEBU keybase log.go:30] 068 | loading link; curr=d4f8a580aa99bca4f542f7a3f3f1c4777f80235a6a6f12cc48cb293c09852b60
13:49:37.979370 ▶ [DEBU keybase log.go:30] 069 + SigChainLoader.Load(519e13aa39b79f424c71b3aea2861e19)
13:49:37.979406 ▶ [DEBU keybase log.go:30] 06a - LevelDb.open -> ok
13:49:37.979421 ▶ [DEBU keybase log.go:30] 06b + LevelDb.open
13:49:37.979455 ▶ [DEBU keybase log.go:30] 06c | Unpacked Link d4f8a580aa99bca4f542f7a3f3f1c4777f80235a6a6f12cc48cb293c09852b60
13:49:37.979469 ▶ [DEBU keybase log.go:30] 06d + LevelDb.open
13:49:37.979501 ▶ [DEBU keybase log.go:30] 06e - LevelDb.open -> ok
13:49:37.979521 ▶ [DEBU keybase log.go:30] 06f | loading link; curr=af8e4508d3740777846d8792431e87efdcb2623d99b84d3fdc23b5cd9000c74f
13:49:37.979557 ▶ [DEBU keybase log.go:30] 070 | Unpacked Link 06c4c9c11622303d0694f91cb6c568ec2b475d83e1034d5881bfd78972a01da4
13:49:37.979561 ▶ [DEBU keybase log.go:30] 071 | Unpacked Link 01be3b64a83f5e62fe4e992d261aa5798c5bb3372cccc1d7f30e4d664242e556
13:49:37.979589 ▶ [DEBU keybase log.go:30] 072 | loading link; curr=7a7b8f0502e7acadcef0c36255280d0403bcc132f0fcbb6c628a883851a7aaa8
13:49:37.979619 ▶ [DEBU keybase log.go:30] 073 + LevelDb.open
13:49:37.979652 ▶ [DEBU keybase log.go:30] 074 | loading link; curr=2b04048b5267d31327c7fb5264c5cbda45690b04e6df811e425c30f9bdaef242
13:49:37.979662 ▶ [DEBU keybase log.go:30] 075 + LevelDb.open
13:49:37.979702 ▶ [DEBU keybase log.go:30] 076 - LevelDb.open -> ok
13:49:37.979710 ▶ [DEBU keybase log.go:30] 077 | Unpacked Link 2b04048b5267d31327c7fb5264c5cbda45690b04e6df811e425c30f9bdaef242
13:49:37.979751 ▶ [DEBU keybase log.go:30] 078 | loading link; curr=06c4c9c11622303d0694f91cb6c568ec2b475d83e1034d5881bfd78972a01da4
13:49:37.979762 ▶ [DEBU keybase log.go:30] 079 + LevelDb.open
13:49:37.979794 ▶ [DEBU keybase log.go:30] 07a - LevelDb.open -> ok
13:49:37.979808 ▶ [DEBU keybase log.go:30] 07b | loading link; curr=01be3b64a83f5e62fe4e992d261aa5798c5bb3372cccc1d7f30e4d664242e556
13:49:37.979852 ▶ [DEBU keybase log.go:30] 07c + LevelDb.open
13:49:37.979918 ▶ [DEBU keybase log.go:30] 07d | Unpacked Link a487829303bdeba0c8aa148fbc9047eb7bc90e3f171edb442ae68eeae903db46
13:49:37.979943 ▶ [DEBU keybase log.go:30] 07e | loading link; curr=67c883dbb4c79498158088846d9f2b5a33227fa112e34a72352b34dc56a34491
13:49:37.979977 ▶ [DEBU keybase log.go:30] 080 + LevelDb.open
13:49:37.980092 ▶ [DEBU keybase log.go:30] 081 - LevelDb.open -> ok
13:49:37.980133 ▶ [DEBU keybase log.go:30] 082 | Unpacked Link 67c883dbb4c79498158088846d9f2b5a33227fa112e34a72352b34dc56a34491
13:49:37.980191 ▶ [DEBU keybase log.go:30] 083 | loading link; curr=a487829303bdeba0c8aa148fbc9047eb7bc90e3f171edb442ae68eeae903db46
13:49:37.979962 ▶ [DEBU keybase log.go:30] 07f - LevelDb.open -> ok
13:49:37.980224 ▶ [DEBU keybase log.go:30] 084 + LevelDb.open
13:49:37.980268 ▶ [DEBU keybase log.go:30] 085 - LevelDb.open -> ok
13:49:37.980290 ▶ [DEBU keybase log.go:30] 086 | Unpacked Link 219385a8be46f59096c283b7343ffa0bf857c87468f5be6a0e23300db5d7eb0a
13:49:37.980336 ▶ [DEBU keybase log.go:30] 087 | loading link; curr=219385a8be46f59096c283b7343ffa0bf857c87468f5be6a0e23300db5d7eb0a
13:49:37.980340 ▶ [DEBU keybase log.go:30] 088 + LevelDb.open
13:49:37.980393 ▶ [DEBU keybase log.go:30] 089 - LevelDb.open -> ok
13:49:37.980403 ▶ [DEBU keybase log.go:30] 08a - LevelDb.open -> ok
13:49:37.980441 ▶ [DEBU keybase log.go:30] 08b - SigChainLoader.LoadFromStorage(519e13aa39b79f424c71b3aea2861e19) -> ok
13:49:37.980451 ▶ [DEBU keybase log.go:30] 08c | SigChainLoader.Load(519e13aa39b79f424c71b3aea2861e19) MakeSigChain
13:49:37.980496 ▶ [DEBU keybase log.go:30] 08d | Unpacked Link 7a7b8f0502e7acadcef0c36255280d0403bcc132f0fcbb6c628a883851a7aaa8
13:49:37.981553 ▶ [DEBU keybase log.go:30] 08e | SigChainLoader.Load(519e13aa39b79f424c71b3aea2861e19) VerifyChain
13:49:37.981609 ▶ [DEBU keybase log.go:30] 08f + SigChain::VerifyChain()
13:49:37.982038 ▶ [DEBU keybase log.go:30] 090 - CheckFreshness (519e13aa39b79f424c71b3aea2861e19) -> (false,ok)
13:49:37.982840 ▶ [DEBU keybase log.go:30] 091 - SigChain::VerifyChain() -> ok
13:49:37.982895 ▶ [DEBU keybase log.go:30] 092 | SigChainLoader.Load(519e13aa39b79f424c71b3aea2861e19) CheckFreshness
13:49:37.982956 ▶ [DEBU keybase log.go:30] 093 + CheckFreshness
13:49:37.982990 ▶ [DEBU keybase log.go:30] 094 | Server triple: &{14 53505dd83df136ae48918109e60a9650a855ac72b4e0e1b6ce594e867b3e31e3 204fb0b0b95439d51c2ff387c41e479d20e4d22b534f2183585c9d236475b7f70f}
13:49:37.983057 ▶ [DEBU keybase log.go:30] 095 | Client triple: &{14 53505dd83df136ae48918109e60a9650a855ac72b4e0e1b6ce594e867b3e31e3 }
13:49:37.983098 ▶ [DEBU keybase log.go:30] 096 | Future triple=nil
13:49:37.983141 ▶ [DEBU keybase log.go:30] 097 - LevelDb.open -> ok
13:49:37.983169 ▶ [DEBU keybase log.go:30] 098 - SigChainLoader.Load(519e13aa39b79f424c71b3aea2861e19) -> (true, ok)
13:49:37.983173 ▶ [DEBU keybase log.go:30] 099 | Local chain version is up-to-date @ version 14
13:49:37.983222 ▶ [DEBU keybase log.go:30] 09a + LoadSigHints(519e13aa39b79f424c71b3aea2861e19)
13:49:37.983257 ▶ [DEBU keybase log.go:30] 09b + LevelDb.open
13:49:37.983264 ▶ [DEBU keybase log.go:30] 09c - LoadSigHints(519e13aa39b79f424c71b3aea2861e19)
13:49:37.983302 ▶ [DEBU keybase log.go:30] 09d | SigHints loaded @v7
13:49:37.983312 ▶ [DEBU keybase log.go:30] 09e + Refresh SigHints() for uid=519e13aa39b79f424c71b3aea2861e19
13:49:37.983358 ▶ [DEBU keybase log.go:30] 09f + API GET request to https://stage0.keybase.io/_/api/1.0/sig/hints.json?low=7&uid=519e13aa39b79f424c71b3aea2861e19
13:49:38.163761 ▶ [DEBU keybase log.go:30] 0a0 | Result is: 200 OK
13:49:38.163815 ▶ [DEBU keybase log.go:30] 0a1 + Store user iarenzana
13:49:38.163843 ▶ [DEBU keybase log.go:30] 0a2 - successful API call
13:49:38.163909 ▶ [DEBU keybase log.go:30] 0a3 - Refresh SigHints() for uid=519e13aa39b79f424c71b3aea2861e19
13:49:38.163910 ▶ [DEBU keybase log.go:30] 0a4 | SigHints.Store() skipped; wasn't dirty
13:49:38.163944 ▶ [DEBU keybase log.go:30] 0a5 + SigHints.Store() for uid=519e13aa39b79f424c71b3aea2861e19
13:49:38.163961 ▶ [DEBU keybase log.go:30] 0a7 - SigHints.Store() for uid=519e13aa39b79f424c71b3aea2861e19 -> ok
13:49:38.163969 ▶ [DEBU keybase log.go:30] 0a8 - Store for iarenzana skipped; user wasn't dirty
13:49:38.163950 ▶ [DEBU keybase log.go:30] 0a6 | No changes; version 7 was up-to-date
13:49:38.167460 ▶ [DEBU keybase log.go:30] 0a9 | Found self-signature for iarenzana @uid=519e13aa39b79f424c71b3aea2861e19, seq=14, link=53505dd83df136ae48918109e60a9650a855ac72b4e0e1b6ce594e867b3e31e3
13:49:38.167541 ▶ [DEBU keybase log.go:30] 0aa | running Gpg: /usr/local/bin/gpg [--armor --export-secret-key afb2336f7ea5be5ab9b22ff82b201107da004171]
13:49:38.167560 ▶ [DEBU keybase log.go:30] 0ab + VerifySelfSig for user iarenzana
13:49:38.167591 ▶ [DEBU keybase log.go:30] 0ac + Populate ID Table
13:49:38.167627 ▶ [DEBU keybase log.go:30] 0ae - Populate ID Table
13:49:38.167627 ▶ [DEBU keybase log.go:30] 0ad - VerifySelfSig via SigChain
13:49:38.178762 ▶ [DEBU keybase log.go:30] 0af an error occurred during provisioning, logging out
13:49:38.178824 ▶ [DEBU keybase log.go:30] 0b0 + Login "logout"
13:49:38.178830 ▶ [DEBU keybase log.go:30] 0b1 - Skipped; already loaded
13:49:38.178864 ▶ [DEBU keybase log.go:30] 0b2 + Loading session
13:49:38.178877 ▶ [DEBU keybase log.go:30] 0b3 clearing cached secret keys
13:49:38.178958 ▶ [DEBU keybase globals.go:234] 0b4 Calling shutdown first time through
13:49:38.178966 ▶ [DEBU keybase log.go:30] 0b5 - Login "logout"
13:49:38.178979 ▶ [DEBU keybase login_state.go:859] 0b6 + Account "LoginState - Shutdown"
13:49:38.179005 ▶ [DEBU keybase login_state.go:861] 0b8 - Account "LoginState - Shutdown"
13:49:38.178999 ▶ [DEBU keybase log.go:30] 0b7 + Account "LoginState - Shutdown"
13:49:38.179017 ▶ [ERRO keybase main.go:43] 0b9 openpgp: invalid data: user ID self-signature invalid: openpgp: invalid signature: hash tag doesn't match

Output of my public key

maxtaco commented 8 years ago

Thanks so much for this feedback. We're puzzling it over. Random question -- you don't happen to have Go installed locally, do you? Our hunch is that it's a bug in Go's OpenPGP secret key parsing library, but we can't ask you to send us any information about that. I might try though to send you a little dummy program so we can test this hypothesis. Otherwise, we have a new release coming out that will at least work around this issue (but not solve the bug). Honestly, we've never seen it before, and we can't repro it with keys that we made on our side.

Thanks so much for your help!

arenzana commented 8 years ago

Actually I do, 1.5.1 (I write utilities in Go). I can help you guys out, as much as my skills allow me to :)

maxtaco commented 8 years ago

Wow, you rock!

Well, if you wouldn't mind, fetch the pgp libs:

go get golang.org/x/crypto/openpgp

then compile this little ditty:

package main

import (
        "golang.org/x/crypto/openpgp"
        "os"
        "fmt"
)

func main() {
        _, err := openpgp.ReadArmoredKeyRing(os.Stdin)
        fmt.Printf("err: %v\n", err)
}

Name as ./test or some such

And then try:

/usr/local/bin/gpg --armor --export-secret-key afb2336f7ea5be5ab9b22ff82b201107da004171 | ./test

I'm very curious to see if an error comes out the other end?

Many thanks!

arenzana commented 8 years ago

Interesting, I get the same error.

/usr/local/bin/gpg --armor --export-secret-key afb2336f7ea5be5ab9b22ff82b201107da004171 | ./x
err: openpgp: invalid data: user ID self-signature invalid: openpgp: invalid signature: hash tag doesn't match

maxtaco commented 8 years ago

w00t! Thanks so much for that. So that confirms our hypothesis. I can't repro that error with keys that I generate from 1.4, so there's something particular to your key. (This means it's definitely a bug in Go's Openpgp library btw).

I guess the last thing we can try is to try to figure out what key options / flags you have, and I can use those. This operation is slightly more sensitive, as it would reveal the salt you use for encrypting your secret key. But it doesn't expose any encrypted secret key material. If you wouldn't mind encrypting this info and sending it to me over email, that would rock even more than all of the other stuff you've done for us has rocked:

gpg --armor --export-secret-key afb2336f7ea5be5ab9b22ff82b201107da004171 | gpg --list-packets

Note the gpg --list-packets, that's crucial, since it will santize all secret key material.

For instance, my output when doing that looks like this:

secret key packet:
    version 4, algo 1, created 1391639420, expires 0
    skey[0]: [4096 bits]
    skey[1]: [17 bits]
    iter+salt S2K, algo: 9, SHA1 protection, hash: 8, salt: 6347a50031ec51ec
    protect count: 65536 (96)
    protect IV:  0f 5c d6 f0 34 aa f0 d3 b0 a8 41 1f 33 9a 6d a1
    encrypted stuff follows
    keyid: 6052B2AD31A6631C
:user ID packet: "keybase.io/max (v0.0.1) <max@keybase.io>"
:signature packet: algo 1, keyid 6052B2AD31A6631C
    version 4, created 1391639420, md5len 0, sigclass 0x10
    digest algo 10, begin of digest 66 be
    hashed subpkt 2 len 4 (sig created 2014-02-05)
    hashed subpkt 27 len 1 (key flags: 2F)
    hashed subpkt 9 len 4 (key expires after 10y0d0h0m)
    hashed subpkt 11 len 2 (pref-sym-algos: 9 7)
    hashed subpkt 21 len 2 (pref-hash-algos: 10 8)
    hashed subpkt 30 len 1 (features: 01)
    hashed subpkt 23 len 1 (key server preferences: 80)
    subpkt 16 len 8 (issuer key ID 6052B2AD31A6631C)
    data: [4096 bits]

etc...

My GPG key is at https://keybase.io/max and you can email me at max@keybase.io. Thanks so much, we really appreciate it!

maxtaco commented 8 years ago

I took a look at your key packets, they are basically the same as the one I'm using for testing w/ 1.4

One more idea, how about try this, using our same Go tester program from yesterday?

/usr/local/bin/gpg --armor --export afb2336f7ea5be5ab9b22ff82b201107da004171 | ./test

Many thanks!

arenzana commented 8 years ago

Different error this time:

/usr/local/bin/gpg --armor --export afb2336f7ea5be5ab9b22ff82b201107da004171 | ./x
err: <nil>

I do get an output when I don't pipe it to the Go tester program.

maxtaco commented 8 years ago

Ok, so it's really only an issue of the secret key import. This is very useful, I'll back to scratching my head on this. Thanks again!

dgyg commented 8 years ago

I got the same error message:

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
keybase passphrase:
ERROR failed to get synced secret key (error 901)

Client: 1.0.0-46 Ubuntu 14.04 LTS

sehe commented 8 years ago

I get the same error with new CLI client:

$ keybase login 
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
Choose a signing option: 3
Your keybase username: sehe
▶ ERROR No synced secret PGP key stored on keybase.io for sehe; please try logging in via GPG, an existing device, or a paper key (error 901)

Of course, Kafka would be proud because creating paperkeys requires login first, devices don't exist yet and what is this GPG option that the message seems to refer to...

---I'll try with installing GPG (this is a new machine)--- EDIT It is installed and working fine. Ubuntu 15.10 here

patrickxb commented 8 years ago

@sehe It only shows option 4 for GPG if you have GPG installed (which it sounds like you do) and if there is a public pgp key in GPG's local keyring that matches a public pgp key on keybase.io.

I'm guessing that since this is a new machine, the pgp key isn't in GPG yet. So if you use gpg to import your full pgp key from another machine, option 4 will be displayed and you will be able to provision this device.

Let us know if that didn't work.

sehe commented 8 years ago

@patrickxb Thanks for the response!

I don't have my old install. GPG is installed. I don't know how to get that GPG key (I don't remember having to meddle with GPG before, thought that was with the nodejs client).

Why can't I login using the passphrase, though? The web client accepts it perfectly fine

patrickxb commented 8 years ago

@sehe with our new device provisioning, if there is an existing PGP key associated with your account, we need to use it to sign a new device.

Since you've lost access to the PGP key in your account, you need to reset your account on the website. On your profile page, there is a settings dropdown with an option for "Reset my keys and start from scratch." Once you reset, login on the new machine (with username and passphrase) will work fine.

Thanks for your persistence!

sehe commented 8 years ago

How/why did I lose access? Should I not have been warned this would happen when switching to the go client then?

Won't resetting the keys lead to ripple effects for everyone who tracks me? What about content previously encrypted? Will it become inaccessible?

Seth

On Tue, Nov 24, 2015, at 05:28 PM, Patrick Crosby wrote:

@sehe[1] with our new device provisioning, if there is an existing PGP key associated with your account, we need to use it to sign a new device.

Since you've lost access to the PGP key in your account, you need to reset your account on the website. On your profile page, there is a settings dropdown with an option for "Reset my keys and start from scratch." Once you reset, login on the new machine (with username and passphrase) will work fine.

Thanks for your persistence!

— Reply to this email directly or view it on GitHub[2].

Links:

maxtaco commented 8 years ago

@sehe do you have the machine you originally ran keybase on, when you signed up and made proofs? Can you run gpg -K on that machine? This will list all of the secret keys that you have access to in your GPG keyring. It will just list their public fingerprint, it won't display their secret contents.

sehe commented 8 years ago

Sure. No access to the machine but I know backups :)

I guess what surprised me here is that keybase uses the user-global keyring then. If you know it, that makes sense. I had assumed keybsse would be self contained and copying the dot files was enough

Gonna try this later. Thanks

Seth

On Tue, Nov 24, 2015, at 05:34 PM, Maxwell Krohn wrote:

@sehe[1] do you hathekenbaardoodlesshouldhavebeenenoughve the machine you originally ran keybase on, when you signed up and made proofs? Can you run gpg -K on that machine? This will list all of the secret keys that you have access to in your GPG keyring. It will just list their public fingerprint, it won't display their secret contents.

— Reply to this email directly or view it on GitHub[2].

Links:

maxtaco commented 8 years ago

Well, a fine line to navigate here. Convenience & security are at odds. Some people are really particular about their GPG keyring and don't want any keys leaving. We want to accommodate those folks, as well as those who would make a convenience trade-off.

sehe commented 8 years ago

@maxtaco, @patrickxb Restoring my .gnupg folder from backup indeed did solve the problem. It was just a bit surprising. To be fair, I must have only half-understood the signup/login process before. And I'm probably one of these people who opted to not have any keys leaving (I saw I had a choice this time, and I totally expect I'll have opted to just use gpg commands if that choice was there in the past).

Thanks for the help!

alexbarton commented 8 years ago

Whats the status of this issue? I'm seeing a similar (I think?) problem as well and can't login with the client:

~ $ LC_ALL=en_US.utf8 keybase login alexbarton
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
▶ ERROR No synced secret PGP key stored on keybase.io for alexbarton; please try logging in via GPG, an existing device, or a paper key (error 901)

~ $ LC_ALL=en_US.utf8 keybase login alexbarton
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    D      C24A0F637E364856   2000-04-18   Alexander Barton <alex@barton.de>, Alexander Barton <alex@barton-it.de>
2    R      45F.............   1999-01-21   ...
3    R      5F4.............   1995-09-10   ...
4    R      284.............   1998-09-08   ...
5    R      FE8.............   2012-01-20   ...
6    D      306.............   2011-01-05   ...
Choose a key: 1
Enter a public name for this device: Thor

You need a passphrase to unlock the secret key for
user: "Alexander Barton <alex@barton.de>"
2048-bit RSA key, ID EAA15A24, created 2008-12-23 (main key ID 7E364856)

▶ ERROR bad signature: Can't find a key for 8a459ad2eaa15a24: No keys match the given key IDs (error 1002)
~ $

I don't have an existing device or an paper key … Any ideas?

Thanks!

maxtaco commented 8 years ago

@alexbarton looks like the key PGP you have on Keybase is expired. Can you use the Website to update it, and then try again?

I see this:

pub  1024D/7E364856  created: 2000-04-18  expired: 2015-02-22  usage: SC  
                     trust: unknown       validity: expired
sub  2048g/623C5EDF  created: 2000-04-18  expired: 2015-02-22  usage: E   
sub  2048R/EAA15A24  created: 2008-12-23  expired: 2015-02-22  usage: S   
sub  2048R/1AE3DE31  created: 2008-12-23  expired: 2015-02-22  usage: E

alexbarton commented 8 years ago

Thanks a lot @maxtaco, you are right! After updating the key using the website, login works. Thanks again, and sorry for "hijacking" this thread in error ;-)

zanchey commented 8 years ago

I'm running into this as well, and getting flashbacks to a similar problem in OpenKeychain - basically, anything except the most recent versions of OpenPGP (anything < 2.1.0) breaks the secret key in a way which emerges only on export after certain changes (expiry date, changing subkeys, etc.)

See https://github.com/open-keychain/open-keychain/issues/1003 - hope that helps.

carlobellettini commented 8 years ago

I'm using keybase on OSX

$ keybase --version
keybase version 1.0.5-0

I received the same error message as others, but it seems to me that i'm not in the same situation... `ERROR No synced secret PGP key stored on keybase.io for carlobellettini; please try logging in via GPG, an existing device, or a paper key (error 901)``
I have no option 4th (login with GPG)

but:

I have installed both gpg and gpg2

$ gpg --version
gpg (GnuPG) 1.4.19
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

$ gpg2 --version
gpg (GnuPG) 2.0.26
libgcrypt 1.6.3
Copyright (C) 2013 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

My GPG key

is recognized by gpg (both public and secret part)
has the same hash (0F333FE0) of the one on my keybase account (https://keybase.io/carlobellettini)
is not expired

$ gpg -k
/Users/belletc/.gnupg/pubring.gpg
---------------------------------
pub   4096R/0F333FE0 2014-12-30 [expires: 2017-12-29]
uid                  keybase.io/carlobellettini <carlobellettini@keybase.io>
uid                  Carlo Bellettini <carlo.bellettini@gmail.com>
sub   4096R/0680EBB3 2014-12-30 [expires: 2017-12-29]

$ gpg -K
/Users/belletc/.gnupg/secring.gpg
---------------------------------
sec   4096R/0F333FE0 2014-12-30 [expires: 2017-12-29]
uid                  Carlo Bellettini <carlo.bellettini@gmail.com>
ssb   4096R/0680EBB3 2014-12-30

what can I do? thanks

maxtaco commented 8 years ago

Can you post a "keybase -d login" trace?

On Sunday, December 6, 2015, Carlo Bellettini notifications@github.com wrote:

I'm using keybase on OSX

$ keybase --version keybase version 1.0.5-0

-

I received the same error message as others, but it seems to me that i'm not in the same situation... ERROR No synced secret PGP key stored on keybase.io for carlobellettini; please try logging in via GPG, an existing device, or a paper key (error 901)`

I have no option 4th (login with GPG)

but:

I have installed both gpg and gpg2

$ gpg --version gpg (GnuPG) 1.4.19 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

$ gpg2 --version gpg (GnuPG) 2.0.26 libgcrypt 1.6.3 Copyright (C) 2013 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

My GPG key

is recognized by gpg (both public and secret part)

has the same hash (0F333FE0) of the one on my keybase account ( https://keybase.io/carlobellettini)

is not expired

$ gpg -k

/Users/belletc/.gnupg/pubring.gpg

pub 4096R/0F333FE0 2014-12-30 [expires: 2017-12-29] uid keybase.io/carlobellettini <carlobellettini@keybase.io javascript:_e(%7B%7D,'cvml','carlobellettini@keybase.io');> uid Carlo Bellettini <carlo.bellettini@gmail.com javascript:_e(%7B%7D,'cvml','carlo.bellettini@gmail.com');> sub 4096R/0680EBB3 2014-12-30 [expires: 2017-12-29]

$ gpg -K

/Users/belletc/.gnupg/secring.gpg

sec 4096R/0F333FE0 2014-12-30 [expires: 2017-12-29] uid Carlo Bellettini <carlo.bellettini@gmail.com javascript:_e(%7B%7D,'cvml','carlo.bellettini@gmail.com');> ssb 4096R/0680EBB3 2014-12-30

what can I do? thanks

— Reply to this email directly or view it on GitHub https://github.com/keybase/keybase-issues/issues/1854#issuecomment-162334150 .

carlobellettini commented 8 years ago

Ok, it is a problem of path... it does not find gpg on the path ...

10:17:20.193441 ▶ [DEBU keybase log.go:30] 02a gpg not an option: get index error: exec: "gpg": executable file not found in $PATH

I installed keybase with brew (gpg too).

$ which gpg
/usr/local/bin/gpg

So both are installed in /usr/local/bin but keybase doesn't find gpg.

clearly /usr/local/bin is in the path in the shell executing keybase...

$ export | grep PATH
declare -x PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/texbin"

where is the right point to setup the PATH such that it is used by keybase looking for gpg?

BTW I presently "solved" my issue by making gpg reachable also by /usr/bin but it is not a clean solution...

thanks for the help

maxtaco commented 8 years ago

This is weird because we are of course just using $PATH to find your gpg (or gpg2). It may be an issue of a different path that the daemonized process has, or it could be a gpg2 v. gpg problem but it is hard to know. We have never seen this problem ourselves.

On Monday, December 7, 2015, Carlo Bellettini notifications@github.com wrote:

Ok, it is a problem of path... it does not find gpg on the path ...

10:17:20.193441 ▶ [DEBU keybase log.go:30] 02a gpg not an option: get index error: exec: "gpg": executable file not found in $PATH

I installed keybase with brew (gpg too).

$ which gpg /usr/local/bin/gpg

So both are installed in /usr/local/bin but keybase don't find gpg.

clearly /usr/local/bin is in the path in the shell executing keybase...

$ export | grep PATH declare -x PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/texbin"

where is the right point to setup the PATH such that it is used by keybase looking for gpg?

BTW I presently "solved" my issue by making gpg reachable also by /usr/bin but it is not a clean solution...

thanks for the help

— Reply to this email directly or view it on GitHub https://github.com/keybase/keybase-issues/issues/1854#issuecomment-162457614 .

carlobellettini commented 8 years ago

I recreated the initial situation:

$ keybase -d login
14:27:30.526743 ▶ [DEBU keybase json.go:48] 001 + loading config file: /Users/belletc/Library/Application Support/Keybase/config.json
14:27:30.526931 ▶ [DEBU keybase json.go:56] 002 No config file found; tried /Users/belletc/Library/Application Support/Keybase/config.json
14:27:30.527122 ▶ [DEBU keybase config.go:114] 003 Config: mapping server -> 
14:27:30.569399 ▶ [DEBU keybase config.go:114] 004 Config: mapping socket_file -> 
14:27:30.569453 ▶ [DEBU keybase config.go:114] 005 Config: mapping home -> 
14:27:30.569608 ▶ [DEBU keybase config.go:114] 006 Config: mapping timers -> 
14:27:30.569626 ▶ [DEBU keybase globals.go:186] 007 Keybase CLI 1.0.5-0
14:27:30.569642 ▶ [DEBU keybase globals.go:186] 008 - Built with go1.5.1
14:27:30.569661 ▶ [DEBU keybase globals.go:186] 009 - Visit https://keybase.io for more details
14:27:30.569694 ▶ [DEBU keybase main.go:100] 00a + configureProcesses
14:27:30.569728 ▶ [DEBU keybase install_osx.go:698] 00b + AutoInstall for launchd
14:27:30.571011 ▶ [DEBU keybase install_osx.go:711] 00c | already installed at /Users/belletc/Library/LaunchAgents/homebrew.mxcl.keybase.plist
14:27:30.571044 ▶ [DEBU keybase install_osx.go:700] 00d - AutoInstall -> false, <nil>
14:27:30.571069 ▶ [DEBU keybase main.go:157] 00e | After forks; newProc=false
14:27:30.571082 ▶ [DEBU keybase main.go:178] 00f + configureLogging
14:27:30.571102 ▶ [DEBU keybase config.go:114] 010 Config: mapping local_rpc_debug -> 
14:27:30.571142 ▶ [DEBU keybase socket_nix.go:23] 011 Dialing unix:/Users/belletc/Library/Caches/Keybase/keybased.sock
14:27:30.571318 ▶ [DEBU keybase config.go:114] 012 Config: mapping local_rpc_debug -> 
14:27:30.571423 ▶ [DEBU keybase main.go:214] 013 Setting remote log level: 1
14:27:30.572392 ▶ [DEBU keybase main.go:180] 014 - configureLogging
14:27:30.572450 ▶ [DEBU keybase versionfix.go:21] 015 + FixVersionClash
14:27:30.573164 ▶ [DEBU keybase log.go:30] 016 Config: mapping server -> 
14:27:30.573575 ▶ [DEBU keybase log.go:30] 017 Config: mapping socket_file -> 
14:27:30.573883 ▶ [DEBU keybase log.go:30] 018 Config: mapping home -> 
14:27:30.617343 ▶ [DEBU keybase log.go:30] 019 Config: mapping config_file -> 
14:27:30.617796 ▶ [DEBU keybase log.go:30] 01a Config: mapping home -> 
14:27:30.618320 ▶ [DEBU keybase versionfix.go:33] 01b | Contacted service; got version: 1.0.5-0
14:27:30.618391 ▶ [DEBU keybase versionfix.go:55] 01c | version check 1.0.5-0 v 1.0.5-0
14:27:30.618427 ▶ [DEBU keybase versionfix.go:57] 01d | versions check out
14:27:30.618446 ▶ [DEBU keybase versionfix.go:23] 01e - FixVersionClash -> <nil>
14:27:30.618463 ▶ [DEBU keybase main.go:102] 01f - configureProcesses -> <nil>
14:27:30.619059 ▶ [DEBU keybase log.go:30] 020 + RunEngine(Login)
14:27:30.619542 ▶ [DEBU keybase log.go:30] 021 + RunEngine(LoginCurrentDevice)
14:27:30.619923 ▶ [DEBU keybase log.go:30] 022 + Account "LoggedInProvisionedLoad"
14:27:30.620319 ▶ [DEBU keybase log.go:30] 023 + Loading session
14:27:30.620664 ▶ [DEBU keybase log.go:30] 024 - Skipped; already loaded
14:27:30.620981 ▶ [DEBU keybase log.go:30] 025 - Account "LoggedInProvisionedLoad"
14:27:30.621399 ▶ [DEBU keybase log.go:30] 026 error getting user config: <root>.current_user: no such key: current_user (*jsonw.Error)
14:27:30.621715 ▶ [DEBU keybase log.go:30] 027 - RunEngine(LoginCurrentDevice) -> ERROR: No user config available
14:27:30.621949 ▶ [DEBU keybase log.go:30] 028 LoginCurrentDevice error: No user config available (continuing with device provisioning...)
14:27:30.622222 ▶ [DEBU keybase log.go:30] 029 + RunEngine(LoginProvision)
14:27:30.622578 ▶ [DEBU keybase log.go:30] 02a gpg not an option: get index error: exec: "gpg": executable file not found in $PATH
14:27:30.622846 ▶ [DEBU keybase log.go:30] 02b found gpg with private keys?: false
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
Choose a signing option:

after create a link to gpg in /usr/bin with sudo ln -s /usr/local/bin/gpg /usr/bin/gpg:

$ keybase -d login
14:31:26.076023 ▶ [DEBU keybase json.go:48] 001 + loading config file: /Users/belletc/Library/Application Support/Keybase/config.json
14:31:26.076101 ▶ [DEBU keybase json.go:56] 002 No config file found; tried /Users/belletc/Library/Application Support/Keybase/config.json
14:31:26.076162 ▶ [DEBU keybase config.go:114] 003 Config: mapping server -> 
14:31:26.076330 ▶ [DEBU keybase config.go:114] 004 Config: mapping socket_file -> 
14:31:26.076362 ▶ [DEBU keybase config.go:114] 005 Config: mapping home -> 
14:31:26.076475 ▶ [DEBU keybase config.go:114] 006 Config: mapping timers -> 
14:31:26.076493 ▶ [DEBU keybase globals.go:186] 007 Keybase CLI 1.0.5-0
14:31:26.076509 ▶ [DEBU keybase globals.go:186] 008 - Built with go1.5.1
14:31:26.076527 ▶ [DEBU keybase globals.go:186] 009 - Visit https://keybase.io for more details
14:31:26.076546 ▶ [DEBU keybase main.go:100] 00a + configureProcesses
14:31:26.076577 ▶ [DEBU keybase install_osx.go:698] 00b + AutoInstall for launchd
14:31:26.077778 ▶ [DEBU keybase install_osx.go:711] 00c | already installed at /Users/belletc/Library/LaunchAgents/homebrew.mxcl.keybase.plist
14:31:26.077810 ▶ [DEBU keybase install_osx.go:700] 00d - AutoInstall -> false, <nil>
14:31:26.077825 ▶ [DEBU keybase main.go:157] 00e | After forks; newProc=false
14:31:26.077838 ▶ [DEBU keybase main.go:178] 00f + configureLogging
14:31:26.077857 ▶ [DEBU keybase config.go:114] 010 Config: mapping local_rpc_debug -> 
14:31:26.077898 ▶ [DEBU keybase socket_nix.go:23] 011 Dialing unix:/Users/belletc/Library/Caches/Keybase/keybased.sock
14:31:26.078057 ▶ [DEBU keybase config.go:114] 012 Config: mapping local_rpc_debug -> 
14:31:26.078146 ▶ [DEBU keybase main.go:214] 013 Setting remote log level: 1
14:31:26.078652 ▶ [DEBU keybase main.go:180] 014 - configureLogging
14:31:26.078685 ▶ [DEBU keybase versionfix.go:21] 015 + FixVersionClash
14:31:26.079151 ▶ [DEBU keybase log.go:30] 016 Config: mapping server -> 
14:31:26.079446 ▶ [DEBU keybase log.go:30] 017 Config: mapping socket_file -> 
14:31:26.079704 ▶ [DEBU keybase log.go:30] 018 Config: mapping home -> 
14:31:26.079997 ▶ [DEBU keybase log.go:30] 019 | configured GPG w/ path: /usr/bin/gpg
14:31:26.080254 ▶ [DEBU keybase log.go:30] 01a | configured GPG w/ path: /usr/bin/gpg
14:31:26.080455 ▶ [DEBU keybase log.go:30] 01b Config: mapping config_file -> 
14:31:26.080667 ▶ [DEBU keybase log.go:30] 01c Config: mapping home -> 
14:31:26.080975 ▶ [DEBU keybase versionfix.go:33] 01d | Contacted service; got version: 1.0.5-0
14:31:26.081018 ▶ [DEBU keybase versionfix.go:55] 01e | version check 1.0.5-0 v 1.0.5-0
14:31:26.081043 ▶ [DEBU keybase versionfix.go:57] 01f | versions check out
14:31:26.081056 ▶ [DEBU keybase versionfix.go:23] 020 - FixVersionClash -> <nil>
14:31:26.081069 ▶ [DEBU keybase main.go:102] 021 - configureProcesses -> <nil>
14:31:26.081399 ▶ [DEBU keybase log.go:30] 022 + RunEngine(Login)
14:31:26.081683 ▶ [DEBU keybase log.go:30] 023 + RunEngine(LoginCurrentDevice)
14:31:26.081884 ▶ [DEBU keybase log.go:30] 024 + Account "LoggedInProvisionedLoad"
14:31:26.082110 ▶ [DEBU keybase log.go:30] 025 + Loading session
14:31:26.082355 ▶ [DEBU keybase log.go:30] 026 - Skipped; already loaded
14:31:26.082628 ▶ [DEBU keybase log.go:30] 027 - Account "LoggedInProvisionedLoad"
14:31:26.082851 ▶ [DEBU keybase log.go:30] 028 error getting user config: <root>.current_user: no such key: current_user (*jsonw.Error)
14:31:26.083069 ▶ [DEBU keybase log.go:30] 029 - RunEngine(LoginCurrentDevice) -> ERROR: No user config available
14:31:26.083303 ▶ [DEBU keybase log.go:30] 02a LoginCurrentDevice error: No user config available (continuing with device provisioning...)
14:31:26.083519 ▶ [DEBU keybase log.go:30] 02b + RunEngine(LoginProvision)
14:31:26.083774 ▶ [DEBU keybase log.go:30] 02c | configured GPG w/ path: /usr/bin/gpg
14:31:26.202004 ▶ [DEBU keybase log.go:30] 02d | running Gpg: /usr/bin/gpg [--no-tty --with-colons --fingerprint -K]
14:31:26.653359 ▶ [DEBU keybase log.go:30] 02e have gpg.  num private keys: 1
14:31:26.654149 ▶ [DEBU keybase log.go:30] 02f found gpg with private keys?: true
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

maxtaco commented 8 years ago

Thanks for all of this info. Can you cat /Users/belletc/Library/LaunchAgents/homebrew.mxcl.keybase.plist ? I'm curious to know what's in there.

carlobellettini commented 8 years ago

$ cat /Users/belletc/Library/LaunchAgents/homebrew.mxcl.keybase.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>Label</key>
  <string>homebrew.mxcl.keybase</string>
  <key>EnvironmentVariables</key>
  <dict>
    <key>PATH</key>
    <string>/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin</string>
    <key>KEYBASE_LABEL</key>
    <string>homebrew.mxcl.keybase</string>
    <key>KEYBASE_LOG_FORMAT</key>
    <string>file</string>
    <key>KEYBASE_RUNTIME_DIR</key>
    <string>/Users/belletc/Library/Caches/Keybase</string>
  </dict>
  <key>ProgramArguments</key>
  <array>
    <string>/usr/local/opt/keybase/bin/keybase</string>
    <string>service</string>
  </array>
  <key>KeepAlive</key>
  <true/>
  <key>RunAtLoad</key>
  <true/>
  <key>StandardErrorPath</key>
  <string>/Users/belletc/Library/Logs/homebrew.mxcl.keybase.log</string>
  <key>StandardOutPath</key>
  <string>/Users/belletc/Library/Logs/homebrew.mxcl.keybase.log</string>
  <key>WorkingDirectory</key>
  <string>/tmp</string>
</dict>
</plist>

maxtaco commented 8 years ago

Thanks @carlobellettini. This is really weird since your path should have /usr/local/bin as stated

carlobellettini commented 8 years ago

yes... I think so too... :-D ... Sorry that go is not a language that I'm used to code with, but If you want that I run some modified version of the client just let me know

Bye

maxtaco commented 8 years ago

@gabriel do you have any ideas here?

maxtaco commented 8 years ago

@carlobellettini one other thing to try. Remove that symlink, and do keybase launchd stop homebrew.mxcl.keybase.service and a keybase launchd start homebrew.mxcl.keybase.service

carlobellettini commented 8 years ago

@maxtaco no changes... sorry

maxtaco commented 8 years ago

Ah, it's ok. Still thinking of what it could be. What does ps show?

ps -axE | grep keybase | grep service

gabriel commented 8 years ago

@carlobellettini Whats your output of keybase launchd list ?

carlobellettini commented 8 years ago

A double definition of PATH (one correct ... on not)

$ ps -axE | grep keybase | grep service
 1901 ??         0:04.12 /usr/local/opt/keybase/bin/keybase service PATH=/usr/bin:/bin:/usr/sbin:/sbin PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin KEYBASE_RUNTIME_DIR=/Users/belletc/Library/Caches/Keybase KEYBASE_LOG_FORMAT=file KEYBASE_LABEL=homebrew.mxcl.keybase XPC_SERVICE_NAME=homebrew.mxcl.keybase DISPLAY=/private/tmp/com.apple.launchd.uZY8NYtw6N/org.macosforge.xquartz:0 SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.ilXEuQGf2a/Listeners Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.npq6BNBUjG/Render XPC_FLAGS=0x1 LOGNAME=belletc USER=belletc HOME=/Users/belletc SHELL=/bin/bash TMPDIR=/var/folders/s2/ysj_dv3d56x_65b1jc93sb6c0000gp/T/

$ keybase launchd list
Keybase service:
homebrew.mxcl.keybase: Running (pid=1901)

No KBFS services.

maxtaco commented 8 years ago

Aha! Well that's... unexpected... but it explains WTH is going on here. Thanks @carlobellettini we'll look into it some more.

gabriel commented 8 years ago

@carlobellettini What version of OSX are you running?

carlobellettini commented 8 years ago

yosemite 10.10.1

gabriel commented 8 years ago

I'm guessing that your launchd global PATH is overriding the one we set in the plist. I think recent OSX's have removed /etc/launchd.conf.

What does this say?

launchctl getenv PATH

If you add /usr/local/bin to your default launchd PATH?

launchctl setenv PATH /sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin

and then restart keybase:

keybase launchd restart homebrew.mxcl.keybase

(edited)

it might fix it.

I wonder if we should manually try to find gpg in other standard locations like /usr/local/bin if exec.Lookpath doesn't find anything?

gabriel commented 8 years ago

Oops I mean restart keybase:

keybase launchd restart homebrew.mxcl.keybase

carlobellettini commented 8 years ago

no... it does not fix it...

the getenv returns empty...

the setenv add a new PATH definition (just before DISPLAY)

to clarify its position ... consider setting it to newpath:

$ launchctl setenv PATH newpath
$ keybase launchd restart homebrew.mxcl.keybase
$ ps -axE | grep keybase | grep service
 3331 ??         0:00.02 /usr/local/opt/keybase/bin/keybase service PATH=/usr/bin:/bin:/usr/sbin:/sbin PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin KEYBASE_RUNTIME_DIR=/Users/belletc/Library/Caches/Keybase KEYBASE_LOG_FORMAT=file KEYBASE_LABEL=homebrew.mxcl.keybase XPC_SERVICE_NAME=homebrew.mxcl.keybase PATH=newpath DISPLAY=/private/tmp/com.apple.launchd.uZY8NYtw6N/org.macosforge.xquartz:0 SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.ilXEuQGf2a/Listeners Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.npq6BNBUjG/Render XPC_FLAGS=0x1 LOGNAME=belletc USER=belletc HOME=/Users/belletc SHELL=/bin/bash TMPDIR=/var/folders/s2/ysj_dv3d56x_65b1jc93sb6c0000gp/T/

Thus also setting as you asked (I did it)... does not solve the problem.

gabriel commented 8 years ago

Ah darn. I poked around open radar and it looks like it's this bug: https://openradar.appspot.com/18945659

BTW, to undo the setenv I suggested you can run launchctl unsetenv PATH

keybase / keybase-issues

stage0 - login with username fails #1854

Gonna try this later. Thanks

I received the same error message as others, but it seems to me that i'm not in the same situation... ERROR No synced secret PGP key stored on keybase.io for carlobellettini; please try logging in via GPG, an existing device, or a paper key (error 901)`

/Users/belletc/.gnupg/pubring.gpg

/Users/belletc/.gnupg/secring.gpg