SNAPPER_SDBOOTUTIL_PLUGIN_SELINUX(8)
π NAME π
okay so this page is snapper_sdbootutil_plugin_selinux(8) β the SELinux policy manual for the snapper_sdbootutil_plugin processes. That's it, that's the whole vibe β¨
π¦ DESCRIPTION π¦
Security-Enhanced Linux keeps the snapper_sdbootutil_plugin processes safe using flexible mandatory access control β like, it doesn't just ask them nicely, it enforces the rules, no cap π
The snapper_sdbootutil_plugin processes run with the snapper_sdbootutil_plugin_t SELinux type. Wanna check if you've got any of these running? Run the ps command with the -Z qualifier, bestie:
ps -eZ | grep snapper_sdbootutil_plugin_t
πͺ ENTRYPOINTS πͺ
You can enter the snapper_sdbootutil_plugin_t SELinux type through the snapper_sdbootutil_plugin_exec_t file type.
The default entrypoint path for the snapper_sdbootutil_plugin_t domain is literally just this one:
/usr/lib/snapper/plugins/10-sdbootutil.snapper
π PROCESS TYPES π
SELinux defines process types (aka domains) for every single process running on the system β yes, every last one π«Ά
You can see the context of a process using the -Z option with ps.
Policy governs what access confined processes have to files. Ngl, the SELinux snapper_sdbootutil_plugin policy is super flexible β it lets you set up your snapper_sdbootutil_plugin processes in as secure a way as possible π₯
Here's the process type defined for snapper_sdbootutil_plugin:
snapper_sdbootutil_plugin_t
Note:semanage permissive -a snapper_sdbootutil_plugin_tcan be used to make the process typesnapper_sdbootutil_plugin_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's still watching you π
π BOOLEANS π
SELinux policy is customizable based on least access required. The snapper_sdbootutil_plugin policy is extremely flexible and has several booleans that let you manipulate the policy and run snapper_sdbootutil_plugin with the tightest access possible β main character energy honestly π
If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. It's enabled by default π
setsebool -P fips_mode 1
ποΈ MANAGED FILES ποΈ
The SELinux process type snapper_sdbootutil_plugin_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Just a heads up β the process's UID still needs to have DAC permissions, so don't forget that part π
dosfs_tefivarfs_t/sys/firmware/efi/efivars
snapper_sdbootutil_plugin_tmp_tsystemd_pcrlock_var_lib_t/var/lib/pcrlock.d(/.*)?/var/lib/systemd/pcrlock.*/run/log/systemd/tpm2-measure.log
unlabeled_t
πΈ FILE CONTEXTS πΈ
SELinux requires files to have an extended attribute to define the file type β it's giving organized β¨
You can see the context of a file using the -Z option with ls.
Policy governs what access confined processes have to these files. The SELinux snapper_sdbootutil_plugin policy is super flexible and lets you set up your snapper_sdbootutil_plugin processes in as secure a method as possible π
β STANDARD FILE CONTEXT β
SELinux defines the file context types for snapper_sdbootutil_plugin. If you wanna store files with these types in different paths, you need to run the semanage command to specify alternate labeling, and then use restorecon to actually put the labels on disk:
semanage fcontext -a -t snapper_sdbootutil_plugin_exec_t '/srv/snapper_sdbootutil_plugin/content(/.*)?'
restorecon -R -v /srv/mysnapper_sdbootutil_plugin_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 snapper_sdbootutil_plugin:
snapper_sdbootutil_plugin_exec_t- Set files with the
snapper_sdbootutil_plugin_exec_ttype if you want to transition an executable to thesnapper_sdbootutil_plugin_tdomain.
- Set files with the
snapper_sdbootutil_plugin_tmp_t- Set files with the
snapper_sdbootutil_plugin_tmp_ttype if you want to store snapper sdbootutil plugin temporary files in the/tmpdirectories.
- Set files with the
Note: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context, you need to use thesemanage fcontextcommand β that modifies the SELinux labeling database. Then you'll needrestoreconto apply the labels. Temporary vs permanent, bestie, know the difference π
π οΈ COMMANDS π οΈ
semanage fcontextcan also be used to manipulate default file context mappings.semanage permissivecan also be used to manipulate whether or not a process type is permissive.semanage modulecan also be used to enable/disable/install/remove policy modules.semanage booleancan also be used to manipulate the booleans.system-config-selinuxis a GUI tool available to customize SELinux policy settings β for when you want to click instead of type π±οΈβ¨
βοΈ AUTHOR βοΈ
This manual page was auto-generated using sepolicy manpage. A bot did it, and honestly? Slay π€π
π SEE ALSO π
selinux(8), snapper_sdbootutil_plugin(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
okay that's the whole page, you're officially educated πβ¨ this was snapper_sdbootutil_plugin (that's the source/version babe), dated 26-10-06, from the snappe...selinux(8) corner of the manual. mwah, go forth and label responsibly ππ¦πΈ
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms