{"action":"created","issue":{"url":"https://api.github.com/repos/keybase/keybase-issues/issues/1636","repository_url":"https://api.github.com/repos/keybase/keybase-issues","labels_url":"https://api.github.com/repos/keybase/keybase-issues/issues/1636/labels{/name}","comments_url":"https://api.github.com/repos/keybase/keybase-issues/issues/1636/comments","events_url":"https://api.github.com/repos/keybase/keybase-issues/issues/1636/events","html_url":"https://github.com/keybase/keybase-issues/issues/1636","id":88132409,"number":1636,"title":"keybase-installer cannot update client when private key is not stored in Keybase","user":{"login":"jflory7","id":4721034,"avatar_url":"https://avatars.githubusercontent.com/u/4721034?v=3","gravatar_id":"","url":"https://api.github.com/users/jflory7","html_url":"https://github.com/jflory7","followers_url":"https://api.github.com/users/jflory7/followers","following_url":"https://api.github.com/users/jflory7/following{/other_user}","gists_url":"https://api.github.com/users/jflory7/gists{/gist_id}","starred_url":"https://api.github.com/users/jflory7/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jflory7/subscriptions","organizations_url":"https://api.github.com/users/jflory7/orgs","repos_url":"https://api.github.com/users/jflory7/repos","events_url":"https://api.github.com/users/jflory7/events{/privacy}","received_events_url":"https://api.github.com/users/jflory7/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2015-06-14T06:30:55Z","updated_at":"2016-08-24T16:12:25Z","closed_at":null,"body":"I tried updating my Keybase client today, as I am currently running 0.7.7. However, when I go to update my software, I receive the exit codes 2 and 254.\r\n\r\n```\r\n$ sudo keybase update\r\nwarn: No config file found; tried '/root/.config/keybase/config.json'\r\ninfo: Computed npm install prefix: /\r\ninfo: Found keybase-installer: keybase-installer v1.0.0\r\ninfo: Detected custom path '/.'; preserving it!\r\ninfo: Attempting software upgrade.....\r\ninfo: Running `keybase-installer -g gpg2 --prefix /.`\r\ninfo: Made temporary directory: /tmp/keybase_install_aBW6rS7IBK_bsf0EU2sPmw\r\ninfo: Using keyset version v1\r\ninfo: Fetching URL https://dist.keybase.io/sig/files/1/index.asc\r\ninfo: cleaning up tmpdir /tmp/keybase_install_aBW6rS7IBK_bsf0EU2sPmw\r\nerror: exit code 2\r\nwarn: gpg: key 7F9E8BFA: public key \"Keybase.io Index Signing (v1) <index@keybase.io>\" imported\r\nwarn: gpg: failed to create temporary file '/root/.gnupg/.#lk0x0000000001036ec0.justin-w-florys-desktop.7697': No such file or directory\r\nwarn: gpg: can't connect to the agent: No such file or directory\r\nwarn: gpg: Total number processed: 1\r\nwarn: gpg:               imported: 1\r\nwarn: gpg: no ultimately trusted keys found\r\nerror: exit code 254\r\n```\r\n\r\nIt seems that when running this under root privileges, it cannot detect my local cached private key to successfully update Keybase? I'm unsure what to make of this.\r\n\r\nFor testing purposes, I tried copying my `config.json` file from my user directory to the root directory `/root/.config/keybase/config.json`, but all this did was eliminate the exit code 254. I still ran into exit code 2 and the update process failed.\r\n\r\nIs there any way to update Keybase without storing your private key in the cloud?"},"comment":{"url":"https://api.github.com/repos/keybase/keybase-issues/issues/comments/242122406","html_url":"https://github.com/keybase/keybase-issues/issues/1636#issuecomment-242122406","issue_url":"https://api.github.com/repos/keybase/keybase-issues/issues/1636","id":242122406,"user":{"login":"atoponce","id":699572,"avatar_url":"https://avatars.githubusercontent.com/u/699572?v=3","gravatar_id":"","url":"https://api.github.com/users/atoponce","html_url":"https://github.com/atoponce","followers_url":"https://api.github.com/users/atoponce/followers","following_url":"https://api.github.com/users/atoponce/following{/other_user}","gists_url":"https://api.github.com/users/atoponce/gists{/gist_id}","starred_url":"https://api.github.com/users/atoponce/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/atoponce/subscriptions","organizations_url":"https://api.github.com/users/atoponce/orgs","repos_url":"https://api.github.com/users/atoponce/repos","events_url":"https://api.github.com/users/atoponce/events{/privacy}","received_events_url":"https://api.github.com/users/atoponce/received_events","type":"User","site_admin":false},"created_at":"2016-08-24T16:12:25Z","updated_at":"2016-08-24T16:12:25Z","body":"Also:\r\n\r\n    # gpg --no-default-keyring --keyring /root/.keybase-installer/keyring/pubring.gpg --secret-keyring /root/.keybase-installer/keyring/secring.gpg --trustdb-name /root/.keybase-installer/keyring/trustdb.gpg --check-trustdb \r\ngpg: no ultimately trusted keys found\r\n\r\nIt seems the broken trustdb is whatever is getting created in `/tmp/`."}}
{"actor":{"display_login":"atoponce"}}