svirt_selinux(8)

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

✨ svirt_selinux(8) ✨

Okay bestie, so this is the manual page for svirt_selinux — the SELinux policy for svirt processes. It's giving security, it's giving virtualization, and it's genuinely iconic. Let's get into it. 💅

💖 NAME 💖

svirt_selinux — Security Enhanced Linux Policy for the svirt processes

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the svirt processes via flexible mandatory access control. No cap, it's literally the bodyguard your virtual machines deserve. 🫶

The svirt processes execute with the svirt_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 svirt_t

🦋 ENTRYPOINTS 🦋

The svirt_t SELinux type can be entered via the qemu_exec_t file type.

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

/usr/libexec/qemu.*, /usr/bin/qemu-system-.*, /usr/bin/qemu,
/usr/bin/qemu-kvm

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. It's a whole vibe. ✨

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

Policy governs the access confined processes have to files. SELinux svirt policy is very flexible allowing users to setup their svirt processes in as secure a method as possible.

The following process types are defined for svirt:

svirt_t, svirt_tcg_t, svirt_qemu_net_t, svirt_socket_t, svirt_kvm_net_t

Note: semanage permissive -a svirt_t can be used to make the process type svirt_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. 💀

💜 MCS Constrained 💜

The SELinux process type svirt_t is an MCS (Multi Category Security) constrained type. Sometimes this separation is referred to as sVirt. These types are usually used for securing multi-tenant environments, such as virtualization, containers or separation of users. The tools used to launch MCS types, pick out a different MCS label for each process group. It's lowkey giving "everyone gets their own room" energy. 🚪✨

For example one process might be launched with svirt_t:s0:c1,c2, and another process launched with svirt_t:s0:c3,c4. The SELinux kernel only allows these processes can only write to content with a matching MCS label, or a MCS Label of s0. A process running with the MCS level of s0:c1,c2 is not allowed to write to content with the MCS label of s0:c3,c4. So yeah, boundaries, bestie. 🛑

🎀 BOOLEANS 🎀

SELinux policy is customizable based on least access required. svirt policy is extremely flexible and has several booleans that allow you to manipulate the policy and run svirt with the tightest access possible. It's literally so customizable, we love to see it. 💖

  • 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
  • virt_use_execmem — If you want to allow confined virtual guests to use executable memory and executable stack, you must turn on the virt_use_execmem boolean. Disabled by default. 🙈
setsebool -P virt_use_execmem 1
  • virt_use_rawip — If you want to allow confined virtual guests to interact with rawip sockets, you must turn on the virt_use_rawip boolean. Disabled by default. 📡
setsebool -P virt_use_rawip 1
  • xen_use_qemu_for_dom0_disk_backend — If you want to allow using qemu for xen dom0 disk backend, you must turn on the xen_use_qemu_for_dom0_disk_backend boolean. Disabled by default. 🐧
setsebool -P xen_use_qemu_for_dom0_disk_backend 1

🧚 MANAGED FILES 🧚

The SELinux process type svirt_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. Like, SELinux is doing its part, but you still need your regular perms too, okay? 🔑

  • fs_t
  • glusterd_var_run_t
/run/gluster(/.*)?
/run/glusterd.*
/run/glusterd.*
/run/glusterd(/.*)?
  • qemu_var_run_t
/run/libvirt/qemu(/.*)?
/var/lib/libvirt/qemu(/.*)?
  • svirt_home_t
/home/[^/]+/.libvirt/qemu(/.*)?
/home/[^/]+/.cache/libvirt/qemu(/.*)?
/home/[^/]+/.config/libvirt/qemu(/.*)?
/home/[^/]+/.local/share/libvirt/boot(/.*)?
/home/[^/]+/.local/share/libvirt/images(/.*)?
/home/[^/]+/.local/share/gnome-boxes/images(/.*)?
  • svirt_image_t
  • svirt_tmp_t
  • svirt_tmpfs_t
  • virt_cache_t
/var/cache/oz(/.*)?
/var/cache/libvirt(/.*)?

🌈 FILE CONTEXTS 🌈

SELinux requires files to have an extended attribute to define the file type. It's like every file has a little name tag. 🏷️

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

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the svirt, 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 svirt_tmp_t '/srv/svirt/content(/.*)?'
restorecon -R -v /srv/mysvirt_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. It's giving pattern-matching queen. 👑

The following file types are defined for svirt:

  • svirt_home_t
    • Set files with the svirt_home_t type, if you want to store svirt files in the users home directory.

Paths:

/home/[^/]+/.libvirt/qemu(/.*)?,
/home/[^/]+/.cache/libvirt/qemu(/.*)?,
/home/[^/]+/.config/libvirt/qemu(/.*)?,
/home/[^/]+/.local/share/libvirt/boot(/.*)?,
/home/[^/]+/.local/share/libvirt/images(/.*)?,
/home/[^/]+/.local/share/gnome-boxes/images(/.*)?
  • svirt_image_t
    • Set files with the svirt_image_t type, if you want to treat the files as svirt image data.
  • svirt_tmp_t
    • Set files with the svirt_tmp_t type, if you want to store svirt temporary files in the /tmp directories.
  • svirt_tmpfs_t
    • Set files with the svirt_tmpfs_t type, if you want to store svirt files on a tmpfs file system.
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. 💅

💀 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.

🫶 AUTHOR 🫶

This manual page was auto-generated using sepolicy manpage. It's literally built different. 🤖✨

🌟 SEE ALSO 🌟

selinux(8), svirt(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), svirt_kvm_net_selinux(8), svirt_kvm_net_selinux(8), svirt_qemu_net_selinux(8), svirt_qemu_net_selinux(8), svirt_socket_selinux(8), svirt_socket_selinux(8), svirt_tcg_selinux(8), svirt_tcg_selinux(8)

Okay bestie, that's the whole page! This was brought to you by the svirt manual, version 26-10-06, dated 26-10-06. Go forth and secure those virtual machines. Periodt. 💖🔥👑

📦 where this page comes from