Replying to @⁨Bluescluestoothpaste@sh.itjust.works⁩

So make the manager’s password massive. There, that complete sentence just now is over 30 characters long and could literally be a password. You can double up security with a secret file that you must locate on your PC, in KeePass, at least. You can also add notes about entries, track more than just website accounts, etc. It’s just too much brainpower to remember individual websites’ passwords. All important ones have 2FA anyway.

Managers are local to your computer so you likely messed up big-time if it got hacked, whereas websites can get hacked entirely out of our control.

Replying to @⁨Natanael@infosec.pub⁩

It’s android version dependent. Only 14 and up support 3rd party providers.

Passkeys are supported on devices that run Android 9 (API level 28) or higher.

On many devices, Credential Manager stores passkeys to Google Password Manager by default. Users can choose other password managers as its passkey providers in the System Settings on Android 14 or higher.

Given the slowness of android version rollouts, this will be an issue for a long time.

I also think supporting older androids is pushing apps to do it the “wrong” way and making it google specific.

Replying to @⁨qevlarr@lemmy.world⁩

Really depends on what you mean by passkey, since it’s actually a fairly vague term for a bundle of technologies.

I don’t really care for password manager passkeys; just use a password, all it really does is save you from needing to enter a username in a login flow.

But I’m a big fan of hardware 2fa using non-resident keys (“passkey” lite); I’ll use a regular login flow with a password manager, then the 2FA step with a hardware token. Basically bulletproof (ditto if you secure your PW manager with hw 2fa) and painless.