keybase / keybase/client

Request to rekey private folder

Open
#12,285 20 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi

I am unsure how to go about rekeying my private folder. Unfortunately I no longer have access to the old device nor the old paper key for rekeying, and using a new paper key does not seem to work.
I have submitted a log:
Success! Your log ID is:

ca00cc46a18404ef04e8b11c

Here's a URL to submit new bug reports containing this ID:

https://github.com/keybase/client/issues/new?body=[write%20something%20useful%20and%20descriptive%20here]%0A%0Amy%20log%20id:%20ca00cc46a18404ef04e8b11c

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 reviewing the issue's rekeying scenario and the submitted log ID ca00cc46a18404ef04e8b11c. Determine which private-folder recovery path is expected when both the old device and paper key are unavailable; done would require a confirmed recovery behavior and tests for the reported case.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.