salt_selinux(8)

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

πŸ’– NAME πŸ’–

okay so bestie, this is salt_selinux(8) β€” the SELinux Policy salt manual, and it's literally all about the SELinux policy for the salt processes. Security Enhanced Linux? We love a secure era. πŸ’…

✨ DESCRIPTION ✨

SELinux secures the salt processes with flexible mandatory access control. It's giving security bouncer, but make it policy.

The salt processes execute with the salt_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier, like this:

ps -eZ | grep salt_t

πŸšͺ ENTRYPOINTS πŸšͺ

The salt_t SELinux type can be entered via the salt_exec_t file type.

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

/usr/libexec/salt/salt-minion(-[0-9._-]+)?

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

The following process types are defined for salt:

  • salt_t
Note: semanage permissive -a salt_t can be used to make the process type salt_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.

πŸŽ›οΈ BOOLEANS πŸŽ›οΈ

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

Here's the boolean lineup, with the exact setsebool glow-ups:

  • daemons_dontaudit_scheduling β€” Enabled by default. Turn this on if you want to dontaudit all daemons scheduling requests (setsched, sys_nice).
setsebool -P daemons_dontaudit_scheduling 1
  • deny_execmem β€” Disabled by default. This denies user domains applications from mapping a memory region as both executable and writable. That behavior is dangerous, and the executable should be reported in bugzilla.
setsebool -P deny_execmem 1
  • mmap_low_allowed β€” Disabled by default. This controls the ability to mmap a low area of the address space, as configured by /proc/sys/vm/mmap_min_addr.
setsebool -P mmap_low_allowed 1
  • secure_mode_insmod β€” Disabled by default. This disables kernel module loading.
setsebool -P secure_mode_insmod 1
  • selinuxuser_execheap β€” Disabled by default. This allows unconfined executables to make their heap memory executable. Doing this is a really bad idea. It probably indicates a badly coded executable, but it could indicate an attack. This executable should be reported in bugzilla.
setsebool -P selinuxuser_execheap 1
  • selinuxuser_execstack β€” Disabled by default. This allows unconfined executables to make their stack executable. This should never, ever be necessary. It probably indicates a badly coded executable, but it could indicate an attack. This executable should be reported in bugzilla.
setsebool -P selinuxuser_execstack 1

πŸ”Œ PORT TYPES πŸ”Œ

SELinux defines port types to represent TCP and UDP ports.

You can see the types associated with a port by using the following command:

semanage port -l

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

The following port types are defined for salt:

  • salt_port_t

Default Defined Ports:

tcp 4505,4506

πŸ“ MANAGED FILES πŸ“

The SELinux process type salt_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note: the process's UID still needs to have DAC permissions.

  • file_type β€” all files on the system

πŸ—‚οΈ FILE CONTEXTS πŸ—‚οΈ

SELinux requires files to have an extended attribute to define the file type.

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

πŸŽ€ STANDARD FILE CONTEXT πŸŽ€

SELinux defines the file context types for salt. 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.

semanage fcontext -a -t salt_exec_t '/srv/salt/content(/.*)?'
restorecon -R -v /srv/mysalt_content
Note: SELinux often uses regular expressions to specify labels that match multiple files.

The following file types are defined for salt:

  • salt_exec_t β€” Set files with the salt_exec_t type if you want to transition an executable to the salt_t domain.
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.

πŸ› οΈ 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 port can also be used to manipulate the port definitions.
  • semanage boolean can also be used to manipulate the booleans.
  • system-config-selinux is a GUI tool available to customize SELinux policy settings.

✍️ AUTHOR ✍️

This manual page was auto-generated using sepolicy manpage.

πŸ‘€ SEE ALSO πŸ‘€

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


mwah πŸ’‹ β€” source/version salt, date 26-10-06, manual salt_selinux(8). That's the whole page, bestie! 🫢

πŸ“¦ where this page comes from