On Fri, Jun 01, 2018 at 03:32:59PM +0200, Miklos Szeredi wrote: > How do you define "safely"? > > Is it safe for root to do > > cp -a /nfs/remotedir /tmp/localdir > > ? > > That's essentially what an overlayfs mount with an NFS layer does with > respect to access permissions: > > - remote files are not modifiable to anyone, unless server allows > > - remote files *readable to root* will provide access based on local DAC check. > > Does that need to be made clear in the docs? Surely. But it does NOT > mean it's dangerous or that it's not useful with an arbitrary NFS > server We should definitely have clear documentation, but despite that, in practice lots of people *will* be surprised when permissions are enforced differently after copy-up, and those surprises may well have unpleasant implications. And the differences will depend on details of the server implementation, which makes documenting the behavior and giving people the correct expectations that much more complicated. > (although my guess is that 99% will involve knfsd). Why is that? There are a *lot* of Linux clients out there talking to non-knfsd servers. I wouldn't have thought knfsd is even a majority--but of course it depends very much on what kind of use exactly we're measuring. And I don't have any numbers. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
