virt_q...selinux(8)

✨ virt_qemu_ga_unconfined_selinux — SELinux Policy for virt_qemu_ga_unconfined 💅

okay bestie, welcome to the virt_qemu_ga_unconfined page of the SELinux manual — it lives in section 8, and it's literally all about keeping the virt_qemu_ga_unconfined processes in line. buckle up 🎀

---

🌸 NAME 🌸

virt_qemu_ga_unconfined_selinux — the Security Enhanced Linux Policy for the virt_qemu_ga_unconfined processes. that's the whole vibe. 🦋

---

💖 DESCRIPTION 💖

Security-Enhanced Linux secures the virt_qemu_ga_unconfined processes via flexible mandatory access control. no cap, that's the entire point of it. ✨

So here's the tea: the virt_qemu_ga_unconfined processes execute with the virt_qemu_ga_unconfined_t SELinux type. want to check if you've got these processes running? just run the ps command with the -Z qualifier, easy.

Like this, for example:

ps -eZ | grep virt_qemu_ga_unconfined_t

literally that simple, iykyk. 🔥

---

🦋 ENTRYPOINTS 🦋

The virt_qemu_ga_unconfined_t SELinux type can be entered via the virt_qemu_ga_unconfined_exec_t file type. that's the front door, bestie. 🚪

The default entrypoint paths for the virt_qemu_ga_unconfined_t domain are these three iconic little regexes:

/etc/qemu-ga/fsfreeze-hook.d(/.*)?, /run/qemu-ga/fsfreeze-hook.d(/.*)?,
/usr/libexec/qemu-ga/fsfreeze-hook.d(/.*)?

---

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. yes, every single one. 💅

You can see the context of a process using the -Z option to ps — same trick as before, it's giving consistency.

Policy governs the access confined processes have to files. the SELinux virt_qemu_ga_unconfined policy is very flexible, allowing users to setup their virt_qemu_ga_unconfined processes in as secure a method as possible. obsessed with the flexibility ngl. 🌈

The following process types are defined for virt_qemu_ga_unconfined:

• virt_qemu_ga_unconfined_t

Note: semanage permissive -a virt_qemu_ga_unconfined_t can be used to make the process type virt_qemu_ga_unconfined_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it stops being a hater but it still writes everything down in its diary. 😭

---

🎀 BOOLEANS 🎀

SELinux policy is customizable based on least access required. the virt_qemu_ga_unconfined policy is extremely flexible and has several booleans that allow you to manipulate the policy and run virt_qemu_ga_unconfined with the tightest access possible. main character energy for real. 👑

If you want to deny user domains applications to map a memory region as both executable and writable, you must turn on the deny_execmem boolean. this is dangerous and the executable should be reported in bugzilla. Disabled by default.

setsebool -P deny_execmem 1

If you want to control the ability to mmap a low area of the address space, as configured by /proc/sys/vm/mmap_min_addr, you must turn on the mmap_low_allowed boolean. Disabled by default.

setsebool -P mmap_low_allowed 1

If you want to disable kernel module loading, you must turn on the secure_mode_insmod boolean. Disabled by default.

setsebool -P secure_mode_insmod 1

If you want to allow unconfined executables to make their heap memory executable, you must turn on the selinuxuser_execheap boolean. doing this is a really bad idea. it probably indicates a badly coded executable, but could indicate an attack. this executable should be reported in bugzilla. Disabled by default. 💀

setsebool -P selinuxuser_execheap 1

If you want to allow unconfined executables to make their stack executable, you must turn on the selinuxuser_execstack boolean. this should never, ever be necessary. it probably indicates a badly coded executable, but could indicate an attack. this executable should be reported in bugzilla. Disabled by default. 🙈

setsebool -P selinuxuser_execstack 1

---

💜 MANAGED FILES 💜

The SELinux process type virt_qemu_ga_unconfined_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. heads up though — the processes UID still need to have DAC permissions. selinux isn't gonna override that for you, bestie. 🫶

file_type

• all files on the system

like. all of them. it's giving greedy but in a slay way. ⭐

---

🍓 FILE CONTEXTS 🍓

SELinux requires files to have an extended attribute to define the file type.

You can see the context of a file using the -Z option to ls. third time's the charm with the -Z thing, it's a whole motif at this point. 😌

Policy governs the access confined processes have to these files. the SELinux virt_qemu_ga_unconfined policy is very flexible, allowing users to setup their virt_qemu_ga_unconfined processes in as secure a method as possible. (yes we said this before, it's still true, it's still iconic.)

🌟 STANDARD FILE CONTEXT 🌟

SELinux defines the file context types for the virt_qemu_ga_unconfined. 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. two-step process, no shortcuts. ✨

semanage fcontext -a -t virt_qemu_ga_unconfined_exec_t '/srv/virt_qemu_ga_unconfined/content(/.*)?'
restorecon -R -v /srv/myvirt_qemu_ga_unconfined_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. so those (/.*)? bits aren't just for decoration, they're doing actual work. 🧚

The following file types are defined for virt_qemu_ga_unconfined:

virt_qemu_ga_unconfined_exec_t

• Set files with the virt_qemu_ga_unconfined_exec_t type, if you want to transition an executable to the virt_qemu_ga_unconfined_t domain.

Paths:

/etc/qemu-ga/fsfreeze-hook.d(/.*)?, /run/qemu-ga/fsfreeze-
hook.d(/.*)?, /usr/libexec/qemu-ga/fsfreeze-hook.d(/.*)?

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. chcon is a one-night stand, semanage fcontext is the committed relationship. 💖

---

🌈 COMMANDS 🌈

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. for the girlies who prefer a little clicky-click over the terminal, we respect it. 🖱️

---

✍️ AUTHOR ✍️

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

---

🔗 SEE ALSO 🔗

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

---

and that's the whole page bestie!! 🎉 this was virt_qemu_ga_unconfined, dated 26-10-06, and you can find it in section 8 of the manual (virt_q...selinux(8) — the abbreviated header, because even manpage headers get tired sometimes). go forth and label things responsibly. 🫶💖✨