keybase / keybase/client

no passphrase required to read Folders

Open
#8,654 5 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

I've added a few files under the KB filesystem:

/keybase/
├── private/
│   └── florinandreicurb/
│       └── private-test.txt
├── public/
│   └── florinandreicurb/
│       └── test.txt
└── team/
    └── XXXXXXXX/
        └── test.txt

After restarting my laptop, I was able to access those files without being prompted for any password. That shifts the burden of security onto the laptop's account password and disk encryption.

I could not do the same test on Android because KB is not exposing the folders to the mobile app yet.

So technically this is either the same as storing those files on your laptop in plain text (if a local plaintext copy is stored all the time in /keybase) or nearly the same (if the Keybase helper service is required to run to access those files). In the first case, disk encryption is mandatory to protect the files; in the second case, a strong account password on the laptop is mandatory.

Either way, I would feel a lot better if KB asked you to enter your GPG password at least once to read those files.

Perhaps this is just because the Folders feature is pretty new?


Or, in case I misunderstand the way things work: with Keybase, how do I regain the same level of protection I had when I was using GPG? How do I make sure the secrets stored in KB are protected by more than just the account password on my laptop? (or the PIN on my phone)

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 reproducing access to the listed /keybase/private, /keybase/public, and /keybase/team folders after restarting the laptop, and determine whether a local plaintext copy or the Keybase helper service provides access. No source file or test is named; done would require a clear security decision and documented behavior for protecting folder contents with more than the device account password or PIN.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.