** Description changed: Binary package hint: ecryptfs-utils What ecryptfs does with ~/Private really is (on-disk) encrpytion. Private in terms of permissions is a different thing. Using another - default, more like ~/Encrypted would avoid misconceptions, and avoid - conflicting with ~/priv or ~/Private directories that are not (on-disk) - encrypted, but private to the the particular user in the system. + default for the ecryptfs directory, more like ~/Encrypted would avoid + misconceptions, and avoid conflicting with ~/priv, ~/private or + ~/Private directories that are not (on-disk) encrypted, but private to + the the particular user in the system. - Managing access permissions among users is explained at + Managing access permissions among users in an easy directory based manner with the "user private groups" used in debian/ubuntu is explained at https://wiki.ubuntu.com/MultiUserManagement - I see the cryptfs actually seems to get mounted with private (rwx------) - permissions. But not every private directory is a crypted directory and - ecryptfs' ~/Private does not point out that it is actually encrypted on - disk. + I see the on-disk-encrypted direcetory actually seems to get mounted + with private (rwx------) permissions. But we can not assume every + private directory is on-disk-encrypted and ecryptfs' ~/Private does not + point out that it is actually encrypted on disk. + + Please change the default directory name ecryptfs uses to something more + crypt specific.
** Summary changed: - The default ~/Private name is confusing (general permissions) but not crypt specific + The default ~/Private name is ambiguous (general permissions) but not crypt specific ** Description changed: Binary package hint: ecryptfs-utils What ecryptfs does with ~/Private really is (on-disk) encrpytion. Private in terms of permissions is a different thing. Using another default for the ecryptfs directory, more like ~/Encrypted would avoid misconceptions, and avoid conflicting with ~/priv, ~/private or ~/Private directories that are not (on-disk) encrypted, but private to the the particular user in the system. Managing access permissions among users in an easy directory based manner with the "user private groups" used in debian/ubuntu is explained at https://wiki.ubuntu.com/MultiUserManagement I see the on-disk-encrypted direcetory actually seems to get mounted with private (rwx------) permissions. But we can not assume every - private directory is on-disk-encrypted and ecryptfs' ~/Private does not - point out that it is actually encrypted on disk. + private directory is on-disk-encrypted. And ecryptfs' current ~/Private + default does not point out that it is actually encrypting things on the + disk. Please change the default directory name ecryptfs uses to something more crypt specific. -- The default ~/Private name is ambiguous (general permissions) but not crypt specific 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
