New issue
Advanced search Search tips

Issue 905111 link

Starred by 2 users
Status: Assigned
Owner:
martinkr@google.com
Cc:
kenrb@chromium.org
martinkr@google.com
engedy@chromium.org
ssoneff@google.com
kpaulhamus@chromium.org
jdoerrie@chromium.org
mknowles@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Feature



Sign in to add a comment

Re-enable caBLE on Windows

Project Member Reported by martinkr@google.com, Nov 14 
caBLE has fallen victim to the USB/BLE blockade on Windows 10 19H1. Once we have moved it to its own GATT service UUID, we need to revisit this. Two implementation strategies:

(1) If caBLE extension is present during GetAssertion, do not talk to the native Windows API. (simpler)
(2) Support requests to a mix of caBLE- and non-caBLE devices. (more complicated; requires some UI work)
Project Member

Comment 1 by bugdroid1@chromium.org, Jan 9 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/46ccf182b9a6c3b756ba6042a48daefa7fb8f417

commit 46ccf182b9a6c3b756ba6042a48daefa7fb8f417
Author: Kim Paulhamus <kpaulhamus@chromium.org>
Date: Wed Jan 09 19:58:12 2019

Make Chrome look for both the FIDO and caBLE GATT service UUIDs

This will allow Chrome to recognize caBLE on both the old and new
UUIDs that GmsCore might be advertising.

TBR=martinkr@google.com

Bug: 905111
Change-Id: I1deffbcad6b5a88cdb7c22b316c7eff421fc30cb
Reviewed-on: https://chromium-review.googlesource.com/c/1370954
Commit-Queue: Kim Paulhamus <kpaulhamus@chromium.org>
Reviewed-by: Kim Paulhamus <kpaulhamus@chromium.org>
Cr-Commit-Position: refs/heads/master@{#621276}
[modify] https://crrev.com/46ccf182b9a6c3b756ba6042a48daefa7fb8f417/device/fido/ble/fido_ble_connection.cc

Comment 2 by kpaulhamus@chromium.org, Jan 10

Labels: M-73
►

Sign in to add a comment