ecryptfs team mailing list archive

[Guillermo Pérez <bisho@xxxxxxxxxxxxxxxxxxxxx>]

For network-shared drives I understand the need of maintaining clean
filenames (or at least use the same key for encrypt them) to avoid
collisions.

But for user directories, there will be only one key, the key of the
user, so that one can be used for encrypt filenames. encfs does this.

It could be an option like "one-user crypted directory". Implementing
this will be a sort path to the real implementation the people from
eCryptfs are working on, and it will be faster to offer to the public.

-- 
Filenames in ~/.Private are not encrypted
https://bugs.launchpad.net/bugs/264977
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in eCryptfs - Enterprise Cryptographic Filesystem: Unknown
Status in “ecryptfs-utils” source package in Ubuntu: Triaged

Bug description:
As Per https://wiki.ubuntu.com/EncryptedPrivateDirectory I created a private directory.
Ii mounted it, then put some files in it.
Then unmounted the Private dir.
~/Private contains only "THIS DIRECTORY HAS BEEN UNMOUNTED TO PROTECT YOUR DATA --  Run mount.ecryptfs_private to mount again"


~/.Private still contains all the private files, albeit the contents are indeed encrypted... 

I had expected that the filesystem of ~/Private would also be encrypted so that a potential data thief would not even know what files I have on my system.