virtqemud_selinux(8)

✨ virtqemud_selinux — the SELinux glow-up for your virtqemud processes 💅

okay bestie, so this is the virtqemud_selinux(8) manual page, and it's literally all about how Security-Enhanced Linux keeps your virtqemud processes on a leash. no cap, it's giving mandatory access control realness.

---

🌸 NAME

virtqemud_selinux — Security Enhanced Linux Policy for the virtqemud processes. periodt. 💖

---

🦋 DESCRIPTION

so Security-Enhanced Linux secures the virtqemud processes via flexible mandatory access control. iconic behavior, honestly.

the virtqemud processes execute with the virtqemud_t SELinux type. you can check if you have these processes running by executing the ps command with the -Z qualifier. like, just vibe check your process list, y'know?

for example:

ps -eZ | grep virtqemud_t

go ahead, run it. i'll wait. 🎀

---

🧚 ENTRYPOINTS

the virtqemud_t SELinux type can be entered via the virtqemud_exec_t file type. that's the doorway, bestie.

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

/usr/bin/virtqemud

one path. one icon. we love a singular moment of clarity. ✨

---

👑 PROCESS TYPES

SELinux defines process types (domains) for each process running on the system. yeah, every single one gets its own little label. main character energy for every process, fr fr.

you can see the context of a process using the -Z option to ps. it's like getting the receipts on what a process is actually doing.

policy governs the access confined processes have to files. SELinux virtqemud policy is very flexible, allowing users to setup their virtqemud processes in as secure a method as possible. highkey the most responsible flex ever.

the following process types are defined for virtqemud:

• virtqemud_t

note: semanage permissive -a virtqemud_t can be used to make the process type virtqemud_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it's not a free pass, it's just a "we're still watching you" kinda situation. 😭

---

💜 BOOLEANS

SELinux policy is customizable based on least access required. virtqemud policy is extremely flexible and has several booleans that allow you to manipulate the policy and run virtqemud with the tightest access possible. so many little switches to flip, it's giving control panel fantasy. 🎛️

if you want to allow virtqemu driver to use executable memory and executable stack, you must turn on the virtqemud_use_execmem boolean. enabled by default.

setsebool -P virtqemud_use_execmem 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 confined virtual guests to manage nfs files, you must turn on the virt_use_nfs boolean. disabled by default.

setsebool -P virt_use_nfs 1

if you want to allow confined virtual guests to interact with the sanlock, you must turn on the virt_use_sanlock boolean. disabled by default.

setsebool -P virt_use_sanlock 1

if you want to allow confined virtual guests to use usb devices, you must turn on the virt_use_usb boolean. enabled by default.

setsebool -P virt_use_usb 1

so many booleans, so many ways to customize. pick your favorites and slay. 🫶

---

🌈 MANAGED FILES

the SELinux process type virtqemud_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. don't forget that, bestie — SELinux isn't the only bouncer at the club. 💅

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

root_t

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

virt_log_t

/var/log/log(/.*)?
/var/log/vdsm(/.*)?
/var/log/libvirt(/.*)?
/var/log/virtqemud.log
/var/log/virtproxyd.log
/var/log/virtsecretd.log
/var/log/virtnetworkd.log
/var/log/virtnodedevd.log
/var/log/virtstoraged.log
/var/log/virtnwfilterd.log
/var/log/virtinterfaced.log
/run/lock/xl

like, look at all those log files. logging is self-care, honestly. 🍓

---

🔥 FILE CONTEXTS

SELinux requires files to have an extended attribute to define the file type. yes, every file needs its little label. it's like giving your files a personality. 🏷️

you can see the context of a file using the -Z option to ls. go ahead, peek at those labels.

policy governs the access confined processes have to these files. SELinux virtqemud policy is very flexible, allowing users to setup their virtqemud processes in as secure a method as possible. we stan a flexible but secure setup.

STANDARD FILE CONTEXT

SELinux defines the file context types for virtqemud. 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. okay so like, you're basically teaching SELinux a new address for these files.

semanage fcontext -a -t virtqemud_t '/srv/virtqemud/content(/.*)?'
restorecon -R -v /srv/myvirtqemud_content

note: SELinux often uses regular expressions to specify labels that match multiple files. regex is lowkey the blueprint, iykyk. 🔍

the following file types are defined for virtqemud:

virtqemud_exec_t

• set files with the virtqemud_exec_t type, if you want to transition an executable to the virtqemud_t domain. it's the gateway executable. 🌟

virtqemud_lock_t

• set files with the virtqemud_lock_t type, if you want to treat the files as virtqemud lock data, stored under the /var/lock directory. locks, but make it SELinux. 🔒

virtqemud_t

• set files with the virtqemud_t type, if you want to treat the files as virtqemud data. this is the main character file type. 👑

virtqemud_tmp_t

• set files with the virtqemud_tmp_t type, if you want to store virtqemud temporary files in the /tmp directories. temporary but still labeled. we love a tidy temp situation. 🧹

virtqemud_tmpfs_t

• set files with the virtqemud_tmpfs_t type, if you want to store virtqemud files on a tmpfs file system. tmpfs but make it virtqemud-coded. 💾

virtqemud_var_run_t

• set files with the virtqemud_var_run_t type, if you want to store the virtqemud files under the /run or /var/run directory.

paths:

/run/libvirt/qemu/channel(/.*)?, /run/virtqemud.pid,
/run/libvirt/virtqemud-sock, /run/libvirt/virtqemud-sock-ro,
/run/libvirt/virtqemud-admin-sock

look at all those socket paths. it's giving runtime realness. ⚡

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 the quick fix and semanage fcontext + restorecon is the permanent glow-up. don't confuse them, bestie. 💖

---

🎀 COMMANDS

semanage fcontext can also be used to manipulate default file context mappings. it's the filing system for your labels.

semanage permissive can also be used to manipulate whether or not a process type is permissive. flip that switch.

semanage module can also be used to enable/disable/install/remove policy modules. modularity is key.

semanage boolean can also be used to manipulate the booleans. all the little toggles in one place.

system-config-selinux is a GUI tool available to customize SELinux policy settings. for when you want to point and click instead of typing. no judgment, we've all been there. 🖱️

---

🫶 AUTHOR

this manual page was auto-generated using sepolicy manpage. a bot wrote this, and honestly? it ate. 🤖✨

---

⭐ SEE ALSO

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

like, go read those too if you want the full lore. iykyk. 🌈

---

okay that's the whole page, bestie. this was virtqemud from 26-10-06, and the manual itself is virtqemud_selinux(8). stay secure, stay slay, and remember: SELinux is just there to keep your processes from being messy. periodt. 💅💖🧚‍♀️