| Current File : //proc/self/root/kunden/usr/share/selinux/devel/html/bluetooth.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>bluetooth_selinux</title>
</head>
<body>
<h1 align="center">bluetooth_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">bluetooth_selinux
− Security Enhanced Linux Policy for the bluetooth
processes</p>
<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Security-Enhanced
Linux secures the bluetooth processes via flexible mandatory
access control.</p>
<p style="margin-left:11%; margin-top: 1em">The bluetooth
processes execute with the bluetooth_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 bluetooth_t</b></p>
<h2>ENTRYPOINTS
<a name="ENTRYPOINTS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The bluetooth_t
SELinux type can be entered via the <b>bluetooth_exec_t</b>
file type.</p>
<p style="margin-left:11%; margin-top: 1em">The default
entrypoint paths for the bluetooth_t domain are the
following:</p>
<p style="margin-left:11%; margin-top: 1em">/usr/bin/dund,
/usr/bin/hidd, /usr/bin/pand, /usr/sbin/hcid,
/usr/sbin/sdpd, /usr/bin/rfcomm, /usr/sbin/hid2hci,
/usr/sbin/hciattach, /usr/sbin/bluetoothd,
/usr/libexec/bluetooth/bluetoothd</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
bluetooth policy is very flexible allowing users to setup
their bluetooth processes in as secure a method as
possible.</p>
<p style="margin-left:11%; margin-top: 1em">The following
process types are defined for bluetooth:</p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_t,
bluetooth_helper_t</b></p>
<p style="margin-left:11%; margin-top: 1em">Note:
<b>semanage permissive -a bluetooth_t</b> can be used to
make the process type bluetooth_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. bluetooth
policy is extremely flexible and has several booleans that
allow you to manipulate the policy and run bluetooth with
the tightest access possible.</p>
<p style="margin-left:11%; margin-top: 1em">If you want to
dontaudit all daemons scheduling requests (setsched,
sys_nice), you must turn on the daemons_dontaudit_scheduling
boolean. Enabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
daemons_dontaudit_scheduling 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
deny all system processes and Linux users to use bluetooth
wireless technology, you must turn on the deny_bluetooth
boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
deny_bluetooth 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
allow system to run with NIS, you must turn on the
nis_enabled boolean. Disabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
nis_enabled 1</b></p>
<p style="margin-left:11%; margin-top: 1em">If you want to
allow xguest to use blue tooth devices, you must turn on the
xguest_use_bluetooth boolean. Enabled by default.</p>
<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
xguest_use_bluetooth 1</b></p>
<h2>MANAGED FILES
<a name="MANAGED FILES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The SELinux
process type bluetooth_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>bluetooth_conf_rw_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>/etc/bluetooth/link_key</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_lock_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/lock/subsys/bluetoothd</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_tmp_t</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_var_lib_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/lib/bluetooth(/.*)?</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_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="92%">
<p>/var/run/sdp</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/bluetoothd_address</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>cluster_conf_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>/etc/cluster(/.*)?</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>cluster_var_lib_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/lib/pcsd(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/cluster(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/openais(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/pengine(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/corosync(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/usr/lib/heartbeat(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/heartbeat(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/pacemaker(/.*)?</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>cluster_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="92%">
<p>/var/run/crm(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/cman_.*</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/rsctmp(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/aisexec.*</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/heartbeat(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/pcsd-ruby.socket</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/corosync-qnetd(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/corosync-qdevice(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/pcsd.socket</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/corosync.pid</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/cpglockd.pid</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/rgmanager.pid</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/cluster/rgmanager.sk</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>krb5_host_rcache_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/tmp/krb5_0.rcache2</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/cache/krb5rcache(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/tmp/nfs_0</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/tmp/DNS_25</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/tmp/host_0</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/tmp/imap_0</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/tmp/HTTP_23</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/tmp/HTTP_48</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/tmp/ldap_55</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/tmp/ldap_487</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/tmp/ldapmap1_0</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>root_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>/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/initrd</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>sysfs_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>/sys(/.*)?</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>usbfs_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
bluetooth policy is very flexible allowing users to setup
their bluetooth 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 bluetooth, 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 bluetooth_unit_file_t
’/srv/mybluetooth_content(/.*)?’ <br>
restorecon -R -v /srv/mybluetooth_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 bluetooth:</i></p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_conf_rw_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the bluetooth_conf_rw_t type, if you want to treat the
files as bluetooth conf read/write content.</p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_conf_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the bluetooth_conf_t type, if you want to treat the
files as bluetooth configuration data, usually stored under
the /etc directory.</p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_exec_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the bluetooth_exec_t type, if you want to transition an
executable to the bluetooth_t domain. <br>
Paths:</p>
<p style="margin-left:18%;">/usr/bin/dund, /usr/bin/hidd,
/usr/bin/pand, /usr/sbin/hcid, /usr/sbin/sdpd,
/usr/bin/rfcomm, /usr/sbin/hid2hci, /usr/sbin/hciattach,
/usr/sbin/bluetoothd, /usr/libexec/bluetooth/bluetoothd</p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_helper_exec_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the bluetooth_helper_exec_t type, if you want to
transition an executable to the bluetooth_helper_t
domain.</p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_helper_tmp_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the bluetooth_helper_tmp_t type, if you want to store
bluetooth helper temporary files in the /tmp
directories.</p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_helper_tmpfs_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the bluetooth_helper_tmpfs_t type, if you want to store
bluetooth helper files on a tmpfs file system.</p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_initrc_exec_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the bluetooth_initrc_exec_t type, if you want to
transition an executable to the bluetooth_initrc_t domain.
<br>
Paths:</p>
<p style="margin-left:18%;">/etc/rc.d/init.d/dund,
/etc/rc.d/init.d/pand, /etc/rc.d/init.d/bluetooth</p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_lock_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the bluetooth_lock_t type, if you want to treat the
files as bluetooth lock data, stored under the /var/lock
directory</p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_tmp_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the bluetooth_tmp_t type, if you want to store
bluetooth temporary files in the /tmp directories.</p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_unit_file_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the bluetooth_unit_file_t type, if you want to treat
the files as bluetooth unit content.</p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_var_lib_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the bluetooth_var_lib_t type, if you want to store the
bluetooth files under the /var/lib directory.</p>
<p style="margin-left:11%; margin-top: 1em"><b>bluetooth_var_run_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the bluetooth_var_run_t type, if you want to store the
bluetooth files under the /run or /var/run directory. <br>
Paths:</p>
<p style="margin-left:18%;">/var/run/sdp,
/var/run/bluetoothd_address</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),
bluetooth(8), semanage(8), restorecon(8), chcon(1),
sepolicy(8), setsebool(8), bluetooth_helper_selinux(8),
bluetooth_helper_selinux(8)</p>
<hr>
</body>
</html>