Can't login / attemt to use wrong device id when trying to login as second user.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
System: Ubuntu
I have two users:
$ cat ~/.config/keybase/config.json
{
"current_user": "phaiax",
"maintenance": {
"phaiax": {
"bug_3964_repair_time": "1498817280394"
}
},
"users": {
"methusalem": {
"device": "206b51...",
"id": "e170...",
"name": "methusalem",
"salt": "52b..."
},
"phaiax": {
"device": "691dc...",
"id": "634...",
"name": "phaiax",
"salt": "bd9..."
}
}
}
When I try to login as phaiax using the GUI, I get this error:
Error: SecretSyncer: no device found for ID=206b5...
This is the apparently the device id of methusalem, not the one of the selected user.
I can login using the comand shell.
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 with the GUI login flow and the users/current_user entries in ~/.config/keybase/config.json; compare the selected user's device ID with the ID used by SecretSyncer. Reproduce the GUI login for phaiax and compare it with the working command-shell login; the issue is resolved when the GUI uses the selected user's device and login succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, ubuntu
- Domain
- authentication, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100