News for hackers. Stuff that matters.
Re:Chrome 56 adds Web Bluetooth API by dhaya on Monday February 06, 2017 @02:08AM (#13577226)
tl;dr: click-bait title. The ability to access Bluetooth peripherals is opt-in and requires an explicit user interaction.
Re:Chrome 56 adds Web Bluetooth API by lm2s on Monday February 06, 2017 @03:27AM (#13577575)
Why is it click-bait? It just says that support for the Bluetooth API was added. Why would anyone extract from that that there were no safeguards in place against abuse?!
Re:Chrome 56 adds Web Bluetooth API by saintfiends on Monday February 06, 2017 @03:43AM (#13577658)
The article title:

  Chrome 56 quietly added Bluetooth snitch API
  Trust us, says Google, we understand privacy
Re:Chrome 56 adds Web Bluetooth API by zafiro17 on Monday February 06, 2017 @10:53AM (#13580548)
I agree the fact that an explicit user interaction is required doesn't necessarily constitute a safeguard. How many times has my Android phone updated an app, which inexplicably now requires additional permissions. Formerly it only needed access to my media. Now it needs access to my phone logs, GPS, address book, etc. etc. Confirm? [Yes] [Cancel]. Like most users, I update the app every time. So when this Bluetooth system says "This web app needs access to your Bluetooth Home Thermostat system. [Accept] [Stop using App] people will more than likely press accept, and away we go.
Re:Chrome 56 adds Web Bluetooth API by joahua on Monday February 06, 2017 @03:30AM (#13577589)
Will admit my first thought was web fingerprinting opportunity…