On Thu, Oct 30, 2008 at 10:22 AM, Sebastian Abate <[EMAIL PROTECTED]> 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
