Current File : //kunden/usr/share/selinux/devel/html/sandbox.html
<!-- Creator     : groff version 1.22.4 -->
<!-- CreationDate: Thu Apr 10 20:00:00 2025 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="Content-Style" content="text/css">
<style type="text/css">
       p       { margin-top: 0; margin-bottom: 0; vertical-align: top }
       pre     { margin-top: 0; margin-bottom: 0; vertical-align: top }
       table   { margin-top: 0; margin-bottom: 0; vertical-align: top }
       h1      { text-align: center }
</style>
<title>sandbox_selinux</title>

</head>
<body>

<h1 align="center">sandbox_selinux</h1>

<a href="#NAME">NAME</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#PROCESS TYPES">PROCESS TYPES</a><br>
<a href="#MCS Constrained">MCS Constrained</a><br>
<a href="#BOOLEANS">BOOLEANS</a><br>
<a href="#FILE CONTEXTS">FILE CONTEXTS</a><br>
<a href="#COMMANDS">COMMANDS</a><br>
<a href="#AUTHOR">AUTHOR</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>

<hr>


<h2>NAME
<a name="NAME"></a>
</h2>



<p style="margin-left:11%; margin-top: 1em">sandbox_selinux
&minus; Security Enhanced Linux Policy for the sandbox
processes</p>

<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>



<p style="margin-left:11%; margin-top: 1em">Security-Enhanced
Linux secures the sandbox processes via flexible mandatory
access control.</p>

<p style="margin-left:11%; margin-top: 1em">The sandbox
processes execute with the sandbox_t SELinux type. You can
check if you have these processes running by executing the
<b>ps</b> command with the <b>&minus;Z</b> qualifier.</p>

<p style="margin-left:11%; margin-top: 1em">For
example:</p>

<p style="margin-left:11%; margin-top: 1em"><b>ps -eZ |
grep sandbox_t</b></p>

<h2>PROCESS TYPES
<a name="PROCESS TYPES"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">SELinux defines
process types (domains) for each process running on the
system</p>

<p style="margin-left:11%; margin-top: 1em">You can see the
context of a process using the <b>&minus;Z</b> option to
<b>ps</b></p>

<p style="margin-left:11%; margin-top: 1em">Policy governs
the access confined processes have to files. SELinux sandbox
policy is very flexible allowing users to setup their
sandbox processes in as secure a method as possible.</p>

<p style="margin-left:11%; margin-top: 1em">The following
process types are defined for sandbox:</p>

<p style="margin-left:11%; margin-top: 1em"><b>sandbox_t,
sandbox_xserver_t, sandbox_min_t, sandbox_min_client_t,
sandbox_x_t, sandbox_x_client_t, sandbox_web_t,
sandbox_web_client_t, sandbox_net_t,
sandbox_net_client_t</b></p>

<p style="margin-left:11%; margin-top: 1em">Note:
<b>semanage permissive -a sandbox_t</b> can be used to make
the process type sandbox_t permissive. SELinux does not deny
access to permissive process types, but the AVC (SELinux
denials) messages are still generated.</p>

<h2>MCS Constrained
<a name="MCS Constrained"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">The SELinux
process type sandbox_t is an MCS (Multi Category Security)
constrained type. Sometimes this separation is referred to
as sVirt. These types are usually used for securing
multi-tenant environments, such as virtualization,
containers or separation of users. The tools used to launch
MCS types, pick out a different MCS label for each process
group.</p>

<p style="margin-left:11%; margin-top: 1em">For example one
process might be launched with sandbox_t:s0:c1,c2, and
another process launched with sandbox_t:s0:c3,c4. The
SELinux kernel only allows these processes can only write to
content with a matching MCS label, or a MCS Label of s0. A
process running with the MCS level of s0:c1,c2 is not
allowed to write to content with the MCS label of
s0:c3,c4</p>

<h2>BOOLEANS
<a name="BOOLEANS"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">SELinux policy
is customizable based on least access required. sandbox
policy is extremely flexible and has several booleans that
allow you to manipulate the policy and run sandbox with the
tightest access possible.</p>

<p style="margin-left:11%; margin-top: 1em">If you want to
deny user domains applications to map a memory region as
both executable and writable, this is dangerous and the
executable should be reported in bugzilla, you must turn on
the deny_execmem boolean. Disabled by default.</p>

<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
deny_execmem 1</b></p>

<h2>FILE CONTEXTS
<a name="FILE CONTEXTS"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">SELinux
requires files to have an extended attribute to define the
file type.</p>

<p style="margin-left:11%; margin-top: 1em">You can see the
context of a file using the <b>&minus;Z</b> option to
<b>ls</b></p>

<p style="margin-left:11%; margin-top: 1em">Policy governs
the access confined processes have to these files. SELinux
sandbox policy is very flexible allowing users to setup
their sandbox processes in as secure a method as
possible.</p>

<p style="margin-left:11%; margin-top: 1em"><b>STANDARD
FILE CONTEXT</b></p>

<p style="margin-left:11%; margin-top: 1em">SELinux defines
the file context types for the sandbox, 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.</p>

<p style="margin-left:11%; margin-top: 1em"><b>semanage
fcontext -a -t sandbox_xserver_tmpfs_t
&rsquo;/srv/mysandbox_content(/.*)?&rsquo; <br>
restorecon -R -v /srv/mysandbox_content</b></p>

<p style="margin-left:11%; margin-top: 1em">Note: SELinux
often uses regular expressions to specify labels that match
multiple files.</p>

<p style="margin-left:11%; margin-top: 1em"><i>The
following file types are defined for sandbox:</i></p>


<p style="margin-left:11%; margin-top: 1em"><b>sandbox_devpts_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the sandbox_devpts_t type, if you want to treat the
files as sandbox devpts data.</p>


<p style="margin-left:11%; margin-top: 1em"><b>sandbox_exec_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the sandbox_exec_t type, if you want to transition an
executable to the sandbox_t domain.</p>


<p style="margin-left:11%; margin-top: 1em"><b>sandbox_file_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the sandbox_file_t type, if you want to treat the files
as sandbox content.</p>


<p style="margin-left:11%; margin-top: 1em"><b>sandbox_min_client_tmpfs_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the sandbox_min_client_tmpfs_t type, if you want to
store sandbox min client files on a tmpfs file system.</p>


<p style="margin-left:11%; margin-top: 1em"><b>sandbox_net_client_tmpfs_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the sandbox_net_client_tmpfs_t type, if you want to
store sandbox net client files on a tmpfs file system.</p>


<p style="margin-left:11%; margin-top: 1em"><b>sandbox_web_client_tmpfs_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the sandbox_web_client_tmpfs_t type, if you want to
store sandbox web client files on a tmpfs file system.</p>


<p style="margin-left:11%; margin-top: 1em"><b>sandbox_x_client_tmpfs_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the sandbox_x_client_tmpfs_t type, if you want to store
sandbox x client files on a tmpfs file system.</p>


<p style="margin-left:11%; margin-top: 1em"><b>sandbox_xserver_tmpfs_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the sandbox_xserver_tmpfs_t type, if you want to store
sandbox xserver files on a tmpfs file system.</p>

<p style="margin-left:11%; margin-top: 1em">Note: File
context can be temporarily modified with the chcon command.
If you want to permanently change the file context you need
to use the <b>semanage fcontext</b> command. This will
modify the SELinux labeling database. You will need to use
<b>restorecon</b> to apply the labels.</p>

<h2>COMMANDS
<a name="COMMANDS"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em"><b>semanage
fcontext</b> can also be used to manipulate default file
context mappings.</p>

<p style="margin-left:11%; margin-top: 1em"><b>semanage
permissive</b> can also be used to manipulate whether or not
a process type is permissive.</p>

<p style="margin-left:11%; margin-top: 1em"><b>semanage
module</b> can also be used to enable/disable/install/remove
policy modules.</p>

<p style="margin-left:11%; margin-top: 1em"><b>semanage
boolean</b> can also be used to manipulate the booleans</p>


<p style="margin-left:11%; margin-top: 1em"><b>system-config-selinux</b>
is a GUI tool available to customize SELinux policy
settings.</p>

<h2>AUTHOR
<a name="AUTHOR"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">This manual
page was auto-generated using <b>sepolicy manpage .</b></p>

<h2>SEE ALSO
<a name="SEE ALSO"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">selinux(8),
sandbox(8), semanage(8), restorecon(8), chcon(1),
sepolicy(8), setsebool(8), sandbox_min_selinux(8),
sandbox_min_selinux(8), sandbox_min_client_selinux(8),
sandbox_min_client_selinux(8), sandbox_net_selinux(8),
sandbox_net_selinux(8), sandbox_net_client_selinux(8),
sandbox_net_client_selinux(8), sandbox_web_selinux(8),
sandbox_web_selinux(8), sandbox_web_client_selinux(8),
sandbox_web_client_selinux(8), sandbox_x_selinux(8),
sandbox_x_selinux(8), sandbox_x_client_selinux(8),
sandbox_x_client_selinux(8), sandbox_xserver_selinux(8),
sandbox_xserver_selinux(8)</p>
<hr>
</body>
</html>