1ganesha_selinux(8) SELinux Policy ganesha ganesha_selinux(8)
2
3
4
6 ganesha_selinux - Security Enhanced Linux Policy for the ganesha pro‐
7 cesses
8
10 Security-Enhanced Linux secures the ganesha processes via flexible
11 mandatory access control.
12
13 The ganesha processes execute with the ganesha_t SELinux type. You can
14 check if you have these processes running by executing the ps command
15 with the -Z qualifier.
16
17 For example:
18
19 ps -eZ | grep ganesha_t
20
21
22
24 The ganesha_t SELinux type can be entered via the ganesha_exec_t file
25 type.
26
27 The default entrypoint paths for the ganesha_t domain are the follow‐
28 ing:
29
30 /usr/bin/ganesha.nfsd
31
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 ganesha policy is very flexible allowing users to setup their ganesha
40 processes in as secure a method as possible.
41
42 The following process types are defined for ganesha:
43
44 ganesha_t
45
46 Note: semanage permissive -a ganesha_t can be used to make the process
47 type ganesha_t permissive. SELinux does not deny access to permissive
48 process types, but the AVC (SELinux denials) messages are still gener‐
49 ated.
50
51
53 SELinux policy is customizable based on least access required. ganesha
54 policy is extremely flexible and has several booleans that allow you to
55 manipulate the policy and run ganesha with the tightest access possi‐
56 ble.
57
58
59
60 If you want to allow ganesha to read/write fuse files, you must turn on
61 the ganesha_use_fusefs boolean. Disabled by default.
62
63 setsebool -P ganesha_use_fusefs 1
64
65
66
67 If you want to allow users to resolve user passwd entries directly from
68 ldap rather then using a sssd server, you must turn on the authlo‐
69 gin_nsswitch_use_ldap boolean. Disabled by default.
70
71 setsebool -P authlogin_nsswitch_use_ldap 1
72
73
74
75 If you want to allow all daemons to write corefiles to /, you must turn
76 on the daemons_dump_core boolean. Disabled by default.
77
78 setsebool -P daemons_dump_core 1
79
80
81
82 If you want to enable cluster mode for daemons, you must turn on the
83 daemons_enable_cluster_mode boolean. Enabled by default.
84
85 setsebool -P daemons_enable_cluster_mode 1
86
87
88
89 If you want to allow all daemons to use tcp wrappers, you must turn on
90 the daemons_use_tcp_wrapper boolean. Disabled by default.
91
92 setsebool -P daemons_use_tcp_wrapper 1
93
94
95
96 If you want to allow all daemons the ability to read/write terminals,
97 you must turn on the daemons_use_tty boolean. Disabled by default.
98
99 setsebool -P daemons_use_tty 1
100
101
102
103 If you want to deny any process from ptracing or debugging any other
104 processes, you must turn on the deny_ptrace boolean. Enabled by
105 default.
106
107 setsebool -P deny_ptrace 1
108
109
110
111 If you want to allow any process to mmap any file on system with
112 attribute file_type, you must turn on the domain_can_mmap_files bool‐
113 ean. Enabled by default.
114
115 setsebool -P domain_can_mmap_files 1
116
117
118
119 If you want to allow all domains write to kmsg_device, while kernel is
120 executed with systemd.log_target=kmsg parameter, you must turn on the
121 domain_can_write_kmsg boolean. Disabled by default.
122
123 setsebool -P domain_can_write_kmsg 1
124
125
126
127 If you want to allow all domains to use other domains file descriptors,
128 you must turn on the domain_fd_use boolean. Enabled by default.
129
130 setsebool -P domain_fd_use 1
131
132
133
134 If you want to allow all domains to have the kernel load modules, you
135 must turn on the domain_kernel_load_modules boolean. Disabled by
136 default.
137
138 setsebool -P domain_kernel_load_modules 1
139
140
141
142 If you want to allow all domains to execute in fips_mode, you must turn
143 on the fips_mode boolean. Enabled by default.
144
145 setsebool -P fips_mode 1
146
147
148
149 If you want to enable reading of urandom for all domains, you must turn
150 on the global_ssp boolean. Disabled by default.
151
152 setsebool -P global_ssp 1
153
154
155
156 If you want to allow confined applications to run with kerberos, you
157 must turn on the kerberos_enabled boolean. Enabled by default.
158
159 setsebool -P kerberos_enabled 1
160
161
162
163 If you want to allow system to run with NIS, you must turn on the
164 nis_enabled boolean. Disabled by default.
165
166 setsebool -P nis_enabled 1
167
168
169
170 If you want to allow confined applications to use nscd shared memory,
171 you must turn on the nscd_use_shm boolean. Disabled by default.
172
173 setsebool -P nscd_use_shm 1
174
175
176
178 The SELinux process type ganesha_t can manage files labeled with the
179 following file types. The paths listed are the default paths for these
180 file types. Note the processes UID still need to have DAC permissions.
181
182 cluster_conf_t
183
184 /etc/cluster(/.*)?
185
186 cluster_var_lib_t
187
188 /var/lib/pcsd(/.*)?
189 /var/lib/cluster(/.*)?
190 /var/lib/openais(/.*)?
191 /var/lib/pengine(/.*)?
192 /var/lib/corosync(/.*)?
193 /usr/lib/heartbeat(/.*)?
194 /var/lib/heartbeat(/.*)?
195 /var/lib/pacemaker(/.*)?
196
197 cluster_var_run_t
198
199 /var/run/crm(/.*)?
200 /var/run/cman_.*
201 /var/run/rsctmp(/.*)?
202 /var/run/aisexec.*
203 /var/run/heartbeat(/.*)?
204 /var/run/corosync-qnetd(/.*)?
205 /var/run/corosync-qdevice(/.*)?
206 /var/run/cpglockd.pid
207 /var/run/corosync.pid
208 /var/run/rgmanager.pid
209 /var/run/cluster/rgmanager.sk
210
211 fusefs_t
212
213 /var/run/user/[^/]*/gvfs
214
215 ganesha_tmp_t
216
217
218 ganesha_var_log_t
219
220 /var/log/ganesha.log.*
221 /var/log/ganesha-gfapi.log.*
222
223 ganesha_var_run_t
224
225 /var/run/ganesha(/.*)?
226
227 glusterd_var_run_t
228
229 /var/run/gluster(/.*)?
230 /var/run/glusterd.*
231 /var/run/glusterd.*
232 /var/run/glusterd(/.*)?
233
234 root_t
235
236 /sysroot/ostree/deploy/.*-atomic.*/deploy(/.*)?
237 /
238 /initrd
239
240
242 SELinux requires files to have an extended attribute to define the file
243 type.
244
245 You can see the context of a file using the -Z option to ls
246
247 Policy governs the access confined processes have to these files.
248 SELinux ganesha policy is very flexible allowing users to setup their
249 ganesha processes in as secure a method as possible.
250
251 STANDARD FILE CONTEXT
252
253 SELinux defines the file context types for the ganesha, if you wanted
254 to store files with these types in a diffent paths, you need to execute
255 the semanage command to sepecify alternate labeling and then use
256 restorecon to put the labels on disk.
257
258 semanage fcontext -a -t ganesha_var_run_t '/srv/myganesha_con‐
259 tent(/.*)?'
260 restorecon -R -v /srv/myganesha_content
261
262 Note: SELinux often uses regular expressions to specify labels that
263 match multiple files.
264
265 The following file types are defined for ganesha:
266
267
268
269 ganesha_exec_t
270
271 - Set files with the ganesha_exec_t type, if you want to transition an
272 executable to the ganesha_t domain.
273
274
275
276 ganesha_tmp_t
277
278 - Set files with the ganesha_tmp_t type, if you want to store ganesha
279 temporary files in the /tmp directories.
280
281
282
283 ganesha_unit_file_t
284
285 - Set files with the ganesha_unit_file_t type, if you want to treat the
286 files as ganesha unit content.
287
288
289 Paths:
290 /usr/lib/systemd/system/nfs-ganesha.*e, /usr/lib/systemd/sys‐
291 tem/nfs-ganesha-lock.*, /usr/lib/systemd/system/nfs-ganesha-con‐
292 fig.*
293
294
295 ganesha_var_log_t
296
297 - Set files with the ganesha_var_log_t type, if you want to treat the
298 data as ganesha var log data, usually stored under the /var/log direc‐
299 tory.
300
301
302 Paths:
303 /var/log/ganesha.log.*, /var/log/ganesha-gfapi.log.*
304
305
306 ganesha_var_run_t
307
308 - Set files with the ganesha_var_run_t type, if you want to store the
309 ganesha files under the /run or /var/run directory.
310
311
312
313 Note: File context can be temporarily modified with the chcon command.
314 If you want to permanently change the file context you need to use the
315 semanage fcontext command. This will modify the SELinux labeling data‐
316 base. You will need to use restorecon to apply the labels.
317
318
320 semanage fcontext can also be used to manipulate default file context
321 mappings.
322
323 semanage permissive can also be used to manipulate whether or not a
324 process type is permissive.
325
326 semanage module can also be used to enable/disable/install/remove pol‐
327 icy modules.
328
329 semanage boolean can also be used to manipulate the booleans
330
331
332 system-config-selinux is a GUI tool available to customize SELinux pol‐
333 icy settings.
334
335
337 This manual page was auto-generated using sepolicy manpage .
338
339
341 selinux(8), ganesha(8), semanage(8), restorecon(8), chcon(1), sepol‐
342 icy(8) , setsebool(8)
343
344
345
346ganesha 19-04-25 ganesha_selinux(8)