keybase / keybase/client

KBFS requesting to rekey

Open
#6,990 30 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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I have a issue using the KBFS: it keeps asking me to "turn on" my paper key to rekey my private folders
I also have the option to enter my paper key, and when I enter it (the original marriage) it tells me that it is rekeying and it is forever like having a child.
After this nothing seems to happen anymore. The rekey option stays and I can't use the folders.
Trying to acces them I get a notification: was modified by or revoked by a bad device.
Is there a way to reset my private folders so I can use them again? There is no data in them.
Thank you for your amazing work and thank you in advance,

Cyllos

my log id: 358357599b099e891c28181c
-----BEGIN PGP SIGNATURE-----
Version: Keybase OpenPGP v2.0.70
Comment: https://keybase.io/crypto

wsFcBAABCgAGBQJZF2eEAAoJEPM5kl6NoC2HQKgP/1q0oFXNZasLyCjophtdlK+Y
GKO/9sr1eBcyb2ahbOhfPwNQ54SJECIhWZap5cUEgDQxleknbi2qQoKmsbHGwpJp
ngaM4aNMpCMLLw3EBYkyJXN7Js2SS/zmjh6HA7ZwD0XdHmCgh8PzFQ6LfhZOcTwu
AFyDv69Mc/qDCZJPlrurux+D9P6YoytEludAOPWMAsmG6e5gLSAQd5mceGov3ca4
q0F9/XEBGXYSCSPPn2griYM2HrUVEragH+qRrzXHRF7AeM4/vjDRybZSTHy8Jnjc
qqGacvYo6EkdH+kYi3ZGC2qxpBTRvKo7KCku0UxCgd61MJOwsBomh+JhgGj8wRzX
8pzoJVOwu6va0yr9kG2Wr5DdRIvfD4Ss1UR1ghfm+GZSqKX4OBxPyU+UDdWeKlmY
yePlklAqcqPTFnjF8IYcxo0ogyL4xyKWRgKsiru3Imm84tm1SSab48QtsGn5t0uV
Jq10V7VuCZnz/P+C5qPhpN/FlSeQOBKZPbQAGWUfjEAI0gh3CKztVpW5uemnDEqi
saiHDrz5zn4vEjBvfq71N8/Wz59LNMbASDI4qK+ActczrNqpHEV5kmFaGRJZF3HP
mymPkFTZq1fWJR1AJUdj8+KVCIv2K9Xxl3mdxAZTOEvb7rcPaiikoXzX6b7bFJNA
pzydvju9canxouDHrsUs
=ibA8
-----END PGP SIGNATURE-----

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

No source file, test, or entry point is identified; begin by investigating the KBFS rekey flow using the provided log ID and the paper-key scenario. Done means private folders can be accessed after rekeying without the recurring rekey prompt or the bad-device notification.

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.