Comment by nerdsniper
16 hours ago
Bluetooth is generally used to prove that the two devices are co-located, which makes it more complex to do your proposed kind of deployment at-scale. Bespoke solutions could perhaps work around for some smaller number of devices, this QR code layer by itself isn't intended to stop 100% of workarounds.
No browser supports Bluetooth.
These passkey QR codes don't need to use Web Bluetooth API, because they utilize the WebAuthn API. The website itself isn't given access to the bluetooth, the task is handed off to the browser, which as a native application, can access bluetooth and abstracts the bluetooth away.
That's passkey QR codes generated by the browser, it has nothing to do with random QR codes offered by websites.
Chrome does...
That's news to me https://developer.mozilla.org/en-US/docs/Web/API/Web_Bluetoo...
Websites cannot use Bluetooth anywhere. The QR codes shown in the blog post are not passkey QR codes, which is likely what's confusing you.
Interestingly, only on desktop/Android and not iOS it seems.
1 reply →