Searched refs:Keymaster (Results 1 – 13 of 13) sorted by relevance
/hardware/interfaces/keymaster/4.1/support/include/keymasterV4_1/ |
D | Keymaster.h | 41 class Keymaster : public IKeymasterDevice { 43 using KeymasterSet = std::vector<android::sp<Keymaster>>; 45 Keymaster(const hidl_string& descriptor, const hidl_string& instanceName) in Keymaster() function 47 virtual ~Keymaster() {} in ~Keymaster() 99 std::ostream& operator<<(std::ostream& os, const Keymaster& keymaster);
|
D | Keymaster3.h | 34 class Keymaster3 : public Keymaster { 40 : Keymaster(IKeymaster3Device::descriptor, instanceName), in Keymaster3()
|
D | Keymaster4.h | 28 class Keymaster4 : public Keymaster { 35 : Keymaster(V4_1::IKeymasterDevice::descriptor, instanceName), in Keymaster4()
|
/hardware/interfaces/keymaster/4.1/support/ |
D | Keymaster.cpp | 76 std::ostream& operator<<(std::ostream& os, const Keymaster& keymaster) { in operator <<() 85 Keymaster::KeymasterSet enumerateDevices(const sp<IServiceManager>& serviceManager) { in enumerateDevices() 86 Keymaster::KeymasterSet result; in enumerateDevices() 110 void Keymaster::logIfKeymasterVendorError(ErrorCode ec) const { in logIfKeymasterVendorError() 123 Keymaster::KeymasterSet Keymaster::enumerateAvailableDevices() { in enumerateAvailableDevices() 145 const Keymaster::KeymasterSet& keymasters) { in getHmacParameters() 163 static void computeHmac(const Keymaster::KeymasterSet& keymasters, in computeHmac() 191 void Keymaster::performHmacKeyAgreement(const KeymasterSet& keymasters) { in performHmacKeyAgreement()
|
D | Android.bp | 27 "Keymaster.cpp",
|
/hardware/interfaces/keymaster/4.0/vts/performance/ |
D | README | 1 # Keymaster Benchmark 3 The Keymaster Benchmark is a standalone tool for measuring the performance of keymaster implementat… 17 Keymaster Benchmark is built on [Google microbenchmark library](https://github.com/google/benchmark…
|
/hardware/interfaces/rebootescrow/aidl/vts/functional/ |
D | README.md | 1 Many of the tests in this directory may require that TEE Keymaster
|
/hardware/interfaces/keymaster/4.0/ |
D | types.hal | 222 * disks, where the file system may not be available until after a Keymaster key is used to 302 * may have a fixed maximum size and Keymaster may fail operations that attempt to use keys with 305 * fails because the table is full, Keymaster returns ErrorCode::TOO_MANY_OPERATIONS. 321 * counters for keys with this tag. Because Keymaster memory is often limited, this table can 322 * have a fixed maximum size and Keymaster can fail operations that attempt to use keys with 451 * except perhaps as implied by an auth token. This means that Keymaster must be able to check 461 * key or another with TRUSTED_USER_PRESENCE_REQUIRED, Keymaster must return 548 * operating system booted (if any). This tag is never provided to or returned from Keymaster 602 * returned from Keymaster in the key characteristics. It exists only to define the tag for use 828 * Keymaster and returned from begin. [all …]
|
D | IKeymasterDevice.hal | 23 * Keymaster device definition. 217 * must be a TEE Keymaster as well. The HMAC key used to MAC and verify authentication tokens 324 * sharingCheck = HMAC(H, "Keymaster HMAC Verification") 339 * For every StrongBox operation, Keystore is required to call this method on the TEE Keymaster, 349 * @param operationHandle the operation handle returned by StrongBox Keymaster's begin(). 369 * Adds entropy to the RNG used by Keymaster. Entropy added through this method must not be the 649 * Keymaster. 824 * Note that Keymaster versions 2 and 3 required that the system and boot images have the same 986 * in which case the Keymaster implementation cannot build a proper PKCS#1 v1.5 signature
|
/hardware/interfaces/keymaster/4.1/ |
D | types.hal | 50 * HAL attests to Credential Keys. IIdentityCredential produces Keymaster-style attestations.
|
/hardware/interfaces/confirmationui/1.0/ |
D | IConfirmationResultCallback.hal | 57 * which is shared with Keymaster. In test mode the test key MUST be
|
/hardware/interfaces/keymaster/3.0/ |
D | IKeymasterDevice.hal | 20 * Keymaster device definition. For thorough documentation see the implementer's reference, at 39 * launched with Nougat or later must support hardware enforcement of Keymaster 42 * @return supportsAttestation is true if the hardware supports generation of Keymaster public 181 * Upgrades an old key. Keys can become "old" in two ways: Keymaster can be upgraded to a new
|
D | types.hal | 235 UNKNOWN = 3, /* Keymaster did not record origin. This value can only be seen on keys in a 266 * Keymaster error codes.
|