KBFS drive is empty, md-server: No secret key available
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Keybase GUI Version: 1.0.18-20170216112451+a5b6199
I updated Keybase on a computer that previously had the old command-line only client on it. After a reboot, I was still signed in, but the KBFS drive did not have the content I'd expect. Instead, I see a kbfs.error.txt file containing:
md-server: No secret key available
It's also probably interesting that I wasn't prompted to enter my secret key. On my other computer I got a challenge for my secret key with KBFS being given as the reason. If I run a command like keybase pgp sign I get prompted for a password every time. This behavior seems different that I'd expect from my other computer and previous versions.
My log ID 66b9b2d3fe362e1c7d0b481c.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with kbfs.error.txt, log ID 66b9b2d3fe362e1c7d0b481c, and the keybase pgp sign command; compare the upgrade and reboot path with the other computer that prompted for the secret key. Done means KBFS shows the expected content and the client handles the required secret-key prompt consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100