mdadm_selinux(8)

πŸ“¦
version 20250627+git412.dbf877ab7 Β· 7 versions
, in opensuse-leap 16.0

πŸ’… mdadm_selinux(8) β€” the SELinux policy for mdadm, explained πŸŽ€

okay so bestie, welcome to mdadm_selinux from the SELinux Policy mdadm manual, and no cap this is the page that tells you how SELinux keeps an eye on everything mdadm does ✨


πŸ’– NAME πŸ’–

mdadm_selinux β€” Security Enhanced Linux Policy for the mdadm processes 🫢


🌸 SYNOPSIS 🌸

(it's a policy page, babe β€” no synopsis line here, just vibes and file contexts πŸ’€)


✨ DESCRIPTION ✨

Security-Enhanced Linux secures the mdadm processes via flexible mandatory access control. That's the whole assignment, and it ate πŸ’…

The mdadm processes execute with the mdadm_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier πŸ‘‘

For example:

ps -eZ | grep mdadm_t

literally just run it and see what's up πŸ’–


πŸ¦‹ ENTRYPOINTS πŸ¦‹

The mdadm_t SELinux type can be entered via the mdadm_exec_t file type. That's the door, bestie πŸšͺ✨

The default entrypoint paths for the mdadm_t domain are the following:

/usr/bin/mdadm, /usr/bin/mdmon, /usr/bin/mdmpd, /usr/bin/iprdump,
/usr/bin/iprinit, /usr/bin/iprupdate, /usr/bin/raid-check

all seven of them, every single one, we don't skip 🫢


πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (domains) for each process running on the system.

You can see the context of a process using the -Z option to ps.

Policy governs the access confined processes have to files. SELinux mdadm policy is very flexible allowing users to setup their mdadm processes in as secure a method as possible 🌈

The following process types are defined for mdadm:

  • mdadm_t
Note: semanage permissive -a mdadm_t can be used to make the process type mdadm_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it stops blocking but it still snitches 😭 periodt.

πŸ’€ BOOLEANS πŸ’€

SELinux policy is customizable based on least access required. mdadm policy is extremely flexible and has several booleans that allow you to manipulate the policy and run mdadm with the tightest access possible πŸ”₯

If you want to dontaudit all daemons scheduling requests (setsched, sys_nice), you must turn on the daemons_dontaudit_scheduling boolean. Enabled by default.

setsebool -P daemons_dontaudit_scheduling 1

If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default.

setsebool -P fips_mode 1

If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default. (yep, off out of the box, bestie πŸ™ˆ)

setsebool -P nis_enabled 1

πŸŽ€ MANAGED FILES πŸŽ€

The SELinux process type mdadm_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions πŸ‘€ (SELinux ain't doing the whole job for you, it's a collab)

πŸ’œ cluster_conf_t

/etc/cluster(/.*)?

πŸ’œ cluster_var_lib_t

/var/lib/pcsd(/.*)?
/var/lib/cluster(/.*)?
/var/lib/openais(/.*)?
/var/lib/pengine(/.*)?
/var/lib/corosync(/.*)?
/usr/lib/heartbeat(/.*)?
/var/lib/heartbeat(/.*)?
/var/lib/pacemaker(/.*)?

πŸ’œ cluster_var_run_t

/run/crm(/.*)?
/run/cman_.*
/run/rsctmp(/.*)?
/run/aisexec.*
/run/heartbeat(/.*)?
/run/pcsd-ruby.socket
/run/corosync-qnetd(/.*)?
/run/corosync-qdevice(/.*)?
/run/pcsd.socket
/run/corosync.pid
/run/cpglockd.pid
/run/rgmanager.pid
/run/cluster/rgmanager.sk

πŸ’œ kdump_lock_t

/run/lock/kdump(/.*)?

πŸ’œ kdumpctl_tmp_t

(no default paths listed β€” it's giving mysterious 🫧)

πŸ’œ krb5_host_rcache_t

/var/tmp/krb5_0.rcache2
/var/cache/krb5rcache(/.*)?
/var/tmp/nfs_0
/var/tmp/DNS_25
/var/tmp/host_0
/var/tmp/imap_0
/var/tmp/HTTP_23
/var/tmp/HTTP_48
/var/tmp/ldap_55
/var/tmp/ldap_487
/var/tmp/ldapmap1_0

πŸ’œ mdadm_conf_t

/etc/mdadm.conf.d(/.*)?
/etc/mdadm.conf
/etc/mdadm.conf.anacbak

πŸ’œ mdadm_log_t

/var/log/iprdump.*
/var/log/iprdbg

πŸ’œ mdadm_tmp_t

(no default paths listed 🌸)

πŸ’œ mdadm_tmpfs_t

(no default paths listed 🌸)

πŸ’œ mdadm_var_run_t

/dev/md/.*
/run/mdadm(/.*)?
/dev/.mdadm.map

πŸ’œ root_t

/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp

yes, that's literally / in there. main character energy πŸ‘‘

πŸ’œ sysfs_t

/sys(/.*)?

πŸ’œ systemd_passwd_var_run_t

/run/systemd/ask-password(/.*)?
/run/systemd/ask-password-block(/.*)?

⭐ FILE CONTEXTS ⭐

SELinux requires files to have an extended attribute to define the file type.

You can see the context of a file using the -Z option to ls πŸ‘€

Policy governs the access confined processes have to these files. SELinux mdadm policy is very flexible allowing users to setup their mdadm processes in as secure a method as possible πŸ’–


🧚 STANDARD FILE CONTEXT 🧚

SELinux defines the file context types for the mdadm, if you wanted to store files with these types in a different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk πŸ”₯

semanage fcontext -a -t mdadm_exec_t '/srv/mdadm/content(/.*)?'
restorecon -R -v /srv/mymdadm_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies stay winning πŸ’…

The following file types are defined for mdadm:

🌟 mdadm_conf_t

  • Set files with the mdadm_conf_t type, if you want to treat the files as mdadm configuration data, usually stored under the /etc directory.

Paths:

/etc/mdadm.conf.d(/.*)?, /etc/mdadm.conf, /etc/mdadm.conf.anacbak

🌟 mdadm_exec_t

  • Set files with the mdadm_exec_t type, if you want to transition an executable to the mdadm_t domain.

Paths:

/usr/bin/mdadm, /usr/bin/mdmon, /usr/bin/mdmpd, /usr/bin/iprdump,
/usr/bin/iprinit, /usr/bin/iprupdate, /usr/bin/raid-check

🌟 mdadm_initrc_exec_t

  • Set files with the mdadm_initrc_exec_t type, if you want to transition an executable to the mdadm_initrc_t domain. (no default paths listed for this one πŸ¦‹)

🌟 mdadm_log_t

  • Set files with the mdadm_log_t type, if you want to treat the data as mdadm log data, usually stored under the /var/log directory.

Paths:

/var/log/iprdump.*, /var/log/iprdbg

🌟 mdadm_tmp_t

  • Set files with the mdadm_tmp_t type, if you want to store mdadm temporary files in the /tmp directories. πŸ“

🌟 mdadm_tmpfs_t

  • Set files with the mdadm_tmpfs_t type, if you want to store mdadm files on a tmpfs file system.

🌟 mdadm_unit_file_t

  • Set files with the mdadm_unit_file_t type, if you want to treat the files as mdadm unit content.

Paths:

/usr/lib/systemd/system/mdmon@.*,
/usr/lib/systemd/system/mdmonitor.*

🌟 mdadm_var_run_t

  • Set files with the mdadm_var_run_t type, if you want to store the mdadm files under the /run or /var/run directory.

Paths:

/dev/md/.*, /run/mdadm(/.*)?, /dev/.mdadm.map
Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels. temporary = chcon, permanent = the whole semanage + restorecon combo, iykyk 😭

🌈 COMMANDS 🌈

semanage fcontext can also be used to manipulate default file context mappings.

semanage permissive can also be used to manipulate whether or not a process type is permissive.

semanage module can also be used to enable/disable/install/remove policy modules.

semanage boolean can also be used to manipulate the booleans

system-config-selinux is a GUI tool available to customize SELinux policy settings. yes bestie, there's a GUI, you don't have to live in the terminal forever (you probably will tho πŸ’…)


πŸ’œ AUTHOR πŸ’œ

This manual page was auto-generated using sepolicy manpage . β€” a robot wrote it, I just gave it the glow-up πŸ€–βœ¨


πŸ”₯ SEE ALSO πŸ”₯

selinux(8), mdadm(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)


and that's the whole page, bestie 🫢 this was mdadm version vibes from 26-10-06 β€” go forth and label responsibly, mwah πŸ’‹πŸ’–

πŸ“¦ where this page comes from