plymouth_selinux(8)
π plymouth_selinux(8) β SELinux Policy plymouth π
Omg bestie, welcome to the plymouth_selinux(8) manual β aka the designated driver for how SELinux handles plymouth. Buckle up, it's giving security but make it cute. π
πΈ NAME πΈ
plymouth_selinux β Security Enhanced Linux Policy for the plymouth processes. Periodt. π
β¨ DESCRIPTION β¨
Security-Enhanced Linux secures the plymouth processes via flexible mandatory access control. No cap, it's the whole vibe. π‘οΈ
The plymouth processes execute with the plymouth_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 plymouth_t
π¦ ENTRYPOINTS π¦
The plymouth_t SELinux type can be entered via the plymouth_exec_t file type.
The default entrypoint paths for the plymouth_t domain are the following:
/usr/bin/plymouth
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. It's literally how it keeps track of who's who. π
You can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. SELinux plymouth policy is very flexible, allowing users to set up their plymouth processes in as secure a method as possible. Slay.
The following process types are defined for plymouth:
plymouth_tplymouthd_t
Note:semanage permissive -a plymouth_tcan be used to make the process typeplymouth_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's not a free pass, it's just a softer no. π
π BOOLEANS π
SELinux policy is customizable based on least access required. plymouth policy is extremely flexible and has several booleans that allow you to manipulate the policy and run plymouth with the tightest access possible. It's giving controlled chaos, but make it secure. π§
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
π FILE CONTEXTS π
SELinux requires files to have an extended attribute to define the file type. Yes, every file needs its little name tag. π·οΈ
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 plymouth policy is very flexible, allowing users to set up their plymouth processes in as secure a method as possible. Iconic behavior, honestly.
π EQUIVALENCE DIRECTORIES π
plymouth policy stores data with multiple different file context types under the /var/spool/plymouth directory. If you would like to store the data in a different directory, you can use the semanage command to create an equivalence mapping. If you wanted to store this data under the /srv directory, you would execute the following command:
semanage fcontext -a -e /var/spool/plymouth /srv/plymouth
restorecon -R -v /srv/plymouth
π STANDARD FILE CONTEXT π
SELinux defines the file context types for the plymouth, so if you wanted to store files with these types in different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk. Bestie, it's a two-step glow-up. β¨
semanage fcontext -a -t plymouth_exec_t '/srv/plymouth/content(/.*)?'
restorecon -R -v /srv/myplymouth_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 plymouth:
plymouth_exec_tβ Set files with theplymouth_exec_ttype if you want to transition an executable to theplymouth_tdomain.plymouthd_exec_tβ Set files with theplymouthd_exec_ttype if you want to transition an executable to theplymouthd_tdomain.plymouthd_spool_tβ Set files with theplymouthd_spool_ttype if you want to store the plymouthd files under the/var/spooldirectory.plymouthd_var_lib_tβ Set files with theplymouthd_var_lib_ttype if you want to store the plymouthd files under the/var/libdirectory.plymouthd_var_log_tβ Set files with theplymouthd_var_log_ttype if you want to treat the data as plymouthd var log data, usually stored under the/var/logdirectory.- Paths:
/var/log/boot.log.*,/var/log/plymouth.*.log.*,/var/spool/plymouth/boot.log.*
- Paths:
plymouthd_var_run_tβ Set files with theplymouthd_var_run_ttype if you want to store the plymouthd files under the/runor/var/rundirectory.
Important: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context, you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels. No shortcuts, bestie. π
π«Ά COMMANDS π«Ά
semanage fcontextcan also be used to manipulate default file context mappings.semanage permissivecan also be used to manipulate whether or not a process type is permissive.semanage modulecan also be used to enable/disable/install/remove policy modules.semanage booleancan also be used to manipulate the booleans.system-config-selinuxis a GUI tool available to customize SELinux policy settings.
π AUTHOR π
This manual page was auto-generated using sepolicy manpage. The robots did this one, not me. π€π
π₯ SEE ALSO π₯
xoxo, this glow-up is from the plymouth page, dated 26-10-06, filed under plymouth_selinux(8) β stay secure and stay iconic, bestie π
ππ¦
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms