Encrypted filenames are listed in the project plan, and in the FAQ there is a example given and a hint that the planned solution at this point is to have a single key per directory for encrypting the filenames. I wonder if anyone could explain in more detail what problem encrypted filenames are intended to solve? I'm concerned that this solution is overly complex when you could use DAC or SELinux permissions to control access to a directory and then just hide any secret filenames below that barrier.
thanks -matt ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ eCryptfs-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ecryptfs-users
