SYSTEMD_NFS_GENERATOR_SELINUX(8)

πŸ“¦
version 20250627+git412.dbf877ab7 Β· 6 versions
, in opensuse-leap 16.0

πŸ’… systemd_nfs_generator_selinux(8) β€” the SELinux Policy for systemd_nfs_generator, bestie edition

okay so this is from the SELinux Policy systemd_nfs_generator manual, and it's literally all about how SELinux keeps the systemd_nfs_generator processes on a leash πŸ¦‹


✨ NAME ✨

systemd_nfs_generator_selinux β€” the Security Enhanced Linux Policy for the systemd_nfs_generator processes πŸ’–


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the systemd_nfs_generator processes via flexible mandatory access control. no cap, that's the whole vibe πŸ‘‘

The systemd_nfs_generator processes execute with the systemd_nfs_generator_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 systemd_nfs_generator_t

πŸŽ€ ENTRYPOINTS πŸŽ€

The systemd_nfs_generator_t SELinux type can be entered via the systemd_nfs_generator_exec_t file type. that's the doorway, the main character entrance πŸšͺ✨

The default entrypoint paths for the systemd_nfs_generator_t domain are the following:

/usr/lib/systemd/system-generators/nfsroot-generator,
/usr/lib/systemd/system-generators/nfs-server-generator,
/usr/lib/systemd/system-generators/rpc-pipefs-generator

πŸ¦‹ PROCESS TYPES πŸ¦‹

SELinux defines process types (domains) for each process running on the system

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

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

The following process types are defined for systemd_nfs_generator:

systemd_nfs_generator_t

Note: semanage permissive -a systemd_nfs_generator_t can be used to make the process type systemd_nfs_generator_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's still gonna gossip about you in the logs 😭

πŸ’œ BOOLEANS πŸ’œ

SELinux policy is customizable based on least access required. systemd_nfs_generator policy is extremely flexible and has several booleans that allow you to manipulate the policy and run systemd_nfs_generator with the tightest access possible. tightest access possible = the icon behavior fr πŸ’…

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

🌈 MANAGED FILES 🌈

The SELinux process type systemd_nfs_generator_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. yeah, SELinux said yes but DAC can still say no πŸ™ˆ

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

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. it's giving ✨metadata✨

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

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the systemd_nfs_generator, 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 systemd_nfs_generator_exec_t '/srv/systemd_nfs_generator/content(/.*)?'
restorecon -R -v /srv/mysystemd_nfs_generator_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise 🫢

The following file types are defined for systemd_nfs_generator:

systemd_nfs_generator_exec_t

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

Paths:

/usr/lib/systemd/system-generators/nfsroot-generator,
/usr/lib/systemd/system-generators/nfs-server-generator,
/usr/lib/systemd/system-generators/rpc-pipefs-generator

systemd_nfs_generator_unit_file_t

  • Set files with the systemd_nfs_generator_unit_file_t type, if you want to treat the files as systemd nfs generator unit content.
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 vs permanent, 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. GUI girlies, this one's for you πŸŽ€


πŸ“ AUTHOR πŸ“

This manual page was auto-generated using sepolicy manpage. not me being generated πŸ˜­πŸ€–


πŸ”₯ SEE ALSO πŸ”₯

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


k that's the whole page, go forth and label things correctly bestie πŸ’œβœ¨

this came from the systemd_nfs_generator source, dated 26-10-06, and it lives under systemd..._selinux(8) β€” mwah, see u in the group chat πŸ«ΆπŸ’…

πŸ“¦ where this page comes from