| Current File : //proc/self/root/kunden/proc/thread-self/root/usr/share/selinux/devel/html/svirt.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>svirt_selinux</title>
</head>
<body>
<h1 align="center">svirt_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">svirt_selinux
− Security Enhanced Linux Policy for the svirt
processes</p>
<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Security-Enhanced
Linux secures the svirt processes via flexible mandatory
access control.</p>
<p style="margin-left:11%; margin-top: 1em">The svirt
processes execute with the svirt_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 svirt_t</b></p>
<h2>ENTRYPOINTS
<a name="ENTRYPOINTS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The svirt_t
SELinux type can be entered via the <b>qemu_exec_t</b> file
type.</p>
<p style="margin-left:11%; margin-top: 1em">The default
entrypoint paths for the svirt_t domain are the
following:</p>
<p style="margin-left:11%; margin-top: 1em">/usr/libexec/qemu.*,
/usr/bin/qemu-system-.*, /usr/bin/qemu,
/usr/bin/qemu-kvm</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 svirt
policy is very flexible allowing users to setup their svirt
processes in as secure a method as possible.</p>
<p style="margin-left:11%; margin-top: 1em">The following
process types are defined for svirt:</p>
<p style="margin-left:11%; margin-top: 1em"><b>svirt_t,
svirt_tcg_t, svirt_qemu_net_t, svirt_socket_t,
svirt_kvm_net_t</b></p>
<p style="margin-left:11%; margin-top: 1em">Note:
<b>semanage permissive -a svirt_t</b> can be used to make
the process type svirt_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 svirt_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 svirt_t:s0:c1,c2, and another
process launched with svirt_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. svirt policy
is extremely flexible and has several booleans that allow
you to manipulate the policy and run svirt with the tightest
access possible.</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
allow confined virtual guests to use executable memory and
executable stack, you must turn on the virt_use_execmem
boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
virt_use_execmem 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow confined virtual guests to interact with rawip
sockets, you must turn on the virt_use_rawip boolean.
Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
virt_use_rawip 1</b></p>
<h2>MANAGED FILES
<a name="MANAGED FILES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The SELinux
process type svirt_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>fs_t</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>qemu_var_run_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/libvirt/qemu(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="7%"></td>
<td width="85%">
<p>/var/run/libvirt/qemu(/.*)?</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>svirt_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/[^/]+/.libvirt/qemu(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.cache/libvirt/qemu(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.config/libvirt/qemu(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.local/share/libvirt/boot(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.local/share/libvirt/images(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/home/[^/]+/.local/share/gnome-boxes/images(/.*)?</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>svirt_image_t</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>svirt_tmp_t</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>svirt_tmpfs_t</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>virt_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>/var/cache/oz(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/cache/libvirt(/.*)?</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
svirt policy is very flexible allowing users to setup their
svirt 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 svirt, 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 svirt_home_t
’/srv/mysvirt_content(/.*)?’ <br>
restorecon -R -v /srv/mysvirt_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 svirt:</i></p>
<p style="margin-left:11%; margin-top: 1em"><b>svirt_home_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the svirt_home_t type, if you want to store svirt files
in the users home directory. <br>
Paths:</p>
<p style="margin-left:18%;">/home/[^/]+/.libvirt/qemu(/.*)?,
/home/[^/]+/.cache/libvirt/qemu(/.*)?,
/home/[^/]+/.config/libvirt/qemu(/.*)?,
/home/[^/]+/.local/share/libvirt/boot(/.*)?,
/home/[^/]+/.local/share/libvirt/images(/.*)?,
/home/[^/]+/.local/share/gnome-boxes/images(/.*)?</p>
<p style="margin-left:11%; margin-top: 1em"><b>svirt_image_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the svirt_image_t type, if you want to treat the files
as svirt image data.</p>
<p style="margin-left:11%; margin-top: 1em"><b>svirt_tmp_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the svirt_tmp_t type, if you want to store svirt
temporary files in the /tmp directories.</p>
<p style="margin-left:11%; margin-top: 1em"><b>svirt_tmpfs_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the svirt_tmpfs_t type, if you want to store svirt
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),
svirt(8), semanage(8), restorecon(8), chcon(1), sepolicy(8),
setsebool(8), svirt_kvm_net_selinux(8),
svirt_kvm_net_selinux(8), svirt_qemu_net_selinux(8),
svirt_qemu_net_selinux(8), svirt_socket_selinux(8),
svirt_socket_selinux(8), svirt_tcg_selinux(8),
svirt_tcg_selinux(8)</p>
<hr>
</body>
</html>