> Yes, that is how the spec is written. See https://www.w3.org/TR/webauthn/#ref-for-enumdef-attestationconveyancepreference and https://www.w3.org/TR/webauthn/#enumdef-attestationconveyancepreference. Gotcha. So, read another way, doesthe existing `AttestationConveyancePreference` roughly accomplish what is being discussed in this thread? If a RP wants to allow syncing, they give a attestation preference of `none` and if they don't, they specify `direct`. It isn't exactly the same thing. But, maybe for all intents and purposes it is unless https://github.com/w3c/webauthn/issues/931 outlines some means of backing up a attestation capable authenticator to another attestation capable authenticator. -- GitHub Notification of comment by ptoomey3 Please view or discuss this issue at https://github.com/w3c/webauthn/issues/969#issuecomment-401135430 using your GitHub accountReceived on Thursday, 28 June 2018 18:47:26 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:33 UTC