ecryptfs team mailing list archive

[Dustin Kirkland <dustin.kirkland@xxxxxxxxx>]

On Thu, Oct 30, 2008 at 10:22 AM, Sebastian Abate
<sebastianabate@xxxxxxxxx> wrote:
> What about an option to use an encrypted filesystem image, instead of a
> directory? Then the image could be loop mounted on the ./Private
> directory, just like TrueCript does. I know this is only practical for a
> private directory, and not in a shared one, but the option could help
> mitigate this situation.

A loop-mounted encrypted image would disallow incremental (rsync)
backups of the encrypted data, which is one of the key design points
of our Encrypted ~/Private Directory.

TrueCrypt has some serious licensing issues:
 * http://fedoraproject.org/wiki/ForbiddenItems#TrueCrypt

Encrypted filenames are coming to eCryptfs.  Give us a little more time.

:-Dustin

-- 
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.