keybase / keybase/client

Client does not sign out on the new device

Open
#7,784 0 comments 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

I just cloned my Mac from the old one to the new one using Disk Target mode & disk restore,
and Keybase didn't sign me out of the app.
Most the other apps (chrome, viber) signed me out.
I would expect this kind of a program to sign out when there is a significant change in the machine's configuration.

Keybase GUI Version: 1.0.24-20170619144856+91a6943

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 reported Disk Target mode and disk-restore migration on macOS using the Keybase GUI version named in the report. Trace how the client identifies the device and handles sign-out; done means a cloned installation signs out when the machine configuration changes significantly.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, macos
Domain
authentication, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.