Lines Matching refs:secure

8 functionality where the key material is restricted to a secure environment.  This functionality is
15 A device may optionally also support a second KeyMint instance, running in a dedicated secure
25 - KeyMint supports *attestation* of public keys: when an asymmetric keypair is created, the secure
33 User authentication must also take place in a secure environment (see the final section below), but
36 to the secure components, so that it's authenticity can be verified.
39 `hardware/interfaces/gatekeeper/`), is co-located in the same secure environment as KeyMint, it can
44 separate secure processor may not have a communication channel with a TEE on the main processor.
52 access to a secure time source that is aligned with the authenticator's time source.
56 implemented if there is a KeyMint instance without a secure source of time.
61 that the secure environment have access to a signing key which in turn chains back to the Google
66 significant disadvantages, as it required secure handling of key material and only allowed for
88 Authentication of users needs to happen in a secure environment, using vendor-specific
98     stretching. This is required to be implemented on a separate secure element, which prevents
103   allow access to biometric authentication functionality that is implemented in a secure
107   functionality where the user confirms that they have seen a specific message in a secure manner.