• Lem453@lemmy.ca
    link
    fedilink
    arrow-up
    19
    arrow-down
    2
    ·
    1 year ago

    Most people that have password managers are already using different passwords for each website. Usually randomly generated. What’s the difference between that and a passkey?

    • jet@hackertalks.com
      link
      fedilink
      English
      arrow-up
      20
      ·
      edit-2
      1 year ago

      The secret key pair of a passkey is never transmitted over the internet. Even if somebody snoops the authentication, they will not be able to reproduce the secret key to login in the future.

      Think of it just like SSH public and private keys.

      Normal passwords, are typically provided at login time, and get transmitted, relying on HTTPS to keep them secure, if somebody could observe the authentication, they could reproduce the password later.

      (Yes someone could hash the password client side and send over the output… But that’s extra work and not guaranteed)

      • towerful@programming.dev
        link
        fedilink
        arrow-up
        10
        ·
        1 year ago

        Client side hashing of a password just makes the hashed result the password, as far as security is concerned.
        Unless there is some back-and-forth with the server providing a one-time-use salt or something to make each submission of the password unique and only valid once, at which point that might get snooped as well.
        Better off relying on client certificates if you are that concerned

        • linearchaos@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Passkey’s approach is actually relatively close to client side certificates. It’s just in a form that is compatible with using a password manager. From the user standpoint once everything supports it properly, logins become relatively transparent and man-in-the-middle is pretty effectively mitigated. The other upside is of course unless you’re hosting your own stuff, no one supports client side certificates. This is an opportunity for all the big players to actually push people into better security.

      • Lem453@lemmy.ca
        link
        fedilink
        arrow-up
        6
        arrow-down
        1
        ·
        1 year ago

        Ah, thanks for that explanation. That makes sense. Eliminates a possible attack vector with https

    • 📛Maven@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      1
      ·
      1 year ago

      Right. Most people that have password managers. Making a password manager easier and more convenient to use means some portion of people who aren’t using one may start.

      • Amju Wolf@pawb.social
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        Realistically this is the biggest overall advantage.

        Sure, there are minor advantages to people already using password managers, but that’s such a tiny minority of people…

    • Natanael@slrpnk.net
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Passkeys use cryptographic keys held client side which are never transmitted, they user cryptographic challenge-response protocols and send a single use value back. You can’t intercept and reuse it unlike with passwords.