• BruisedMoose@piefed.social
    cake
    link
    fedilink
    English
    arrow-up
    1
    ·
    27 days ago

    Or “Like all questions of security vs convenience, a user should decide what they are or are not comfortable with.”

  • BrianTheeBiscuiteer@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    26 days ago

    The biggest problem I see is that it requires OS or browser integration. While possibly a better solution than simple passwords this feels like a vendor lock-in scheme.

    • Auli@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      1
      ·
      26 days ago

      You don’t remember them you are not expected to moving from iOS to Android lets say generate new ones for your new device.

    • Captain Aggravated@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      26 days ago

      If the computer is in even a marginally secure place, storing passwords on physical paper is better than what a lot of people do.

      Of all the proverbial bullets I’ve been hit with, none had my name on them; they were all addressed “To whom it may concern”. The times my identity has been stolen or my accounts compromised it was because somebody attacked some fairly large entity, like Alphabet or Equifax or Microsoft or Visa. Nobody’s going to walk into my house looking for my passwords. They might walk into my house looking for my television, but that hasn’t happened to this house longer than I’ve been alive.

  • NoLemurs@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    27 days ago

    They really aren’t a trap. They’re a well designed standard. The tooling around them isn’t quite perfect yet, but they’re a huge improvement over passwords.

    People upvote because they hate change.

    • ell1e@leminal.space
      link
      fedilink
      English
      arrow-up
      1
      ·
      26 days ago

      People upvote because they hate change.

      People upvote because big tech has a tendency of forcing the most anti ownership outcome possible on everyone. Here, such an outcome likely would be mandatory passkeys that are set up to require hardware attestation.

      One way to reduce that risk is to boycott passkeys until TPM and hardware attestation are removed from the standard. You may not think that’s a fair response, or that such a boycott won’t save us from the inevitable outcome, but nevertheless it’s not a completely irrational reaction.

        • NoLemurs@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          26 days ago

          And… honestly, you should probably buy 3. Losing your main key only to find out that your backup key broke a month ago and you haven’t been testing it is a real risk.

          • Viceversa@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            26 days ago

            Not every service allow for registering more than one passkey

            And what are they odds of simultaneous losing / breakdown of all three keys? I think they are not negligible.

          • doodlebob@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            26 days ago

            I ended up getting one through arstechnica (they sent one if you subscribed back then), then I got more through some sale or something

    • tyler@programming.dev
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      26 days ago

      Password manager can store passkeys as well. They’re way easier to fill than passwords, they always work and never have issues with filling like you can have on some websites that just don’t work well with pw managers.

    • lemdeggity@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      0
      ·
      26 days ago

      It’s essentially just public key cryptography streamlined to reduce friction for the user. When you’re prompted to create a passkey for a service a new public/private keypair is created. The private key can then be synced to other devices for example via the iCloud keychain or Bitwarden. Obviously you have to then trust that provider to keep your keys safe. The upside is that your passkey can be automatically discovered and used to sign in without using a password. Alternatively the private key can be device bound but the downside is that if you lose the device you lose the private key too.

      • ell1e@leminal.space
        link
        fedilink
        English
        arrow-up
        1
        ·
        26 days ago

        If it was just to helpfully reduce friction, it wouldn’t be so controversial. The inclusion of any sort of TPM and hardware attestation support at all is what has some people sounding the alarm (in my opinion rightfully).

        • Ooops@feddit.org
          link
          fedilink
          arrow-up
          1
          ·
          26 days ago

          It’s mainly controversial because the actual use contradicts its purpose. Passkeys are phishing-resistent, which is still the main risk for password in real world scenarios, and are a good idea.

          But the websites supporting it put out big warnings when you don’t have another method to login configured. And they don’t actually advise you how to backup your passkey and keep it safe, but instead want you to set up an alternative way to login or recover your account. Which totally defeats the purpose in the first place.

          Quite the contrary: “there is a problem with your passkey/account, please use the recovery method you set up” even makes for more convincing phishing. So why are they pushing for passkeys when it isn’t for security reasons?

          • lastweakness@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            26 days ago

            This is, imo, the bigger issue. No clean way to export and move passkeys around, even between the open source options like Bitwarden and Proton Pass or as plain backups…