bluetooth_selinux(8)

📦
version 20250627+git412.dbf877ab7 · 7 versions
, in opensuse-leap 16.0

💙 bluetooth_selinux(8) — the SELinux policy for bluetooth, but make it make sense

okay so bestie, this page is bluetooth_selinux(8) from the bluetooth SELinux policy section, and it's literally the whole rundown on how SELinux keeps an eye on your bluetooth processes. grab a snack, we're getting into it 🎀

✨ NAME ✨

bluetooth_selinux — the Security Enhanced Linux Policy for the bluetooth processes. that's it, that's the whole name, and honestly? iconic.

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the bluetooth processes via flexy mandatory access control. yes, mandatory — not advisory, not "if you feel like it." the policy is the main character here 👑

Your bluetooth processes run with the bluetooth_t SELinux type. want to check if you've got these processes running rn? just run the ps command with the -Z qualifier, like this:

ps -eZ | grep bluetooth_t

that's the vibe check, and it never misses 💅

🦋 ENTRYPOINTS 🦋

So the bluetooth_t SELinux type can be entered via the bluetooth_exec_t file type. that's the door, periodt.

The default entrypoint paths for the bluetooth_t domain are literally these, no cap:

/usr/bin/dund, /usr/bin/hcid, /usr/bin/hidd, /usr/bin/pand,
/usr/bin/sdpd, /usr/bin/rfcomm, /usr/bin/hid2hci, /usr/bin/hciattach,
/usr/bin/bluetoothd, /usr/libexec/bluetooth/bluetoothd

🌈 PROCESS TYPES 🌈

SELinux defines process types (domains) for each process running on the system. yes, every single one gets a little label, it's giving personalized name tag at a party 🎉

You can peek at the context of a process using the -Z option to ps.

Policy governs the access confined processes have to files. the SELinux bluetooth policy is super flexible, allowing users to set up their bluetooth processes in as secure a method as possible. lowkey obsessed with how customizable this is.

The following process types are defined for bluetooth:

bluetooth_t, bluetooth_helper_t

Note: semanage permissive -a bluetooth_t 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. so like, you're not off the hook — the receipts still show up 😭

⭐ BOOLEANS ⭐

SELinux policy is customizable based on least access required. the bluetooth policy is extremely flexible and has several booleans that let you manipulate the policy and run bluetooth with the tightest access possible. toggles upon toggles, we love to see it 🫶

If you want to dontaudit all daemons scheduling requests (setsched, sys_nice), you must turn on the daemons_dontaudit_scheduling boolean. Enabled by default.

setsebool -P daemons_dontaudit_scheduling 1

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.

setsebool -P deny_bluetooth 1

If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default.

setsebool -P fips_mode 1

If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.

setsebool -P nis_enabled 1

If you want to allow xguest to use blue tooth devices, you must turn on the xguest_use_bluetooth boolean. Enabled by default.

setsebool -P xguest_use_bluetooth 1

🎀 MANAGED FILES 🎀

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. and hey — note that the process's UID still needs to have DAC permissions, so no sneaky shortcuts 🔥

bluetooth_conf_rw_t

/etc/bluetooth/link_key

bluetooth_lock_t

/run/lock/subsys/bluetoothd

bluetooth_tmp_t

(no paths listed, it's just out here living its life)

bluetooth_var_lib_t

/var/lib/bluetooth(/.*)?

bluetooth_var_run_t

/run/sdp
/run/bluetoothd_address

cluster_conf_t

/etc/cluster(/.*)?

cluster_var_lib_t

/var/lib/pcsd(/.*)?
/var/lib/cluster(/.*)?
/var/lib/openais(/.*)?
/var/lib/pengine(/.*)?
/var/lib/corosync(/.*)?
/usr/lib/heartbeat(/.*)?
/var/lib/heartbeat(/.*)?
/var/lib/pacemaker(/.*)?

cluster_var_run_t

/run/crm(/.*)?
/run/cman_.*
/run/rsctmp(/.*)?
/run/aisexec.*
/run/heartbeat(/.*)?
/run/pcsd-ruby.socket
/run/corosync-qnetd(/.*)?
/run/corosync-qdevice(/.*)?
/run/pcsd.socket
/run/corosync.pid
/run/cpglockd.pid
/run/rgmanager.pid
/run/cluster/rgmanager.sk

krb5_host_rcache_t

/var/tmp/krb5_0.rcache2
/var/cache/krb5rcache(/.*)?
/var/tmp/nfs_0
/var/tmp/DNS_25
/var/tmp/host_0
/var/tmp/imap_0
/var/tmp/HTTP_23
/var/tmp/HTTP_48
/var/tmp/ldap_55
/var/tmp/ldap_487
/var/tmp/ldapmap1_0

root_t

/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp

sysfs_t

/sys(/.*)?

usbfs_t

(again, no paths listed — it's a vibe, not a path)

💜 FILE CONTEXTS 💜

SELinux requires files to have an extended attribute to define the file type. yes, files get labeled too, everyone's got lore 🧚

You can see the context of a file using the -Z option to ls.

Policy governs the access confined processes have to these files. the SELinux bluetooth policy is very flexible, allowing users to set up their bluetooth processes in as secure a method as possible.

🌟 STANDARD FILE CONTEXT 🌟

SELinux defines the file context types for the bluetooth, so if you wanted to store files with these types in different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk. like this:

semanage fcontext -a -t bluetooth_exec_t '/srv/bluetooth/content(/.*)?'
restorecon -R -v /srv/mybluetooth_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies stay winning 💅

The following file types are defined for bluetooth:

bluetooth_conf_rw_t

  • Set files with the bluetooth_conf_rw_t type, if you want to treat the files as bluetooth conf read/write content.

bluetooth_conf_t

  • 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.

bluetooth_exec_t

  • Set files with the bluetooth_exec_t type, if you want to transition an executable to the bluetooth_t domain.

Paths:

/usr/bin/dund, /usr/bin/hcid, /usr/bin/hidd, /usr/bin/pand,
/usr/bin/sdpd, /usr/bin/rfcomm, /usr/bin/hid2hci,
/usr/bin/hciattach, /usr/bin/bluetoothd,
/usr/libexec/bluetooth/bluetoothd

bluetooth_helper_exec_t

  • Set files with the bluetooth_helper_exec_t type, if you want to transition an executable to the bluetooth_helper_t domain.

bluetooth_helper_tmp_t

  • Set files with the bluetooth_helper_tmp_t type, if you want to store bluetooth helper temporary files in the /tmp directories.

bluetooth_helper_tmpfs_t

  • Set files with the bluetooth_helper_tmpfs_t type, if you want to store bluetooth helper files on a tmpfs file system.

bluetooth_initrc_exec_t

  • Set files with the bluetooth_initrc_exec_t type, if you want to transition an executable to the bluetooth_initrc_t domain.

Paths:

/etc/rc.d/init.d/dund, /etc/rc.d/init.d/pand,
/etc/rc.d/init.d/bluetooth

bluetooth_lock_t

  • 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.

bluetooth_tmp_t

  • Set files with the bluetooth_tmp_t type, if you want to store bluetooth temporary files in the /tmp directories.

bluetooth_unit_file_t

  • Set files with the bluetooth_unit_file_t type, if you want to treat the files as bluetooth unit content.

bluetooth_var_lib_t

  • Set files with the bluetooth_var_lib_t type, if you want to store the bluetooth files under the /var/lib directory.

bluetooth_var_run_t

  • Set files with the bluetooth_var_run_t type, if you want to store the bluetooth files under the /run or /var/run directory.

Paths:

/run/sdp, /run/bluetoothd_address
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 semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels. temporary vs permanent, choose wisely bestie 🙈

🔥 COMMANDS 🔥

semanage fcontext can also be used to manipulate default file context mappings.

semanage permissive can also be used to manipulate whether or not a process type is permissive.

semanage module can also be used to enable/disable/install/remove policy modules.

semanage boolean can also be used to manipulate the booleans.

system-config-selinux is a GUI tool available to customize SELinux policy settings. yes, a GUI — for when the terminal is doing too much 😌

👑 AUTHOR 👑

This manual page was auto-generated using sepolicy manpage . no human typed this out by hand, and honestly? respect the automation.

💀 SEE ALSO 💀

selinux(8), bluetooth(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), bluetooth_helper_selinux(8), bluetooth_helper_selinux(8)

(and yes, bluetooth_helper_selinux(8) is listed twice — that's not a typo on my end, that's just how the page comes, fr fr 💖)

and that's the whole page!! 🫶 this one's from the bluetooth manual, dated 26-10-06, living at bluetooth_selinux(8). go forth and label responsibly, bestie 🌸✨

📦 where this page comes from