- From: Adam Langley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Sep 2019 22:59:14 +0000
- To: public-webauthn@w3.org
The transport values are recorded by the site during registration and echoed back the browser when an assertion is requested. They are intended to guide the browser about hopeless cases, for example a credential with “internal” transport when the browser knows that it doesn't have any internal authenticators. The “lightning” transport is intended for the same reason. Many authenticators support “usb” but USB HID devices cannot be used by iOS apps, even assuming that the user has some dongle that takes care of the physical connection. (Unless you want to update our understanding on that point.) USB-A and USB-C are merged into a single transport because, in practice, converters between the two are common and widely used. Thus it would be excessive to drop a credential just because a laptop only has USB-C, but the authenticator reports that it's USB-A. -- GitHub Notification of comment by agl Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1294#issuecomment-528124351 using your GitHub account
Received on Wednesday, 4 September 2019 22:59:16 UTC