- From: GitHub <noreply@github.com>
- Date: Wed, 02 May 2018 10:13:17 -0700
- To: public-webauthn@w3.org
- Message-ID: <5ae9f1add2c10_57332ad9b48f1c00800fe@hookshot-fe-31feec6.cp1-iad.github.net.mail>
Branch: refs/heads/master
Home: https://github.com/w3c/webauthn
Commit: 4e19fe4099a5f7c0248c25fdf4b9e3ce7ba4a86d
https://github.com/w3c/webauthn/commit/4e19fe4099a5f7c0248c25fdf4b9e3ce7ba4a86d
Author: Arnar Birgisson <arnarbi@gmail.com>
Date: 2018-03-12 (Mon, 12 Mar 2018)
Changed paths:
M index.bs
Log Message:
-----------
Clarify the U2F Attestation format to have a single certificate
The [U2F Raw Message Format](https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fido-u2f-raw-message-formats-v1.2-ps-20170411.html#h3_registration-response-message-success) only allows for a single attestation certificate in U2F responses.
This PR reflects this in the U2F Attestation Format to reduce the chance of misunderstanding when implementing the server verification.
Commit: 92142acd0359d1d82fc7420b2704d011d560e1cc
https://github.com/w3c/webauthn/commit/92142acd0359d1d82fc7420b2704d011d560e1cc
Author: Adam Langley <agl@imperialviolet.org>
Date: 2018-05-02 (Wed, 02 May 2018)
Changed paths:
M index.bs
Log Message:
-----------
Merge pull request #836 from arnar/patch-1
Clarify the U2F Attestation format to have a single certificate
Compare: https://github.com/w3c/webauthn/compare/4f584b82eb9f...92142acd0359
**NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/
Functionality will be removed from GitHub.com on January 31st, 2019.
Received on Wednesday, 2 May 2018 17:13:47 UTC