Thanks, that is very good you already implemented the path to be configurable.
The issue here is more about the particular default, though. People using the "user private group" scheme (used and advocated for user collaboration in debian/ubuntu system, but still broken due to some minor bugs) use "priv", "private" or "Private" to indicate subdirectories with permissions that make anything within them private to them or the group in the filesystem. Now, if people start using ecryptfs and ecryptfs uses "Private" as default instead of say "Encrypted", the ecryptfs feature doesn't look very distinguishable or descriptive from the users point of view browsing his filesystem. Thats why I'd suggest ecryptfs to default to a more crypt oriented default directory name, it should be correctly describing what it does for all cases. Of course granting only "private" permissions for the on-disk-encrypted "Encrypted" directory in the filesystem would continue to be a sane default. -- The default ~/Private name is not very clear https://bugs.launchpad.net/bugs/575096 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
