Comment 12 for bug 264977

Revision history for this message
Dustin Kirkland  (kirkland) wrote : Re: [Bug 264977] Re: Filenames in ~/.Private are not encrypted

On Thu, Oct 30, 2008 at 10:22 AM, Sebastian Abate
<email address hidden> 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