qdiskd_selinux(8)

💖 qdiskd_selinux — the qdiskd SELinux manual, but make it make sense 💖

okay bestie, welcome to qdiskd_selinux(8). yes that's the manual name, yes it's a mouthful, no we're not skipping it. this is the whole page, every flag and every path, just with the vibes turned all the way up. let's go 🫶

---

✨ NAME ✨

qdiskd_selinux — the Security Enhanced Linux Policy for the qdiskd processes. that's it, that's the name, slay 💅

---

🌸 DESCRIPTION 🌸

so Security-Enhanced Linux secures the qdiskd processes via flexible mandatory access control. mandatory means you don't get a vote, it just is the rules. periodt.

the qdiskd processes execute with the qdiskd_t SELinux type. you can check if you have these processes running by executing the ps command with the -Z qualifier. like so:

ps -eZ | grep qdiskd_t

literally just run that and you'll see who's hanging out in that domain 🦋

---

🎀 ENTRYPOINTS 🎀

the qdiskd_t SELinux type can be entered via the qdiskd_exec_t file type. that's the doorway, the entry, the main character of file types here.

the default entrypoint paths for the qdiskd_t domain are the following:

/usr/bin/qdiskd

one path. iconic. no notes 💜

---

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. yeah, every process gets its own little kingdom.

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

policy governs the access confined processes have to files. SELinux qdiskd policy is very flexible, allowing users to setup their qdiskd processes in as secure a method as possible. flexible and secure, we love a both/and situation ✨

the following process types are defined for qdiskd:

qdiskd_t

Note: semanage permissive -a qdiskd_t can be used to make the process type qdiskd_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so it stops blocking but it still talks about you. relatable honestly 💀

---

🧚 BOOLEANS 🧚

SELinux policy is customizable based on least access required. qdiskd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run qdiskd with the tightest access possible. booleans are basically the on/off switches of the security world 🔥

• cluster_use_execmem — if you want to allow cluster administrative cluster domains memcheck-amd64- to use executable memory, you must turn on the cluster_use_execmem boolean. disabled by default.

setsebool -P cluster_use_execmem 1

• daemons_dontaudit_scheduling — 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

• fips_mode — 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

• nis_enabled — 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

ok that's all four, we did not skip one, you're welcome 🍓

---

🦋 MANAGED FILES 🦋

the SELinux process type qdiskd_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 — SELinux is not out here overriding the whole filesystem for you, bestie, it's a layer 😭

cluster_conf_t

/etc/cluster(/.*)?

cluster_log

(no default paths listed, it's giving mysterious ✨)

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

qdiskd_tmpfs_t

(no default paths listed — mysterious, again, we stan a private queen)

qdiskd_var_lib_t

/var/lib/qdiskd(/.*)?

qdiskd_var_run_t

/run/qdiskd.pid

root_t

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

yes root_t really does list / as a path, don't come for me, that's what the page says 💀

---

🌈 FILE CONTEXTS 🌈

SELinux requires files to have an extended attribute to define the file type. yes, the file itself is carrying metadata about itself, main character energy fr.

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

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the qdiskd, 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 qdiskd_exec_t '/srv/qdiskd/content(/.*)?'
restorecon -R -v /srv/myqdiskd_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. regex my beloved 😌

the following file types are defined for qdiskd:

• qdiskd_exec_t — Set files with the qdiskd_exec_t type, if you want to transition an executable to the qdiskd_t domain.
• qdiskd_tmpfs_t — Set files with the qdiskd_tmpfs_t type, if you want to store qdiskd files on a tmpfs file system.
• qdiskd_var_lib_t — Set files with the qdiskd_var_lib_t type, if you want to store the qdiskd files under the /var/lib directory.
• qdiskd_var_log_t — Set files with the qdiskd_var_log_t type, if you want to treat the data as qdiskd var log data, usually stored under the /var/log directory.
• qdiskd_var_run_t — Set files with the qdiskd_var_run_t type, if you want to store the qdiskd files under the /run or /var/run directory.

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, know the difference bestie 🎀

---

💅 COMMANDS 💅

yknow the tooling, here's the tooling:

• 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, a GUI, for when the terminal is not the vibe today 🖱️✨

---

🫶 AUTHOR 🫶

This manual page was auto-generated using sepolicy manpage.

auto-generated and still ate, honestly 👑

---

🔥 SEE ALSO 🔥

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

go read those next, iykyk 💖

---

aaaand that's the whole page bestie 🌸 this one came from qdiskd, dated 26-10-06, and it's the qdiskd_selinux(8) manual — signed, sealed, and delivered with love. now go label a file, you've got this 💜🎀