[w3c/webauthn] b7149f: Include an AuthenticatorTransport when creating a ...

  Branch: refs/heads/transports
  Home:   https://github.com/w3c/webauthn
  Commit: b7149f48f162a1cd48217fe90a28b9abd6f31a85
      https://github.com/w3c/webauthn/commit/b7149f48f162a1cd48217fe90a28b9abd6f31a85
  Author: Adam Langley <agl@imperialviolet.org>
  Date:   2018-04-24 (Tue, 24 Apr 2018)

  Changed paths:
    M index.bs

  Log Message:
  -----------
  Include an AuthenticatorTransport when creating a new credential.

FIDO U2F found it neccessary to wedge the authenticator transport in an
X.509 extension of the attestation certificate in order to communicate
this information to the RP.

In Webauthn, we currently note that it's possible that an RP might learn
this information from the attestation, but now have several kinds of
attesattion and it seems dumb to define ways to wedge this information
in each.

Instead, have the client include the transport in the
AuthenticatorAttestationResponse. Also, define another transport type
for cases where a non-standard protocol is used to communicate with a
platform authenticator.

Since interface attributes cannot be optional, technically this is a
breaking change, although I don't believe that it will break anything in
practice. Still, this could also be punted to an extension if we wished.
However, given that U2F found it to be so important, I've gone this
route.


  Commit: 0ef2f2a4057434e03c1c1797ee282e6214e2c397
      https://github.com/w3c/webauthn/commit/0ef2f2a4057434e03c1c1797ee282e6214e2c397
  Author: Adam Langley <agl@imperialviolet.org>
  Date:   2018-05-01 (Tue, 01 May 2018)

  Changed paths:
    M index.bs

  Log Message:
  -----------
  Include updates from the pull request.


Compare: https://github.com/w3c/webauthn/compare/b7149f48f162^...0ef2f2a40574
      **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.