We had originally planned to go all-in on passkeys for ONCE/Campfire, and we built the early authentication system entirely around that. It was not a simple setup! Handling passkeys properly is surprisingly complicated on the backend, but we got it done. Unfortunately, the user experience kinda sucked, so we ended up ripping it all out...
  • stravanasu@lemmy.caEnglish
    4·
    1 hour ago

    The current security philosophy almost seems to be: “In order to make it secure, make it difficult to use”. This is why I propose to go a step further: “In order to make it secure, just don’t make it”. The safest account is the one that doesn’t exist or that can’t be accessed by anyone, including its owner.

  • ranandtoldthat@beehaw.orgEnglish
    8·
    1 day ago

    I use a password manager with passkey support and still disabled all my passkeys. The user experience for passkeys is so much worse even when support exists.

    • ericjmorey@beehaw.orgEnglish
      1·
      2 hours ago

      I’d like to hear more about the specifics if the issues you ran into. I keep delaying my options to start using passkeys because it’s a lot to take in at once and the only services implementing them seem to be the most important ones that I really don’t want to experiment with my ability to acess them. I haven’t even been looking at the details of each service’s implementation.

  • smeg@feddit.ukEnglish
    2·
    1 hour ago

    Using a security key as a password manager passkey seems to resolve this issue (I think?), but I guess the issue is more a problem for the casual user who wouldn’t bother with a security key!

    • ericjmorey@beehaw.orgEnglish
      2·
      2 hours ago

      Can you elaborate on what it means to use a security key as a password manager? I’m not sure if I understand what you mean.