Authorize or import from existing Keybase
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I'm on Linux. Recently I changed my laptop. I no longer have the old one, but have a copy of my old disk on my new one. I was logged on Keybase on my old laptop so I should still have everything that is needed to authenticate.
Can I use it to authorize my new laptop?
I tried to copy `old_laptop_home_copy/.config/Keybase/` to `~/.config/Keybase`, but it's not enough:
```
> keybase id
▶ ERROR Login required: to identify without specifying a user assertion
> keybase login
Your keybase username: ***
▶ WARNING Failed to reach system keyring (primary store (system keyring): failed to create item: No such interface “org.freedesktop.Secret.Collection” on object at path /org/freedesktop/secrets/collection/login), falling back to secondary store (file-based secret store (see https://keybase.io/docs/crypto/local-key-security)). [tags:ENG=***,LOGIN=***]
The device you are currently using needs to be provisioned.
Which one of your existing devices would you like to use
to provision this new device?
```
What should I try?
Contributor guide
No contributing guide indexed for this repository
Research direction
The report centers on ~/.config/Keybase/, `keybase id`, and `keybase login` on Linux; begin by reproducing the copied-config flow and inspecting the shown system-keyring and provisioning errors. Done would require a documented or implemented recovery path that lets the new laptop authenticate, but the issue does not identify a target file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100