NETWORKMANAGER_DISPATCHER_WINBIND_SELINUX(8)

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

πŸ’… NetworkManager_dispatcher_winbind_selinux β€” the SELinux glow-up for your winbind dispatcher bestie

okay so this is the NetworkManager_dispatcher_winbind_selinux(8) man page, and it's literally all about the SELinux policy for the NetworkManager_dispatcher_winbind processes. yes bestie, we're getting into mandatory access control today and honestly? it's giving security ✨


πŸŽ€ NAME πŸŽ€

NetworkManager_dispatcher_winbind_selinux β€” the Security Enhanced Linux Policy for the NetworkManager_dispatcher_winbind processes 🫢


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the NetworkManager_dispatcher_winbind processes via flexible mandatory access control. that's the whole vibe β€” SELinux is the bouncer at the club and it does not play πŸ™…β€β™€οΈ

The NetworkManager_dispatcher_winbind processes execute with the NetworkManager_dispatcher_winbind_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 NetworkManager_dispatcher_winbind_t

πŸ¦‹ ENTRYPOINTS πŸ¦‹

so the NetworkManager_dispatcher_winbind_t SELinux type can be entered via the NetworkManager_dispatcher_winbind_script_t file type. that's the door, that's the entrypoint, iykyk πŸ”₯

the default entrypoint paths for the NetworkManager_dispatcher_winbind_t domain are literally:

/usr/lib/NetworkManager/dispatcher.d/30-winbind

πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (domains) for each process running on the system β€” yes, every single one gets its own little main character label πŸ’…

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

The following process types are defined for NetworkManager_dispatcher_winbind:

  • NetworkManager_dispatcher_winbind_t
Note: semanage permissive -a NetworkManager_dispatcher_winbind_t can be used to make the process type NetworkManager_dispatcher_winbind_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. the NetworkManager_dispatcher_winbind policy is extremely flexible and has several booleans that allow you to manipulate the policy and run NetworkManager_dispatcher_winbind with the tightest access possible. we love a customizable queen 🌈

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_winbind_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. note that the processes UID still need to have DAC permissions β€” SELinux isn't gonna override your regular perms, they both gotta sign off fr fr.

  • samba_var_t
/var/nmbd(/.*)?
/var/lib/samba(/.*)?
/var/cache/samba(/.*)?
  • 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 basically a little name tag for every file, obsessed.

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

🧚 STANDARD FILE CONTEXT 🧚

SELinux defines the file context types for the NetworkManager_dispatcher_winbind, so 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. two-step process bestie, don't skip the second one πŸ™ˆ

semanage fcontext -a -t NetworkManager_dispatcher_winbind_script_t
'/srv/NetworkManager_dispatcher_winbind/content(/.*)?'
restorecon -R -v /srv/myNetworkManager_dispatcher_winbind_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_winbind:

  • 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, chcon is the temporary tattoo and semanage fcontext is the real one πŸ’€

πŸ’œ 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 whole GUI, for the visual learners πŸŽ€

⭐ AUTHOR ⭐

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


🌟 SEE ALSO 🌟

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


and that's the whole page bestie!! πŸ’…βœ¨ this one's from NetworkManager_dispatcher_winbind, 26-10-06, and it's filed under Netw...linux(8) β€” go forth and label responsibly, mwah πŸŽ€πŸ’–

πŸ“¦ where this page comes from