- From: jensatch via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Mar 2020 17:49:01 +0000
- To: public-webauthn@w3.org
I'm also seeing the issue on Windows 10 versions 1903, 1909. We're developing FIDO authenticator apps for Android and iOS and both exhibit the same problem where after the authenticator's Bluetooth address changes, the platform cannot find the device during calls to getAssertion and makeCredential. Running an advertisement scanner on the platform prior to calling webauthn works around the problem. The problem returns when the address changes again. The address changes every 15 minutes. It feels like a bug in the Windows CTAP implementation. If so, it will likely affect any BLE authenticator that uses the BLE privacy feature. Android and iOS both use the feature (we have no choice), and the FIDO spec recommends that BLE authenticators use the privacy feature. -- GitHub Notification of comment by jensatch Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1371#issuecomment-596680304 using your GitHub account
Received on Monday, 9 March 2020 17:49:03 UTC