FREEIPMI_BMC_WATCHDOG_SELINUX(8)

💖 freeipmi_bmc_watchdog_selinux 💖

okay bestie, so this is the manual page for freeipmi_bmc_watchdog_selinux — it's from the SELinux Policy freeipmi_bmc_watchdog collection (that's the little dangling bit from the header, yw ✨). It's giving "security paperwork but make it cute," and honestly? We ate.

---

🌸 NAME 🌸

freeipmi_bmc_watchdog_selinux — the Security Enhanced Linux Policy situation for all the freeipmi_bmc_watchdog processes 💅

---

✨ DESCRIPTION ✨

So like, Security-Enhanced Linux secures the freeipmi_bmc_watchdog processes through flexible mandatory access control. That's the whole vibe — it's not "please don't do bad things," it's "you literally cannot, the policy says no." 👑

The freeipmi_bmc_watchdog processes execute with the freeipmi_bmc_watchdog_t SELinux type. Wanna check if you've got these processes running? Just run the ps command with the -Z qualifier. Iconic, easy, no cap:

ps -eZ | grep freeipmi_bmc_watchdog_t

---

🚪 ENTRYPOINTS 🚪

The freeipmi_bmc_watchdog_t SELinux type can be entered via the freeipmi_bmc_watchdog_exec_t file type. Like, that's the doorway, that's the guest list. 🫶

The default entrypoint paths for the freeipmi_bmc_watchdog_t domain are literally just:

/usr/bin/bmc-watchdog

---

🧚 PROCESS TYPES 🧚

SELinux defines process types (aka domains) for each process running on the system. Every process gets its own little labeled identity, yes ma'am. 💜

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

Policy governs the access confined processes have to files. The SELinux freeipmi_bmc_watchdog policy is very flexible, allowing users to set up their freeipmi_bmc_watchdog processes in as secure a method as possible. Flexible and safe? That's main character energy fr fr. 🌈

The following process types are defined for freeipmi_bmc_watchdog:

• freeipmi_bmc_watchdog_t

Note: semanage permissive -a freeipmi_bmc_watchdog_t can be used to make the process type freeipmi_bmc_watchdog_t permissive. Heads up though: SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's still watching you 👀 — nothing gets past SELinux.

---

🎀 BOOLEANS 🎀

SELinux policy is customizable based on least access required — which, honestly, is the most "only give them what they need" mindset ever. The freeipmi_bmc_watchdog policy is extremely flexible and has several booleans that allow you to manipulate the policy and run freeipmi_bmc_watchdog 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. 🔥

setsebool -P nis_enabled 1

---

📁 MANAGED FILES 📁

The SELinux process type freeipmi_bmc_watchdog_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Quick reminder bestie: the process's UID still needs to have DAC permissions. SELinux is a whole extra layer, not a replacement — you still gotta have the perms. 🫶

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

freeipmi_bmc_watchdog_var_run_t

/run/bmc-watchdog.pid

freeipmi_var_cache_t

/var/cache/ipmiseld(/.*)?
/var/cache/ipmimonitoringsdrcache(/.*)?

freeipmi_var_lib_t

/var/lib/freeipmi(/.*)?

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

root_t

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

---

🦋 FILE CONTEXTS 🦋

SELinux requires files to have an extended attribute to define the file type. That's the little label sticker on every file, basically. 🏷️

You can see the context of a file using the -Z option to ls. Slay.

Policy governs the access confined processes have to these files. The SELinux freeipmi_bmc_watchdog policy is very flexible, allowing users to set up their freeipmi_bmc_watchdog processes in as secure a method as possible. We love a flexible-but-secure queen. 👑

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for freeipmi_bmc_watchdog. 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. Like so:

semanage fcontext -a -t freeipmi_bmc_watchdog_exec_t '/srv/freeipmi_bmc_watchdog/content(/.*)?'
restorecon -R -v /srv/myfreeipmi_bmc_watchdog_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. So those (/.*)? bits are doing the "and everything under it" work, iykyk.

The following file types are defined for freeipmi_bmc_watchdog:

freeipmi_bmc_watchdog_exec_t

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

freeipmi_bmc_watchdog_unit_file_t

• Set files with the freeipmi_bmc_watchdog_unit_file_t type, if you want to treat the files as freeipmi bmc watchdog unit content.

freeipmi_bmc_watchdog_var_run_t

• Set files with the freeipmi_bmc_watchdog_var_run_t type, if you want to store the freeipmi bmc watchdog files under the /run or /var/run directory.

Note: File context can be temporarily modified with the chcon command. But if you want to permanently change the file context you need to use the semanage fcontext command. That will modify the SELinux labeling database. And then you will need to use restorecon to apply the labels. Temporary vs. permanent, know the difference bestie 💅

---

💻 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. A whole GUI, for the girlies who prefer clicking 🎀

---

👑 AUTHOR 👑

This manual page was auto-generated using sepolicy manpage. A robot wrote it, we just gave it the group-chat glow-up ✨

---

🔗 SEE ALSO 🔗

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

---

okay that's the whole page, bestie, go forth and label responsibly 🫶

freeipmi_bmc_watchdog · 26-10-06 · freeipm..._selinux(8) — mwah, that's the source/version/date sign-off, ily, bye! 💖🦋🌸