Networ...elinux(8)

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

✨ NetworkManager_priv_helper_selinux β€” the manual page but make it a group chat ✨

okay so bestie, this is the SELinux manual page for NetworkManager_priv_helper, and it's literally your guide to keeping those helper processes locked down and slaying secure. It's giving "mandatory access control but make it fashion" πŸ’… ngl this page is a whole vibe.


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the NetworkManager_priv_helper processes via flexible mandatory access control. That's the whole point of it, fr fr β€” flexibility plus security, a combo we love to see.

The NetworkManager_priv_helper processes execute with the NetworkManager_priv_helper_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. Like so:

ps -eZ | grep NetworkManager_priv_helper_t

Run that and see who's showing up in the process list. It's a vibe check for your running processes, basically. 🫢


πŸŽ€ ENTRYPOINTS πŸŽ€

The NetworkManager_priv_helper_t SELinux type can be entered via the NetworkManager_priv_helper_exec_t file type. So that's the door these processes walk through, iykyk.

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

/usr/lib/nm-priv-helper, /usr/libexec/nm-priv-helper

Those are the two spots, periodt. ✨


πŸ’œ PROCESS TYPES πŸ’œ

So SELinux defines process types (domains) for each process running on the system. Each process gets its own little labelled home in the policy, and honestly? iconic.

You can see the context of a process using the -Z option to ps. That's your window into what type a process is running as.

Policy governs the access confined processes have to files. The SELinux NetworkManager_priv_helper policy is very flexible, allowing users to setup their NetworkManager_priv_helper processes in as secure a method as possible. Highkey the security is doing its job while staying flexible β€” we stan.

The following process types are defined for NetworkManager_priv_helper:

  • NetworkManager_priv_helper_t β€” the main character type for these processes πŸ‘‘
Note: semanage permissive -a NetworkManager_priv_helper_t can be used to make the process type NetworkManager_priv_helper_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 with the access but still logs everything β€” no cap, it's still watching.

🌈 BOOLEANS 🌈

SELinux policy is customizable based on least access required. The NetworkManager_priv_helper policy is extremely flexible and has several booleans that allow you to manipulate the policy and run NetworkManager_priv_helper with the tightest access possible. Lowkey this is where you tune the settings to match your exact needs.

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

That command right there flips it on, and the -P makes it persistent so it survives a reboot β€” a set-it-and-forget-it moment, we love that for you. πŸ’–


πŸ¦‹ FILE CONTEXTS πŸ¦‹

SELinux requires files to have an extended attribute to define the file type. Think of it like every file wearing a little name tag so the policy knows exactly what it is.

You can see the context of a file using the -Z option to ls. Add that flag and suddenly you know all the gossip about a file's label.

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

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for NetworkManager_priv_helper. 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. It's a two-step glow-up for your filesystem labels.

semanage fcontext -a -t NetworkManager_priv_helper_exec_t '/srv/NetworkManager_priv_helper/content(/.*)?'
restorecon -R -v /srv/myNetworkManager_priv_helper_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. So that (/.*)? at the end is doing a lot of heavy lifting, matching the whole tree. Slay.

The following file types are defined for NetworkManager_priv_helper:

  • NetworkManager_priv_helper_exec_t β€” Set files with the NetworkManager_priv_helper_exec_t type, if you want to transition an executable to the NetworkManager_priv_helper_t domain.

Paths:

/usr/lib/nm-priv-helper, /usr/libexec/nm-priv-helper
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 cute for a quick fix, but semanage fcontext is the real permanent move β€” don't skip the restorecon step, bestie, or it's not actually applied.

🧚 COMMANDS 🧚

Here's your toolkit, all the commands that can help you run the whole show:

  • 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. For when you want the whole thing with a graphical interface, and honestly? valid. 🎨

🌸 AUTHOR 🌸

This manual page was auto-generated using sepolicy manpage. The robots wrote this one so you don't have to, and we're grateful. πŸ™ˆ


πŸ’« SEE ALSO πŸ’«


and that's the whole page, bestie! 🫢 Source/version vibes: NetworkManager_priv_helper, dated 26-10-06, brought to you via Networ...elinux(8). Now go forth and keep those processes secure β€” periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from