Closing gaps in strong auth: FIDO2 device support
summary
A D-Bus proxy service lets sandboxed apps use CTAP2 authenticators without raw USB access by routing requests through a host agent that enforces per-device permissions and activates on demand via systemd. Implementation uses D-Bus proxy, libfido2 and TPM2 with xdg-dbus-proxy, an unnamed pipe forwards PINs from the app to the host, and demos show GitHub login from a Flatpak and an emulated passwordless flow; Firefox integration is implemented and awaiting review.
AI-written summary · about
chapters (9)
- 0:00Introduction to FIDO
- 0:50Authentication concepts
- 2:11Security and authentication
- 3:51Technical workflow and protocols
- 6:16Passwordless authentication
- 8:21Challenges in sandboxing
- 10:41Implementing host services
- 12:25Demonstrations
- 14:30Status and future work
related talks
56mPasskeys 101: Technical Principles of FIDO
02h 22mFIDO 101
17mFIDO CTAP 2.1
23mBorderline: Examining the edge cases of FIDO
23mEnhancing FIDO2 Security for Safety-Critical Applications: Best Practices and Consid...
14mSecuring Authentication with and within FIDO
22mPasskeys through FIDO: How to write your own client?
38mBreaking FIDO: Are Exploits in There?
