firewalld_selinux(8)

💖 firewalld_selinux(8) — the SELinux glow-up for firewalld 💖

okay bestie, gather round, because this is the manual page for firewalld_selinux and it's literally the blueprint for how SELinux keeps the firewalld processes in check. no cap, this is important stuff. it's giving "security but make it mandatory access control" and honestly? iconic.

---

✨ NAME ✨

firewalld_selinux — the Security Enhanced Linux Policy for the firewalld processes. periodt. 💅

---

🦋 DESCRIPTION 🦋

so like, Security-Enhanced Linux secures the firewalld processes via flexible mandatory access control. yes bestie, mandatory — not the vibe where you get to opt out. 🙈

the firewalld processes execute with the firewalld_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 firewalld_t

run that and see what's up. iykyk. 👑

---

🎀 ENTRYPOINTS 🎀

the firewalld_t SELinux type can be entered via the firewalld_exec_t file type. that's the doorway, bestie. 🚪✨

the default entrypoint paths for the firewalld_t domain are the following:

/usr/bin/firewalld

that's it. one path. main character energy fr fr. 🌟

---

💜 PROCESS TYPES 💜

SELinux defines process types (domains) for each process running on the system. lowkey a whole taxonomy. 🧬

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

policy governs the access confined processes have to files. SELinux firewalld policy is very flexible allowing users to setup their firewalld processes in as secure a method as possible. highkey obsessed with the flexibility tbh. 🫶

the following process types are defined for firewalld:

• firewalld_t

Note: semanage permissive -a firewalld_t can be used to make the process type firewalld_t permissive. 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, the receipts still exist. 💀

---

🌈 BOOLEANS 🌈

SELinux policy is customizable based on least access required. firewalld policy is extremely flexible and has several booleans that allow you to manipulate the policy and run firewalld with the tightest access possible. we love a customizable queen. 👑

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

if you want to disable kernel module loading, you must turn on the secure_mode_insmod boolean. Disabled by default.

setsebool -P secure_mode_insmod 1

four booleans, four little switches for your security vibe check. slay. ✨

---

🧚 MANAGED FILES 🧚

the SELinux process type firewalld_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. so like, SELinux isn't doing everything for you, bestie. 🙈

• 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

• firewalld_etc_rw_t

/etc/firewalld(/.*)?

• firewalld_tmp_t — no paths listed, it's just vibing. 💅
• firewalld_tmpfs_t — also no paths, still valid. 🫶
• firewalld_var_run_t

/run/firewalld(/.*)?
/run/firewalld.pid

• iptables_var_lib_t

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

• 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

that's a lot of file types and honestly? the organization is giving spreadsheet realness. 🗂️✨

---

🌸 FILE CONTEXTS 🌸

SELinux requires files to have an extended attribute to define the file type. no attribute, no entry. 🙅‍♀️

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 firewalld policy is very flexible allowing users to setup their firewalld processes in as secure a method as possible. we been knew. 💅

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the firewalld, 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 firewalld_exec_t '/srv/firewalld/content(/.*)?'
restorecon -R -v /srv/myfirewalld_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise. 🧚‍♀️

the following file types are defined for firewalld:

• firewalld_etc_rw_t — set files with the firewalld_etc_rw_t type, if you want to treat the files as firewalld etc read/write content.
• firewalld_exec_t — set files with the firewalld_exec_t type, if you want to transition an executable to the firewalld_t domain.
• firewalld_initrc_exec_t — set files with the firewalld_initrc_exec_t type, if you want to transition an executable to the firewalld_initrc_t domain.
• firewalld_tmp_t — set files with the firewalld_tmp_t type, if you want to store firewalld temporary files in the /tmp directories.
• firewalld_tmpfs_t — set files with the firewalld_tmpfs_t type, if you want to store firewalld files on a tmpfs file system.
• firewalld_unit_file_t — set files with the firewalld_unit_file_t type, if you want to treat the files as firewalld unit content.
• firewalld_var_log_t — set files with the firewalld_var_log_t type, if you want to treat the data as firewalld var log data, usually stored under the /var/log directory.
• firewalld_var_run_t — set files with the firewalld_var_run_t type, if you want to store the firewalld files under the /run or /var/run directory.

Paths:

/run/firewalld(/.*)?, /run/firewalld.pid

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. so like, chcon is a quick fix, semanage fcontext is the forever commitment. choose wisely 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. yes, a GUI, for when you're not in the mood to type. we respect it. 🖥️✨

---

👑 AUTHOR 👑

This manual page was auto-generated using sepolicy manpage. the robot did it, not me. 🤖💖

---

🔥 SEE ALSO 🔥

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

like, read those too if you wanna be a whole SELinux scholar. i believe in you. 🫶📚

---

and that's a wrap! this was firewalld manual page version 26-10-06, dated 26-10-06, and honestly it ate. no crumbs. go forth and be secure, bestie. 💅✨💖