PWN-Hunter/android_system_sepolicy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

compos_verify_key no longer creates a vsock

Browse Source 
Instead it gets it from virtualization_service, so this TODO is now
done.

Test: Manually run comps_verify_key
Test: Trigger odsign to run compos_verify_key at boot
Bug: 186126194
Change-Id: I705e7fd43b853a19c928ab76209ec321f10ec2d7
This commit is contained in:
Alan Stokes 2021-09-15 11:21:31 +01:00
parent c5e8db55f9
commit 6c00021051
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
private/compos_verify_key.te
View File

@ -15,9 +15,6 @@ allow compos_verify_key apex_compos_data_file:file create_file_perms;
allow compos_verify_key odsign:fd use;
allow compos_verify_key odsign_devpts:chr_file { read write };
# TODO: Remove this!
allow compos_verify_key self:vsock_socket create_socket_perms_no_ioctl;
# Only odsign can enter the domain via exec
neverallow { domain -odsign } compos_verify_key:process transition;
neverallow * compos_verify_key:process dyntransition;