platform_system_core/trusty/confirmationui
Rajesh Nyamagoud 4092a77774 Replaced -1 with EXIT_FAILURE and validated confirmationui service
status after registering it with `CHECK_EQ` macro.

Bug: b/205760172
Test: atest VtsHalConfirmationUITargetTest
Change-Id: I00f5a09ca525e3abb63a5d1f404fb6f3daed9442
2022-10-24 19:25:35 +00:00
..
fuzz Adding trong@google.com as fuzzer owner for trusty fuzzers 2022-04-18 20:42:10 +00:00
include Changes to adapt confirmationui AIDL spec. 2022-10-13 15:17:34 +00:00
.clang-format
Android.bp Changes to adapt confirmationui AIDL spec. 2022-10-13 15:17:34 +00:00
android.hardware.confirmationui-service.trusty.rc Changes to adapt confirmationui AIDL spec. 2022-10-13 15:17:34 +00:00
android.hardware.confirmationui-service.trusty.xml Changes to adapt confirmationui AIDL spec. 2022-10-13 15:17:34 +00:00
NotSoSecureInput.cpp
README
service.cpp Replaced -1 with EXIT_FAILURE and validated confirmationui service 2022-10-24 19:25:35 +00:00
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 Changes to adapt confirmationui AIDL spec. 2022-10-13 15:17:34 +00:00
TrustyConfirmationUI.h Changes to adapt confirmationui AIDL spec. 2022-10-13 15:17:34 +00: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.