keybase / keybase/client

Unable to enter "Keybase passphrase" to add second desktop client (Ubuntu)

Open
#4,634 19 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

Adding a second desktop client (ubuntu)
Installed keybase, ran it, typed a long passphrase in my first client
GUI shows me a list of private folders I can not get into. There's a dialog labeled "Pinentry" that says:

Please enter your Keybase passphrase to unlock the secret key for Device [...] Reason: you must sign your new paper key

It will not accept my keybase passphrase. I tried putting in my paper key, but nada. I am totally locked out on the second computer:

djh@djh-dell-p5510:~$ ls /keybase/private
dannyman  dannyman,genos,rjmb  dannyman,rjmb
djh@djh-dell-p5510:~$ ls /keybase/private/dannyman

Used to be an error. Now it just hands.

my log id: 1be4929a0457ca5a723e3a1c

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 with the Ubuntu desktop client's Pinentry dialog and the provided log ID 1be4929a0457ca5a723e3a1c, then reproduce the passphrase rejection while accessing /keybase/private/dannyman. Done means the second client accepts the Keybase passphrase and the private folder becomes accessible.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, ubuntu
Domain
desktop, 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.