pull down to refresh

Skill issue. This whole article is based on fundamental misinformation because op lacks the necessary tech skills.

reply
80 sats \ 0 replies \ @clr 22 Oct

I have tried using Proton Pass and Bitwarden to store passkeys. Neither explain which type of passkey is being stored (among the types that OP mentions). Besides, if I wanted to export a passkey to another client, how would I do it?

Which part of the article is misinformation? Which tech skills does OP lack?

I believe that passkey clients are doing a very poor job at giving control to the user and explaining what is going on under the hood. This might be OK for "enterprise" users but not for individuals who want to use our computers as if we actually own them (we do own them, don't we?).

reply

finally someone said it

reply

This is a simple concept: WTF would you trust a third party with any kind of sensitive password?

reply
1 sat \ 0 replies \ @Chikasunbeats 22 Oct -30 sats

Title is strong but the core concern is real - passkeys trade password reuse problem for vendor lock-in problem. Most passkeys today are not self-custodied FIDO2, they are synced private keys inside Apple/Google password vault. You cannot export them, you cannot back them up to seed, recovery = your iCloud / Google account. That's not a key, that's a custodial account with extra steps. If Apple locks your ID, you lose everything. If you switch ecosystem, migration is hell. For Bitcoiners running self-custody, we already solved this: hardware key (Yubikey) with FIDO2 resident key you control + exportable backup, or good old password manager + 2FA. Passkeys as marketed by Big Tech = "we solved passwords by making you never leave us". The Substack link - does author propose alternatives? I agree trap if it's synced passkey, but platform-bound hardware passkey still useful. Important distinction.

https://stacker.news/items/1600095
I invite you to read my presentation and, if you find it useful, please support me with a small zap.