NETWORKMANAGER_DISPATCHER_SELINUX(8)

📦
version 20250627+git412.dbf877ab7 · 7 versions
, in opensuse-leap 16.0

💖 NETWORKMANAGER_DISPATCHER_SELINUX(8) 💖

okay bestie, so this is the NetworkManager_dispatcher_selinux manual page, and it's literally all about the SELinux security policy for the NetworkManager_dispatcher processes. it's giving "mandatory access control but make it fashion" ✨

🌸 NAME 🌸

NetworkManager_dispatcher_selinux — Security Enhanced Linux Policy for the NetworkManager_dispatcher processes. periodt. 💅

✨ DESCRIPTION ✨

so, Security-Enhanced Linux is out here securing the NetworkManager_dispatcher processes via flexible mandatory access control. it's iconic, honestly. 🛡️

the NetworkManager_dispatcher processes run with the NetworkManager_dispatcher_t SELinux type, and if you wanna check if you've got these processes running, you just run the ps command with the -Z qualifier. easy peasy. 🍓

for example:

ps -eZ | grep NetworkManager_dispatcher_t

🚪 ENTRYPOINTS 🚪

the NetworkManager_dispatcher_t SELinux type can be entered via the NetworkManager_dispatcher_exec_t file type. it's like the VIP entrance, iykyk. 🎀

the default entrypoint paths for the NetworkManager_dispatcher_t domain are literally:

/usr/lib/nm-dispatcher, /usr/libexec/nm-dispatcher

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. it's a whole thing. 💫

you can see the context of a process using the -Z option to ps. it's giving "peek behind the curtain."

policy governs the access confined processes have to files. the SELinux NetworkManager_dispatcher policy is very flexible, allowing users to set up their NetworkManager_dispatcher processes in as secure a method as possible. slay. 🔥

the following process types are defined for NetworkManager_dispatcher:

  • NetworkManager_dispatcher_t
  • NetworkManager_dispatcher_custom_t
  • NetworkManager_dispatcher_chronyc_t
  • NetworkManager_dispatcher_cloud_t
  • NetworkManager_dispatcher_console_t
  • NetworkManager_dispatcher_ddclient_t
  • NetworkManager_dispatcher_dhclient_t
  • NetworkManager_dispatcher_dnssec_t
  • NetworkManager_dispatcher_iscsid_t
  • NetworkManager_dispatcher_nvme_t
  • NetworkManager_dispatcher_sendmail_t
  • NetworkManager_dispatcher_tlp_t
  • NetworkManager_dispatcher_winbind_t
💡 note: semanage permissive -a NetworkManager_dispatcher_t can be used to make the process type NetworkManager_dispatcher_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it's chill but it's still watching you. 👀

🎛️ BOOLEANS 🎛️

SELinux policy is customizable based on least access required. the NetworkManager_dispatcher policy is extremely flexible and has several booleans that let you manipulate the policy and run NetworkManager_dispatcher with the tightest access possible. it's highkey customizable. ✨

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 NetworkManager_dispatcher_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 needs to have DAC permissions. so like, don't forget the basics, 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

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 like a lil name tag for your files. 🏷️

you can see the context of a file using the -Z option to ls. so you can literally just look at it.

policy governs the access confined processes have to these files. the SELinux NetworkManager_dispatcher policy is very flexible, allowing users to set up their NetworkManager_dispatcher processes in as secure a method as possible. we love to see it. 🌈

🛠️ STANDARD FILE CONTEXT 🛠️

SELinux defines the file context types for the NetworkManager_dispatcher. if you wanted to store files with these types in different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk. it's a two-step process, bestie. 💅

semanage fcontext -a -t NetworkManager_dispatcher_console_var_run_t '/srv/NetworkManager_dispatcher/content(/.*)?'
restorecon -R -v /srv/myNetworkManager_dispatcher_content
💡 note: SELinux often uses regular expressions to specify labels that match multiple files. regex is lowkey iconic. 🧚

the following file types are defined for NetworkManager_dispatcher:

NetworkManager_dispatcher_chronyc_script_t

  • set files with the NetworkManager_dispatcher_chronyc_script_t type if you want to treat the files as NetworkManager dispatcher chronyc script data.

paths:

/usr/lib/NetworkManager/dispatcher.d/20-chrony,
/etc/NetworkManager/dispatcher.d/20-chrony-dhcp,
/usr/lib/NetworkManager/dispatcher.d/20-chrony-dhcp,
/etc/NetworkManager/dispatcher.d/20-chrony-onoffline,
/usr/lib/NetworkManager/dispatcher.d/20-chrony-onoffline

NetworkManager_dispatcher_cloud_script_t

  • set files with the NetworkManager_dispatcher_cloud_script_t type if you want to treat the files as NetworkManager dispatcher cloud script data.

paths:

/etc/NetworkManager/dispatcher.d/hook-network-manager,
/etc/NetworkManager/dispatcher.d/cloud-init-azure-hook,
/usr/lib/NetworkManager/dispatcher.d/90-nm-cloud-setup.sh,
/usr/lib/NetworkManager/dispatcher.d/no-wait.d/90-nm-cloud-setup.sh

NetworkManager_dispatcher_console_script_t

  • set files with the NetworkManager_dispatcher_console_script_t type if you want to treat the files as NetworkManager dispatcher console script data.

NetworkManager_dispatcher_console_var_run_t

  • set files with the NetworkManager_dispatcher_console_var_run_t type if you want to store the NetworkManager dispatcher console files under the /run or /var/run directory.

NetworkManager_dispatcher_ddclient_script_t

  • set files with the NetworkManager_dispatcher_ddclient_script_t type if you want to treat the files as NetworkManager dispatcher ddclient script data.

NetworkManager_dispatcher_dhclient_script_t

  • set files with the NetworkManager_dispatcher_dhclient_script_t type if you want to treat the files as NetworkManager dispatcher dhclient script data.

paths:

/etc/NetworkManager/dispatcher.d/11-dhclient,
/usr/lib/NetworkManager/dispatcher.d/11-dhclient

NetworkManager_dispatcher_dnssec_script_t

  • set files with the NetworkManager_dispatcher_dnssec_script_t type if you want to treat the files as NetworkManager dispatcher dnssec script data.

NetworkManager_dispatcher_exec_t

  • set files with the NetworkManager_dispatcher_exec_t type if you want to transition an executable to the NetworkManager_dispatcher_t domain.

paths:

/usr/lib/nm-dispatcher, /usr/libexec/nm-dispatcher

NetworkManager_dispatcher_iscsid_script_t

  • set files with the NetworkManager_dispatcher_iscsid_script_t type if you want to treat the files as NetworkManager dispatcher iscsid script data.

NetworkManager_dispatcher_nvme_script_t

  • set files with the NetworkManager_dispatcher_nvme_script_t type if you want to treat the files as NetworkManager dispatcher nvme script data.

NetworkManager_dispatcher_script_t

  • set files with the NetworkManager_dispatcher_script_t type if you want to treat the files as NetworkManager dispatcher script data.

paths:

/etc/NetworkManager/dispatcher.d(/.*)?,
/usr/lib/NetworkManager/dispatcher.d(/.*)?

NetworkManager_dispatcher_sendmail_script_t

  • set files with the NetworkManager_dispatcher_sendmail_script_t type if you want to treat the files as NetworkManager dispatcher sendmail script data.

NetworkManager_dispatcher_tlp_script_t

  • set files with the NetworkManager_dispatcher_tlp_script_t type if you want to treat the files as NetworkManager dispatcher tlp script data.

NetworkManager_dispatcher_winbind_script_t

  • set files with the NetworkManager_dispatcher_winbind_script_t type if you want to treat the files as NetworkManager dispatcher winbind script data.
💡 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, don't forget the restorecon step or it's giving "all dressed up and nowhere to go." 😭

💻 COMMANDS 💻

semanage fcontext can also be used to manipulate default file context mappings. it's very versatile. 🎀

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. it's a whole suite, honestly.

system-config-selinux is a GUI tool available to customize SELinux policy settings. for when you want to point and click instead of type. we respect the visual learners. 🖱️✨

👑 AUTHOR 👑

this manual page was auto-generated using sepolicy manpage. so like, a robot wrote it, but i'm here to make it cute. 🤖💖

🔗 SEE ALSO 🔗

selinux(8), NetworkManager_dispatcher(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), NetworkManager_dispatcher_chronyc_selinux(8), NetworkManager_dispatcher_chronyc_selinux(8), NetworkManager_dispatcher_cloud_selinux(8), NetworkManager_dispatcher_cloud_selinux(8), NetworkManager_dispatcher_console_selinux(8), NetworkManager_dispatcher_console_selinux(8), NetworkManager_dispatcher_custom_selinux(8), NetworkManager_dispatcher_custom_selinux(8), NetworkManager_dispatcher_ddclient_selinux(8), NetworkManager_dispatcher_ddclient_selinux(8), NetworkManager_dispatcher_dhclient_selinux(8), NetworkManager_dispatcher_dhclient_selinux(8), NetworkManager_dispatcher_dnssec_selinux(8), NetworkManager_dispatcher_dnssec_selinux(8), NetworkManager_dispatcher_iscsid_selinux(8), NetworkManager_dispatcher_iscsid_selinux(8), NetworkManager_dispatcher_nvme_selinux(8), NetworkManager_dispatcher_nvme_selinux(8), NetworkManager_dispatcher_sendmail_selinux(8), NetworkManager_dispatcher_sendmail_selinux(8), NetworkManager_dispatcher_tlp_selinux(8), NetworkManager_dispatcher_tlp_selinux(8), NetworkManager_dispatcher_winbind_selinux(8), NetworkManager_dispatcher_winbind_selinux(8). go read these next, bestie. you'll be so informed. 📚💅

okay that's the whole page! this version of the manual page is from 26-10-06, and it's part of the NetworkManager_dispatcher documentation for SELinux. hope this helped you understand the vibes and the facts. stay secure out there! 🦋💖✨

📦 where this page comes from