ecryptfs team mailing list archive

[Chris Roddy <cmr@xxxxxxxx>]

I understand that there are challenges to implementing encryption of the
file names, but as it stands now I would describe these tools as
unreleasable. I encourage the maintainers to withdraw this package from
the distribution until this glaring design defect can be corrected.

An encrypted directory that leaks the names, directory structure, and
file sizes in plain text is almost completely useless, and is in many
ways worse than simply trying to hide them with dotfiles and
misdirection -- at least in that case, I'm not waving a gigantic red
flag that says "hey! here's all my secret shit! here's how i keep it
organized, what i call it, and how big each file is!"

-- 
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: Confirmed

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.