1chrome_sandbox_nacl_selSiEnLuixn(u8x)Policy chrome_sandbcohxr_onmaec_lsandbox_nacl_selinux(8)
2
3
4
6 chrome_sandbox_nacl_selinux - Security Enhanced Linux Policy for the
7 chrome_sandbox_nacl processes
8
10 Security-Enhanced Linux secures the chrome_sandbox_nacl processes via
11 flexible mandatory access control.
12
13 The chrome_sandbox_nacl processes execute with the chrome_sand‐
14 box_nacl_t SELinux type. You can check if you have these processes run‐
15 ning by executing the ps command with the -Z qualifier.
16
17 For example:
18
19 ps -eZ | grep chrome_sandbox_nacl_t
20
21
22
24 The chrome_sandbox_nacl_t SELinux type can be entered via the bin_t,
25 chrome_sandbox_nacl_exec_t, usr_t file types.
26
27 The default entrypoint paths for the chrome_sandbox_nacl_t domain are
28 the following:
29
30 All executeables with the default executable label, usually stored in
31 /usr/bin and /usr/sbin. /opt/google/chrome[^/]*/nacl_helper_bootstrap,
32 /opt/google/chrome/nacl_helper_bootstrap, /usr/lib/chromium-
33 browser/nacl_helper_bootstrap, /usr/.*, /opt/.*, /emul/.*,
34 /ostree(/.*)?, /export(/.*)?, /usr/doc(/.*)?/lib(/.*)?,
35 /usr/inclu.e(/.*)?, /usr/share/doc(/.*)?/README.*, /usr, /opt, /emul
36
38 SELinux defines process types (domains) for each process running on the
39 system
40
41 You can see the context of a process using the -Z option to ps
42
43 Policy governs the access confined processes have to files. SELinux
44 chrome_sandbox_nacl policy is very flexible allowing users to setup
45 their chrome_sandbox_nacl processes in as secure a method as possible.
46
47 The following process types are defined for chrome_sandbox_nacl:
48
49 chrome_sandbox_nacl_t
50
51 Note: semanage permissive -a chrome_sandbox_nacl_t can be used to make
52 the process type chrome_sandbox_nacl_t permissive. SELinux does not
53 deny access to permissive process types, but the AVC (SELinux denials)
54 messages are still generated.
55
56
58 SELinux policy is customizable based on least access required.
59 chrome_sandbox_nacl policy is extremely flexible and has several bool‐
60 eans that allow you to manipulate the policy and run chrome_sand‐
61 box_nacl with the tightest access possible.
62
63
64
65 If you want to deny any process from ptracing or debugging any other
66 processes, you must turn on the deny_ptrace boolean. Enabled by
67 default.
68
69 setsebool -P deny_ptrace 1
70
71
72
73 If you want to allow any process to mmap any file on system with
74 attribute file_type, you must turn on the domain_can_mmap_files bool‐
75 ean. Enabled by default.
76
77 setsebool -P domain_can_mmap_files 1
78
79
80
81 If you want to allow all domains write to kmsg_device, while kernel is
82 executed with systemd.log_target=kmsg parameter, you must turn on the
83 domain_can_write_kmsg boolean. Disabled by default.
84
85 setsebool -P domain_can_write_kmsg 1
86
87
88
89 If you want to allow all domains to use other domains file descriptors,
90 you must turn on the domain_fd_use boolean. Enabled by default.
91
92 setsebool -P domain_fd_use 1
93
94
95
96 If you want to allow all domains to have the kernel load modules, you
97 must turn on the domain_kernel_load_modules boolean. Disabled by
98 default.
99
100 setsebool -P domain_kernel_load_modules 1
101
102
103
104 If you want to allow all domains to execute in fips_mode, you must turn
105 on the fips_mode boolean. Enabled by default.
106
107 setsebool -P fips_mode 1
108
109
110
111 If you want to enable reading of urandom for all domains, you must turn
112 on the global_ssp boolean. Disabled by default.
113
114 setsebool -P global_ssp 1
115
116
117
119 The SELinux process type chrome_sandbox_nacl_t can manage files labeled
120 with the following file types. The paths listed are the default paths
121 for these file types. Note the processes UID still need to have DAC
122 permissions.
123
124 chrome_sandbox_home_t
125
126 /home/[^/]+/.cache/chromium(/.*)?
127 /home/[^/]+/.cache/google-chrome(/.*)?
128 /home/[^/]+/.cache/google-chrome-unstable(/.*)?
129
130 chrome_sandbox_tmpfs_t
131
132
133
135 SELinux requires files to have an extended attribute to define the file
136 type.
137
138 You can see the context of a file using the -Z option to ls
139
140 Policy governs the access confined processes have to these files.
141 SELinux chrome_sandbox_nacl policy is very flexible allowing users to
142 setup their chrome_sandbox_nacl processes in as secure a method as pos‐
143 sible.
144
145 The following file types are defined for chrome_sandbox_nacl:
146
147
148
149 chrome_sandbox_nacl_exec_t
150
151 - Set files with the chrome_sandbox_nacl_exec_t type, if you want to
152 transition an executable to the chrome_sandbox_nacl_t domain.
153
154
155 Paths:
156 /opt/google/chrome[^/]*/nacl_helper_bootstrap,
157 /opt/google/chrome/nacl_helper_bootstrap, /usr/lib/chromium-
158 browser/nacl_helper_bootstrap
159
160
161 Note: File context can be temporarily modified with the chcon command.
162 If you want to permanently change the file context you need to use the
163 semanage fcontext command. This will modify the SELinux labeling data‐
164 base. You will need to use restorecon to apply the labels.
165
166
168 semanage fcontext can also be used to manipulate default file context
169 mappings.
170
171 semanage permissive can also be used to manipulate whether or not a
172 process type is permissive.
173
174 semanage module can also be used to enable/disable/install/remove pol‐
175 icy modules.
176
177 semanage boolean can also be used to manipulate the booleans
178
179
180 system-config-selinux is a GUI tool available to customize SELinux pol‐
181 icy settings.
182
183
185 This manual page was auto-generated using sepolicy manpage .
186
187
189 selinux(8), chrome_sandbox_nacl(8), semanage(8), restorecon(8),
190 chcon(1), sepolicy(8) , setsebool(8)
191
192
193
194chrome_sandbox_nacl 19-04-25 chrome_sandbox_nacl_selinux(8)