VIRT_BRIDGEHELPER_SELINUX(8)

πŸ“¦
version 20250627+git412.dbf877ab7 Β· 7 versions
, in opensuse-leap 16.0

πŸ’… virt_bridgehelper_selinux β€” the manual page, bestie edition

okay so this is the virt_bridgehelper_selinux(8) page, and honestly? it's giving "SELinux but make it make sense." sit down, grab a strawberry πŸ“, and let's get into it.


✨ NAME ✨

virt_bridgehelper_selinux β€” the Security Enhanced Linux policy for the virt_bridgehelper processes. that's it, that's the whole vibe check. πŸ’–


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the virt_bridgehelper processes via flexible mandatory access control. yes, mandatory. not a suggestion, not a "if u feel like it" β€” mandatory, periodt.

the virt_bridgehelper processes execute with the virt_bridgehelper_t SELinux type. wanna check if you've got these processes running? just run the ps command with the -Z qualifier. easy.

for example:

ps -eZ | grep virt_bridgehelper_t

like, literally just do that and you'll see. iykyk. πŸ”₯


πŸ¦‹ ENTRYPOINTS πŸ¦‹

the virt_bridgehelper_t SELinux type can be entered via the virt_bridgehelper_exec_t file type. that's the doorway, bestie πŸšͺ✨

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

/usr/libexec/qemu-bridge-helper

one path. one icon. no cap.


πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (domains) for each process running on the system. slay, very structured of it.

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

policy governs the access confined processes have to files. the SELinux virt_bridgehelper policy is very flexible, allowing users to set up their virt_bridgehelper processes in as secure a method as possible. flexible and secure? we love a balanced icon. πŸ’…

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. so like, it's not a hall pass β€” the receipts still get printed. πŸ‘€

πŸŽ€ BOOLEANS πŸŽ€

SELinux policy is customizable based on least access required. the 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. tightest access = main character energy fr fr.

if you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. it's Enabled by default.

setsebool -P fips_mode 1

that -P is not optional bestie, it makes it persistent. don't skip it. πŸ™ˆ


🧚 MANAGED FILES 🧚

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 β€” SELinux isn't out here doing DAC's homework for it. 😭

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

look at all those regexes. she's thorough. she contains multitudes. 🌈


πŸ’œ FILE CONTEXTS πŸ’œ

SELinux requires files to have an extended attribute to define the file type. no attribute, no entry, that's the rule.

you can see the context of a file using the -Z option to ls.

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

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the virt_bridgehelper β€” and if you wanted to store files with these types in 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, we respect the pipeline. 🫢

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. regex girlies rise. ✨

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. that's the whole point of it, honestly.
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. temporary vs permanent is a whole personality difference, don't mix them up πŸ’€

πŸ”₯ 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. a GUI! for the visual learners! we love accessibility 🎨

πŸ“ AUTHOR πŸ“

this manual page was auto-generated using sepolicy manpage. not me being written by a script and still serving this much cunt πŸ’…βœ¨


🌟 SEE ALSO 🌟

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

go read those too, bestie, knowledge is free and it's cute πŸ¦‹


okay that's the whole page!! this one came from virt_bridgehelper, dated 26-10-06, and it's the virt_bridgehelper_selinux(8) manual through and through. mwah πŸ’– go label something responsibly, and remember: restorecon is your friend, not your enemy. πŸŽ€πŸ‘‘

πŸ“¦ where this page comes from