Move bluetoothdomain rules into their own file.
Don't mix bluetooth rules with bluetoothdomain. The bluetoothdomain
rules are used by several other SELinux domains, not just bluetooth,
and keeping them in the same file is confusing.
Change-Id: I487251ab1c1392467a39c7a87328cdaf802fc1f8
diff --git a/bluetoothdomain.te b/bluetoothdomain.te
new file mode 100644
index 0000000..9626e4b
--- /dev/null
+++ b/bluetoothdomain.te
@@ -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 };