keybase / keybase/keybase-issues
Failed to get track token (osx cli)
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Got a weird error during `keybase login`, although everything seemed to work out
> Your keybase username or email address: xxxxxx
> In order to authorize this installation, keybase needs to sign this installation
> with your GPG secret key XXXXXXXXXXXXXX
>
> 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?: ▶ ERROR Failed to get track token%!(EXTRA libkb.IdentifyTimeoutError=Identification expired.)
> 1
> Enter a public name for this device: xxxxxxxxx
>
> You need a passphrase to unlock the secret key for....
Note: I am using Little Snitch and I may have waited too long to approve an outbound connection.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the `keybase login` flow on macOS, including the GPG signing choice and a delayed Little Snitch approval. Compare the resulting “Failed to get track token” and identification-expired output with the later successful prompts. Done means the failure cause is confirmed and the login flow handles this situation correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- authentication, cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100