overlayfs access checks on underlying layers
sds at tycho.nsa.gov
Mon Mar 4 18:44:43 UTC 2019
On 3/4/19 12:01 PM, Mark Salyzyn wrote:
> On 11/29/2018 05:49 AM, Vivek Goyal wrote:
>> So will override_creds=off solve the NFS issue also where all access will
>> happen with the creds of task now? Though it will stil require more
>> priviliges in task for other operations in overlay to succeed.
> NFS problems seems to have ended the discussion, too many stakeholders?
> too many outstanding questions?
> Do we accept the limitations of the override_creds patch as is, and then
> have the folks more familiar with the NFS scenario(s) build on it?
> After looking at all this discussion, it feels like a larger audited
> rewrite of the security model is in order and override_creds=off may be
> a disservice (although expediently deals with Android's needs) to a
> correct general solution. I admit I have little idea where to go from
> here for a general solution.
> As far as I see it, the model of creator && caller credentials is a
> problem for any non-overlapping (MAC) privilege models. This patch
> allows one to drop any creator privilege escalation, re-introducing the
> "caller" to the lower layers.
> As such I would expect a better model is to _always_ check the caller
> credentials again in the lower layers, and only check the creator
> credentials, some without caller credentials, for some special cases?
> Change an && to an || for some of the checks? What are those special
> cases? I must admit _none_ of those special cases need attention in the
> Android usage models though making it difficult for me to do the fight
> thing for the associated stakeholders.
As I recall, there were multiple problems with using current process'
creds for the operations on the lower/upper/work directories:
- Some overlayfs operations on the lower/upper/work directories required
privilege (capabilities) that the current process might lack, e.g. to
set ownership and the like on upper or work files, to set special xattrs
used internally by overlayfs for whiteouts or similar purposes, to act
on files within the work dir which was inaccessible to the current
process to prevent accessing files in an incomplete state, etc.
Originally that was handled by temporarily elevating the effective
capabilities around the privileged operation in the overlayfs code but
that didn't help with the SELinux or other LSM capability checking that
was triggered upon the capable calls. Without some change there you'd
have to allow all client process domains all of the relevant
capabilities in policy, greatly increasing their privileges.
- The original logic was checking access to the lower dir/files in the
context of the current process when performing some operation that
modifies the file content or metadata, thereby triggering a SELinux/LSM
write or similar check, even though the actual data or metadata
modification occurs to the copied-up file instead and does not affect
the lower dir/files. That was preventing making the lower dir/file
labels read-only to the client processes in the policy, which was
desired for the container use case.
You'd need to solve those problems in some way.
> The lower privileged application access to the directory cache inherited
> by other callers troubles me (not for Android, but in general) and feels
> troublesome (flush out the directory cache? how to tag the privileges
> associated with the current instance of the directory cache?). Some
> operations (eg: delete a file for incoming, create mknod in upperdir)
> are special cases requiring the checking of caller credentaisl to
> function (not a problem for Android as the caller that deletes a file
> just so happens to have the necessary privileges).
> Also, mount namespaces (in upper, lower, etc), how will they affect this
> all, is there a need for more attention to this as well?
> -- Mark
More information about the Linux-security-module-archive