Move bluetoothdomain rules into their own file.

am: 85dcd53b

* commit '85dcd53b':
  Move bluetoothdomain rules into their own file.

bluetooth.te

@@ -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;
 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.
 allow bluetooth sysfs_bluetooth_writable:file rw_file_perms;
 allow bluetooth self:capability net_admin;
 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
 allow bluetooth self:tun_socket create_socket_perms;
 allow bluetooth efs_file:dir search;

bluetoothdomain.te

+# 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 };