Those are awfully dangerous on their own these days.

As soon as a poorly salted hash leaks or gasp, a hash with no salt, it's super easy to reverse those passwords now.

2FA severely reduces the danger of rainbow tables and keyloggers. The only real worry with 2FA is login replacement and interception. and passkey solves that, allbeit at the cost of complexity.

Almost every company has some way to work around the 2FA loss.

1. password + 2FA AND/OR passkey required.

• baby steps, start with getting them secure, then when most are ready start dropping the password
• iron out the kinks, give all apps a chance to implement
• if you only ever login with passkey and it asks you for 2fa, you can scrutinize the page more

You can tell just from the response on this post people aren't all ready for passkey yet, but you can't wait fo them to decide they're ready before you start.

Everybody does it differently. GitHub in particular allows multiple

If you are doing development or admin work, I would greatly advise you to pick up a Yubi Key.

My basic setup for any app/site that will allow it is two yubis and one passkey.

One yubi in the safe with next of kin instructions, one on my key ring.

Then any site that supports passkey, I'll also have one of those there too.

Same thing as any file full of credentials.

The KeePass file is encrypted so it's reasonably secure