So, the problem with USB tokens that we basically have two choices: - Unauditable black boxes built on *supposedly* more secure ICs that require NDAs to develop for - Open and auditable, but definitely pwnable off the shelf microcontrollers. Which poison do you prefer?
-
Show this thread
-
So far I've favored the first one, because you *know* all those keys based on a random STM32 are going to be glitchable, and closed stuff *might* be better. But after ROCA and other fails, maybe open firmware is better and just hope nobody physically attacks your key?
3 replies 0 retweets 10 likesShow this thread -
Keep in mind that this depends on your use case, e.g. a key keeping SSH keys needs to be more secure than a key used for FIDO U2F login for a handful of websites, because the latter is a second factor only and easier to revoke/replace.
2 replies 0 retweets 10 likesShow this thread -
Replying to @marcan42
Microsoft will happily log you in with the fido token only, and they’re pushing for this to be a standard across the web, so “only a 2nd factor” might hold true for now, but who knows for how long
2 replies 0 retweets 0 likes -
Replying to @13xforever @marcan42
What I don’t understand is why can’t all these vendors open source their firmware blobs and protocols for attestation of the device
1 reply 0 retweets 0 likes
Because the IC vendors don't let them, because it's all behind a pile of NDAs.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.