search

keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.89k stars 1.23k forks source link

Provisioning Failure on Windows 10 with existing Keybase Account #5935

Open orcmid opened 7 years ago

orcmid commented 7 years ago

[write something useful and descriptive here]

my log id: 63006d025080dc7d8ff8701c

It appears that the current release of Keybase does install properly. It also appears that the attempt to login succeeds (it recognizes the name and recovers my profile picture). I am also logged in at the web interface, so I think that did work. The previous successful install was 0.8.25 on node.js, which now produces a config file warning.

keybase-2017-02-19-0932-node js-keybaseversion

I confirmed that cmd started at the location where the newer Keybase is installed does find gpg. And the send log operation works there.

keybase-2017-02-19-0913-gpg-pathconfirmed

But on startup of Keybase, which apparently happens automatically on Windows startup, the login fails with a provisioning error.

keybase-2017-02-19-0845-provisioningerror

Hints: 1. I have not changed the group policy that prevents execution under AppData, but the current install seems to overcome that, at least partially. 2. AppData is on an SSD with compression (and I would love to move AppData to the D: HDD but have found no way to do that).

[PS: It is unfortunate that the Help panel does not provide an About with Keybase version identification]

maxtaco commented 7 years ago

Looks like this version of gpg4win doesn't output in the format that we expect.

Can you run:

gpg -K --with-colons --fingerprint
orcmid commented 7 years ago

keybase-2017-02-19-1210-gpgfingerprint

C:\Users\orcmi_000\AppData\Local\Keybase>gpg -K --with-colons --fingerprint
sec::2048:1:F96E89FFD456628A:1395683761:2184083761:::::::::
fpr:::::::::04D04322979B84DE10770334F96E89FFD456628A:
uid:::::::2B00394B44EE6D138464C7D71968AF99AE3EBFDD::Dennis E. Hamilton (orcmid) <dennis.hamilton@acm.org>:
uid:::::::C5A29A113F53D4A8075F1F1EE422E4248F8DD1AD::orcmid (Dennis E. Hamilton) <orcmid@msn.com>:
uid:::::::A19033CB4EDA1EB9BD377D5FDA7240FA9009AAFB::orcmid Apache (code signing) <orcmid@apache.org>:
uid:::::::4B1158C74495BD69DBFC4ABFFD11EAE9CC38842B::keybase.io/orcmid (confirmed identifier) <orcmid@keybase.io>:
ssb::2048:1:831140B5BB3F266D:1395683761::::::::::
sec::4096:1:508D5AF28D8443CD:1400729929:2116526400:::::::::
fpr:::::::::3368ED67A69B6BD1F8605A37508D5AF28D8443CD:
uid:::::::4D7ED5EEAAAC3179257DB983DFDFBBCDFE3C8159::Trust Worthiness (TROST assessment) <trust@worthiness.org>:
uid:::::::CF8144CD991BD0F636C00D560638A6809F647C52::keybase.io/worthiness (confirmed identifier) <worthiness@keybase.io>:

C:\Users\orcmi_000\AppData\Local\Keybase>
maxtaco commented 7 years ago

Thanks for the update. I'll make a ticket for it in our internal tracker.