keybase / keybase/client

Locked myself out after trying to rename my device name

Open
#5,776 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

This might be a little tricky to explain, but I'll try my best:

After I logged into the Keybase OSX app, I was asked to give a name to my device. I entered my device name but right after clicking submit, I noticed it was supposed to be a public name. I was prompted with the paper key code but I just clicked back because I wanted to change the device's name.

First issue: Immediately after clicking back to change the device's name, I got to what I think is the main section of the app.

I then clicked my device trying to rename it, but I couldn't. So I decided to click to remove its acess, thinking I'd be prompted to add it again.

Second issue: After trying to log in, I'm getting a message Unknown error: eldest called on user with existing eldest KID. I don't have kids, Keybase friends. 😅

my log id: 2f092984344aeedcb5b1421c

I hope someone can help getting access back to it through the app and hopefully the bug's solved and/or we can change a device's name afterwards.

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the OS X app flow described here: rename the device, go back, remove its access, and try to sign in again. Use log id 2f092984344aeedcb5b1421c to inspect the reported “eldest called on user with existing eldest KID” failure. Done means the flow no longer locks the user out and device naming or recovery behaves as intended.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, macos
Domain
authentication, desktop-dev, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.