• Big Tech has implemented passkeys in a way that locks users into their platforms rather than providing universal security
  • Passkeys were developed to replace passwords for better account security, but their rollout by Apple and Google has limited their potential
  • Proton Pass offers passkeys that are universal, easy to use, and available to everyone for improved online security and privacy.
  • BeatTakeshi@lemmy.world
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    18
    ·
    9 months ago

    How is 25 bad? Do you need a passkey for each service /app/website? Can’t you use the same key for many services? (trying to understand how they work)

    • lemmyvore@feddit.nl
      link
      fedilink
      English
      arrow-up
      19
      ·
      9 months ago

      Ideally yes, they’re supposed to eventually replace all passwords. Of which I have hundreds. And yes not 100% of them will do that on the near future but a lot more than 25 will.

      • capital@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        9 months ago

        Being down-voted for asking questions is bullshit. Your questions are valid and those people suck.

    • CriticalMiss@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      9 months ago

      I have 150 passwords in my password manager. I’m not buying 7 YubiKeys (and to be fair that’s not what they’re designated for)

    • paraphrand@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      9 months ago

      Having a key shared across sites wouldn’t be great. If it was great it would be an article talking about “passkey” not “passkeys” because you would just have one. Like some sort of Skeleton Passkey that unlocks all your shit when compromised.

    • laughterlaughter@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      3
      ·
      9 months ago

      No, sharing passkeys across services is way too risky. One service gets compromised, someone gets your passkey, and then they have access to all of your services. It’s the same principle with regular passwords.

      • Spotlight7573@lemmy.world
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        1
        ·
        9 months ago

        Uh, each service only has access to your public key, not the private one that stays with you. It’s less risky than a regular password.

        Even with U2F hardware keys where the server-side stores the encrypted key (to allow for infinite sites to be used with a single hardware key), it’s only decryptable on your key and thus isn’t that useful for someone who has compromised a service.

    • Natanael@slrpnk.net
      link
      fedilink
      English
      arrow-up
      3
      ·
      9 months ago

      You only need one per website if you want it to autofill the username, because resident keys held on the security token can be recognized and suggested automatically but otherwise you must first enter your username on the website and let the website send its challenge value for the corresponding domain and account pair so that your security token can respond correctly.