http://webbluetoothcg.github.io/web-bluetooth/use-cases.html#security_privacy
lists some of the risks we want to avoid in implementations.
The basic model is that the website tells the UA what kinds of devices
it can productively connect to, and then the UA presents the user a
dialog from which
The main question that I have is what is the security model?
The security section of the spec is very light.
/ Jonas
On Aug 22, 2014 6:34 PM, Jeffrey Yasskin jyass...@chromium.org wrote:
We have a draft API for Bluetooth device access at
https://webbluetoothcg.github.io/web-bluetooth/, for
We have a draft API for Bluetooth device access at
https://webbluetoothcg.github.io/web-bluetooth/, for which I'm planning to
send a Blink Intent to Implement email soon. The spec isn't really up to
web standard quality yet: we're planning to refine it as we get feedback
from implementation and
It's fairly similar to the BluetoothGatt API that was posted to
https://wiki.mozilla.org/B2G/Bluetooth/WebBluetooth-v2 yesterday. The
FFOS API provides more control over discovery and pairing, as is
appropriate for an API aimed at certified applications.
We have been actively communicating with
