3 ms·
This essentially turns "something you know" into "something you have", with no requirements that any of the remote websites change what they are doing. It seem
by jerf 13y ago
This essentially turns "something you know" into "something you have", with no requirements that any of the remote websites change what they are doing.
It seems like this is an interesting counter to the recent budding trend of arguing that "something you know" (passwords) is broken and we should all throw it out and switch to "something you have". This shows that a user can unilaterally convert "something you know" into "something you have", and unlike the inevitable clusterfuck of trying to standardize on "something you know" with the inevitable gold rush of competing, fragmented standards, resulting in users having to have an unbounded number of "things" in their possesion [1], authentication consumers can continue to work with standardized password approaches.
It seems to me that rather than rewriting the Internet to not use passwords, we'd be better off making this approach even easier (although it's not all that hard right now, really).
[1]: Yes, I'm aware of things like RFC 4226. History's pretty clear though; if there was more value to capture in this space it would break into proprietary fragments in a heartbeat. All the proprietary fragments would probably be beaten down by RFC 4226 in the end, but there would be an unhappy few years in the middle.
- apazzolini 13y agoI think you missed the part where he's not combining something he has (the Yubikey, which stores part of his password) with something he knows (the other part of his password). He needs both to log in.
- mapgrep 13y ago>This essentially turns "something you know" into "something you have" It really doesn't. This essence of "something you have" is that you really, truly must have it for authentication to work -- every time. In this case, if you capture the data on the Yubikey once you never need to have the Yubikey again (since he's using the static slot). Or to flip it around, if you just once leave your Yubikey in your pocket in coat check, or in a checked airline bag, or in your USB slot when you go to a meeting, etc., it is potentially 100% compromised without your ever knowing. This is why true "something you have" systems like Google Authenticator, or the actual Yubikey system as it was designed, use constantly changing keys.
- dpeck 13y agoIt really doesn't change it into something you have, it simply gives the user and anyone compromising them via keylogger, slipping yubikey into their own system and pressing button, etc a way to avoid typing. Something you have exists in the form of things like smartcards. Crypto stick, https://www.crypto-stick.com/ https://www.crypto-stick.com/, being a great and user friendly example of.