▲ 391 ▼ I don't like passkeys | Ethan Hawksley (hawksley.dev) submitted 1 month ago by lemmydividebyzero@reddthat.com to c/technology@lemmy.world 154 comments fedilink hide all child comments
[–] qevlarr@lemmy.world 56 points 1 month ago (11 children) A password manager is better than passkeys in 2026 permalink fedilink source parent hideshow 11 child comments replies: [–] Natanael@infosec.pub 13 points 1 month ago (5 children) Some password managers can sync passkeys for you! Bitwarden can handle it permalink fedilink source parent hideshow 5 child comments replies: [–] Redjard@reddthat.com 4 points 1 month ago (4 children) android doesn't allow 3rd party apps to use passkeys nor autofill 2fa consistently. For passkeys, you are forced to use google services for it, or loose access, making it pointless. TOTP codes meanwhile can at least be copied and pasted manually from a password manager. permalink fedilink source parent hideshow 4 child comments replies: [–] Natanael@infosec.pub 5 points 1 month ago* (3 children) https://developer.android.com/identity/passkeys/manage-passkeys Actually not, 3rd party Android apps can act as passkeys providers With Bitwarden you can even do your own self hosted sync of passkeys https://bitwarden.com/blog/bitwarden-passkeys-mobile/ Any app where it doesn't work has chosen to not use the right API permalink fedilink source parent hideshow 3 child comments replies: [–] Redjard@reddthat.com 2 points 1 month ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Zak@lemmy.world 4 points 1 month ago (1 child) 14 and up seems to be about 80% of users, and I suspect there's a correlation between people who want to use passkeys with a third party password manager and being within two major versions of current. permalink fedilink source parent hideshow 1 child comment replies: [–] LodeMike@lemmy.today 2 points 1 month ago "I can't run Linux because version 1.0 doesn't support my GPU" permalink fedilink source parent [–] Glitchvid@lemmy.world 3 points 1 month ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] Natanael@infosec.pub 2 points 1 month ago Even pw synced passkeys at least have the benefits of both being phishing resisting + replay protected, as well as being able to use the TPM chip for extra local protection. Hardware keys are logically simpler though permalink fedilink source parent [–] arrowMace@lemmy.world 1 point 1 month ago (2 children) It's a false dichotomy to have one or the other. I use passkeys as a quicker and more convenient way to log in to some sites, but I still have passwords in my password manager as a fallback. permalink fedilink source parent hideshow 2 child comments replies: [–] Scrollone@feddit.it 2 points 1 month ago (1 child) Some websites prevent you from using a password if you set up a passkey. Pass keys are horrible. permalink fedilink source parent hideshow 1 child comment replies: [–] Flagstaff@programming.dev 4 points 1 month ago It seems like what's actually horrible would be those websites' implementation. But yeah, I'm definitely sticking with a manager. permalink fedilink source parent
[–] Natanael@infosec.pub 13 points 1 month ago (5 children) Some password managers can sync passkeys for you! Bitwarden can handle it permalink fedilink source parent hideshow 5 child comments replies: [–] Redjard@reddthat.com 4 points 1 month ago (4 children) android doesn't allow 3rd party apps to use passkeys nor autofill 2fa consistently. For passkeys, you are forced to use google services for it, or loose access, making it pointless. TOTP codes meanwhile can at least be copied and pasted manually from a password manager. permalink fedilink source parent hideshow 4 child comments replies: [–] Natanael@infosec.pub 5 points 1 month ago* (3 children) https://developer.android.com/identity/passkeys/manage-passkeys Actually not, 3rd party Android apps can act as passkeys providers With Bitwarden you can even do your own self hosted sync of passkeys https://bitwarden.com/blog/bitwarden-passkeys-mobile/ Any app where it doesn't work has chosen to not use the right API permalink fedilink source parent hideshow 3 child comments replies: [–] Redjard@reddthat.com 2 points 1 month ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Zak@lemmy.world 4 points 1 month ago (1 child) 14 and up seems to be about 80% of users, and I suspect there's a correlation between people who want to use passkeys with a third party password manager and being within two major versions of current. permalink fedilink source parent hideshow 1 child comment replies: [–] LodeMike@lemmy.today 2 points 1 month ago "I can't run Linux because version 1.0 doesn't support my GPU" permalink fedilink source parent
[–] Redjard@reddthat.com 4 points 1 month ago (4 children) android doesn't allow 3rd party apps to use passkeys nor autofill 2fa consistently. For passkeys, you are forced to use google services for it, or loose access, making it pointless. TOTP codes meanwhile can at least be copied and pasted manually from a password manager. permalink fedilink source parent hideshow 4 child comments replies: [–] Natanael@infosec.pub 5 points 1 month ago* (3 children) https://developer.android.com/identity/passkeys/manage-passkeys Actually not, 3rd party Android apps can act as passkeys providers With Bitwarden you can even do your own self hosted sync of passkeys https://bitwarden.com/blog/bitwarden-passkeys-mobile/ Any app where it doesn't work has chosen to not use the right API permalink fedilink source parent hideshow 3 child comments replies: [–] Redjard@reddthat.com 2 points 1 month ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Zak@lemmy.world 4 points 1 month ago (1 child) 14 and up seems to be about 80% of users, and I suspect there's a correlation between people who want to use passkeys with a third party password manager and being within two major versions of current. permalink fedilink source parent hideshow 1 child comment replies: [–] LodeMike@lemmy.today 2 points 1 month ago "I can't run Linux because version 1.0 doesn't support my GPU" permalink fedilink source parent
[–] Natanael@infosec.pub 5 points 1 month ago* (3 children) https://developer.android.com/identity/passkeys/manage-passkeys Actually not, 3rd party Android apps can act as passkeys providers With Bitwarden you can even do your own self hosted sync of passkeys https://bitwarden.com/blog/bitwarden-passkeys-mobile/ Any app where it doesn't work has chosen to not use the right API permalink fedilink source parent hideshow 3 child comments replies: [–] Redjard@reddthat.com 2 points 1 month ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Zak@lemmy.world 4 points 1 month ago (1 child) 14 and up seems to be about 80% of users, and I suspect there's a correlation between people who want to use passkeys with a third party password manager and being within two major versions of current. permalink fedilink source parent hideshow 1 child comment replies: [–] LodeMike@lemmy.today 2 points 1 month ago "I can't run Linux because version 1.0 doesn't support my GPU" permalink fedilink source parent
[–] Redjard@reddthat.com 2 points 1 month ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Zak@lemmy.world 4 points 1 month ago (1 child) 14 and up seems to be about 80% of users, and I suspect there's a correlation between people who want to use passkeys with a third party password manager and being within two major versions of current. permalink fedilink source parent hideshow 1 child comment replies: [–] LodeMike@lemmy.today 2 points 1 month ago "I can't run Linux because version 1.0 doesn't support my GPU" permalink fedilink source parent
[–] Zak@lemmy.world 4 points 1 month ago (1 child) 14 and up seems to be about 80% of users, and I suspect there's a correlation between people who want to use passkeys with a third party password manager and being within two major versions of current. permalink fedilink source parent hideshow 1 child comment replies: [–] LodeMike@lemmy.today 2 points 1 month ago "I can't run Linux because version 1.0 doesn't support my GPU" permalink fedilink source parent
[–] LodeMike@lemmy.today 2 points 1 month ago "I can't run Linux because version 1.0 doesn't support my GPU" permalink fedilink source parent
[–] Glitchvid@lemmy.world 3 points 1 month ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] Natanael@infosec.pub 2 points 1 month ago Even pw synced passkeys at least have the benefits of both being phishing resisting + replay protected, as well as being able to use the TPM chip for extra local protection. Hardware keys are logically simpler though permalink fedilink source parent
[–] Natanael@infosec.pub 2 points 1 month ago Even pw synced passkeys at least have the benefits of both being phishing resisting + replay protected, as well as being able to use the TPM chip for extra local protection. Hardware keys are logically simpler though permalink fedilink source parent
[–] arrowMace@lemmy.world 1 point 1 month ago (2 children) It's a false dichotomy to have one or the other. I use passkeys as a quicker and more convenient way to log in to some sites, but I still have passwords in my password manager as a fallback. permalink fedilink source parent hideshow 2 child comments replies: [–] Scrollone@feddit.it 2 points 1 month ago (1 child) Some websites prevent you from using a password if you set up a passkey. Pass keys are horrible. permalink fedilink source parent hideshow 1 child comment replies: [–] Flagstaff@programming.dev 4 points 1 month ago It seems like what's actually horrible would be those websites' implementation. But yeah, I'm definitely sticking with a manager. permalink fedilink source parent
[–] Scrollone@feddit.it 2 points 1 month ago (1 child) Some websites prevent you from using a password if you set up a passkey. Pass keys are horrible. permalink fedilink source parent hideshow 1 child comment replies: [–] Flagstaff@programming.dev 4 points 1 month ago It seems like what's actually horrible would be those websites' implementation. But yeah, I'm definitely sticking with a manager. permalink fedilink source parent
[–] Flagstaff@programming.dev 4 points 1 month ago It seems like what's actually horrible would be those websites' implementation. But yeah, I'm definitely sticking with a manager. permalink fedilink source parent