crond_selinux(8)

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

πŸ’… crond_selinux β€” the whole vibe (man page 8, SELinux Policy crond)

okay so bestie, buckle up β€” this is the manual page for crond_selinux, and it's literally all about how SELinux keeps the crond processes in check. no cap, it's useful. πŸŽ€


✨ NAME ✨

crond_selinux β€” Security Enhanced Linux Policy for the crond processes 🌸


πŸ¦‹ DESCRIPTION πŸ¦‹

Security-Enhanced Linux secures the crond processes via flexible mandatory access control. like, it's not out here asking nicely β€” it's enforcing. πŸ’…

The crond processes execute with the crond_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 crond_t

go check it, i'll wait. 🫢


🌈 ENTRYPOINTS 🌈

The crond_t SELinux type can be entered via the crond_exec_t file type.

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

/usr/bin/cron(d)?, /usr/bin/atd, /usr/bin/fcron, /usr/libexec/fcron

those are the doors, that's how you get in. πŸšͺ✨


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

The following process types are defined for crond:

  • crond_t
Note: semanage permissive -a crond_t can be used to make the process type crond_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. πŸ’€ like it still snitches, just doesn't block.

πŸ”₯ BOOLEANS πŸ”₯

SELinux policy is customizable based on least access required. crond policy is extremely flexible and has several booleans that allow you to manipulate the policy and run crond with the tightest access possible. yes, tightest. main character energy for your security settings. πŸ‘‘

If you want to determine whether crond can execute jobs in the user domain as opposed to the the generic cronjob domain, you must turn on the cron_userdomain_transition boolean. Enabled by default.

setsebool -P cron_userdomain_transition 1

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 deny user domains applications to map a memory region as both executable and writable, this is dangerous and the executable should be reported in bugzilla, you must turn on the deny_execmem boolean. Disabled by default.

setsebool -P deny_execmem 1

If you want to control the ability to mmap a low area of the address space, as configured by /proc/sys/vm/mmap_min_addr, you must turn on the mmap_low_allowed boolean. Disabled by default.

setsebool -P mmap_low_allowed 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

If you want to enable polyinstantiated directory support, you must turn on the polyinstantiation_enabled boolean. Disabled by default.

setsebool -P polyinstantiation_enabled 1

If you want to disable kernel module loading, you must turn on the secure_mode_insmod boolean. Disabled by default.

setsebool -P secure_mode_insmod 1

If you want to allow unconfined executables to make their heap memory executable. Doing this is a really bad idea. Probably indicates a badly coded executable, but could indicate an attack. This executable should be reported in bugzilla, you must turn on the selinuxuser_execheap boolean. Disabled by default.

🚨 bestie this one is actually scary β€” "really bad idea" is the manpage's words, not mine.
setsebool -P selinuxuser_execheap 1

If you want to allow unconfined executables to make their stack executable. This should never, ever be necessary. Probably indicates a badly coded executable, but could indicate an attack. This executable should be reported in bugzilla, you must turn on the selinuxuser_execstack boolean. Disabled by default.

😭 "never, ever" β€” they mean it. report it in bugzilla, don't just flip this.
setsebool -P selinuxuser_execstack 1

πŸŽ€ MANAGED FILES πŸŽ€

The SELinux process type crond_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.

  • file_type β€” all files on the system
all files on the system

like... all of them. the whole system. ok periodt. πŸ’€


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

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the crond, 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 crond_exec_t '/srv/crond/content(/.*)?'
restorecon -R -v /srv/mycrond_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies stay winning. πŸ¦‹

The following file types are defined for crond:

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

Paths:

/usr/bin/cron(d)?, /usr/bin/atd, /usr/bin/fcron, /usr/libexec/fcron
  • crond_initrc_exec_t β€” Set files with the crond_initrc_exec_t type, if you want to transition an executable to the crond_initrc_t domain.
  • crond_tmp_t β€” Set files with the crond_tmp_t type, if you want to store crond temporary files in the /tmp directories.
  • crond_unit_file_t β€” Set files with the crond_unit_file_t type, if you want to treat the files as crond unit content.

Paths:

/usr/lib/systemd/system/atd.*, /usr/lib/systemd/system/crond.*
  • crond_var_run_t β€” Set files with the crond_var_run_t type, if you want to store the crond files under the /run or /var/run directory.

Paths:

/run/.*cron.*, /run/crond?.pid, /run/crond?.reboot, /run/atd.pid,
/run/fcron.pid, /run/fcron.fifo, /run/anacron.pid
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. iykyk β€” chcon is the temporary tattoo, semanage 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.

🌸 AUTHOR 🌸

This manual page was auto-generated using sepolicy manpage.

(yeah, the robots wrote this one, not me β€” but i still styled it 🫢)


πŸ“ SEE ALSO πŸ“

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


and that's the page, bestie β€” crond_selinux(8), crond, dated 26-10-06, all wrapped up. go forth and label responsibly βœ¨πŸ’–πŸŽ€

πŸ“¦ where this page comes from