Update vnc_server communication.
It is actually using a socket to talk to the sensors hal,
not system_server where the sensors hal was formally hosted.
If the sensors hal is moved back to system_server, this new
rule will still be applied properly.
Bug: 71707530
Test: boot device, check for denials, but note that /var/run
is currently not being mounted on the device.
Test: one less neverallow hit when PRODUCT_SEPOLICY_SPLIT is enabled
Change-Id: I4f2e7c31a00ce659cd2ce0a79ff96f33a4eb9516
(cherry picked from commit 37556a8eeec29dc4e873d282de7bba94d4a536bf)
diff --git a/shared/sepolicy/vnc_server.te b/shared/sepolicy/vnc_server.te
index cdd9fc7..7e0c140 100644
--- a/shared/sepolicy/vnc_server.te
+++ b/shared/sepolicy/vnc_server.te
@@ -16,7 +16,7 @@
# TODO(b/65062047): Remove these rules (incl. the two file type definitions) once vnc_server is gone
# I/O with system_server via sensors_hal_socket Unix domain socket. Needed for orientation changes.
-unix_socket_connect(vnc_server, sensors_hal, system_server)
+unix_socket_connect(vnc_server, sensors_hal, hal_sensors_server)
# For some reason vnc_server attempts a search of /var/run/system directory instead of going
# straight for opening the sensors_hal_socket
allow vnc_server var_run_system_file:dir search;
