• BrianTheeBiscuiteer@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 month 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.

      • IanTwenty@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        Potentially the server can request hardware/software attestation that would limit the choice of password safe to approved ones only. We don’t yet know how big/likely this could be, but in theory it’s possible.

        • neclimdul@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          1 month ago

          well, if I’ve seen a vendor lockin before, and I’ve seen a couple, they’ll push them with open standards until they’re accepted and normalized.

          Then suddenly the big players like Google and Microsoft will block all the open platforms sighting “security” forcing businesses to adopt closed proprietary versions while touting their free and easy too use platforms.

          then the monitize it.

  • DonutsRMeh@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 month ago

    Passkeys are greate as long you make sure you use a third party (partial) password app, like proton or bitwarden that works everywhere.

    • LewdLemon@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      This right here. KeepassXC (PC) already had passkey support for a while, KeepassDX (Android) recently implemented support. If you use FOSS implementations, vendor lock-in and potential future corporate enshittification are non-issues.

      • lemdeggity@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        The argument from the “it’s a trap” article is that the service you are registering to can use attestation to ensure that you are only using passkey managers that they approve.

        I have to admit that I haven’t investigated this thoroughly myself but if the protocol can be abused in that way then your only choice really would be not to use the service. If it is related to banking or government services then you may not have much of a choice.

          • Mozilla’s warning is funny. “Don’t use this to reject attestations from unapproved authenticators!” That’s, like, almost the entire purpose to attestation. It tells you an Apple device or a YubiKey or whatever created the credential. What else could you use this information for other than to make life harder for users using certain authenticators?

      • mnemonicmonkeys@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        vendor lock-in and potential future corporate enshittification are non-issues.

        For now.

        In some countries, banks require users use their app on IOS or Google’d Android. You can’t use their services via browser, LineageOS, GrapheneOS

          • mnemonicmonkeys@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 month ago

            Fuck off with that defeatist bullshit.

            Make them drag you ckicking and screaming. Only morons and cowards walk in lock-step with the corpos

          • StoneStar@feddit.nl
            link
            fedilink
            arrow-up
            1
            ·
            1 month ago

            This mentality is so gross. “Well might as well roll over and get pounded in the A by big corpo! what else am I going to do, right? Hehe!”

              • StoneStar@feddit.nl
                link
                fedilink
                arrow-up
                1
                ·
                1 month ago

                Me personally, I’d get a burner smartphone in a drawer just for banking that is on airplane mode 24/7 except when I need it for banking and use a dumbphone for everything else. Also, I run linux and I have strict control over my router and I have ZERO subscriptions and creditcards. It’s not much but it’s something. Beats blindly rimming apple and alphabet.

                • krolden@lemmy.ml
                  link
                  fedilink
                  arrow-up
                  0
                  ·
                  1 month ago

                  That’s not gonna stop them from doing any of these things you’re afraid of it’s just sparing you from it

      • m-p{3}@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        Until they only allow specific AAGUIDs to enroll passkeys that don’t include the one used by KeePassXC (fdb141b2-5d84-443e-8a35-4698c205a502) or KeePassDX (eaecdef2-1c31-5634-8639-f1cbd9c00a08) because they don’t consider them secure enough.

        https://aaguid.nicolasuter.ch/

    • lemdeggity@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      0
      ·
      1 month 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
        ·
        1 month 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).

        • lemdeggity@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          1
          ·
          1 month ago

          My post was only meant to be a quick explanation of what passkeys are so I’ll leave it as is. I do think it’s healthy to be suspicious of big tech corporations and their motivations though so I’ll be doing some further reading.

      • NoLemurs@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        1 month ago

        They’re actually not tied to a device. They can be synced across devices.

        Bitwarden, 1Password, Dashlane, Google, Apple, and Microsoft will all do passkey syncing for you.

        We don’t yet have a good Linux native passkey store. I believe the credentialsd project is working on a spec for that. Once that’s up and running I would expect to see some options for syncing without relying on a third party service (though, you can self-host bitwarden right now). It’s definitely not seamless on Linux yet though.

  • NoLemurs@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 month 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
      ·
      1 month 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.

    • 0_o7@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      The trap is they’re pushing passkeys before password managers that make them portable are yet to be mainstream. And that platform lock in may be a motive driving it.

      “To login to your account, please use the device assigned to your identity.”

      Right now, if someone who doesn’t know about password managers starts using passkeys because of a few popups you just have to follow through to enroll, they’re going to get very confused when they try to login somewhere else. There may be alternative login methods for now, but that may change.

      It doesn’t seem all that forced yet, but if we have any idea of how big tech works, that’s where it is going.

      Passkeys are great, Big tech aren’t.

      I use them with my password manager but I’m cautious on which services and how often i may need to login to them on other devices.

    • zerofk@lemmy.zip
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      I’ve honestly not seen any benefits over passwords.

      If I want to check my mail on a library computer, I can type in a password and I’m in. If it’s using passkeys I need an already logged-in smartphone - which I probably don’t have if I need that library computer in the first place. That’s just one example.

      • m-p{3}@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        Personally I like Passkeys, and I enroll them in both my KeePassXC vault and on my two hardware keys (a primary Yubikey which I carry with me and a spare one at home).

        It doesn’t absolve one from neglecting proper security best practices (don’t login on a system you don’t trust, logout / clear cookies when done, etc), but a Passkey on a hardware key is much more difficult to phish or extract if you’re using someone else’s computer.

      • NoLemurs@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        Memorizing passwords doesn’t scale well.

        You’ve likely got dozens of accounts. You’re not going to memorize a password for every account. Re-using passwords is a serious security problem though. Poorly secured sites get their password databases leaked all the time. If you use the same password on lots of sites, it’s basically a sure thing that the hashes are out there on the darkweb already along with your email, and your password is compromised.

        Also, typing your email password into an unsecured library computer is a terrible idea. It is ridiculously easy for someone to install a keylogger and gather emails and passwords. In the past, your main protection was that it wasn’t worth anyone’s time to break into the computers, install keyloggers, collect lists of passwords, then figure out how to use them to get money. But with LLMs that can all be automated. It has become ridiculously cheap, and can be done by someone with a bot farm in Russia.

        A password manager largely fixes the first problem, but at that point you need a device with your password manager with you to log in anyway. And the password manager doesn’t fix the second problem at all.

  • BruisedMoose@piefed.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

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

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

      I think the reason passkeys are so controversial is that tech has a long history of ignoring user choice and pushing the most anti ownership solutions possible. Therefore, I think there is fair concern emerging along with any new mechanism that has any sort of TPM or hardware attestation components at all.

  • davel [he/him]@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    Admittedly I didn’t read that one guy’s blog post very closely, but it seemed to claim that because some companies may some day misuse/abuse some features of passkeys, passkeys are poison and no one should ever use them.

    • wewbull@feddit.uk
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      Well if that’s possible, it doesn’t sound like a good basis for security.

      • FauxLiving@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        The features they’re talking about are secure from a cryptographic standpoint.

        However, there are features built into the passkey system so that a company could decide that it will only accept passkeys from a specific piece of hardware or software.

        This isn’t necessarily bad, you may only want your server to allow you access if the passkey comes from your phone’s hardware. A person could have stolen your passkey but they’re unable to fake the attestation step.

        On the other end of things, a company like Google could provide a passkey service which requires you to use hardware provided by vendors that they approve of and they could abuse their position to force it’s implementation, such as how you can use Google to sign into websites via OIDC.

        Google could just as easily provide a service for ‘secure’ passkeys which are only allowed to be issued by phones provided by Google, Verizon or AT&T. No more third-party OSs (at least, if you want to sign into anything on the Internet) and no more jailbroken phones. You would have to use the exact, spyware laden, operating system that comes installed directly from your cellular provider who would have remote root access to your device.

        I think the idea that we can just boycott passkeys and prevent this is nonsense magical thinking. It requires some hypothetical world where we can perfectly coordinate a boycott of otherwise useful technology. In reality this issue will remain obscure and generally only known to people interested in the topic while Google can pour tens of millions in advertising to reach everybody on the planet explaining how good and secure attested passkeys are to mainstream Internet users.

        Use passkeys, they’re useful and more secure than passwords. Not using them won’t prevent enshittification, just sit back and watch the slow motion attested passkey trainwreck as it unfolds over the next decade.

    • blackbrook@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      It’s a very basic principle, that you don’t create powers that could be abused. That they haven’t been abused yet does not make doing so ok. It like saying it’s ok that my government was given the power to lock people up with no reason or due process because they haven’t used it yet.

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    If you read the pro article you can tell its a bunch of hogwash as they don’t understand Tue point of passkeys.

    • tyler@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      The person that wrote the anti article thinks that 2fa is a form of password… they’re the one that doesn’t understand passkeys.

  • myyass@lemmy.world
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    1 month ago

    Last time I was in Thailand and my buddy told me don’t worry, she’s not a trap.