1sandbox_x_selinux(8) SELinux Policy sandbox_x sandbox_x_selinux(8)
2
6 sandbox_x_selinux - Security Enhanced Linux Policy for the sandbox_x
7 processes
8
10 Security-Enhanced Linux secures the sandbox_x processes via flexible
11 mandatory access control.
12 The sandbox_x processes execute with the sandbox_x_t SELinux type. You
14 can check if you have these processes running by executing the ps com‐
15 mand with the -Z qualifier.
16 For example:
18 ps -eZ | grep sandbox_x_t
20
24 SELinux defines process types (domains) for each process running on the
25 system
26 You can see the context of a process using the -Z option to ps
28 Policy governs the access confined processes have to files. SELinux
30 sandbox_x policy is very flexible allowing users to setup their sand‐
31 box_x processes in as secure a method as possible.
32 The following process types are defined for sandbox_x:
34 sandbox_xserver_t, sandbox_x_t, sandbox_x_client_t
36 Note: semanage permissive -a sandbox_x_t can be used to make the
38 process type sandbox_x_t permissive. SELinux does not deny access to
39 permissive process types, but the AVC (SELinux denials) messages are
40 still generated.
41
44 The SELinux process type sandbox_x_t is an MCS (Multi Category Secu‐
45 rity) constrained type. Sometimes this separation is referred to as
46 sVirt. These types are usually used for securing multi-tenant environ‐
47 ments, such as virtualization, containers or separation of users. The
48 tools used to launch MCS types, pick out a different MCS label for each
49 process group.
50 For example one process might be launched with sandbox_x_t:s0:c1,c2,
52 and another process launched with sandbox_x_t:s0:c3,c4. The SELinux
53 kernel only allows these processes can only write to content with a
54 matching MCS label, or a MCS Label of s0. A process running with the
55 MCS level of s0:c1,c2 is not allowed to write to content with the MCS
56 label of s0:c3,c4
57
60 SELinux policy is customizable based on least access required. sand‐
61 box_x policy is extremely flexible and has several booleans that allow
62 you to manipulate the policy and run sandbox_x with the tightest access
63 possible.
64 If you want to deny user domains applications to map a memory region as
68 both executable and writable, this is dangerous and the executable
69 should be reported in bugzilla, you must turn on the deny_execmem bool‐
70 ean. Enabled by default.
71 setsebool -P deny_execmem 1
73
77 The SELinux process type sandbox_x_t can manage files labeled with the
78 following file types. The paths listed are the default paths for these
79 file types. Note the processes UID still need to have DAC permissions.
80 fusefs_t
82 /var/run/user/[^/]*/gvfs
84 mozilla_plugin_rw_t
86 /usr/lib/mozilla/plugins-wrapped(/.*)?
88 sandbox_file_t
90 sandbox_x_client_tmpfs_t
93 security_t
96 /selinux
98
101 semanage fcontext can also be used to manipulate default file context
102 mappings.
103 semanage permissive can also be used to manipulate whether or not a
105 process type is permissive.
106 semanage module can also be used to enable/disable/install/remove pol‐
108 icy modules.
109 semanage boolean can also be used to manipulate the booleans
111 system-config-selinux is a GUI tool available to customize SELinux pol‐
114 icy settings.
115
118 This manual page was auto-generated using sepolicy manpage .
119
122 selinux(8), sandbox_x(8), semanage(8), restorecon(8), chcon(1), sepol‐
123 icy(8), setsebool(8), sandbox_x_client_selinux(8), sand‐
124 box_x_client_selinux(8)
125sandbox_x 21-03-26 sandbox_x_selinux(8)