virt_dbus_selinux(8)

📦

version 20250627+git412.dbf877ab7 · 6 versions

20250627+git412.dbf877ab7 · opensuse-leap 16.0 (latest)
42.1.28 · centos-stream 10
43.10 · fedora 43
42.12 · fedora 43
44.11 · fedora 44
43.3 · fedora 44

✨ virt_dbus_selinux — bestie edition ✨

Okay so this is the manual page for virt_dbus_selinux, straight from section 8 of the manual (system administration commands, iykyk). Let's get into it 💅

NAME

virt_dbus_selinux — the Security Enhanced Linux policy for the virt_dbus processes. Periodt.

DESCRIPTION

Security-Enhanced Linux secures the virt_dbus processes via flexible mandatory access control. It's literally giving bodyguard energy for your processes 🫶

The virt_dbus processes execute with the virt_dbus_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 virt_dbus_t

No cap, that command will show you exactly what's running with that context.

ENTRYPOINTS

The virt_dbus_t SELinux type can be entered via the virt_dbus_exec_t file type. That's the doorway, the main character entrance if you will 👑

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

/usr/bin/libvirt-dbus

That's it. Just the one path. Simple, iconic, clean.

PROCESS TYPES

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

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

Policy governs the access confined processes have to files. SELinux virt_dbus policy is very flexible allowing users to setup their virt_dbus processes in as secure a method as possible. Flexible and secure? We love to see it 💖

The following process types are defined for virt_dbus:

virt_dbus_t

Note: semanage permissive -a virt_dbus_t can be used to make the process type virt_dbus_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 warning system. Understand the assignment.

BOOLEANS

SELinux policy is customizable based on least access required. virt_dbus policy is extremely flexible and has several booleans that allow you to manipulate the policy and run virt_dbus with the tightest access possible. Tightest access possible is the vibe, fr fr.

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

Both of those are already on by default, so like, you're already slaying if you haven't touched them. But now you know 💅

MANAGED FILES

The SELinux process type virt_dbus_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 doesn't override that, bestie, it's a whole team effort.

`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

That's a lot of paths, but like, that's the whole point. Details matter 💖

FILE CONTEXTS

SELinux requires files to have an extended attribute to define the file type. It's very "everything has a label" energy and honestly? Respect.

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 virt_dbus policy is very flexible allowing users to setup their virt_dbus processes in as secure a method as possible. (Yes, this sentence is a repeat, no I'm not sorry, it's important 😤)

STANDARD FILE CONTEXT

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

Note: SELinux often uses regular expressions to specify labels that match multiple files. So those (/.*)? bits are doing the lord's work.

The following file types are defined for virt_dbus:

`virt_dbus_exec_t`

Set files with the virt_dbus_exec_t type, if you want to transition an executable to the virt_dbus_t domain.

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, semanage fcontext + restorecon is the forever fix. Choose wisely 🎀

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. (Yes, a GUI, for the visual learners 💅)

AUTHOR

This manual page was auto-generated using sepolicy manpage. It literally wrote itself, we love a self-sufficient king 👑