keybase / keybase/client

Can't Add Device With Paper Key

Open
#25,115 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 haven't logged into my account since probably 2018 (when files were first added), and now I'm trying to add the program to my computer but it is saying I need to verify with either that computer or that device I used back then, but then all the message prompts say "if you don't have any of these devices or a paper key" but I do have the paper key still, I just don't have those devices... however, I don't see anywhere to input it.

I tried using the CLI and get this:

C:\Users\teamc>keybase login --paperkey "words that are being replaced for security" teamcoltra

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?

        1. [mobile]     Honor8
        2. [computer]   Windoze10
        3. I don't have access to any of these devices.

Choose a device: 2


************************************************************
* Name your new device!                                    *
************************************************************



Enter a public name for this device: NEW_DEVICE


Type this verification code into your other device:

        I SHOULD PROBABLY REPLACE THESE TOO

If you are using the command line client on your other device, run this command:

        keybase device add

It will then prompt you for the verification code above.

- ERROR interrupted

I've also tried using the program as I said and only see this:

image

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 recovery flow with keybase login --paperkey and compare it with the desktop flow shown in the issue. Trace how the CLI handles choosing “I don't have access to any of these devices” and how keybase device add is invoked. Done means an existing paper key can provision a new device without access to the old devices, with consistent CLI and desktop behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.