1## Secure UI Architecture 2 3To implement confirmationui a secure UI architecture is required. This entails a way 4to display the confirmation dialog driven by a reduced trusted computing base, typically 5a trusted execution environment (TEE), without having to rely on Linux and the Android 6system for integrity and authenticity of input events. This implementation provides 7neither. But it provides most of the functionlity required to run a full Android Protected 8Confirmation feature when integrated into a secure UI architecture. 9 10## Secure input (NotSoSecureInput) 11 12This implementation does not provide any security guaranties. 13The input method (NotSoSecureInput) runs a cryptographic protocols that is 14sufficiently secure IFF the end point is implemented on a trustworthy 15secure input device. But since the endpoint is currently in the HAL 16service itself this implementation is not secure. 17 18NOTE that a secure input device end point needs a good source of entropy 19for generating nonces. The current implementation (NotSoSecureInput.cpp#generateNonce) 20uses a constant nonce.