kdump_selinux(8)

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

πŸ’– kdump_selinux β€” bestie edition πŸ’–

okay so this is the kdump_selinux(8) page from the SELinux Policy kdump manual, and it's literally all about how SELinux locks down the kdump processes. buckle up πŸŽ€


✨ NAME ✨

kdump_selinux β€” the Security Enhanced Linux Policy for the kdump processes, no cap πŸ’…


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the kdump processes via flexible mandatory access control. yeah. flexible. mandatory. access control. she's that girl πŸ’–

The kdump processes execute with the kdump_t SELinux type. wanna check if you've got these processes running? just run the ps command with the -Z qualifier, easy peasy πŸ¦‹

For example:

ps -eZ | grep kdump_t

πŸ¦‹ ENTRYPOINTS πŸ¦‹

The kdump_t SELinux type can be entered via the kdump_exec_t file type πŸ‘‘

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

/usr/bin/kdump, /usr/bin/kexec


πŸ‘‘ 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 kdump policy is very flexible allowing users to setup their kdump processes in as secure a method as possible. highkey obsessed with how flexible this is tbh πŸ’œ

The following process types are defined for kdump:

kdump_t, kdump_dep_generator_t, kdumpctl_t, kdumpgui_t

Note: semanage permissive -a kdump_t can be used to make the process type kdump_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, she's not blocking you anymore but she's still taking notes πŸ“πŸ’€

πŸŽ€ BOOLEANS πŸŽ€

SELinux policy is customizable based on least access required. kdump policy is extremely flexible and has several booleans that allow you to manipulate the policy and run kdump with the tightest access possible. tightest access. periodt πŸ’…

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 kdump_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. like, SELinux isn't gonna override your DAC, bestie, that's a whole separate vibe check πŸ™ˆ

  • kdump_crash_t
    • /var/crash(/.*)?
  • kdump_lock_t
    • /run/lock/kdump(/.*)?
  • kdump_tmpfs_t
  • kdump_var_lib_t
    • /var/lib/kdump(/.*)?
  • tmp_t
    • /sandbox(/.*)?
    • /tmp
    • /usr/tmp
    • /var/tmp
    • /var/tmp
    • /tmp-inst
    • /var/tmp-inst
    • /var/tmp/tmp-inst
    • /var/tmp/vi.recover

(and yes, /var/tmp really is listed twice in the original, I'm not gonna gaslight you and pretend it's once πŸ“)


⭐ FILE CONTEXTS ⭐

SELinux requires files to have an extended attribute to define the file type. it's giving "files have vibes" and honestly? correct ✨

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

πŸ’– STANDARD FILE CONTEXT πŸ’–

SELinux defines the file context types for the kdump, 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. moving day for your labels, slay 🚚✨

semanage fcontext -a -t kdump_exec_t '/srv/kdump/content(/.*)?'
restorecon -R -v /srv/mykdump_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 kdump:

kdump_crash_t

  • Set files with the kdump_crash_t type, if you want to treat the files as kdump crash data.

kdump_dep_generator_exec_t

  • Set files with the kdump_dep_generator_exec_t type, if you want to transition an executable to the kdump_dep_generator_t domain.

kdump_dep_generator_unit_file_t

  • Set files with the kdump_dep_generator_unit_file_t type, if you want to treat the files as kdump dep generator unit content.

kdump_dep_unit_file_t

  • Set files with the kdump_dep_unit_file_t type, if you want to treat the files as kdump dep unit content.

kdump_etc_t

  • Set files with the kdump_etc_t type, if you want to store kdump files in the /etc directories.

kdump_exec_t

  • Set files with the kdump_exec_t type, if you want to transition an executable to the kdump_t domain.

Paths:

/usr/bin/kdump, /usr/bin/kexec

kdump_initrc_exec_t

  • Set files with the kdump_initrc_exec_t type, if you want to transition an executable to the kdump_initrc_t domain.

kdump_lock_t

  • Set files with the kdump_lock_t type, if you want to treat the files as kdump lock data, stored under the /var/lock directory.

kdump_log_t

  • Set files with the kdump_log_t type, if you want to treat the data as kdump log data, usually stored under the /var/log directory.

kdump_tmpfs_t

  • Set files with the kdump_tmpfs_t type, if you want to store kdump files on a tmpfs file system.

kdump_unit_file_t

  • Set files with the kdump_unit_file_t type, if you want to treat the files as kdump unit content.

kdump_var_lib_t

  • Set files with the kdump_var_lib_t type, if you want to store the kdump files under the /var/lib directory.

kdumpctl_exec_t

  • Set files with the kdumpctl_exec_t type, if you want to transition an executable to the kdumpctl_t domain.

kdumpctl_tmp_t

  • Set files with the kdumpctl_tmp_t type, if you want to store kdumpctl temporary files in the /tmp directories.

kdumpgui_exec_t

  • Set files with the kdumpgui_exec_t type, if you want to transition an executable to the kdumpgui_t domain.

kdumpgui_tmp_t

  • Set files with the kdumpgui_tmp_t type, if you want to store kdumpgui temporary files in the /tmp directories.
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. temporary vs permanent is literally the whole plot of this story 😭

πŸ”₯ 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 bestie, a GUI. for the mouse girlies πŸ–±οΈβœ¨

🧚 AUTHOR 🧚

This manual page was auto-generated using sepolicy manpage. she was born automated and she's thriving πŸ’…


πŸ’œ SEE ALSO πŸ’œ

selinux(8), kdump(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), kdump_dep_generator_selinux(8), kdump_dep_generator_selinux(8)

(and yes, kdump_dep_generator_selinux(8) shows up twice. iconic of her, honestly. she said "again" πŸ’€)


🌈 okay that's the whole page!! this one came from kdump, dated 26-10-06, and it's kdump_selinux(8) β€” go forth and label responsibly, bestie πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from