On Fri, May 3, 2019 at 11:35 AM J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote:
>
> On Thu, May 02, 2019 at 12:02:33PM +1000, NeilBrown wrote:
> > Silently not copying the ACLs is probably not a good idea as it might
> > result in inappropriate permissions being given away. So if the
> > sysadmin wants this (and some clearly do), they need a way to
> > explicitly say "I accept the risk".
>
> So, I feel like silently copying ACLs up *also* carries a risk, if that
> means switching from server-enforcement to client-enforcement of those
> permissions.
That's not correct: permissions are checked on the overlay layer,
regardless of where the actual file resides. For filesystems using a
server enforced permission model that means possibly different
permissions for accesses through overlayfs than for accesses without
overlayfs. Apparently this is missing from the documentation and
definitely needs to be added.
So I think it's perfectly fine to allow copying up ACLs, as long as
the ACL is representable on the upper fs. If that cannot be ensured,
then the only sane thing to do is to disable ACL checking across the
overlay ("noacl" option).
Thanks,
Miklos
