- From: Adam Langley <noreply@github.com>
- Date: Thu, 25 Aug 2022 15:40:48 -0700
- To: public-webauthn@w3.org
Branch: refs/heads/jeffh-fix-1658-device-bound-key-extension
Home: https://github.com/w3c/webauthn
Commit: 3430c953e47ab35085e80ac0086623f443de2f8e
https://github.com/w3c/webauthn/commit/3430c953e47ab35085e80ac0086623f443de2f8e
Author: Adam Langley <agl@imperialviolet.org>
Date: 2022-08-25 (Thu, 25 Aug 2022)
Changed paths:
M index.bs
Log Message:
-----------
Hopefully fix up my misinterpretation of emlun's comment.
Commit: 5af393d40ff4275a343cb7b7cec19ac6876045be
https://github.com/w3c/webauthn/commit/5af393d40ff4275a343cb7b7cec19ac6876045be
Author: Adam Langley <agl@imperialviolet.org>
Date: 2022-08-25 (Thu, 25 Aug 2022)
Changed paths:
M index.bs
Log Message:
-----------
RPs shouldn't check DPK attestation for equality.
Otherwise they'll consider fresh attestations to be different devices.
The attestation for existing DPKs is already checked in the “exactly one
match” case.
Commit: fe333fe13b5a6b16a8012a49b680adf4a30e056a
https://github.com/w3c/webauthn/commit/fe333fe13b5a6b16a8012a49b680adf4a30e056a
Author: Adam Langley <agl@imperialviolet.org>
Date: 2022-08-25 (Thu, 25 Aug 2022)
Changed paths:
M index.bs
Log Message:
-----------
Remove incorrect note about nonces.
Just because the attestation is changing doesn't mean that the
authenticator is using a nonce. It could just be signing the same
message repeatedly.
Commit: ece61f0870936697d3b78427191e73598c147a3d
https://github.com/w3c/webauthn/commit/ece61f0870936697d3b78427191e73598c147a3d
Author: Adam Langley <agl@imperialviolet.org>
Date: 2022-08-25 (Thu, 25 Aug 2022)
Changed paths:
M index.bs
Log Message:
-----------
Include enterpriseAttestationPossible when calling authenticatorGetAssertion
Compare: https://github.com/w3c/webauthn/compare/88be1a6dd670...ece61f087093
Received on Thursday, 25 August 2022 22:41:01 UTC