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
In L3 platform-based authenticators are allowed AAGUIDs that are not all-zero even when credentialCreationData.attestationConveyancePreferenceOption is "none". As a result, there is no additional privacy obtained by replacing self attestation with none attestation. Specifically the steps describing constructCredentialAlg in § 5.1.3. should be changed from:
Thinking of this more, if platform authenticators are excluded from the privacy-preserving practice of having their AAGUID replaced with all zeros when passed a "none"AttestationConveyancePreferenceOption, what is the point of replacing the attestation when self attestation is not used? Is AAGUID not strictly more privacy-disrespecting than any X.509 v3 certificate chain? Specifically, I'm thinking the following also seems to work:
In L3 platform-based authenticators are allowed AAGUIDs that are not all-zero even when
credentialCreationData.
attestationConveyancePreferenceOption
is"none"
. As a result, there is no additional privacy obtained by replacing self attestation with none attestation. Specifically the steps describing constructCredentialAlg in § 5.1.3. should be changed from:to
The text was updated successfully, but these errors were encountered: