touch-packages team mailing list archive

[Bib <1376443@xxxxxxxxxxxxxxxxxx>]

Please Seth could you be more clear? I can't see the difference when an admin sets a default+access acl to some directory to grant write to a group, he knows what he does. Furthermore, imagine the admin is been under so heavy load so that he didn't got time enough to regrant the group write perm to newly copied data when such a mail comes with the attached file arrives... then what???? only the new data of group members others than the recipient would survive. Then what would you think of such an admin? He didn't backed up. Should he never use chmod g+sw at all ? And what prevents a user to destroy its own past contribution to a group team, killing the job of the whole team? 
Sorry but not being native english, maybe I missed subtleties in your post.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1376443

Title:
  Default ACL not inherited as Access ACL on copy and move

Status in “coreutils” package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop 14.04 fresh default installation
  Default ACL and gid are set OK on parent folder (/srv/parent). (ext4)
  mkdir child /srv/parent
  and
  touch /srv/parent/file /srv/parent/child/file
  OK Both /srv/parent/file, /srv/parent/child/,  /srv/parent/child/file show correct same acl as /srv/parent (getfacl)

  cp -r /media/<user>/<label>/SomeTree ends in corrupted ACL where Access ACL mask::--- instead of rwx, resulting in acl set for named users and groups are ineffective. KO
  Although, default:mask::rwx is ok.

  For regular (i.e. non dir) files in the copied SomeTree,  Access ACL
  mask::r-- instead of rwx, resulting in only r out of the set
  permissions for named users and groups will survive. KO

  setfacl --set or -m reports no error

  Workaround : grant permissions to users that would not have them, eg.
  o+rX or adduser reader writersgroup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1376443/+subscriptions