sanlock_selinux(8)

📦
version 20250627+git412.dbf877ab7 · 7 versions
, in opensuse-leap 16.0

✨ sanlock_selinux ✨

Okay so bestie, welcome to the manual page for sanlock_selinux 💅 This is the Security Enhanced Linux Policy for the sanlock processes, and honestly? It's giving secure. Let me break it all down for you, no cap.

🌸 NAME 🌸

sanlock_selinux — Security Enhanced Linux Policy for the sanlock processes

🎀 DESCRIPTION 🎀

Security-Enhanced Linux secures the sanlock processes via flexible mandatory access control. It's literally the bodyguard for your processes, and it takes its job very seriously 💖

The sanlock processes execute with the sanlock_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 sanlock_t

Go ahead, run it, I'll wait 🫶

🦋 ENTRYPOINTS 🦋

The sanlock_t SELinux type can be entered via the sanlock_exec_t file type.

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

/usr/bin/sanlock

That's the only way in, periodt 💅

💜 PROCESS TYPES 💜

SELinux defines process types (domains) for each process running on the system. It's like every process gets its own little vibe check.

You can see the context of a process using the -Z option to ps.

Policy governs the access confined processes have to files. SELinux sanlock policy is very flexible, allowing users to setup their sanlock processes in as secure a method as possible. Highkey obsessed with how flexible this is.

The following process types are defined for sanlock:

sanlock_t
Note: semanage permissive -a sanlock_t can be used to make the process type sanlock_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's chill but it's still watching you 👀

🌈 BOOLEANS 🌈

SELinux policy is customizable based on least access required. sanlock policy is extremely flexible and has several booleans that allow you to manipulate the policy and run sanlock with the tightest access possible. Tightest access? Iconic behavior.

If you want to allow sanlock to read/write user home directories, you must turn on the sanlock_enable_home_dirs boolean. Disabled by default.

setsebool -P sanlock_enable_home_dirs 1

If you want to allow sanlock to read/write fuse files, you must turn on the sanlock_use_fusefs boolean. Disabled by default.

setsebool -P sanlock_use_fusefs 1

If you want to allow sanlock to manage nfs files, you must turn on the sanlock_use_nfs boolean. Disabled by default.

setsebool -P sanlock_use_nfs 1

If you want to allow sanlock to manage cifs files, you must turn on the sanlock_use_samba boolean. Disabled by default.

setsebool -P sanlock_use_samba 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 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 sanlock_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the process's UID still needs to have DAC permissions. So like, don't forget about DAC, bestie.

cifs_t

(No default paths listed, it's mysterious like that 💅)

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

fs_t

(No default paths listed, keeping it lowkey ✨)

fusefs_t

/run/user/[0-9]+/gvfs

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

nfs_t

(No default paths listed, it's giving mystery 🌸)

root_t

/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp

sanlock_conf_t

/etc/sanlock(/.*)?

sanlock_log_t

/var/log/sanlock.log.*

sanlock_var_run_t

/run/sanlock(/.*)?
/run/sanlk-resetd(/.*)?

sysfs_t

/sys(/.*)?

user_home_t

/home/[^/]+/.+

🧚 FILE CONTEXTS 🧚

SELinux requires files to have an extended attribute to define the file type. It's like every file needs its own little label, you know?

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 sanlock policy is very flexible, allowing users to setup their sanlock processes in as secure a method as possible. Again, highkey flexible, we stan.

STANDARD FILE CONTEXT

SELinux defines the file context types for the sanlock. If you wanted to store files with these types in 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 sanlock_exec_t '/srv/sanlock/content(/.*)?'
restorecon -R -v /srv/mysanlock_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex? We love to see it 💖

The following file types are defined for sanlock:

  • sanlock_conf_t — Set files with the sanlock_conf_t type, if you want to treat the files as sanlock configuration data, usually stored under the /etc directory.
  • sanlock_exec_t — Set files with the sanlock_exec_t type, if you want to transition an executable to the sanlock_t domain.
  • sanlock_initrc_exec_t — Set files with the sanlock_initrc_exec_t type, if you want to transition an executable to the sanlock_initrc_t domain.
  • sanlock_log_t — Set files with the sanlock_log_t type, if you want to treat the data as sanlock log data, usually stored under the /var/log directory.
  • sanlock_unit_file_t — Set files with the sanlock_unit_file_t type, if you want to treat the files as sanlock unit content.
  • sanlock_var_run_t — Set files with the sanlock_var_run_t type, if you want to store the sanlock files under the /run or /var/run directory.

Paths:

/run/sanlock(/.*)?, /run/sanlk-resetd(/.*)?
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. So like, chcon is for quick fixes, semanage fcontext is for the permanent glow-up 💅

👑 COMMANDS 👑

semanage fcontext can also be used to manipulate default file context mappings. It's giving multitasking.

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. GUI? For when you want to point and click instead of typing, no judgment 🫶

💀 AUTHOR 💀

This manual page was auto-generated using sepolicy manpage. Auto-generated? The robots did this one, not me, but I'm just here to make it cute ✨

⭐ SEE ALSO ⭐

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

Okay bestie, that's the whole page! This was the sanlock manual page, rendered on 26-10-06, and honestly? You ate that. Go forth and be secure 💖🔥👑

📦 where this page comes from