3 ms·
Hence using an HSM, e.g. something like a Yubikey. Of course, they can be lost or stolen, which is why certificate revocation is necessary, and they would need
by philjohn 8y ago
Hence using an HSM, e.g. something like a Yubikey.
Of course, they can be lost or stolen, which is why certificate revocation is necessary, and they would need broad adoption among OS and browser vendors.
Plus you still have the issue of proving your identity if it's lost/stolen.
- akerl_ 8y agoHardware tokens don't really solve any of the problems I listed. You still have to deal w/ devices that don't do cert auth from a Yubikey (iOS being a great example), so as a site operator you don't get to avoid supporting new device / temp device workflows. Hardware tokens can allow individual power users to solve issues around multiple devices, lost devices, etc themselves, but unless you're suggesting porting 100% of users to hardware tokens, it doesn't change the workflows a site must support.
- jrockway 8y agoI believe Yubikeys work from iOS now. I have not tried it, however.