Visitar URL original
Remove ECDAA? · Issue #1410 · w3c/webauthn · GitHub
Skip to content

Remove ECDAA? #1410

Closed
Closed

Description

@bdewater

I was wondering if anything had changed since the PIE blog from August 2018 (Security Concerns Surrounding WebAuthn: Don't Implement ECDAA (Yet)), which also mentions nobody had implemented ECDAA yet so there was time to fix things.

Unless something's happening in FIDO-land where mere mortals like me are not privy to, FIDO ECDAA Algorithm from July 2018 predates the concerns raised in the blog post, so nothing seems addressed.

Unless I'm mistaken, "nobody implemented it" is still the case as well:

Given the recent removal of unimplemented extensions should ECDAA also be removed?

Activity

  1. selfissued commented on Apr 28, 2020

    @selfissued
    Contributor

    I support removing the ECDAA algorithm.

  2. ve7jtb commented on Apr 28, 2020

    @ve7jtb
    Contributor

    Nothing has happened in the Fido2 working group.
    I think it has been supported in UAF.
    There was some theory that UAF authenticators could work through WebAuthn.
    I have never really understood how that could work via a browser.
    Perhaps you might manage to get it to work in a native APP using a direct connection to a Fido server.
    I don't personally see a value to having it in the WebAuthn spec personally.

  3. added this to the L2-WD-03 milestone on Apr 29, 2020
  4. selfissued commented on Apr 29, 2020

    @selfissued
    Contributor

    I'll also point out that this working already decided not to register a COSE algorithm identifier for ECDAA, so this is already unusable. (Compare this to the algorithm identifiers that we are registering in https://tools.ietf.org/html/draft-ietf-cose-webauthn-algorithms-05). We should finish removing ECDAA.

  5. ve7jtb commented on Apr 29, 2020

    @ve7jtb
    Contributor

    Mike points out that there is no COSE algorithm identifier registered for this so it is not usable anyway.
    I have been asked by the WG to create a pull request to remove it.

  6. assigned and unassigned on May 20, 2020
  7. added a commit that references this issue on May 20, 2020
    62d49db
  8. added a commit that references this issue on May 23, 2020
  9. added a commit that references this issue on May 27, 2020
    0881ded
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions