| ▲ | tptacek 2 hours ago | |||||||||||||||||||||||||||||||
TOTP is phishable. The push to get away from TOTP is driven by phishing. I've done authentication projects for financial institutions that were actively targeted by phishing attacks, and it is difficult to mitigate TOTP phishing. Defeating TOTP is very much in the standard playbook for high-dollar scam operations. | ||||||||||||||||||||||||||||||||
| ▲ | AnthonyMouse an hour ago | parent [-] | |||||||||||||||||||||||||||||||
The objection here isn't to something that uses public keys instead of TOTP. It's that they added support for remote attestation to passkeys, which an enormous red flag and enables That Which Is To Be Prevented, i.e. permanently entrenching the incumbents because many third parties won't support new device makers with no user adoption yet and users won't adopt a device that won't work with many third party services. Moreover, the large majority of ordinary people are going to use whatever comes with their phone anyway, which can then lock the key in the device's secure processor by default independent of remote attestation. So then it's not getting you anything for those people and the primary thing it does is to impede Linux Girl from using Linux and anyone new from ever trying to create a competing mobile platform or even a usable non-Google fork of Android. The obvious way to satisfy people is to remove support for remote attestation from the spec. | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||