Netw...linux(8)

💅 NAME

ok so <pink>NetworkManager_dispatcher_cloud_selinux</pink> — that's the Security Enhanced Linux Policy for the NetworkManager_dispatcher_cloud processes. that's it, that's the whole vibe. 🎀

---

✨ DESCRIPTION

bestie, real talk: Security-Enhanced Linux secures the NetworkManager_dispatcher_cloud processes via flexible mandatory access control. that's the whole point. ✨

Those NetworkManager_dispatcher_cloud processes? they run with the NetworkManager_dispatcher_cloud_t SELinux type. you can check if you've got them running by executing the ps command with the -Z qualifier. like this:

ps -eZ | grep NetworkManager_dispatcher_cloud_t

go check, i'll wait. 🫶

---

🚪 ENTRYPOINTS

so the NetworkManager_dispatcher_cloud_t SELinux type can be entered via the NetworkManager_dispatcher_cloud_script_t file type. that's the doorway, periodt.

and the default entrypoint paths for the NetworkManager_dispatcher_cloud_t domain are these bad boys:

/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

---

🌈 PROCESS TYPES

okay so SELinux defines process types (domains) for each process running on the system. one per process, no sharing, no cap.

you can see the context of a process using the -Z option to ps. yes, same -Z as before. iconic.

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

the following process types are defined for NetworkManager_dispatcher_cloud:

• NetworkManager_dispatcher_cloud_t

📌 Note: semanage permissive -a NetworkManager_dispatcher_cloud_t can be used to make the process type NetworkManager_dispatcher_cloud_t permissive. 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 👀

---

🎛️ BOOLEANS

SELinux policy is customizable based on least access required. the NetworkManager_dispatcher_cloud policy is extremely flexible and has several booleans that allow you to manipulate the policy and run NetworkManager_dispatcher_cloud with the tightest access possible. 🔥

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_cloud_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. heads up tho — the processes UID still need to have DAC permissions. no skipping that, bestie. 🙈

systemd_passwd_var_run_t

/run/systemd/ask-password(/.*)?
/run/systemd/ask-password-block(/.*)?

---

🏷️ 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. yup, -Z again. they love that flag over here. 💀

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

STANDARD FILE CONTEXT

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

📌 Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise 🌸

the following file types are defined for NetworkManager_dispatcher_cloud:

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

📌 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. no shortcuts, sorry babe 😭

---

🛠️ 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 GUI! for the girlies who like clicking 🖱️💖)

---

✍️ AUTHOR

this manual page was auto-generated using sepolicy manpage. a bot wrote it, and honestly? it ate. 👑

---

👀 SEE ALSO

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

---

that's the whole page, bestie 💜 — brought to you by NetworkManager_dispatcher_cloud, dated 26-10-06, chillin' in section 8 of the manual under that truncated Netw...linux(8) header. go forth and label your files responsibly 🦋✨