device/fido: don't use the caBLE transport as a signal.
Previously, having the caBLE transport in the list of transports was special and indicated that a caBLE discovery should be created. Also, unlike all over discoveries, the caBLE discovery was created in the GetAssertion request handler, not the base class. This change makes the caBLE transport no longer special because, in the future, we'll want to create a caBLE discovery without the extension. It also regularises the handling of the caBLE transport to match all other transports. As a consequence, the caBLE discovery data becomes the property of the FidoDiscoveryFactory and two tests become inapplicable at the level at which they were being tested. Change-Id: Ibcd758fa9304a7cb8a868b1bcf2c692c15f72221 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756951 Auto-Submit: Adam Langley <agl@chromium.org> Reviewed-by:Martin Kreichgauer <martinkr@google.com> Commit-Queue: Adam Langley <agl@chromium.org> Cr-Commit-Position: refs/heads/master@{#691798}
Showing
Please register or sign in to comment