|
Server : Apache System : Linux server.mata-lashes.com 3.10.0-1160.90.1.el7.x86_64 #1 SMP Thu May 4 15:21:22 UTC 2023 x86_64 User : matalashes ( 1004) PHP Version : 8.1.29 Disable Function : NONE Directory : /usr/share/selinux/devel/html/ |
Upload File : |
<!-- Creator : groff version 1.22.2 -->
<!-- CreationDate: Mon Nov 16 16:49:56 2020 -->
<!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>container_selinux</title>
</head>
<body>
<h1 align="center">container_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="#MCS Constrained">MCS Constrained</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">container_selinux
− Security Enhanced Linux Policy for the container
processes</p>
<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Security-Enhanced
Linux secures the container processes via flexible mandatory
access control.</p>
<p style="margin-left:11%; margin-top: 1em">The container
processes execute with the container_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 container_t</b></p>
<h2>ENTRYPOINTS
<a name="ENTRYPOINTS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The container_t
SELinux type can be entered via the <b>file_type</b> file
type.</p>
<p style="margin-left:11%; margin-top: 1em">The default
entrypoint paths for the container_t domain are the
following:</p>
<p style="margin-left:11%; margin-top: 1em">all files on
the system</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
container policy is very flexible allowing users to setup
their container processes in as secure a method as
possible.</p>
<p style="margin-left:11%; margin-top: 1em">The following
process types are defined for container:</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_runtime_t,
container_auth_t, container_t</b></p>
<p style="margin-left:11%; margin-top: 1em">Note:
<b>semanage permissive -a container_t</b> can be used to
make the process type container_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 container_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 container_t:s0:c1,c2, and
another process launched with container_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. container
policy is extremely flexible and has several booleans that
allow you to manipulate the policy and run container with
the tightest access possible.</p>
<p style="margin-left:11%; margin-top: 1em">If you want to
deny any process from ptracing or debugging any other
processes, you must turn on the deny_ptrace boolean. Enabled
by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
deny_ptrace 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow any process to mmap any file on system with attribute
file_type, you must turn on the domain_can_mmap_files
boolean. Enabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
domain_can_mmap_files 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow all domains write to kmsg_device, while kernel is
executed with systemd.log_target=kmsg parameter, you must
turn on the domain_can_write_kmsg boolean. Disabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
domain_can_write_kmsg 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow all domains to use other domains file descriptors, you
must turn on the domain_fd_use boolean. Enabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
domain_fd_use 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow all domains to have the kernel load modules, you must
turn on the domain_kernel_load_modules boolean. Disabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
domain_kernel_load_modules 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow all domains to execute in fips_mode, you must turn on
the fips_mode boolean. Enabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
fips_mode 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
enable reading of urandom for all domains, you must turn on
the global_ssp boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
global_ssp 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow sandbox containers manage fuse files, you must turn on
the virt_sandbox_use_fusefs boolean. Disabled by
default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
virt_sandbox_use_fusefs 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow confined virtual guests to manage nfs files, you must
turn on the virt_use_nfs boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
virt_use_nfs 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow confined virtual guests to manage cifs files, you must
turn on the virt_use_samba boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
virt_use_samba 1</b></p>
<h2>MANAGED FILES
<a name="MANAGED FILES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The SELinux
process type container_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>cephfs_t</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>cifs_t</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>container_file_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>/var/lib/kubelet(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="7%"></td>
<td width="85%">
<p>/var/lib/docker/vfs(/.*)?</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>fusefs_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>/var/run/user/[^/]*/gvfs</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>hugetlbfs_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>/dev/hugepages</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/usr/lib/udev/devices/hugepages</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>nfs_t</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>−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
container policy is very flexible allowing users to setup
their container processes in as secure a method as
possible.</p>
<p style="margin-left:11%; margin-top: 1em"><b>EQUIVALENCE
DIRECTORIES</b></p>
<p style="margin-left:11%; margin-top: 1em">container
policy stores data with multiple different file context
types under the /var/lib/docker directory. If you would like
to store the data in a different directory you can use the
semanage command to create an equivalence mapping. If you
wanted to store this data under the /srv dirctory you would
execute the following command:</p>
<p style="margin-left:11%; margin-top: 1em"><b>semanage
fcontext -a -e /var/lib/docker /srv/docker <br>
restorecon -R -v /srv/docker</b></p>
<p style="margin-left:11%; margin-top: 1em">container
policy stores data with multiple different file context
types under the /var/run/docker directory. If you would like
to store the data in a different directory you can use the
semanage command to create an equivalence mapping. If you
wanted to store this data under the /srv dirctory you would
execute the following command:</p>
<p style="margin-left:11%; margin-top: 1em"><b>semanage
fcontext -a -e /var/run/docker /srv/docker <br>
restorecon -R -v /srv/docker</b></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 container, if you wanted to
store files with these types in a diffent paths, you need to
execute the semanage command to sepecify 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 container_var_run_t
’/srv/mycontainer_content(/.*)?’ <br>
restorecon -R -v /srv/mycontainer_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 container:</i></p>
<p style="margin-left:11%; margin-top: 1em"><b>container_auth_exec_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_auth_exec_t type, if you want to
transition an executable to the container_auth_t domain.
<br>
Paths:</p>
<p style="margin-left:18%;">/usr/bin/docker-novolume-plugin,
/usr/lib/docker/docker-novolume-plugin</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_config_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_config_t type, if you want to treat the
files as container configuration data, usually stored under
the /etc directory.</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_file_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_file_t type, if you want to treat the
files as container content. <br>
Paths:</p>
<p style="margin-left:18%;">/var/lib/kubelet(/.*)?,
/var/lib/docker/vfs(/.*)?</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_home_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_home_t type, if you want to store
container files in the users home directory.</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_lock_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_lock_t type, if you want to treat the
files as container lock data, stored under the /var/lock
directory</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_log_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_log_t type, if you want to treat the data
as container log data, usually stored under the /var/log
directory.</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_plugin_var_run_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_plugin_var_run_t type, if you want to
store the container plugin files under the /run or /var/run
directory.</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_runtime_exec_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_runtime_exec_t type, if you want to
transition an executable to the container_runtime_t
domain.</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_runtime_tmp_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_runtime_tmp_t type, if you want to store
container runtime temporary files in the /tmp
directories.</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_runtime_tmpfs_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_runtime_tmpfs_t type, if you want to
store container runtime files on a tmpfs file system.</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_share_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_share_t type, if you want to treat the
files as container share data. <br>
Paths:</p>
<p style="margin-left:18%;">/var/lib/docker/.*/config.env,
/var/lib/docker/init(/.*)?, /var/lib/docker/overlay(/.*)?,
/var/lib/docker/containers/.*/hosts,
/var/lib/docker/containers/.*/hostname</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_unit_file_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_unit_file_t type, if you want to treat
the files as container unit content. <br>
Paths:</p>
<p style="margin-left:18%;">/usr/lib/systemd/system/docker.service,
/usr/lib/systemd/system/docker-novolume-plugin.service</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_var_lib_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_var_lib_t type, if you want to store the
container files under the /var/lib directory. <br>
Paths:</p>
<p style="margin-left:18%;">/var/lib/docker(/.*)?,
/var/lib/kublet(/.*)?, /var/lib/containers(/.*)?</p>
<p style="margin-left:11%; margin-top: 1em"><b>container_var_run_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the container_var_run_t type, if you want to store the
container files under the /run or /var/run directory. <br>
Paths:</p>
<p style="margin-left:18%;">/var/run/docker(/.*)?,
/var/run/containerd(/.*)?, /var/run/docker-client(/.*)?,
/var/run/docker.pid, /var/run/docker.sock</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),
container(8), semanage(8), restorecon(8), chcon(1),
sepolicy(8) , setsebool(8), container_auth_selinux(8),
container_auth_selinux(8), container_runtime_selinux(8),
container_runtime_selinux(8)</p>
<hr>
</body>
</html>