Bug 2126879 - [BACKPORT] init: Add tunable for systemd to create all its mountpoints
Summary: [BACKPORT] init: Add tunable for systemd to create all its mountpoints
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: selinux-policy
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Zdenek Pytela
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-14 16:11 UTC by Pat Riehecky
Modified: 2023-08-04 20:52 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-134329 0 None None None 2022-09-19 14:27:50 UTC

Description Pat Riehecky 2022-09-14 16:11:34 UTC
Description of problem:
When using TemporaryFileSystem=/:ro and then the suggested
BindReadOnlyPaths=/dev/log /run/systemd/journal/socket /run/systemd/journal/stdout
to generate an isolated runtime with logging, selinux needs to permit
init_t to create files under the root_t and syslogd_var_run_t type.
This allows systemd to spin up a mount namespace for service isolation.

Version-Release number of selected component (if applicable):
selinux-policy-34.1.41-1.el9.noarch

How reproducible:
100%

Steps to Reproduce:
1. Try to use systemd's private mount isolation
2. get selinux errors
3.

Actual results:

selinux errors

Expected results:


For non-security mounting, only dir and file access are added, as these are the only ones allowed in the mounton call.


Additional info:

https://github.com/SELinuxProject/refpolicy/pull/535

Comment 1 Zdenek Pytela 2022-09-19 14:06:08 UTC
Pat,

Thanks for reporting. As a first response I need to state that the referred commit is not one we can backport from refpolicy right away. We are currenly discussing with systemd folks how to approach issues like this in general.


Note You need to log in before you can comment on or make changes to this bug.