| Current File : //kunden/usr/share/selinux/devel/html/chrome_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>chrome_sandbox_selinux</title>
</head>
<body>
<h1 align="center">chrome_sandbox_selinux</h1>
<a href="#NAME">NAME</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#ENTRYPOINTS">ENTRYPOINTS</a><br>
<a href="#PROCESS TYPES">PROCESS TYPES</a><br>
<a href="#BOOLEANS">BOOLEANS</a><br>
<a href="#MANAGED FILES">MANAGED FILES</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">chrome_sandbox_selinux
− Security Enhanced Linux Policy for the
chrome_sandbox processes</p>
<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Security-Enhanced
Linux secures the chrome_sandbox processes via flexible
mandatory access control.</p>
<p style="margin-left:11%; margin-top: 1em">The
chrome_sandbox processes execute with the chrome_sandbox_t
SELinux type. You can check if you have these processes
running by executing the <b>ps</b> command with the
<b>−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 chrome_sandbox_t</b></p>
<h2>ENTRYPOINTS
<a name="ENTRYPOINTS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The
chrome_sandbox_t SELinux type can be entered via the
<b>chrome_sandbox_exec_t</b> file type.</p>
<p style="margin-left:11%; margin-top: 1em">The default
entrypoint paths for the chrome_sandbox_t domain are the
following:</p>
<p style="margin-left:11%; margin-top: 1em">/opt/google/chrome[^/]*/chrome-sandbox,
/usr/lib/chromium-browser/chrome-sandbox</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>−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
chrome_sandbox policy is very flexible allowing users to
setup their chrome_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 chrome_sandbox:</p>
<p style="margin-left:11%; margin-top: 1em"><b>chrome_sandbox_t,
chrome_sandbox_nacl_t</b></p>
<p style="margin-left:11%; margin-top: 1em">Note:
<b>semanage permissive -a chrome_sandbox_t</b> can be used
to make the process type chrome_sandbox_t permissive.
SELinux does not deny access to permissive process types,
but the AVC (SELinux denials) messages are still
generated.</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.
chrome_sandbox policy is extremely flexible and has several
booleans that allow you to manipulate the policy and run
chrome_sandbox with the tightest access possible.</p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow confined applications to use nscd shared memory, you
must turn on the nscd_use_shm boolean. Enabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
nscd_use_shm 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow regular users direct dri device access, you must turn
on the selinuxuser_direct_dri_enabled boolean. Enabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
selinuxuser_direct_dri_enabled 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow unconfined users to transition to the chrome sandbox
domains when running chrome-sandbox, you must turn on the
unconfined_chrome_sandbox_transition boolean. Enabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
unconfined_chrome_sandbox_transition 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
support ecryptfs home directories, you must turn on the
use_ecryptfs_home_dirs boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
use_ecryptfs_home_dirs 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
support fusefs home directories, you must turn on the
use_fusefs_home_dirs boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
use_fusefs_home_dirs 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
support NFS home directories, you must turn on the
use_nfs_home_dirs boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
use_nfs_home_dirs 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
support SAMBA home directories, you must turn on the
use_samba_home_dirs boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
use_samba_home_dirs 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allows clients to write to the X server shared memory
segments, you must turn on the xserver_clients_write_xshm
boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
xserver_clients_write_xshm 1</b></p>
<h2>MANAGED FILES
<a name="MANAGED FILES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The SELinux
process type chrome_sandbox_t can manage files labeled with
the following file types. The paths listed are the default
paths for these file types. Note the processes UID still
need to have DAC permissions.</p>
<p style="margin-left:11%; margin-top: 1em"><b>cgroup_t</b></p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="8%"></td>
<td width="7%"></td>
<td width="85%">
<p>/sys/fs/cgroup</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>chrome_sandbox_home_t</b></p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.cache/chromium(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.config/chromium(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.cache/google-chrome(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.cache/google-chrome-unstable(/.*)?</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>chrome_sandbox_tmp_t</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>chrome_sandbox_tmpfs_t</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>home_cert_t</b></p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/root/.pki(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/root/.cert(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.pki(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.cert(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.local/share/networkmanagement/certificates(/.*)?</p> </td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.kde/share/apps/networkmanagement/certificates(/.*)?</p> </td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>mozilla_home_t</b></p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.lyx(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.java(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.adobe(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.gnash(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.webex(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.IBMERS(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.galeon(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.spicec(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/POkemon.*(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.icedtea(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.mozilla(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.phoenix(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.netscape(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.ICAClient(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.quakelive(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.macromedia(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.thunderbird(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.gcjwebplugin(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.grl-podcasts(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.cache/mozilla(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.icedteaplugin(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/zimbrauserdata(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.juniper_networks(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.cache/icedtea-web(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/abc</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/mozilla.pdf</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.gnashpluginrc</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>user_fonts_cache_t</b></p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/root/.fontconfig(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/root/.fonts/auto(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/root/.fonts.cache-.*</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/root/.cache/fontconfig(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.fontconfig(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.fonts/auto(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.fonts.cache-.*</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.cache/fontconfig(/.*)?</p></td></tr>
</table>
<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>−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
chrome_sandbox policy is very flexible allowing users to
setup their chrome_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 chrome_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 chrome_sandbox_home_t
’/srv/mychrome_sandbox_content(/.*)?’ <br>
restorecon -R -v /srv/mychrome_sandbox_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 chrome_sandbox:</i></p>
<p style="margin-left:11%; margin-top: 1em"><b>chrome_sandbox_exec_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the chrome_sandbox_exec_t type, if you want to
transition an executable to the chrome_sandbox_t domain.
<br>
Paths:</p>
<p style="margin-left:18%;">/opt/google/chrome[^/]*/chrome-sandbox,
/usr/lib/chromium-browser/chrome-sandbox</p>
<p style="margin-left:11%; margin-top: 1em"><b>chrome_sandbox_home_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the chrome_sandbox_home_t type, if you want to store
chrome sandbox files in the users home directory. <br>
Paths:</p>
<p style="margin-left:18%;">/home/[^/]+/.cache/chromium(/.*)?,
/home/[^/]+/.config/chromium(/.*)?,
/home/[^/]+/.cache/google-chrome(/.*)?,
/home/[^/]+/.cache/google-chrome-unstable(/.*)?</p>
<p style="margin-left:11%; margin-top: 1em"><b>chrome_sandbox_nacl_exec_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the chrome_sandbox_nacl_exec_t type, if you want to
transition an executable to the chrome_sandbox_nacl_t
domain. <br>
Paths:</p>
<p style="margin-left:18%;">/opt/google/chrome[^/]*/nacl_helper_bootstrap,
/opt/google/chrome/nacl_helper_bootstrap,
/usr/lib/chromium-browser/nacl_helper_bootstrap</p>
<p style="margin-left:11%; margin-top: 1em"><b>chrome_sandbox_tmp_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the chrome_sandbox_tmp_t type, if you want to store
chrome sandbox temporary files in the /tmp directories.</p>
<p style="margin-left:11%; margin-top: 1em"><b>chrome_sandbox_tmpfs_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the chrome_sandbox_tmpfs_t type, if you want to store
chrome sandbox 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),
chrome_sandbox(8), semanage(8), restorecon(8), chcon(1),
sepolicy(8), setsebool(8), chrome_sandbox_nacl_selinux(8),
chrome_sandbox_nacl_selinux(8)</p>
<hr>
</body>
</html>