• hummingbird@lemmy.world
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    2 days ago

    You seem to be falling for what the author was writing about. Only because you could technically try to use keepassxc to store passkeys, that does not mean that it will work. You see passkeys were build in a way the service you’re trying to login to can decide if they accept your keepassxc for passkey storage or not. It looks like you are in control when you are actually not.

    • SMillerNL@lemmy.world
      link
      fedilink
      arrow-up
      9
      arrow-down
      1
      ·
      2 days ago

      So, same as passwords then. The service can determine what they accept as a password. And if they’re being assholes about it you can decide to go elsewhere.

      • Beej Jorgensen@lemmy.sdf.org
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        1 day ago

        The service can determine what they accept as a password.

        And what password manager you use, I think was the poster’s point.

        • hummingbird@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 day ago

          There is indeed a big difference between requiring a specific password vs. requiring a specific device or software to be able to use the service. Keep in mind that big tech can very conveniently leverage this technology to lock you in. For example think about Apple, Google and Microsoft requiring you to use passkeys, and then later require you to use your certified phone and app. Most people will not be able to “go elsewhere”.