Move bluetoothdomain rules into their own file.

am: 85dcd53b74

* commit '85dcd53b745dfcce534ea35443816057c6122887':
  Move bluetoothdomain rules into their own file.
This commit is contained in:
Nick Kralevich 2015-11-18 18:39:27 +00:00 committed by android-build-merger
commit eedee59726
2 changed files with 11 additions and 12 deletions

View file

@ -23,23 +23,11 @@ r_dir_file(bluetooth, bluetooth_efs_file)
allow bluetooth { tun_device uhid_device hci_attach_dev }:chr_file rw_file_perms; allow bluetooth { tun_device uhid_device hci_attach_dev }:chr_file rw_file_perms;
auditallow bluetooth tun_device:chr_file rw_file_perms; auditallow bluetooth tun_device:chr_file rw_file_perms;
# Other domains that can create and use bluetooth sockets.
# SELinux does not presently define a specific socket class for
# bluetooth sockets, nor does it distinguish among the bluetooth protocols.
# TODO: This should no longer be needed with bluedroid for bluetooth
# but may be getting used for other non-bluetooth sockets that has no
# specific class defined. Consider taking to specific domains.
allow bluetoothdomain self:socket create_socket_perms;
# sysfs access. # sysfs access.
allow bluetooth sysfs_bluetooth_writable:file rw_file_perms; allow bluetooth sysfs_bluetooth_writable:file rw_file_perms;
allow bluetooth self:capability net_admin; allow bluetooth self:capability net_admin;
allow bluetooth self:capability2 wake_alarm; allow bluetooth self:capability2 wake_alarm;
# Allow clients to use a socket provided by the bluetooth app.
# TODO: See if this is still required under bluedroid.
allow bluetoothdomain bluetooth:unix_stream_socket { getopt setopt getattr read write ioctl shutdown };
# tethering # tethering
allow bluetooth self:tun_socket create_socket_perms; allow bluetooth self:tun_socket create_socket_perms;
allow bluetooth efs_file:dir search; allow bluetooth efs_file:dir search;

11
bluetoothdomain.te Normal file
View file

@ -0,0 +1,11 @@
# Other domains that can create and use bluetooth sockets.
# SELinux does not presently define a specific socket class for
# bluetooth sockets, nor does it distinguish among the bluetooth protocols.
# TODO: This should no longer be needed with bluedroid for bluetooth
# but may be getting used for other non-bluetooth sockets that has no
# specific class defined. Consider taking to specific domains.
allow bluetoothdomain self:socket create_socket_perms;
# Allow clients to use a socket provided by the bluetooth app.
# TODO: See if this is still required under bluedroid.
allow bluetoothdomain bluetooth:unix_stream_socket { getopt setopt getattr read write ioctl shutdown };