platform_system_sepolicy/private/compos_verify_key.te
Alan Stokes 6c00021051 compos_verify_key no longer creates a vsock
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
2021-09-15 11:22:47 +01:00

20 lines
840 B
Text

# Run by odsign to verify a CompOs instance's keys.
type compos_verify_key, domain, coredomain;
type compos_verify_key_exec, exec_type, file_type, system_file_type;
binder_use(compos_verify_key);
virtualizationservice_use(compos_verify_key);
# Access the image & key files, delete on failure, rename pending to current
allow compos_verify_key apex_module_data_file:dir search;
allow compos_verify_key apex_compos_data_file:dir create_dir_perms;
allow compos_verify_key apex_compos_data_file:file create_file_perms;
# Allow odsign to redirect our stdout/stderr to log
allow compos_verify_key odsign:fd use;
allow compos_verify_key odsign_devpts:chr_file { read write };
# Only odsign can enter the domain via exec
neverallow { domain -odsign } compos_verify_key:process transition;
neverallow * compos_verify_key:process dyntransition;