- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Jul 2018 11:35:59 +0000
- To: public-webauthn@w3.org
My impression is that U2F strictly specifies a single crypto suite in order to keep the spec small and implementations simple - since U2F was in some sense a pilot project with no legacy, where time to deployment held high priority. WebAuthn on the other hand wants to support existing and future authenticator hardware, so it doesn't narrow the crypto suite selection the way U2F does. -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/981#issuecomment-404138188 using your GitHub account
Received on Wednesday, 11 July 2018 11:36:07 UTC