keybase / keybase/client

login: ERROR missing paper key in login context

Open
#9,497 8 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 installed the linux client on an Ubuntu 16.04 machine, but used a name I didn't want.

keybase version 1.0.35-20171110170110+68245d46b

I removed the device through the web interface and figured I'd log back in on the client again but use a new name. Now when I try to log in:

Your keybase username or email address: USERNAME
Please enter the Keybase passphrase for USERNAME (6+ characters): 
In order to authorize this installation, keybase needs to sign this installation
with your GPG secret key SECRETKEY.

You have two options.

(1) Keybase can use GPG commands to sign the installation.

(2) Keybase can export your secret key from GPG and save it to keybase's local encrypted
    keyring. This way, it can be used in 'keybase pgp sign' and 'keybase pgp decrypt'
    going forward.
Which do you prefer?: 1


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



Enter a public name for this device: mother
▶ ERROR missing paper key in login context

Not sure what to do here?

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

The report names the Linux client, Ubuntu 16.04, and the interactive login flow but no source file or test. Start by reproducing the login after removing the device through the web interface, using the captured version and inputs. Done means the flow no longer ends with “missing paper key in login context” or the required recovery path is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, linux, ubuntu
Domain
authentication, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.