Age | Commit message (Collapse) | Author |
|
Bug: 190050919
Test: build, boot
Change-Id: If899f52095ab79b2515fa8befca2c314428fffec
|
|
Allows the vendor TEE access to GSI metadata files (which are publicly
readable). Storageproxyd needs access to this metadata to determine if a
GSI image is currently booted. Also allows the TEE domain to make new
directories in its data path.
Test: access /metadata/gsi/dsu/booted from storageproxyd
Bug: 203719297
Change-Id: I696ef8912de396531987e1104fb2b7ceebfbe44c
|
|
Bug: 199435757
Test: boot Trusty emulator
Change-Id: I1cef3f0aff3834d27cc32e873da07428dc2433bd
|
|
Address following denials:
avc: denied { read } for comm="securedpud" name="system" dev="tmpfs"
ino=321 scontext=u:r:securedpud:s0
tcontext=u:object_r:dmabuf_system_heap_device:s0 tclass=chr_file
permissive=1
avc: denied { open } for comm="securedpud" path="/dev/dma_heap/system"
dev="tmpfs" ino=321 scontext=u:r:securedpud:s0
tcontext=u:object_r:dmabuf_system_heap_device:s0 tclass=chr_file
permissive=1
avc: denied { ioctl } for comm="securedpud" path="/dev/dma_heap/system"
dev="tmpfs" ino=321 ioctlcmd=0x4800 scontext=u:r:securedpud:s0
tcontext=u:object_r:dmabuf_system_heap_device:s0 tclass=chr_file
permissive=1
Bug: 176508588
Test: m selinux_policy
Change-Id: Ibb1f07c6341920c061323105ea2486b516a18915
|
|
Bug: 148421469
Test: VtsHalConfirmationUIV1_0TargetTest
Change-Id: Ic148e7c4a5d3d45c081ad0e83b7fdcf8c583237e
|
|
Update sepocily as secure DPU needs to access to ION device
for allocating buffers.
Bug: 176508588
Change-Id: I49c768f3c72e24b17feeb32f3b6d1d425dae20f8
|
|
1. Add daemon implementation
2. Update sepolicy
Bug: 176508588
Change-Id: I1186a205d60f1cf0e308d636f9828b249b5513f4
|
|
Bug: 118762930
Test: /data/nativetest64/trusty-ut-ctrl/trusty-ut-ctrl \
-D /dev/trusty-ipc-dev0 com.android.trusty.swspi.test
Change-Id: I47e406430532abe57307e0cc0d55a0a01ad0ab94
|
|
This patch adds the confirmationui HAL service to the trusty qemu board
configuration. This includes PRODUCT_PACKAGES and sepolicy updates.
Test: VtsHalConfirmationUIV1_0TargetTest
Bug: 146078942
Change-Id: Icd011b3af0c660c7368be3417febcb5a5ee28f92
|
|
Test: Booted with trusty, network came up without setenforce 0
Bug: 145549509
Change-Id: I532d1277b212a5080fc0537cf691bcd431f72b2e
|
|
* Switch our manifest to use KM4 instead of KM3.
* Include framework_manifest.xml, needed by Keymaster 4 VTS to find the
service manager.
* Label Trusty KM4 as a keymaster daemon
Bug: 128851722
Test: Keymaster VTS 4.0 + Trusty
Change-Id: I268fe08e3af3f1311b163f9f2ebb42796ed0a5b9
|
|
Activates both services, and installs VTS to allow for testing them.
Fails one subtest of keymaster@3.0 VTS at the moment, but so does the
default emulator, so this is either a bug in system/keymaster or VTS.
Bug: 127700127
Test: VTS for gatekeeper@1.0, VTS for keymaster@3.0
Change-Id: I53a901c090dd5cbaddab0d430e28f9b7de8dda89
|
|
Bug: 124277696
Test: Boot with trusty, run trusty-ut-ctrl "com.android.storage-unittest.td"
Change-Id: Idc447015f222cb5a5cbcc2be2ca84c73d4045d1d
|
|
Create an android target suitable for running tests against via adb +
trusty qemu
Test: 'lunch qemu_trusty_arm64-userdebug; make'
Change-Id: I2e6d99bd83ff1d4b55051420a8a14704b86a1e0b
|