more vm socket isolation am: 378ed74529
am: 57061954d2
Original change: https://android-review.googlesource.com/c/platform/system/sepolicy/+/3114226 Change-Id: If484cab984486b6c884d0ce53a8b460cdcd009e1 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This commit is contained in:
commit
5db4cf2605
2 changed files with 2 additions and 0 deletions
|
@ -61,6 +61,7 @@ dontaudit virtualizationmanager self:dir write;
|
|||
|
||||
# Let virtualizationmanager to accept vsock connection from the guest VMs
|
||||
allow virtualizationmanager self:vsock_socket { create_socket_perms_no_ioctl listen accept };
|
||||
neverallow { domain -virtualizationmanager } virtualizationmanager:vsock_socket { accept bind create connect listen };
|
||||
|
||||
# Allow virtualizationmanager to inspect all hypervisor capabilities.
|
||||
get_prop(virtualizationmanager, hypervisor_prop)
|
||||
|
|
|
@ -83,6 +83,7 @@ allow virtualizationservice apex_virt_data_file:file create_file_perms;
|
|||
# Let virtualizationservice to accept vsock connection from the guest VMs to singleton services
|
||||
# such as the guest tombstone server.
|
||||
allow virtualizationservice self:vsock_socket { create_socket_perms_no_ioctl listen accept };
|
||||
neverallow { domain -virtualizationservice } virtualizationservice:vsock_socket { accept bind create connect listen };
|
||||
|
||||
# Allow virtualizationservice to read/write its own sysprop. Only the process can do so.
|
||||
set_prop(virtualizationservice, virtualizationservice_prop)
|
||||
|
|
Loading…
Reference in a new issue