Support /run/* creation for initrc_t
v3 cover Support /run/* creation for initrc_t
Due to the introduction of /run, many init scripts need to create the daemon run dirs (such as /run/udev for the udev init script). To simplify this, we introduce the "daemonrundir" attribute to which initrc_t has the necessary create_dirs_perms granted.
Changes since v2
----------------
- Complete rewrite based on feedback from mailinglist
PATCH v3 1/3 Introduce init_daemon_run_dir transformation
Due to the introduction of /run, many init scripts need to create the daemon run dirs (such as /run/udev for the udev init script). To simplify this, we introduce the "daemonrundir" attribute to which initrc_t has the necessary create_dirs_perms granted.
Then, when needed, the modules can call this interface while adding the name of the directory. This will trigger a named file transition when initrc_t creates this directory:
init_daemon_run_dir(udev_var_run_t, "udev")
will trigger
files_pid_filetrans(initrc_t, udev_var_run_t, dir, "udev")
--- policy/modules/system/init.if | 27 +++++++++++++++++++++++++++ policy/modules/system/init.te | 5 +++++ 2 files changed, 32 insertions(+), 0 deletions(-)
policy/modules/system/init.if +27 -0
@@ -417,6 +417,33 @@ interface(`init_ranged_system_domain',` ######################################## ## <summary> +## Mark the file type as a daemon run dir, allowing +## initrc_t to create it +## </summary> +## <param name="filetype"> +## <summary> +## Type to mark as a daemon run dir +## </summary> +## </param> +## <param name="filename"> +## <summary> +## Filename of the directory that the init script creates +## </summary> +## </param> +# +interface(`init_daemon_run_dir',` + gen_require(` + attribute daemonrundir; + type initrc_t; + ') + + typeattribute $1 daemonrundir; + + files_pid_filetrans(initrc_t, $1, dir, $2) +') + +######################################## +## <summary> ## Execute init (/sbin/init) with a domain transition. ## </summary> ## <param name="domain">
policy/modules/system/init.te +5 -0
@@ -29,6 +29,9 @@ attribute init_run_all_scripts_domain; # Mark process types as daemons attribute daemon; +# Mark file type as a daemon run directory +attribute daemonrundir; + # # init_t is the domain of the init process. #
@@ -242,6 +245,8 @@ init_telinit(initrc_t) can_exec(initrc_t, init_script_file_type) +create_dirs_pattern(initrc_t, daemonrundir, daemonrundir) + domtrans_pattern(init_run_all_scripts_domain, initrc_exec_t, initrc_t) manage_dirs_pattern(initrc_t, initrc_state_t, initrc_state_t)
Signature · 1 line
1.7.8.6
PATCH v3 1/3 Introduce init_daemon_run_dir transformation
Quoted 4 lines · Sven Vermeulen
Due to the introduction of /run, many init scripts need to create the daemon run dirs (such as
/run/udevfor the udev init script). To simplify this, we introduce the "daemonrundir" attribute to whichinitrc_thas the necessarycreate_dirs_permsgranted.
[...]
policy/modules/system/init.te init_telinit(initrc_t) · line 252
Quoted 9 lines
policy/modules/system/init.te +2
-0@@ -242,6 +245,8 @@ init_telinit(initrc_t) can_exec(initrc_t, init_script_file_type) +create_dirs_pattern(initrc_t, daemonrundir, daemonrundir) + domtrans_pattern(init_run_all_scripts_domain, initrc_exec_t, initrc_t) manage_dirs_pattern(initrc_t, initrc_state_t, initrc_state_t)
I seem to have a few cases where the init script is also responsible for changing the ownership of the directories (actually every time the service itself doesn't run as root), which would need the following added as well:
setattr_dirs_pattern(initrc_t, daemonrundir, daemonrundir)
(or the allow-rule).
Does it make sense to add it here as well (so allow this generally)? If not, I'd need to enhance the initrc_t domain with all the necessary *_setattr_run_dir interface calls anyhow.
Wkr,
Sven Vermeulen
PATCH v3 1/3 Introduce init_daemon_run_dir transformation
Quoted 20 lines · Sven Vermeulen
Quoted 4 lines · Sven Vermeulen
Due to the introduction of /run, many init scripts need to create the daemon run dirs (such as
/run/udevfor the udev init script). To simplify this, we introduce the "daemonrundir" attribute to whichinitrc_thas the necessarycreate_dirs_permsgranted.[...]
policy/modules/system/init.te init_telinit(initrc_t) · line 252
Quoted 9 lines
policy/modules/system/init.te +2
-0@@ -242,6 +245,8 @@ init_telinit(initrc_t) can_exec(initrc_t, init_script_file_type) +create_dirs_pattern(initrc_t, daemonrundir, daemonrundir) + domtrans_pattern(init_run_all_scripts_domain, initrc_exec_t, initrc_t) manage_dirs_pattern(initrc_t, initrc_state_t, initrc_state_t)I seem to have a few cases where the init script is also responsible for changing the ownership of the directories (actually every time the service itself doesn't run as root), which would need the following added as well:
Quoted 7 lines
setattr_dirs_pattern(initrc_t, daemonrundir, daemonrundir)(or the allow-rule).
Does it make sense to add it here as well (so allow this generally)? If not, I'd need to enhance the
initrc_tdomain with all the necessary*_setattr_run_dirinterface calls anyhow.
I'm ok with adding this.
Signature · 3 lines
Chris PeBenito Tresys Technology, LLC www.tresys.com | oss.tresys.com
PATCH v3 2/3 Use the init_daemon_run_dir interface for udev
In reply to Sven VermeulenUse the init_daemon_run_dir interface in order to allow initrc_t to create the run dirs of the udev daemon with the proper file transition.
--- policy/modules/system/init.te | 1 - policy/modules/system/udev.if | 9 +++------ policy/modules/system/udev.te | 1 + 3 files changed, 4 insertions(+), 7 deletions(-)
policy/modules/system/init.te +0 -1
@@ -834,7 +834,6 @@ optional_policy(` optional_policy(` udev_rw_db(initrc_t) - udev_generic_pid_filetrans_run_dirs(initrc_t, "udev") udev_manage_pid_files(initrc_t) udev_manage_pid_dirs(initrc_t) udev_manage_rules_files(initrc_t)
policy/modules/system/udev.if +3 -6
@@ -263,7 +263,8 @@ interface(`udev_manage_pid_dirs',` ######################################## ## <summary> -## Create directories in the run location with udev_var_run_t type +## Create directories in the run location with udev_var_run_t type. +## This method is deprecated in favor of the init_daemon_run_dir interface. ## </summary> ## <param name="domain"> ## <summary>
@@ -277,11 +278,7 @@ interface(`udev_manage_pid_dirs',` ## </param> # interface(`udev_generic_pid_filetrans_run_dirs',` - gen_require(` - type udev_var_run_t; - ') - - files_pid_filetrans($1, udev_var_run_t, dir, $2) + refpolicywarn(`$0($*) has been deprecated, please use init_daemon_run_dir instead.') ') ########################################
policy/modules/system/udev.te +1 -0
@@ -25,6 +25,7 @@ files_type(udev_rules_t) type udev_var_run_t; files_pid_file(udev_var_run_t) +init_daemon_run_dir(udev_var_run_t, "udev") ifdef(`enable_mcs',` kernel_ranged_domtrans_to(udev_t, udev_exec_t, s0 - mcs_systemhigh)
Signature · 1 line
1.7.8.6
PATCH v3 3/3 Allow initrc_t to create run dirs for dbus, mysqld and tor
In reply to Sven VermeulenUse the init_daemon_run_dir interface in order to allow initrc_t to create the run dirs of the dbus, mysqld and tor daemons with the proper file transitions.
--- dbus.te | 1 + mysql.te | 1 + tor.te | 1 + 3 files changed, 3 insertions(+), 0 deletions(-)
dbus.te +1 -0
@@ -35,6 +35,7 @@ files_type(system_dbusd_var_lib_t) type system_dbusd_var_run_t; files_pid_file(system_dbusd_var_run_t) +init_daemon_run_dir(system_dbusd_var_run_t, "dbus") ifdef(`enable_mcs',` init_ranged_system_domain(system_dbusd_t, dbusd_exec_t, s0 - mcs_systemhigh)
mysql.te +1 -0
@@ -22,6 +22,7 @@ init_daemon_domain(mysqld_safe_t, mysqld_safe_exec_t) type mysqld_var_run_t; files_pid_file(mysqld_var_run_t) +init_daemon_run_dir(mysqld_var_run_t, "mysqld") type mysqld_db_t; files_type(mysqld_db_t)
tor.te +1 -0
@@ -35,6 +35,7 @@ logging_log_file(tor_var_log_t) # pid files type tor_var_run_t; files_pid_file(tor_var_run_t) +init_daemon_run_dir(tor_var_run_t, "tor") ######################################## #
Signature · 1 line
1.7.8.6