Your concerns are noted, and the upstream ecryptfs kernel developers are working on it. They have working prototypes, and are submitting to -mm as soon as possible. We absolutely understand, respect, and desire the additional security that will bring.
I disagree with your points that this should be disabled or removed, and that the feature is useless. When you use gpg to encrypt a single file, does it encrypt the file name as well? No, it does not. We're not forcing anyone to use this feature. And we're not dictating what data goes into ~/Private. This entirely an opt-in program. I'm attaching the private half of an ssh key, pulled from the encrypted .Private directory. If you or anyone else is able to crack it, we would like to hear about it. :-Dustin ** Attachment added: "id_rsa" http://launchpadlibrarian.net/18819390/id_rsa -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
