HEALTH_CHECKER_PLUGIN_SELINUX(8)
π
health_..._selinux(8) β the SELinux Policy for health_checker_plugin glow-up guide
okay so bestie, welcome to the manual page for health_checker_plugin_selinux β that's the SELinux policy situation for the health_checker_plugin processes. yes the title is literally abbreviated with dots, that's just how it is, we don't question the manpage gods π«Ά. this whole thing lives in section 8, and it's about to be your new favorite read (or at least a very cute one).
β¨ NAME β¨
health_checker_plugin_selinux β Security Enhanced Linux Policy for the health_checker_plugin processes. that's it, that's the name, slay π
π¦ DESCRIPTION π¦
okay so here's the vibe: Security-Enhanced Linux secures the health_checker_plugin processes via flexible mandatory access control. flexible! mandatory! access control! the whole package π
The health_checker_plugin processes execute with the health_checker_plugin_t SELinux type. wanna check if you've got these processes running? run the ps command with the -Z qualifier. easy peasy.
For example:
ps -eZ | grep health_checker_plugin_t
that's the whole test. grep and slay π₯
π ENTRYPOINTS π
so the health_checker_plugin_t SELinux type can be entered via the health_checker_plugin_exec_t file type. that's the doorway, the portal, the main character entrance π
The default entrypoint paths for the health_checker_plugin_t domain are the following:
/usr/libexec/health-checker/.*.sh, /usr/local/libexec/health-checker/.*.sh
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. every process gets a little domain, like a little outfit for each one π
You can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. SELinux health_checker_plugin policy is very flexible, allowing users to setup their health_checker_plugin processes in as secure a method as possible. flexible AND secure, we love a multitasker β¨
The following process types are defined for health_checker_plugin:
health_checker_plugin_t
Note:semanage permissive -a health_checker_plugin_tcan be used to make the process typehealth_checker_plugin_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it stops blocking you but it's still gonna text about it π
πΈ BOOLEANS πΈ
SELinux policy is customizable based on least access required. health_checker_plugin policy is extremely flexible and has several booleans that allow you to manipulate the policy and run health_checker_plugin with the tightest access possible. tightest access possible!! we're being responsible bestie π
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
one boolean, one line, done. iconic.
π MANAGED FILES π
The SELinux process type health_checker_plugin_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 isn't out here doing DAC's job, no cap π
health_checker_etc_thealth_checker_tmp_tsystemd_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. every file's gotta carry its little label around, it's giving accessories π
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 health_checker_plugin policy is very flexible, allowing users to setup their health_checker_plugin processes in as secure a method as possible.
β STANDARD FILE CONTEXT β
SELinux defines the file context types for the health_checker_plugin. 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 health_checker_plugin_exec_t '/srv/health_checker_plugin/content(/.*)?'
restorecon -R -v /srv/myhealth_checker_plugin_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regexes! in MY labeling?? it's more likely than you think π¦
The following file types are defined for health_checker_plugin:
health_checker_plugin_exec_t
- Set files with the
health_checker_plugin_exec_ttype, if you want to transition an executable to thehealth_checker_plugin_tdomain.
Paths:
/usr/libexec/health-checker/.*.sh, /usr/local/libexec/health-checker/.*.sh
Note: 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. temporarychcon= a story post, permanentsemanage fcontext= the grid post. know the difference 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. a GUI!! for the visual learners, we respect it π
π AUTHOR π
This manual page was auto-generated using sepolicy manpage .
(no human author to thank, the machine did it, and honestly? it ate π)
π SEE ALSO π
selinux(8), health_checker_plugin(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
go read those too, iykyk π«Ά
and that's the whole page bestie!! this one's from health_checker_plugin, dated 26-10-06, and it lives in the health_..._selinux(8) section β yes the abbreviated name again, we love her, no cap πβ¨
π¦ 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