Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

This is a good start, but like everything Google introduces, it's only designed to be useful to Google, and has a number of flaws:

- syncs to the cloud without E2E encrypted. there's no reason any person should ever put all their private keys somewhere they can be stolen without at least a secret master password protecting them.

- they're not one standard. web apps will use WebAuthN, non-web apps will use a FIDO API. Passkeys are a mix of different technologies that is more complex than needed.

- they aren't interoperable with different software and devices. Currently, if you make a passkey, it can only work with whatever you used to make it. trying to use a passkey on different operating systems or apps etc requires manual workarounds, exporting/importing, etc.

- different providers have different levels of support. some support sign-in, some support MFA, some support both.

- the choice of only being able to use biometrics or a pin to protect the passkey store is stupid. you should be able to enter in text as well, so you can use a long and complex key to protect it, if you want. instead your options are 3 incredibly easy to crack methods.

- there isn't an easy way to back up everything offline in case your devices get lost.

- all this doesn't address attacks on account recovery, which is the most common way to compromise an account (nobody brute-forces passwords anymore, with the exception of giant password compromises which are used for lateral attacks against other services)



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: