platform_system_core/trusty/confirmationui
Tri Vo 5ff073e832 trusty: Fuzzer for ConfirmationUI messages
ConfirmationUI messages are a higher-level abstraction than TIPC
messages (which is what TIPC fuzzer fuzzes).

Bug: 174402999
Test: trusty_confirmationui_msg_fuzzer
Change-Id: I1e1e2c7070b87b78d6236993330df65202840ce6
2021-03-02 12:21:49 -08:00
..
fuzz trusty: Fuzzer for ConfirmationUI messages 2021-03-02 12:21:49 -08:00
include trusty: Export ConfirmationUI helper classes 2021-02-23 11:31:35 -08:00
.clang-format
Android.bp [LSC] Add LOCAL_LICENSE_KINDS to system/core 2021-02-19 12:59:05 -08:00
android.hardware.confirmationui@1.0-service.trusty.rc trusty: ConfirmationUI HAL<->TA IPC using shared memory 2021-02-17 11:10:14 -08:00
android.hardware.confirmationui@1.0-service.trusty.xml
NotSoSecureInput.cpp
README
service.cpp
TrustyApp.cpp trusty: Export ConfirmationUI helper classes 2021-02-23 11:31:35 -08:00
TrustyApp.h trusty: Export ConfirmationUI helper classes 2021-02-23 11:31:35 -08:00
TrustyConfirmationUI.cpp trusty: Export ConfirmationUI helper classes 2021-02-23 11:31:35 -08:00
TrustyConfirmationUI.h trusty: Export ConfirmationUI helper classes 2021-02-23 11:31:35 -08:00

## Secure UI Architecture

To implement confirmationui a secure UI architecture is required. This entails a way
to display the confirmation dialog driven by a reduced trusted computing base, typically
a trusted execution environment (TEE), without having to rely on Linux and the Android
system for integrity and authenticity of input events. This implementation provides
neither. But it provides most of the functionlity required to run a full Android Protected
Confirmation feature when integrated into a secure UI architecture.

## Secure input (NotSoSecureInput)

This implementation does not provide any security guaranties.
The input method (NotSoSecureInput) runs a cryptographic protocols that is
sufficiently secure IFF the end point is implemented on a trustworthy
secure input device. But since the endpoint is currently in the HAL
service itself this implementation is not secure.

NOTE that a secure input device end point needs a good source of entropy
for generating nonces. The current implementation (NotSoSecureInput.cpp#generateNonce)
uses a constant nonce.