3 ms·
This is annoying security-wise. Looks like a single click/touch/keydown event will allow javascript to start scanning for devices. Remember what happened the la
by 0x0 10y ago
This is annoying security-wise. Looks like a single click/touch/keydown event will allow javascript to start scanning for devices. Remember what happened the last time Chrome added support for odd hardware APIs? https://googleprojectzero.blogspot.no/2016/02/racing-midi-messages-in-chrome.html https://googleprojectzero.blogspot.no/2016/02/racing-midi-me...
- pitaj 10y agoJavaScript 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.
- 0x0 10y agoBut 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?