"Please open one of your other computers to unlock /keybase/private/" when trying to read shared private folder
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I got an email saying a new encrypted folder is waiting for me, apparently between me and my friend. When I ls /keybase/private/him,me, I get a notification telling me to open one of my other computers to unlock /keybase/private. This is the first and only computer I've installed Keybase on.
my log id: 5c407cad0b3849b0fa01081c
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 by reviewing the issue's log ID and reproducing ls /keybase/private/him,me on a first Keybase installation. Trace the unlock behavior for the shared private folder; done means the folder can be read without incorrectly requiring another computer, with the relevant failure verified against the logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100