virt_bridgehelper_selinux - Man Page

Security-Enhanced Linux secures the virt_bridgehelper processes via flexible mandatory access control.

The virt_bridgehelper processes execute with the virt_bridgehelper_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_bridgehelper_t

The virt_bridgehelper_t SELinux type can be entered via the virt_bridgehelper_exec_t file type.

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

/usr/libexec/qemu-bridge-helper

SELinux defines process types (domains) for each process running on the system

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

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

The following process types are defined for virt_bridgehelper:

virt_bridgehelper_t

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

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

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

The SELinux process type virt_bridgehelper_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.

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(/.*)?

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 lsbP

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

STANDARD FILE CONTEXT

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

Note: SELinux often uses regular expressions to specify labels that match multiple files.

The following file types are defined for virt_bridgehelper:

virt_bridgehelper_exec_t

- Set files with the virt_bridgehelper_exec_t type, if you want to transition an executable to the virt_bridgehelper_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.

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.

This manual page was auto-generated using sepolicy manpage .

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

virtd_selinux(8).