Re:Chrome 56 adds Web Bluetooth API
by pitaj on Monday February 06, 2017 @04:49PM
(#13584480)
JavaScript doesn't scan. It opens a native modal for selecting a device. JS can provide filters, which are simply strings, they don't get any information about devices.
[ Parent
| on HN ]
But the native modal obviously runs a whole lot of native code including calling into the bluetooth stack and starting the radio etc. Even just exposing a way to "start scan" could be enough to shake out 0days in the native OS bluetooth stack. I'd much rather have a way to disable chrome.app from even as much as loading the corebluetooth dylib.
Also, is scanning for devices a 100% passive receive-only operation, or would it be possible to design a custom beacon device that identifies hosts that try to scan the beacon?