Use the existing U2F protocol implementation in "device/u2f/". At the moment it focuses on USB/HID security keys, but it is possible to factor out transport-specific part of the implementation, and plug in another transport, i.e., Bluetooth Low Energy (BLE).
The specification of U2F over BLE can be found here: https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fido-u2f-bt-protocol-v1.2-ps-20170411.html
Use the existing U2F protocol implementation in "device/u2f/". At the moment it focuses on USB/HID security keys, but it is possible to factor out transport-specific part of the implementation, and plug in another transport, i.e., Bluetooth Low Energy (BLE). Primitives from "device/bluetooth/" should be utilized.
The specification of U2F over BLE can be found here: https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fido-u2f-bt-protocol-v1.2-ps-20170411.html
Your change meets the bar and is auto-approved for M67. Please go ahead and merge the CL to branch 3396 manually. Please contact milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), kbleicher@(ChromeOS), govind@(Desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Pls merge your change to M67 branch 3396 ASAP so we can pick it up for next M67 Dev/Beta release.
If already merged to M67 and nothing is pending, pls remove "Merge=Approved-67" label. Thank you.
Comment 1 by pkalinnikov@chromium.org
, Sep 8 2017