- From: Sage Pointer via GitHub <noreply@w3.org>
- Date: Sat, 06 Sep 2025 04:01:21 +0000
- To: public-webauthn@w3.org
> What's surprising is that there are some Windows 11 installations, even when up to date, that still only allow creating passkeys with RS256. Is there any reasonable explanation for this? I quick tested on Virtualbox, and to me this happened when TPM was off. Without TPM, Windows 11 failed to use ES256 (but attempted to do so, if algo list contained ES256 before RS256 it requested the PIN twice). This can be figured out by AAGUID which is 6028B017-B1D4-4C02-B4B3-AFCDAFC96BB2 for Windows Hello software implementation and 08987058-CADC-4B81-B6E1-30DE50DCBE96 for the TPM-backed one. -- GitHub Notification of comment by SagePtr Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1757#issuecomment-3260409133 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 6 September 2025 04:01:23 UTC