Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confidentiality of filename and metadata #6

Closed
MeanMangosteen opened this issue Mar 6, 2019 · 5 comments
Closed

Confidentiality of filename and metadata #6

MeanMangosteen opened this issue Mar 6, 2019 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@MeanMangosteen
Copy link
Contributor

The filename and a file's metadata (size, date modified, permission) should be encrypted. This is because these entities can leak information about the file, which is meant to be secret, even though the file content is encrypted.

I think to start with, just the filename can be encrypted, we can deal with encrypted metadata after.

Both CryFS and EncFS encrypt filenames, however, only CryFS encrypts metadata aswell. It needs to be revisited on how they accomplish this.

@MeanMangosteen
Copy link
Contributor Author

VeraCrypt encrypts both filename and metadata too.
https://github.com/veracrypt/VeraCrypt.

@CMCDragonkai
Copy link
Member

CMCDragonkai commented Mar 6, 2019 via email

@MeanMangosteen MeanMangosteen added the research Requires research label Mar 7, 2019
@CMCDragonkai
Copy link
Member

This is addressed in #8? If so, we can close this.

@CMCDragonkai CMCDragonkai added enhancement New feature or request and removed research Requires research labels Apr 19, 2019
@robert-cronin
Copy link
Contributor

One way to implement encrypted file structure would be to encrypt the directory
and file names in the lowerfs so that at each level in the heirachy, EFS will
have to decrypt in order to continue its traversal. This would mean O(n) on
every directory traversal.

Another way would be to store the entire directory listing as a unit of plaintext
that gets decrypted into ciphertext. This requires the directory listing to be
consistent. This comes with some possible errors, e.g. it will fail if the
underlying folder structure changes.

@robert-cronin robert-cronin self-assigned this May 12, 2020
@robert-cronin
Copy link
Contributor

Closing on account of migration to gitlab

CMCDragonkai pushed a commit that referenced this issue May 7, 2021
Managing UpperFS Permissions and Metadata in the LowerFS

Closes #38, #8, #6, and #2

See merge request MatrixAI/Engineering/Polykey/js-encryptedfs!42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

3 participants