overlayfs override_creds=off
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v13 Latest posting 2/20 of 5 patches 0 repliesNew
- v13 posting 1/25 patches 1 replySuperseded
- v125 patches 1 replySuperseded
Earlier versions · 6
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v11 | 4 patches | 0 replies | Superseded | |
| v10 | 5 patches | 15 replies | Superseded | |
| v9 | 2 patches | 0 replies | Superseded | |
| v8 | 2 patches | 10 replies | Superseded | |
| v7 | 2 patches | 1 reply | Superseded | |
| v6 | 2 patches | 5 replies | Superseded |
Changes in v13 from the cover letter
- add flags argument to __vfs_getxattr
- drop GFP_NOFS side-effect
Patches in v13 posting 2/2 No applies recorded yet
None of the 5 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v13 yet.
Cover letter [PATCH v13 0/5] overlayfs override_creds=off
Patch series:
overlayfs: check CAP_DAC_READ_SEARCH before issuing exportfs_decode_fh Add flags option to get xattr method paired to __vfs_getxattr
overlayfs: handle XATTR_NOSECURITY flag for get xattr method
overlayfs: internal getxattr operations without sepolicy checking
overlayfs: override_creds=off option bypass creator_cred
The first four patches address fundamental security issues that should be solved regardless of the override_creds=off feature.
on them).
The fifth adds the feature depends on these other fixes.
By default, all access to the upper, lower and work directories is the recorded mounter's MAC and DAC credentials. The incoming accesses are checked against the caller's credentials.
If the principles of least privilege are applied for sepolicy, the mounter's credentials might not overlap the credentials of the caller's when accessing the overlayfs filesystem. For example, a file that a lower DAC privileged caller can execute, is MAC denied to the generally higher DAC privileged mounter, to prevent an attack vector.
We add the option to turn off override_creds in the mount options; all subsequent operations after mount on the filesystem will be only the caller's credentials. The module boolean parameter and mount option override_creds is also added as a presence check for this "feature", existence of /sys/module/overlay/parameters/overlay_creds
---
v13:
- add flags argument to __vfs_getxattr
- drop GFP_NOFS side-effect
v12:
- Restore squished out patch 2 and 3 in the series, then change algorithm to add flags argument. Per-thread flag is a large security surface.
v11:
- Squish out v10 introduced patch 2 and 3 in the series, then and use per-thread flag instead for nesting.
- Switch name to ovl_do_vds_getxattr for __vds_getxattr wrapper.
- Add sb argument to ovl_revert_creds to match future work.
v10:
- Return NULL on CAP_DAC_READ_SEARCH
- Add __get xattr method to solve sepolicy logging issue
- Drop unnecessary sys_admin sepolicy checking for administrative driver internal xattr functions.
v6:
- Drop CONFIG_OVERLAY_FS_OVERRIDE_CREDS.
- Do better with the documentation, drop rationalizations.
- pr_warn message adjusted to report consequences.
v5:
- beefed up the caveats in the Documentation
- Is dependent on
"overlayfs: check CAP_DAC_READ_SEARCH before issuing exportfs_decode_fh" "overlayfs: check CAP_MKNOD before issuing vfs_whiteout"
- Added prwarn when override_creds=off
v4:
- spelling and grammar errors in text
v3:
- Change name from caller_credentials / creator_credentials to the boolean override_creds.
- Changed from creator to mounter credentials.
- Updated and fortified the documentation.
- Added CONFIG_OVERLAY_FS_OVERRIDE_CREDS
v2:
- Forward port changed attr to stat, resulting in a build error.
- altered commit message.