snapperd_selinux(8)
๐ snapperd_selinux(8) โ the glow-up edition ๐
okay bestie, welcome to snapperd_selinux(8), the manual page for the SELinux policy that keeps the snapperd processes on a leash. this is the whole lore, no skips, no cap. let's get into it ๐ซถ
โจ NAME โจ
snapperd_selinux โ the Security Enhanced Linux Policy for the snapperd processes. literally the whole point of this page ๐
๐ธ DESCRIPTION ๐ธ
Security-Enhanced Linux secures the snapperd processes via flexible mandatory access control. yes, mandatory โ SELinux is the main character and it will be respected โจ
The snapperd processes execute with the snapperd_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier.
for example, run this little icon:
ps -eZ | grep snapperd_t
that's it, that's the vibe check ๐
๐ฆ ENTRYPOINTS ๐ฆ
The snapperd_t SELinux type can be entered via the snapperd_exec_t file type. so if you're wondering "how do i even get into this domain", that's the door ๐ชโจ
The default entrypoint paths for the snapperd_t domain are the following:
/usr/bin/snapperd, /usr/lib/snapper/systemd-helper
those two. periodt. ๐
๐ PROCESS TYPES ๐
SELinux defines process types (domains) for each process running on the system. yes, every process gets a whole personality type, it's giving astrology for daemons ๐ฎ
You can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. SELinux snapperd policy is very flexible allowing users to setup their snapperd processes in as secure a method as possible.
The following process types are defined for snapperd:
snapperd_tsnapper_grub_plugin_tsnapper_tu_etc_plugin_tsnapper_sdbootutil_plugin_t
Note:semanage permissive -a snapperd_tcan be used to make the process typesnapperd_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.
so like, permissive mode is the "i'm not mad, i'm just disappointed" setting โ it won't block stuff, but the receipts (AVC messages) still show up ๐ญ
๐ BOOLEANS ๐
SELinux policy is customizable based on least access required. snapperd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run snapperd with the tightest access possible. lowkey iconic that you can just toggle the vibes ๐
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
see? three booleans, three little switches. flip responsibly ๐ซถ
๐ MANAGED FILES ๐
The SELinux process type snapperd_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. so yeah โ SELinux says yes, but the UID still has to have its own permission slip, and SELinux will not cover for it, bestie ๐
cluster_conf_t
/etc/cluster(/.*)?
cluster_var_lib_t
/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
/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
/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
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
that's the whole list, every single path, i would never gatekeep ๐ซถ
๐ FILE CONTEXTS ๐
SELinux requires files to have an extended attribute to define the file type. it's like a little name tag for your files, and honestly? slay ๐
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 snapperd policy is very flexible allowing users to setup their snapperd processes in as secure a method as possible.
โญ STANDARD FILE CONTEXT โญ
SELinux defines the file context types for the snapperd, 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.
like so:
semanage fcontext -a -t snapperd_exec_t '/srv/snapperd/content(/.*)?'
restorecon -R -v /srv/mysnapperd_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 snapperd:
snapperd_conf_t
- Set files with the
snapperd_conf_ttype, if you want to treat the files assnapperdconfiguration data, usually stored under the/etcdirectory.
Paths:
/etc/snapper(/.*)?, /etc/sysconfig/snapper
snapperd_data_t
- Set files with the
snapperd_data_ttype, if you want to treat the files assnapperdcontent.
Paths:
/mnt/(.*/)?.snapshots(/.*)?
/.snapshots(/.*)?
/etc/.snapshots(/.*)?
/opt/.snapshots(/.*)?
/usr/.snapshots(/.*)?
/var/.snapshots(/.*)?
/home/.snapshots(/.*)?
/home/(.*/)?.snapshots(/.*)?
snapperd_exec_t
- Set files with the
snapperd_exec_ttype, if you want to transition an executable to thesnapperd_tdomain.
Paths:
/usr/bin/snapperd, /usr/lib/snapper/systemd-helper
snapperd_log_t
- Set files with the
snapperd_log_ttype, if you want to treat the data assnapperdlog data, usually stored under the/var/logdirectory.
snapperd_tmp_t
- Set files with the
snapperd_tmp_ttype, if you want to storesnapperdtemporary files in the/tmpdirectories.
Note: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels.
so chcon is the "just for tonight" label and semanage fcontext + restorecon is the "we're making this official" label. know the difference, bestie ๐ญ๐
๐ฅ 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.
a whole little toolkit. go off, queen ๐โจ
๐ธ AUTHOR ๐ธ
This manual page was auto-generated using sepolicy manpage. no human wrote this, it was the machines, and honestly they ate ๐ค๐
๐ฆ SEE ALSO ๐ฆ
selinux(8), snapperd(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), snapper_grub_plugin_selinux(8), snapper_sdbootutil_plugin_selinux(8), snapper_tu_etc_plugin_selinux(8)
go read those too, i'm not gatekeeping the lore ๐ซถโจ
and that's the page, bestie! this iconic little number is from snapperd, version/date 26-10-06, and it says snapperd_selinux(8) right there at the bottom like a signature ๐ slay, stay labeled, and may your contexts always be correct ๐๐
๐ฆ 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