virt_bridgehelper_selinux(8)

1virt_bridgehelper_selinuSxE(L8i)nux Policy virt_bridgehevlipretr_bridgehelper_selinux(8)
2
3
4

NAME

6       virt_bridgehelper_selinux  -  Security  Enhanced  Linux  Policy for the
7       virt_bridgehelper processes
8

DESCRIPTION

10       Security-Enhanced Linux secures  the  virt_bridgehelper  processes  via
11       flexible mandatory access control.
12
13       The  virt_bridgehelper  processes  execute with the virt_bridgehelper_t
14       SELinux type. You can check if you have these processes running by exe‐
15       cuting the ps command with the -Z qualifier.
16
17       For example:
18
19       ps -eZ | grep virt_bridgehelper_t
20
21
22

ENTRYPOINTS

24       The   virt_bridgehelper_t   SELinux   type   can  be  entered  via  the
25       virt_bridgehelper_exec_t file type.
26
27       The default entrypoint paths for the virt_bridgehelper_t domain are the
28       following:
29
30       /usr/libexec/qemu-bridge-helper
31

PROCESS TYPES

33       SELinux defines process types (domains) for each process running on the
34       system
35
36       You can see the context of a process using the -Z option to ps
37
38       Policy governs the access confined processes have  to  files.   SELinux
39       virt_bridgehelper policy is very flexible allowing users to setup their
40       virt_bridgehelper processes in as secure a method as possible.
41
42       The following process types are defined for virt_bridgehelper:
43
44       virt_bridgehelper_t
45
46       Note: semanage permissive -a virt_bridgehelper_t can be  used  to  make
47       the  process type virt_bridgehelper_t permissive. SELinux does not deny
48       access to permissive process types, but the AVC (SELinux denials)  mes‐
49       sages are still generated.
50
51

BOOLEANS

53       SELinux   policy  is  customizable  based  on  least  access  required.
54       virt_bridgehelper policy is extremely flexible and has several booleans
55       that  allow you to manipulate the policy and run virt_bridgehelper with
56       the tightest access possible.
57
58
59
60       If you want to deny any process from ptracing or  debugging  any  other
61       processes,  you  must  turn  on  the  deny_ptrace  boolean.  Enabled by
62       default.
63
64       setsebool -P deny_ptrace 1
65
66
67
68       If you want to allow any process  to  mmap  any  file  on  system  with
69       attribute  file_type,  you must turn on the domain_can_mmap_files bool‐
70       ean. Enabled by default.
71
72       setsebool -P domain_can_mmap_files 1
73
74
75
76       If you want to allow all domains write to kmsg_device, while kernel  is
77       executed  with  systemd.log_target=kmsg parameter, you must turn on the
78       domain_can_write_kmsg boolean. Disabled by default.
79
80       setsebool -P domain_can_write_kmsg 1
81
82
83
84       If you want to allow all domains to use other domains file descriptors,
85       you must turn on the domain_fd_use boolean. Enabled by default.
86
87       setsebool -P domain_fd_use 1
88
89
90
91       If  you  want to allow all domains to have the kernel load modules, you
92       must  turn  on  the  domain_kernel_load_modules  boolean.  Disabled  by
93       default.
94
95       setsebool -P domain_kernel_load_modules 1
96
97
98
99       If you want to allow all domains to execute in fips_mode, you must turn
100       on the fips_mode boolean. Enabled by default.
101
102       setsebool -P fips_mode 1
103
104
105
106       If you want to enable reading of urandom for all domains, you must turn
107       on the global_ssp boolean. Disabled by default.
108
109       setsebool -P global_ssp 1
110
111
112

MANAGED FILES

114       The  SELinux  process type virt_bridgehelper_t can manage files labeled
115       with the following file types.  The paths listed are the default  paths
116       for  these  file  types.  Note the processes UID still need to have DAC
117       permissions.
118
119       svirt_home_t
120
121            /home/[^/]+/.libvirt/qemu(/.*)?
122            /home/[^/]+/.cache/libvirt/qemu(/.*)?
123            /home/[^/]+/.config/libvirt/qemu(/.*)?
124            /home/[^/]+/.local/share/libvirt/boot(/.*)?
125            /home/[^/]+/.local/share/libvirt/images(/.*)?
126            /home/[^/]+/.local/share/gnome-boxes/images(/.*)?
127
128

FILE CONTEXTS

130       SELinux requires files to have an extended attribute to define the file
131       type.
132
133       You can see the context of a file using the -Z option to ls
134
135       Policy  governs  the  access  confined  processes  have to these files.
136       SELinux virt_bridgehelper policy is very  flexible  allowing  users  to
137       setup their virt_bridgehelper processes in as secure a method as possi‐
138       ble.
139
140       The following file types are defined for virt_bridgehelper:
141
142
143
144       virt_bridgehelper_exec_t
145
146       - Set files with the virt_bridgehelper_exec_t  type,  if  you  want  to
147       transition an executable to the virt_bridgehelper_t domain.
148
149
150
151       Note:  File context can be temporarily modified with the chcon command.
152       If you want to permanently change the file context you need to use  the
153       semanage fcontext command.  This will modify the SELinux labeling data‐
154       base.  You will need to use restorecon to apply the labels.
155
156

COMMANDS

158       semanage fcontext can also be used to manipulate default  file  context
159       mappings.
160
161       semanage  permissive  can  also  be used to manipulate whether or not a
162       process type is permissive.
163
164       semanage module can also be used to enable/disable/install/remove  pol‐
165       icy modules.
166
167       semanage boolean can also be used to manipulate the booleans
168
169
170       system-config-selinux is a GUI tool available to customize SELinux pol‐
171       icy settings.
172
173

AUTHOR

175       This manual page was auto-generated using sepolicy manpage .
176
177