shorewall_selinux(8)

💅 shorewall_selinux(8)

okay bestie, welcome to the shorewall_selinux manual page — it lives in section 8 of the SELinux Policy shorewall man family. grab a snack, this one's a whole tour 🎀

✨ NAME ✨

shorewall_selinux — the Security Enhanced Linux Policy for the shorewall processes. that's it, that's the vibe 💖

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the shorewall processes via flexible mandatory access control. yes, MAC, not the makeup kind (though honestly both slay) 💅

The shorewall processes execute with the shorewall_t SELinux type. wanna check if you've got these processes running? just run the ps command with the -Z qualifier. easy ✨

for example:

ps -eZ | grep shorewall_t

🦋 ENTRYPOINTS 🦋

The shorewall_t SELinux type can be entered via the shorewall_var_lib_t, shorewall_exec_t file types. those are the doors, no cap 🚪

The default entrypoint paths for the shorewall_t domain are literally these:

/var/lib/shorewall(/.*)?, /var/lib/shorewall6(/.*)?, /var/lib/shorewall-lite(/.*)?, /var/lib/shorewall6-lite(/.*)?, /usr/bin/shorewall6?, /usr/bin/shorewall-lite

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. everyone gets a domain, main character energy for all 🔥

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

Policy governs the access confined processes have to files. The SELinux shorewall policy is very flexible, allowing users to setup their shorewall processes in as secure a method as possible. secure AND flexible?? we love a versatile icon 💜

The following process types are defined for shorewall:

• shorewall_t

Note: semanage permissive -a shorewall_t can be used to make the process type shorewall_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 talks about it. gossipy behavior honestly 💀

🍓 BOOLEANS 🍓

SELinux policy is customizable based on least access required. the shorewall policy is extremely flexible and has several booleans that allow you to manipulate the policy and run shorewall with the tightest access possible. tightest access = the most locked-down, most exclusive-club vibe 🎀

• 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 shorewall_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. heads up: the process's UID still needs to have DAC permissions. SELinux said "you still gotta have the regular perms too, 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

initrc_var_run_t

/run/sysconfig(/.*)?
/run/utmp
/run/keymap
/run/numlock-on
/run/setleds-on
/run/runlevel.dir
/run/setmixer_flag
/run/bootsplashctl

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

shorewall_lock_t

/run/lock/subsys/shorewall

shorewall_log_t

/var/log/shorewall.*

shorewall_tmp_t

(this one's just vibes, no default paths listed 🫶)

shorewall_var_lib_t

/var/lib/shorewall(/.*)?
/var/lib/shorewall6(/.*)?
/var/lib/shorewall-lite(/.*)?
/var/lib/shorewall6-lite(/.*)?

🌈 FILE CONTEXTS 🌈

SELinux requires files to have an extended attribute to define the file type. yeah, files have labels too, everyone's got a little something ✨

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

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

🎀 EQUIVALENCE DIRECTORIES 🎀

The shorewall policy stores data with multiple different file context types under the /var/lib/shorewall directory. if you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. say you wanted to store this data under the /srv directory — you'd execute the following command:

semanage fcontext -a -e /var/lib/shorewall /srv/shorewall
restorecon -R -v /srv/shorewall

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for shorewall. 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 shorewall_exec_t '/srv/shorewall/content(/.*)?'
restorecon -R -v /srv/myshorewall_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. regex said "I contain multitudes" 😭

The following file types are defined for shorewall:

shorewall_etc_t

• Set files with the shorewall_etc_t type, if you want to store shorewall files in the /etc directories.

Paths:

/etc/shorewall(/.*)?, /etc/shorewall6(/.*)?, /etc/shorewall-lite(/.*)?

shorewall_exec_t

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

Paths:

/usr/bin/shorewall6?, /usr/bin/shorewall-lite

shorewall_initrc_exec_t

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

shorewall_lock_t

• Set files with the shorewall_lock_t type, if you want to treat the files as shorewall lock data, stored under the /var/lock directory.

shorewall_log_t

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

shorewall_tmp_t

• Set files with the shorewall_tmp_t type, if you want to store shorewall temporary files in the /tmp directories.

shorewall_var_lib_t

• Set files with the shorewall_var_lib_t type, if you want to store the shorewall files under the /var/lib directory.

Paths:

/var/lib/shorewall(/.*)?, /var/lib/shorewall6(/.*)?, /var/lib/shorewall-lite(/.*)?, /var/lib/shorewall6-lite(/.*)?

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 = semanage fcontext + restorecon. don't mix 'em up 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 the mouse girlies 🖱️✨

🌸 AUTHOR 🌸

This manual page was auto-generated using sepolicy manpage. a bot wrote this and honestly it ate 🤖💅

🦋 SEE ALSO 🦋

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

---

okay that's the whole page bestie, you're officially educated 🎓💜 this came from the shorewall package, dated 26-10-06, and it's the shorewall_selinux(8) page — go forth and label things correctly, ily, bye 🫶✨