[OSX] After update, have to re-provision same laptop
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I let Keybase update today, on the same laptop I used to set up my keybase account yesterday. Now, when I launch the client I'm prompted to either create an account, or to log in. If I select log in, and enter my username, I'm asked to pick which device I want to connect from: my laptop or a paper key.
Selecting my laptop prompts me to run keybase device add and enter a code; however, keybase device add times out, every time:
$ keybase device add
▶ ERROR Operation timed out
If I use my paper key, I can provision this same laptop as a new device. Neat? Have I misunderstood something about how this works, or is something hinky?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported OS X update flow and the keybase device add command that times out. Trace the existing-device provisioning path and compare it with provisioning through the paper key. Done means an updated client can reconnect the same laptop without requiring it to be provisioned as a new device.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100