Breaking FIDO: Are Exploits in There?
summary
FIDO U2F uses per-site public/private key pairs generated by the authenticator, transports over USB NFC Bluetooth, and requires a signed, origin-bound signature plus a user-presence touch to defeat phishing. Chrome is the reference client; token binding / Channel ID ties assertions to the client so stolen assertions can’t be replayed from another device. Authenticators may use ECC P-256 keys and increment a global counter to detect cloned keys; client compromise and recovery/backup flows remain the hardest risks to solve.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:45FIDO Authentication Protocol
- 6:57Registration
- 12:57Challenge Parameter (c)
- 15:47Phishing Protection
- 19:08Channel ID (Token Binding)
- 25:50Device Cloning
- 29:27Authentication Alternatives?
related talks
30mHow FIDO U2F Security Keys Work
33mSimple. Open. Mobile: A Look at the Future of Strong Authentication
02h 22mFIDO 101
32mSecuring Online Identities with Simple, Secure, Open Standards
56mPasskeys 101: Technical Principles of FIDO
29mWebAuthn and security keys - unlocking the key to authentication
33mNavigating Passwordless Authentication with FIDO2 & WebAuthn
47mWhy FIDO Security Keys & Webauthn are Awesome
