• IrateAnteater@sh.itjust.works
    link
    fedilink
    arrow-up
    114
    ·
    2 months ago

    Passkeys are a great idea, but everyone involved seems like they want the process to be as much of a pain in the dick as possible. So until the industry pulls it’s collective head out of its collective ass (not going to hold my breath on that one), it’ll be passwords+2FA for me.

    • casmael@lemm.ee
      link
      fedilink
      arrow-up
      19
      ·
      2 months ago

      I hate 2fa so much, I never thought they would come up with anything more irritating. Little did I know.

    • vonbaronhans@midwest.social
      link
      fedilink
      arrow-up
      15
      ·
      2 months ago

      Jesus Christ, dude, that is exactly it.

      We’re trying to implement passkeys at work and the testing has been an absolute nightmare. Literally have no control over the onboarding experience because each tech giant is clamoring over each other, interjecting into the process to be the “home” for your passkeys. It’s bananas.

      When it’s all set up, it’s kinda great! But getting set up in the first place is an exercise in frustration.

      • lemming741@lemmy.world
        link
        fedilink
        English
        arrow-up
        10
        ·
        2 months ago

        It’s a chance for them to lock you (normies) into their platform forever. They’re not going to give that up.

      • brbposting@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        2 months ago

        Silly.

        Are they learning?

        Edit: my bet is the experience was so ridiculously frustrating, Chrome/Google actually saw some attrition - maybe enough people made Yahoo! Mail accounts that Google noticed

  • tabularasa@lemmy.ca
    link
    fedilink
    arrow-up
    54
    ·
    2 months ago

    The amount of people in this thread that don’t understand passkeys surprises me. This is Lemmy. Aren’t we the technical Linux nerds of the Internet?

    • Maggoty@lemmy.world
      link
      fedilink
      arrow-up
      12
      ·
      2 months ago

      2FA is just dead simple. I contact you, you contact me, handshake achieved. If you call me out of the blue I raise the alarm. If you get a login attempt with a failed handshake you raise the alarm.

      Putting it all behind a pop up screen just isn’t trustworthy to the human brain.

      • bearboiblake@pawb.social
        link
        fedilink
        English
        arrow-up
        7
        ·
        2 months ago

        TOTP 2FA is less secure than passkeys. 2FA TOTP keys can be phished. Passkey authentication cannot be phished. This is a security improvement which can make people completely immune to phishing attacks. That’s huge. And it doesn’t have any privacy risks, no loss of anonymity. It’s an open standard.

        This is, objectively, a rare example of new technology which will make the world better and safer for us.

        • Tiger@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          3
          ·
          2 months ago

          But I also worry about new areas of weakness with passkeys - anyone accessing the device with the passkey on it, or hacked that device, gets access automatically to the accounts. Also if logins are too fluid I worry that anything out of the ordinary during sign ins won’t be noticed.

          • bearboiblake@pawb.social
            link
            fedilink
            English
            arrow-up
            3
            ·
            edit-2
            2 months ago

            yeah that’s totally true, but usually modern devices ensure that the passkeys are protected with a PIN or some biometric security, so I think it’s at least as strong as having a password manager on your device that can be unlocked with a PIN.

            not really sure what you mean about “out of the ordinary” logins - it sounds like you’re thinking about phishing risks? but remember - passkeys cannot be phished. they verify the identity of both sides of the authentication token exchange - the server verifies you, and you verify the server. If you only use passkey authentication, you are safe from being phished. the most secure system would be one entirely without passwords/oath totp

            • Tiger@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              1
              ·
              2 months ago

              I guess I mean if people are too used to critical services opening up without any friction, a pause to complete some sign in step, they’ll stop taking a moment to look for any warning signs, so they might miss the fact that they’re at a spoofed url, for example. Yes you’re right that the passkey wouldn’t be working at this fake site, but it could still take them out and harvest some data, interactions or credentials.

          • bearboiblake@pawb.social
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 months ago

            everyone is sick and tired of tech promising to make the world better, only to make everything worse. i totally get the mistrust, the feeling that this is probanly just another trick from big corporations to steal even more of your privacy. i know much better than most people what it’s like. i know you’ve got no real reason to believe me, i’m just a random silly gay furry boy, but, trust me, in this case, we should be adopting this tech. if you’ve got family members or friends who are more vulnerable to phishing scams - often scammers target the elderly - i’d really encourage you to encourage them to set up passkeys. as always, i strongly recommend bitwarden - it can manage passkeys and sync them between devices and it’s totally secure and open source.

            much love & solidarity!

            • Maggoty@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              2 months ago

              First, I love your self description. But second, I’m not trying to say I’m not on board. I should have been more clear, I was simply trying to answer why more people are not on board.

    • areyouevenreal@lemm.ee
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      2 months ago

      You understand that technical people often are the least likely to trust new technology and are often stuck in the mud when it comes to technology? Doubly so if you are anti-corporation. It seems anything that isn’t the Unix way of doing things can be questioned.

      There is a good meme about people who love technology vs people who actually work with the stuff. The former using IoT devices to turn their lights on while the latter uses a light switch and has a gun in case the printer starts making weird noises.

      • I Cast Fist@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        It seems anything that isn’t the Unix way of doing things can be questioned.

        I think Unix is the thing that indirectly gets questioned most often, because everyone wants to be on the “right” side of how to unix things (see latest rust in kernel for a very recent example). When I think about it, unix alone feels like a recurring xkcd standards comic

    • Natanael@infosec.pub
      link
      fedilink
      arrow-up
      6
      ·
      2 months ago

      The synchronization part is the annoying part. And when you have multiple accounts on one site you can end up with multiple passkeys for it.

  • Katana314@lemmy.world
    link
    fedilink
    English
    arrow-up
    38
    ·
    2 months ago

    There’s been a lot of pain in the attempt to portray it as “Just click the passkey button, and that’s it! Your login is secured for life!”

    No - Buddy. It is secured for this one specific device that I have biometric authentication for. What about my computer? What about my other computer that isn’t on the same operating system? I have a password manager that stores these things, why didn’t you save to that when I registered? Why is it trying to take this shit from my Apple Keychain when it’s in Bitwarden?

    And, the next ultra-big step: How would a non-techie figure this shit out?

    • BorgDrone@lemmy.one
      link
      fedilink
      arrow-up
      6
      ·
      2 months ago

      No - Buddy. It is secured for this one specific device that I have biometric authentication for. What about my computer? What about my other computer that isn’t on the same operating system?

      Then use a Yubikey.

      • MDCCCLV@lemmy.ca
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 months ago

        I tried a yubikey but most websites want you to use the pin for that which requires windows hello, and if you reset windows you lose that.

    • I use both Bitwarden and Apple’s native Passwords.app and just save a passkey for each app. Usually you can name the passkey on the website/in the app as well.
      This is also the system I use when saving 2FA TOTP codes as well so I guess I’m used to it, but it makes good sense to me to have reduncancy in my password apps. Also I lock up *the apps themselves* with passkeys in the respective app for ease of use.
      :mastozany:

    • I Cast Fist@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      2 months ago

      And, the next ultra-big step: How would a non-techie figure this shit out?

      They wouldn’t, because the people calling the shots in the tech world create UX with a focus on it sucking for everyone

    • candybrie@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      2 months ago

      And, the next ultra-big step: How would a non-techie figure this shit out?

      They don’t have a computer, another computer with a different OS, or bitwarden.

    • jj4211@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      This was roughly the state of affairs before but the state of things have relented where software password managers are now allowed to serve the purpose.

      So if a hardened security guy wants to only use his dedicated hardware token with registering backups, that’s possible.

      If a layman wants to use Google password manager to just take care of it, that’s fine too.

      Also much in between, using a phone instead of a yubikey like, using an offline password manager, etc.

  • yesman@lemmy.world
    link
    fedilink
    arrow-up
    34
    ·
    2 months ago

    Passkeys are light years ahead of 2fA in user experience. Why do you dislike them?

    Security based on devices is one of the positive innovations of smartphones and perhaps the only area where they’ve improved over the desktop experience.

    • IrateAnteater@sh.itjust.works
      link
      fedilink
      arrow-up
      60
      ·
      2 months ago

      I very specifically don’t want my security tied to my device. Trying to migrate to new phones, and keeping things synced between a phone, desktop, and laptop is why I long ago moved to a password manager. Now, especially in the phone space, getting passkeys to function fully with a password manager ranges from “pain in the ass” to “not actually possible”.

      • thesohoriots@lemmy.world
        link
        fedilink
        English
        arrow-up
        30
        ·
        2 months ago

        I had a botched phone battery replacement once resulting in the phone getting replaced very unexpectedly. It was a nightmare trying to get everything back together because I stupidly used google authenticator, which is tied to the specific phone it’s on. Not tying it to the device is the way to go.

        • yesman@lemmy.world
          link
          fedilink
          arrow-up
          5
          ·
          edit-2
          2 months ago

          I didn’t consider the friction of integrating it into your existing process because I use a manual password manager. But who is saying you should replace a password manager with passkeys? It was always meant to be a parallel system.

          Edit: I just wanted to add that people like you and I who have “solved” our credentials problems are a tiny minority. Passwords are shit. Just because we’ve grown accustomed to them doesn’t change that.

          • WhatAmLemmy@lemmy.world
            link
            fedilink
            English
            arrow-up
            6
            ·
            2 months ago

            You’ll find that nobody has a problem with passkeys specifically. They have a problem with the implementation, and companies forcing passkeys onto users who don’t want or need them.

            I don’t need passkeys because I use a password manager. My threat model requires that I can restore my password manager, all 2FA, and regain full access to all my accounts from anywhere in the world, even if a natural disaster occurs and all my devices are destroyed.

            Passkeys and SMS 2FA are a direct threat to my threat model, and I can’t help but feel they’re designed to further entrench surveillance capitalism, and the invasion of privacy as a prerequisite for security.

        • potustheplant@feddit.nl
          link
          fedilink
          arrow-up
          3
          ·
          2 months ago

          Authenticator no longer works like that. You can now restore all of your 2fa codes by logging in to you google account and it’s been that way for almost 2 years now.

          • beepaboopa@lemmy.world
            link
            fedilink
            arrow-up
            8
            ·
            2 months ago

            I’m using Bitwarden, Firefox, and Android and passkeys have been working fine for me.

            What am I doing wrong?

        • rollerbang@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          It just doesn’t work for apps on Android, which is a bummer. For example the Playstation app login with passkey stored in Bitwarden simply doesn’t work for me.

      • Quokka@mastodon.au
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        @IrateAnteater @yesman if they do the “show secret” or whatever the option is called when your 2FA setup shows a QR code then you can copy that plain-text and save it somewhere (safe!) to just plumb it in to whatever authenticator app you decide to use elsewhere.
        If you use something like BitWarden then it can generate those 2FA codes for you and sync between whichever devices you use.

    • Engywook@lemm.ee
      link
      fedilink
      arrow-up
      12
      ·
      2 months ago

      Why would I want security based on a device? What security this offers greater than a 64 chars password + 2FA?

        • Engywook@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          I doubt that anyone that doesn’t use “password” as a password and who knows what 2FA is could be easily subject to phishing.

          • Natanael@infosec.pub
            link
            fedilink
            arrow-up
            3
            ·
            2 months ago

            It literally just takes a slightly different domain name. Lots of infosec pros have been phished when not paying attention

    • mspencer712@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      2 months ago

      Passkeys make plausible deniability more difficult. “This user name isn’t necessarily associated with my real world identity” permits some important good things.

      • dblsaiko@discuss.tchncs.de
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        The kicker is this used to be solved with passwordless webauthn, the same standard, until some morons decided that resident keys were the way to go (they aren’t)

          • Natanael@infosec.pub
            link
            fedilink
            arrow-up
            1
            ·
            2 months ago

            That’s literally no different from a regular password manager or having a 2FA TOTP code app set up for it

            • mspencer712@programming.dev
              link
              fedilink
              arrow-up
              1
              ·
              edit-2
              2 months ago

              Are you sure? TOTP secrets can be exported. I think passkey implementations explicitly prevent that. Unless I’m missing an option to export passkey creds, e.g. print them out.

              That same disaster recovery feature (which I need) also helps avoid a future where every forum and avenue of dissent requires dis-repudiation via passkeys. It’s a weird nuance, ascribing a social effect to a simple ability to back up your keys without backing up your whole phone.

              • Natanael@infosec.pub
                link
                fedilink
                arrow-up
                1
                ·
                2 months ago

                Passkeys can be synchronized, but aren’t intended to be exported raw as they’re meant to be used with a TPM / secure element chip or equivalent secure hardware to protect the key in use. Bitwarden can synchronize them.

                Also, they intentionally create distinct keys per site, so you can’t link multiple accounts using the same passkey / hardware security key.

  • bennypr0fane@discuss.tchncs.de
    link
    fedilink
    arrow-up
    29
    ·
    2 months ago

    Passkeys are one exception to the familiar pattern of “we give you more SeCuRiTY so we can spy on you more and control your behaviour better”. They actually are more secure. Problem is, a lot of technical issues with it still, a ton of stuff not working correctly yet

    • asdfasdfasdf@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      2 months ago

      I’m still appalled that my Yubikey / FIDO2 still doesnt work on Firefox. I have it as a passkey for GitHub, realized it doesnt work on Firefox, so they just prompt me for my password. That seems backwards to have password as a fallback, too.

      • bennypr0fane@discuss.tchncs.de
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        I’m also having problems using passkeys (stored in Bitwarden) with Github in Firefox. It keeps prompting me to touch the security key, which I don’t have, so I plain can’t use a passkey for Github. Works perfectly for Google though

  • nimble
    link
    fedilink
    English
    arrow-up
    26
    ·
    2 months ago

    On the contrary i want more services using passkeys instead of 2fa methods that are less secure (sms).

  • darvit@lemmy.darvit.nl
    link
    fedilink
    arrow-up
    22
    ·
    2 months ago

    ITT: people who think only SMS, email and TOTP exist as 2FA.

    And people who think only your phone can be used as passkey.

  • geoff@lemm.ee
    link
    fedilink
    arrow-up
    19
    ·
    2 months ago

    I use passkeys through 1Password and it’s vastly less irritating to me than anything involving passwords, especially 2fa. I really don’t like having to wait for email to arrive or copying down digits from a text message, which seems to be how 2fa typically works 90% of the time.

  • povario@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    17
    ·
    2 months ago

    Unless I’ve missed something big, passkeys are pretty easy for me if the website supports them imo.

    Using KeePassXC, I click register on the website, register the passkey with KeePass, then it just works when I need to authenticate or login. My database is then synced across all my devices.

    Passkey support is yet to come to KeePassDX on Android though, so I’ll be awaiting that feature

  • Randelung@lemmy.world
    link
    fedilink
    arrow-up
    16
    ·
    2 months ago

    It’s not for your security, it’s for the company’s. People suuuuuuuuck when it comes to credentials.

    • NocturnalEngineer@lemmy.world
      link
      fedilink
      arrow-up
      17
      ·
      edit-2
      2 months ago

      My company insists on expiring passwords every 28 days, and prevents reuse of the last 24 passwords. Passwords must be 14+ characters long, with forced minimum complexity requirements. All systems automatically lock or logout after 10 minutes of inactivity, so users are forced to type in their credentials frequently throughout the day.

      Yes people suck with creating decent credentials, but it’s the company’s security policies breeding that behavior.

      • oatscoop@midwest.social
        link
        fedilink
        arrow-up
        11
        ·
        2 months ago

        I don’t get why people get upset at frequently expiring passwords. It’s not hard: just write it on a postit note and stick it on your monitor.

      • Tiger@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 months ago

        Tell them the NIST recommendations for password frequency changes have been really reduced in recent times because it pushes people into other bad password practices. Among all factors, changing the password frequently is the least important.

      • greenskye@lemm.ee
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 months ago

        Same. They also don’t allow password managers and I have multiple systems that don’t use my main password, so I have at least 5-6 work passwords for different systems.

        Nobody can remember all that.

        So everyone makes the simplest password they can (since it has to be regularly typed in) and writes it down somewhere so they don’t forget it.

      • Randelung@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        And yet admin, 1234, test, etc. remain the most commonly ‘hacked’ passwords. Your company’s policies may be annoying, but they certainly don’t make you use unsafe passwords.

  • Boozilla@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    14
    ·
    2 months ago

    Remember when tap-to-pay was new and didn’t work at a lot of places and some people were freaked out over it?

    And now most of us use it without a 2nd thought.

    I speculate passkeys will be like that.

    • Natanael@infosec.pub
      link
      fedilink
      arrow-up
      13
      ·
      2 months ago

      They’re using the same standard as FIDO2 / WebAuthn hardware security keys. The protocol is phishing resistant, unlike TOTP and similar one time code solutions.

      I prefer the physical ones, because they’re easy to organize. Passkey synchronization can be annoying.

      • null_dot@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 months ago

        I don’t think that’s true.

        You can store them in keepassxc which can be accessed with a password.

        I think it’s “have” + “know” or “are”.

        So you have the device with the passkey, and know the unlock pin or are the person with the biometrics.

      • bitwolf@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 months ago

        How i interpretted it is that the biometrics provide access to the tpm which is like a built in yubikey you “own”.

    • Swarfega@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      2 months ago

      And how many sites support Yubikeys/Security Keys? Not many. I doubt we’ll see more either now with Passkeys becoming more prominent.

      I have two Yubikeys and other than securing my password manager vault they are rarely used elsewhere.

  • lightsblinken@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    2 months ago

    sure, you can use a passkey as a primary authentication, but only “a device” or “system”(keypass/1pass etc) knows the passkey detail. with only passkey, if my passkey provider/ device is compromised then everything is lost. having single factor auth seems like a bad idea.

    a password is something that I can know, so is still useful as a protection mechanism. having two factor auth should include password and passkey, which seems entirely reasonable whilst also providing an easier path forward for people used to TOTP.