• LewdLemon@sh.itjust.works
    16·
    2 days 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.

    • m-p{3}@lemmy.ca
      3·
      1 day 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/

    • mnemonicmonkeys@sh.itjust.worksEnglish
      7·
      2 days 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

      • LewdLemon@sh.itjust.works
        2·
        1 day ago

        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

        True. I’m kind of affected by this in GOS, although I found a workaround to bludgeon my banking app into submission.

        Still, this is an issue that is already here, and it exists independently of passkeys.

        • mnemonicmonkeys@sh.itjust.worksEnglish
          71·
          2 days 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