bluetooth_selinux man page on RedHat

Man page or keyword search:  
man Server   29550 pages
apropos Keyword Search (all sections)
Output format
RedHat logo
[printable version]

bluetooth_selinux(8)	   SELinux Policy bluetooth	  bluetooth_selinux(8)

NAME
       bluetooth_selinux  -  Security  Enhanced Linux Policy for the bluetooth
       processes

DESCRIPTION
       Security-Enhanced Linux secures the bluetooth  processes	 via  flexible
       mandatory access control.

       The  bluetooth processes execute with the bluetooth_t SELinux type. You
       can check if you have these processes running by executing the ps  com‐
       mand with the -Z qualifier.

       For example:

       ps -eZ | grep bluetooth_t

ENTRYPOINTS
       The  bluetooth_t	 SELinux  type can be entered via the bluetooth_exec_t
       file type.

       The default entrypoint paths for the bluetooth_t domain are the follow‐
       ing:

       /usr/bin/dund,	  /usr/bin/hidd,     /usr/bin/pand,    /usr/sbin/hcid,
       /usr/sbin/sdpd,	/usr/bin/rfcomm,  /usr/sbin/hid2hci,  /usr/sbin/hciat‐
       tach, /usr/sbin/bluetoothd, /usr/libexec/bluetooth/bluetoothd

PROCESS TYPES
       SELinux defines process types (domains) for each process running on the
       system

       You can see the context of a process using the -Z option to ps

       Policy governs the access confined processes have  to  files.   SELinux
       bluetooth  policy  is very flexible allowing users to setup their blue‐
       tooth processes in as secure a method as possible.

       The following process types are defined for bluetooth:

       bluetooth_helper_t, bluetooth_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.

BOOLEANS
       SELinux	policy	is customizable based on least access required.	 blue‐
       tooth policy is extremely flexible and has several booleans that	 allow
       you to manipulate the policy and run bluetooth with the tightest access
       possible.

       If you want to allow users to resolve user passwd entries directly from
       ldap  rather  then  using  a  sssd server, you must turn on the authlo‐
       gin_nsswitch_use_ldap boolean. Disabled by default.

       setsebool -P authlogin_nsswitch_use_ldap 1

       If you want to allow all daemons to write corefiles to /, you must turn
       on the daemons_dump_core boolean. Disabled by default.

       setsebool -P daemons_dump_core 1

       If  you	want  to enable cluster mode for daemons, you must turn on the
       daemons_enable_cluster_mode boolean. Enabled by default.

       setsebool -P daemons_enable_cluster_mode 1

       If you want to allow all daemons to use tcp wrappers, you must turn  on
       the daemons_use_tcp_wrapper boolean. Disabled by default.

       setsebool -P daemons_use_tcp_wrapper 1

       If  you	want to allow all daemons the ability to read/write terminals,
       you must turn on the daemons_use_tty boolean. Disabled by default.

       setsebool -P daemons_use_tty 1

       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.

       setsebool -P deny_ptrace 1

       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.

       setsebool -P domain_fd_use 1

       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.

       setsebool -P domain_kernel_load_modules 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 enable reading of urandom for all domains, you must turn
       on the global_ssp boolean. Disabled by default.

       setsebool -P global_ssp 1

       If  you	want  to allow confined applications to run with kerberos, you
       must turn on the kerberos_enabled boolean. Enabled by default.

       setsebool -P kerberos_enabled 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 confined applications to use nscd shared memory,
       you must turn on the nscd_use_shm boolean. Disabled by default.

       setsebool -P nscd_use_shm 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

NSSWITCH DOMAIN
       If you want to allow users to resolve user passwd entries directly from
       ldap rather then	 using	a  sssd	 server	 for  the  bluetooth_t,	 blue‐
       tooth_helper_t,	you must turn on the authlogin_nsswitch_use_ldap bool‐
       ean.

       setsebool -P authlogin_nsswitch_use_ldap 1

       If you want to allow confined applications to run with kerberos for the
       bluetooth_t,  bluetooth_helper_t, you must turn on the kerberos_enabled
       boolean.

       setsebool -P kerberos_enabled 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.  Note the processes UID still need to have DAC permissions.

       bluetooth_conf_rw_t

	    /etc/bluetooth/link_key

       bluetooth_lock_t

	    /var/lock/subsys/bluetoothd

       bluetooth_tmp_t

       bluetooth_var_lib_t

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

       bluetooth_var_run_t

	    /var/run/sdp
	    /var/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

	    /var/run/crm(/.*)?
	    /var/run/cman_.*
	    /var/run/rsctmp(/.*)?
	    /var/run/aisexec.*
	    /var/run/heartbeat(/.*)?
	    /var/run/cpglockd.pid
	    /var/run/corosync.pid
	    /var/run/rgmanager.pid
	    /var/run/cluster/rgmanager.sk

       root_t

	    /
	    /initrd

       usbfs_t

FILE CONTEXTS
       SELinux requires files to have an extended attribute to define the file
       type.

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

       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.

       STANDARD FILE CONTEXT

       SELinux defines the file context types for the bluetooth, 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.

       semanage	 fcontext  -a  -t   bluetooth_conf_rw_t	  '/srv/bluetooth/con‐
       tent(/.*)?'
       restorecon -R -v /srv/mybluetooth_content

       Note:  SELinux  often  uses  regular expressions to specify labels that
       match multiple files.

       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/hidd,   /usr/bin/pand,   /usr/sbin/hcid,
	    /usr/sbin/sdpd, /usr/bin/rfcomm, /usr/sbin/hid2hci, /usr/sbin/hci‐
	    attach, /usr/sbin/bluetoothd, /usr/libexec/bluetooth/bluetoothd

       bluetooth_helper_exec_t

       - Set files with the bluetooth_helper_exec_t type, if you want to tran‐
       sition 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 tran‐
       sition 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	 blue‐
       tooth 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:
	    /var/run/sdp, /var/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 data‐
       base.  You will need to use restorecon to apply the labels.

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 pol‐
       icy modules.

       semanage boolean can also be used to manipulate the booleans

       system-config-selinux is a GUI tool available to customize SELinux pol‐
       icy settings.

AUTHOR
       This manual page was auto-generated using sepolicy manpage .

SEE ALSO
       selinux(8),  bluetooth(8), semanage(8), restorecon(8), chcon(1), sepol‐
       icy(8)	 ,    setsebool(8),	bluetooth_helper_selinux(8),	 blue‐
       tooth_helper_selinux(8)

bluetooth			   13-11-20		  bluetooth_selinux(8)
[top]

List of man pages available for RedHat

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net