The kernel patches required to solve this problem were accepted by Andrew Morton into the Linux -mm experimental tree. They're going to bake there for a little while and hopefully be merged by Linus into a stable Linux kernel release soon. At which point, we will ask the Ubuntu kernel team to bump kernel versions for Jaunty.
Please sit tight a little longer ;-) And if you're really brave, go compile your own -mm kernel on a test machine and try it out ;-) :-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. _______________________________________________ Mailing list: https://launchpad.net/~ecryptfs Post to : [email protected] Unsubscribe : https://launchpad.net/~ecryptfs More help : https://help.launchpad.net/ListHelp
