-
Notifications
You must be signed in to change notification settings - Fork 3
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
Comments
VeraCrypt encrypts both filename and metadata too. |
We can revisit metadata encryption later. Hopefully no path dependency.
…On 6 March 2019 14:49:52 GMT+11:00, ll-aashwin-ll ***@***.***> wrote:
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.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#6
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
This is addressed in #8? If so, we can close this. |
One way to implement encrypted file structure would be to encrypt the directory Another way would be to store the entire directory listing as a unit of plaintext |
Closing on account of migration to gitlab |
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.
The text was updated successfully, but these errors were encountered: