Chromium Cyrptotoken extension should support BLE U2F authenticators
Reported by
bto...@github.com,
Sep 21 2016
|
||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Steps to reproduce the problem: Chromium supports FIDO U2F over USB/HID using the internal Cryptotoken extension. In addition to HID, the U2F specification allows for BLE authenticators. The `chrome.bluetoothLowEnergy` API should be used to implement BLE U2F support in the Cryptotoken extension. What is the expected behavior? What went wrong? Nothing. This is a feature request. Did this work before? No Chrome version: 53.0.2785.116 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 23.0 r0 I started working on implementing this, but, as suggested by the "Contributing Code" documentation, I wanted to get feedback before putting too much effort into it. The OWNERS file for the Cryptotoken extension lists arnarb@chromium.org and juanlang@chromium.org. I'm not sure how to CC them on this bug.
,
Sep 21 2016
,
Sep 22 2016
Note that chrome.bluetoothLowEnergy only works on Chrome OS I don't think this belongs under Blink but I'm not sure what the right label is. Adding steel@ for further triage.
,
Sep 22 2016
Also jleong
,
Sep 22 2016
chrome.bluetoothLowEnergy does work on OS X, though I understand that this is a very recent change. It's currently only enabled for Chromium apps, but it can be whitelisted for specific extensions as well.
,
Sep 27 2016
,
Sep 27 2016
I think Dmitry is already working on this.
,
Mar 3 2017
,
Mar 3 2017
,
Jun 7 2017
The CryptoToken extension will eventually be replaced by the Web Authentication API.
,
Mar 31 2018
Merging into the tracking bug for the WebAuthn work. For the new API, BLE support is slated for M68 if all goes well. |
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 by bto...@github.com
, Sep 21 2016