openvswitch_selinux(8)
β¨ openvswitch_selinux β bestie edition β¨
okay so this is the SELinux manual page for the openvswitch processes, from the SELinux Policy openvswitch collection, and honestly? it's giving "mandatory access control but make it cute." let's get into it π
πΈ NAME πΈ
openvswitch_selinux β the Security Enhanced Linux Policy for the openvswitch processes. yes bestie, that's the whole vibe. π¦
π DESCRIPTION π
Security-Enhanced Linux secures the openvswitch processes via flexible mandatory access control. periodt. π₯
The openvswitch processes execute with the openvswitch_t SELinux type. you can check if you have these processes running by executing the ps command with the -Z qualifier, like this:
ps -eZ | grep openvswitch_t
slay, now you know if they're out there living their best life. π
π ENTRYPOINTS π
The openvswitch_t SELinux type can be entered via the openvswitch_exec_t file type. lowkey iconic how that works.
The default entrypoint paths for the openvswitch_t domain are literally these:
/usr/bin/ovs-vsctl, /usr/bin/ovsdb-ctl, /usr/bin/ovs-appctl,
/usr/bin/ovs-vswitchd, /usr/bin/ovsdb-server,
/usr/share/openvswitch/scripts/ovs-ctl
no cap, memorize these if you're tryna transition something. π
π¦ PROCESS TYPES π¦
SELinux defines process types (domains) for each process running on the system. it's giving "every queen gets her own category." β¨
You can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. SELinux openvswitch policy is very flexible allowing users to setup their openvswitch processes in as secure a method as possible. we love a flexible icon. π
The following process types are defined for openvswitch:
openvswitch_t
Note:semanage permissive -a openvswitch_tcan be used to make the process typeopenvswitch_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, she's chill but she still keeps receipts. π
π BOOLEANS π
SELinux policy is customizable based on least access required. openvswitch policy is extremely flexible and has several booleans that allow you to manipulate the policy and run openvswitch with the tightest access possible. tightest access = bestie behavior, fr fr. π«Ά
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
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
if you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.
setsebool -P nis_enabled 1
see? easy. booleans are just vibes you can toggle. π
πΊ PORT TYPES πΊ
SELinux defines port types to represent TCP and UDP ports. yes, ports have types now. we stan structured networking.
You can see the types associated with a port by using the following command:
semanage port -l
Policy governs the access confined processes have to these ports. SELinux openvswitch policy is very flexible allowing users to setup their openvswitch processes in as secure a method as possible. (say it with me: flexible, secure, iconic.) π
The following port types are defined for openvswitch:
openvswitch_port_t
Default Defined Ports:
tcp 6634
remember that number, bestie. it's on the test. π
π§ MANAGED FILES π§
The SELinux process type openvswitch_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 is powerful but she's not doing everything for you, okay?)
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
hugetlbfs_t
/dev/hugepages
/usr/lib/udev/devices/hugepages
ipsec_conf_file_t
/etc/racoon(/.*)?
/etc/strongswan.conf
/etc/strongimcv(/.*)?
/etc/strongswan(/.*)?
/etc/strongswan.d(/.*)?
/etc/ipsec.conf
/etc/strongswan/ipsec.conf
ipsec_key_file_t
/etc/ipsec.d(/.*)?
/etc/racoon/certs(/.*)?
/etc/ipsec.secrets.*
/var/lib/ipsec/nss(/.*)?
/etc/strongswan/ipsec.d(/.*)?
/etc/strongswan/swanctl/rsa(/.*)?
/etc/strongswan/swanctl/pkcs.*
/etc/strongswan/swanctl/x509.*
/etc/strongswan/ipsec.secrets.*
/etc/strongswan/swanctl/ecdsa(/.*)?
/etc/strongswan/swanctl/bliss/(/.*)?
/etc/strongswan/swanctl/pubkey(/.*)?
/etc/strongswan/swanctl/private(/.*)?
/etc/racoon/psk.txt
krb5_host_rcache_t
/var/tmp/krb5_0.rcache2
/var/cache/krb5rcache(/.*)?
/var/tmp/nfs_0
/var/tmp/DNS_25
/var/tmp/host_0
/var/tmp/imap_0
/var/tmp/HTTP_23
/var/tmp/HTTP_48
/var/tmp/ldap_55
/var/tmp/ldap_487
/var/tmp/ldapmap1_0
openvswitch_log_t
/var/log/openvswitch(/.*)?
openvswitch_rw_t
/etc/openvswitch(/.*)?
openvswitch_tmp_t
(no default paths listed, she's mysterious like that) π
openvswitch_var_lib_t
/var/lib/openvswitch(/.*)?
openvswitch_var_run_t
/run/openvswitch(/.*)?
root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
svirt_image_t
(no default paths listed)
svirt_tmp_t
(no default paths listed)
sysfs_t
/sys(/.*)?
that's a whole lot of file types, but honestly? she ate. π
β FILE CONTEXTS β
SELinux requires files to have an extended attribute to define the file type. it's like a little name tag for your files, so cute. π
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 openvswitch policy is very flexible allowing users to setup their openvswitch processes in as secure a method as possible.
π« STANDARD FILE CONTEXT π«
SELinux defines the file context types for the openvswitch, 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 openvswitch_exec_t '/srv/openvswitch/content(/.*)?'
restorecon -R -v /srv/myopenvswitch_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex bestie, we love her. π¦
The following file types are defined for openvswitch:
openvswitch_exec_tβ set files with theopenvswitch_exec_ttype, if you want to transition an executable to theopenvswitch_tdomain.
Paths:
/usr/bin/ovs-vsctl, /usr/bin/ovsdb-ctl, /usr/bin/ovs-appctl,
/usr/bin/ovs-vswitchd, /usr/bin/ovsdb-server,
/usr/share/openvswitch/scripts/ovs-ctl
openvswitch_log_tβ set files with theopenvswitch_log_ttype, if you want to treat the data asopenvswitchlog data, usually stored under the/var/logdirectory.openvswitch_rw_tβ set files with theopenvswitch_rw_ttype, if you want to treat the files asopenvswitchread/write content.openvswitch_tmp_tβ set files with theopenvswitch_tmp_ttype, if you want to storeopenvswitchtemporary files in the/tmpdirectories.openvswitch_tmpfs_tβ set files with theopenvswitch_tmpfs_ttype, if you want to storeopenvswitchfiles on atmpfsfile system.openvswitch_unit_file_tβ set files with theopenvswitch_unit_file_ttype, if you want to treat the files asopenvswitchunit content.openvswitch_var_lib_tβ set files with theopenvswitch_var_lib_ttype, if you want to store theopenvswitchfiles under the/var/libdirectory.openvswitch_var_run_tβ set files with theopenvswitch_var_run_ttype, if you want to store theopenvswitchfiles under the/runor/var/rundirectory.
Note: file context can be temporarily modified with thechconcommand. If you want to permanently change the file context you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels. so like,chconis the temp tattoo,semanage fcontext+restoreconis the real permanent ink. π
π 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 port can also be used to manipulate the port definitions
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 whole GUI, for when you're feeling fancy. β¨
π AUTHOR π
This manual page was auto-generated using sepolicy manpage. (auto-generated and still ate, honestly.) π«Ά
π SEE ALSO π
selinux(8), openvswitch(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
and that's the whole page bestie!! this one's from the openvswitch collection, dated 26-10-06, and it's page openvswitch_selinux(8). go forth and SELinux responsibly πππ¦
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms