cfengine_...d_selinux(8)

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

okay bestie, you opened cfengine_...d_selinux(8) and this is the cfengine_execd_selinux manual β€” a whole page about the SELinux policy for the cfengine_execd processes. it's giving security admin but make it cute πŸ’… no cap.

✨ NAME ✨

cfengine_execd_selinux β€” Security Enhanced Linux Policy for the cfengine_execd processes 🫢

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the cfengine_execd processes via flexible mandatory access control. yes, mandatory, not vibe-based 😌

The cfengine_execd processes execute with the cfengine_execd_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier.

For example:

ps -eZ | grep cfengine_execd_t

πŸšͺ ENTRYPOINTS πŸšͺ

The cfengine_execd_t SELinux type can be entered via the cfengine_execd_exec_t file type.

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

/usr/bin/cf-execd

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

The following process types are defined for cfengine_execd:

cfengine_execd_t
Note: semanage permissive -a cfengine_execd_t can be used to make the process type cfengine_execd_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. cfengine_execd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run cfengine_execd with the tightest access possible. tightest access possible, periodt.

  • 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
  • If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.
setsebool -P nis_enabled 1

πŸ“‚ MANAGED FILES πŸ“‚

The SELinux process type cfengine_execd_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 need to have DAC permissions. yes, DAC permissions stay invited to the group chat πŸ”₯

  • cfengine_var_lib_t β€” default paths:
    • /var/cfengine(/.*)?
  • cluster_conf_t β€” default paths:
    • /etc/cluster(/.*)?
  • cluster_var_lib_t β€” default paths:
    • /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 β€” default paths:
    • /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
  • krb5_host_rcache_t β€” default paths:
    • /var/tmp/krb5_0.rcache2
    • /var/cache/krb5rcache(/.*)?
    • /var/tmp/nfs_0
    • /var/tmp/DNS_25
    • /var/tmp/host_0
    • /var/tmp/imap_0
    • /var/tmp/HTTP_23
    • /var/tmp/HTTP_48
    • /var/tmp/ldap_55
    • /var/tmp/ldap_487
    • /var/tmp/ldapmap1_0
  • root_t β€” default paths:
    • /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.

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 cfengine_execd policy is very flexible allowing users to setup their cfengine_execd processes in as secure a method as possible. we love flexible but secure πŸ’–

πŸ“ STANDARD FILE CONTEXT πŸ“

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

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

The following file types are defined for cfengine_execd:

  • cfengine_execd_exec_t β€” Set files with the cfengine_execd_exec_t type, if you want to transition an executable to the cfengine_execd_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 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 . the robots really said β€œwe got this one” 😭

πŸ‘€ SEE ALSO πŸ‘€


cute sign-off bestie 🫢 source/version + date check: cfengine_execd · 26-10-06 · cfengine_...d_selinux(8) ✨

πŸ“¦ where this page comes from