You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Android SafetyNet attestation type identifier is presently given as: Android Attestation (type="android")
However, Android N adds another form of "hardware attestation" for which we will have to allocate another attestation type identifier.
Do we leave the SafetyNet attestation type identifier as "android" and, e.g., define the new so-called "android N hardware attestation" type identifier as "android2" ?
Or redefine SafetyNet attestation type identifier as say "AndroidSafetyNet" and the new so-called "android N hardware attestation" type identifier as say "AndroidN" ?
Personally, I think I'd go with (1) at this point. And if for some reason yet another attestation signature format emerges from Android, it can just be labeled "android3".
The text was updated successfully, but these errors were encountered:
I propose to replace the existing SafetyNet with Android "N" attestation, since in Android "N", the (1) attestation is computed by the Authenticator and (2) the the authenticator includes the public key.
In SafetyNet, the App provides a public key to be included and the attestation is computed by the platform.
Also cleaned up wording and naming for consistency.
Added Android N attestation format. Fixes#103.
Changed name for SafetyNet attestation format. Fixes#128.
Android SafetyNet attestation type identifier is presently given as:
Android Attestation (type="android")
However, Android N adds another form of "hardware attestation" for which we will have to allocate another attestation type identifier.
Personally, I think I'd go with (1) at this point. And if for some reason yet another attestation signature format emerges from Android, it can just be labeled "android3".
The text was updated successfully, but these errors were encountered: