** Description changed: Originally discovered when installing latest git from original sources, see discussion here http://marc.info/?t=133882478900001&r=1&w=2 cat /proc/version_signature Ubuntu 3.2.0-25.40-generic 3.2.18 + + This bug is exposed when the eCryptfs mount options do not include '-o + acl', but the lower filesystem's mount options do include the 'acl'. + This results in the MS_POSIXACL flag *not* being set in the eCryptfs + super_block.s_flags. This flag is what the VFS checks in do_last() when + deciding if the current umask should be applied to a newly created + inode's mode or not. When POSIX acl's are in use, the umask is + incorrectly applied to new eCryptfs inodes. Test case from Jeff King (the setfacl command was incorrect in the original email from Jeff): setfacl -dm m:rwx . perl -MFcntl -e 'sysopen(X, "a", O_WRONLY|O_CREAT, 0444)' umask 077 perl -MFcntl -e 'sysopen(X, "b", O_WRONLY|O_CREAT, 0444)' getfacl a b On ext4, both files will have the read bit set in the mask. On ecryptfs, "b" will have an empty mask. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ecryptfs-utils 96-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu9 Architecture: amd64 Date: Tue Jun 5 22:37:36 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: ecryptfs-utils UpgradeStatus: Upgraded to precise on 2012-02-18 (108 days ago)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1009207 Title: Default ACL masks not working properly in eCryptfs To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1009207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
