- From: Antony R Mott via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Apr 2024 18:05:16 +0000
- To: public-webauthn@w3.org
@MasterKale, petrdvorak and other contributors: thanks for this discussion which I find very useful, and even though closed now, perhaps useful to add April 2024 update on my experience with algorithm order. I'm doing webauthn from scratch with a library mentality, and expect most of my customers to be early-adopters or mobile users with standard platform biometrics (touch or faceid). I thought about not supporting ancient windows Hello users, but I also had those chrome warnings when I left out the legacy -257. I followed Matthew's suggestion and reorganized my algs to put -8 first, to encourage the more current algorithms to bubble up...sure enough latest Chrome used -8, and ignored -7 which was second in my alg list. I did keep last the -257 alg. I store the public-key algorithm, so over the next year or so I can measure what percentage if any of my customers will create keys with -257. If anyone is interested shout out to me and I'll post the metrics here or somewhere more useful. Exciting technology: the way forward! -- GitHub Notification of comment by antonymott Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1757#issuecomment-2032716679 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 April 2024 18:05:17 UTC