• DonutsRMeh@lemmy.world
    link
    fedilink
    arrow-up
    34
    arrow-down
    1
    ·
    9 hours ago

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

    • IanTwenty@piefed.social
      link
      fedilink
      English
      arrow-up
      16
      ·
      6 hours ago

      I think the worry is that if passkey attestation is required it will force people into a narrow set of authenticators controlled by the big orgs.

      At this point in time it’s not a problem, but how can we know it won’t be in future?

    • LewdLemon@sh.itjust.works
      link
      fedilink
      arrow-up
      20
      arrow-down
      1
      ·
      9 hours 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.

      • mnemonicmonkeys@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 hours 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

      • lemdeggity@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        20
        ·
        8 hours 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.