293
Passkeys Explained: The End of Passwords (sentientrant.com)
submitted 10 months ago by to c/technology@lemmy.world
225 comments fedilink hide all child comments
 

Passkeys are built on the FIDO2 standard (CTAP2 + WebAuthn standards). They remove the shared secret, stop phishing at the source, and make credential-stuffing useless.

But adoption is still low, and interoperability between Apple, Google, and Microsoft isn’t seamless.

I broke down how passkeys work, their strengths, and what’s still missing

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 10 months ago (12 children)

You don't share your personal password across the whole team now, do you? At least for your teams sake I hope you don't.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 12 child comments
    •
  • [–] 3 points 10 months ago (3 children)

    You know that not every account is only used by a single user, right?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] -1 points 10 months ago (2 children)

    I think that's the problem right there... If you share accounts across multiple people you have far greater problems than how passkeys work...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 10 months ago (1 child)

    Or they're using it as intended. I've had more than one account I've gotten by cost sharing with friends. That's not a problem, that's a solution.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 10 months ago

    And it only takes one person with a grudge to cause a problem. I have seen it. I have shared accounts but very carefully and if someone abuses it then they permanently lose access to my stuff even if they are family.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 10 months ago (6 children)

    share your personal password

    We share a password. Then we don't call it a personal password anymore. Was that your question?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 4 points 10 months ago (5 children)

    That’s an IAM no-no.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 1 point 10 months ago (4 children)

    So? Read my question above.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 10 months ago (3 children)

    You create unique accounts for every team member so that access can appropriately be logged.

    Or you implement a PAM tool that logs access and vaults the password and rotates it after use.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 10 months ago

    Obviously not the personal password, but sometimes you need to share a password. Think about the password for a remote desktop your team may need to connect to for troubleshooting a problem for example.

  • permalink
  • fedilink
  • source
  • parent