4 ms·
>> All Android devices certified by Google will have a hardware security module which should keep the keys secure. Source? I understood that having a HW-backed
by zimmerfrei 8y ago
>> All Android devices certified by Google will have a hardware security module which should keep the keys secure.
Source? I understood that having a HW-backed key store is still entirely optional for the purpose of Android certification.
On top of that, I noticed some ambiguity on whether a TEE like ARM TrustZone qualifies as a hardware-grade protection mechanism in the same way a discrete and dedicated crypto processor is (I think the two technologies provide very different assurance levels).
- kpU8efre7r 8y agoTitan M. They have it built into their Pixel devices much like a tiny mobile TPM. https://www.blog.google/products/pixel/titan-m-makes-pixel-3-our-most-secure-phone-yet/ https://www.blog.google/products/pixel/titan-m-makes-pixel-3... With that said, I cant find mention of this on the page so it's probably not leveraging this.
- dgacmu 8y agoIt is. If you have a pixel you can just use a button press, because the Titan m can directly sense the button state.
- guelo 8y agoHere's the CTS for Android 7.0 https://source.android.com/compatibility/7.0/android-7.0-cdd#9_11_keys_and_credentials https://source.android.com/compatibility/7.0/android-7.0-cdd... "When the device implementation supports a secure lock screen it MUST back up the keystore implementation with secure hardware and meet following requirements: MUST have hardware backed implementations of RSA, AES, ECDSA and HMAC cryptographic algorithms and MD5, SHA1, SHA-2 Family hash functions to properly support the Android Keystore system's supported algorithms. MUST perform the lock screen authentication in the secure hardware and only when successful allow the authentication-bound keys to be used. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) that can be used to satisfy this requirement. "