We had originally planned to go all-in on passkeys for ONCE/Campfire, and we built the early authentication system entirely around that. It was not a simple setup! Handling passkeys properly is surprisingly complicated on the backend, but we got it done. Unfortunately, the user experience kinda sucked, so we ended up ripping it all out...
  • Im_old@lemmy.world
    382·
    2 months ago

    Seems to me the whole argument boils down to “they (the passkeys) are generally saved in proprietary non-communicating stores”, which is fair. But then the problem is not the passkey, it’s the fact that we (as usual) give all our stuff to corps. It’s the eternal struggle of easy of use vs. better security.

    I host my own vaultwarden btw 😊

  • M600@lemmy.world
    15·
    2 months ago

    Every time I’ve tried to understand passkeys I either don’t get it and it’s scary to potentially be locked out or I do understand it and I still find it scary to potentially be locked out.

    Even 2fa is tricky.

    If my phone is stolen and I don’t have my laptop with backup codes, then I’m not getting into my accounts.

    What if both are stolen or damaged at the same time?

    • shapis@lemmy.ml
      3·
      2 months ago

      Passkeys are basically passwords that you don’t send to the server. So they are safer against phishing.

      Basically the server has a message. They will scramble it with your public key. And send it to you. Your private key unscrambles the message and then you send the message back to them. So if they receive the original message back. They know you are you. And they never got their hands on your private key at any point. It’s awesome.

      2fa is an entirely different thing. And I do wish it was more standard how it works. Some places if you lose it you lose your account (bitwarden). Others you don’t (protonmail).

      Everyone should use passkeys. 2fa you have to decide if your case warrants it.

      Edit: example of passkeys:

      Step 1: they have the message “cat”

      Step 2: they encrypt it with your public key and it becomes “acm”

      Step 3: they send you the encrypted message “acm”

      Step 4: you decrypt the message “acm” into “cat” with your private key.

      Step 5: you send them back the message “cat”

      Only your private key would be able to decrypt something encrypted with your public key. So they now know you are you. And they never got a hand on your private key. It’s the same as a password except you never send it directly to the server.

    • Fushuan [he/him]@lemm.eeEnglish
      54·
      2 months ago

      Bitwarden has a passkey service + a paid totp service, so I can always use either to log into whatever within two clicks. Yeah it’s less secure than a physical keychain but… Whatever, it’s better than passwords and as easy to use.

      In any case, if you atore the backup codes in a place where you can lose them, that’s on you. Upload them into somewhere you control that has good privacy laws.

  • unskilled5117@feddit.orgEnglish
    131·
    2 months ago

    The problem with passkeys is that they’re essentially a halfway house to a password manager, but tied to a specific platform in ways that aren’t obvious to a user at all, and liable to easily leave them unable to access of their accounts.

    Agreed, in its current state I wouldn‘t teach someone less technically inclined to solely rely on passkeys saved by the default platform if you plan on using different devices, it just leads to trouble.

    If you’re going to teach someone how to deal with all of this, and all the potential pitfalls that might lock them out of your service, you almost might as well teach them how to use a cross-platform password manager

    Using a password manager is still the solution. Pick one where your passkeys can be safed and most of the authors problems are solved.

    The only thing that remains is how to log in if you are not on a device you own (and don’t have the password manager). The author mentions it: the QR code approach for cross device sign in. I don’t think it’s cumbersome, i think it’s actually a great and foolproof way to sign in. I have yet to find a website which implements it though.

  • sir_pronoun@lemmy.worldEnglish
    7·
    2 months ago

    I’d be interested in a discussion of his points here :) those sound like valid points he’s making

    • asap@lemmy.worldEnglish
      7·
      2 months ago

      edit: I think I’ve misunderstood the point of the article. He is saying passkeys are dangerous for people without password managers, therefore for most people passwords are still better (since most people don’t use password managers). It’s not so much a problem with passkeys, but the lack of password managers.

      Even in the best case scenario, where you’re using an iPhone and a Mac that are synced with Keychain Access via iCloud

      Surely the better-case scenario would be using a password manager?

      The article doesn’t address the recommended use-case of passkeys + password manager, which makes it kind of irrelevant.

      • sir_pronoun@lemmy.worldEnglish
        4·
        2 months ago

        But that is exactly what he recommends, using a password manager - with one time email authentication for the first login as an extra step, right?

        • asap@lemmy.worldEnglish
          3·
          2 months ago

          edit: I think I’ve misunderstood the point of the article. In a non-obvious (to me at least) way, he is saying passkeys are dangerous for people without password managers, therefore for most people passwords are still better.

  • Matt The Horwood@lemmy.horwood.cloudEnglish
    5·
    2 months ago

    I use passkeys and find them great, mind you I know that you need at least 2 of them so you have a backup. I also use yubikeys at work and they are the same issue, you need 2 of them in case 1 breaks or gets lost.

    Maybe the setup should be, make sure you have 2 passkeys on 2 different devices? but not in your password manager