Hi John, Wow, thanks for stepping up and taking a crack at this!
Just a few words of feedback on your concerns about leaking that long filenames exist... I agree that meta leakage is suboptimal, and should be avoided when possible. On the other hand, this sort of thing happens elsewhere with eCryptfs. File permissions, owners, and timestamps all must be stored in the clear, as well as file structures. That's sometimes enough to identify which file is which. I've always preferred calling eCryptfs' filename "encryption" -> "obfuscation", which is a more accurate description, in my opinion. File contents are most certainly encrypted, in a rather strong manner. File names and file metadata are merely obfuscated. ie, the filename is not immediately available, but enough metadata about the file (perms, owners, timestamps, rough sizes) to make reasonable guesses as to real filenames in a regularly laid out filesystem. Dustin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/344878 Title: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry) -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
