I will be VERY interested to see how Blizzard handles this. Although they're more using tokens to avoid keylogger attacks than any sort of real physical security.
It's unlikely they'll do anything, as the one that Blizzard uses works differently. It's just a time-sensitive generated number code, not a communications cypher.
If they get *physical* access to the token generator, they have compromised it because at that point all they need to do is write down the serial # on the back of it and they have the key.
The code generation code is well known for the authenticator that is used by blizzard. Given a devices serial # and a reasonably accurate idea of what time it is, generate a key to hand to the server to prove whom you are.
The whole point of the blizzard authenticator is to require a physical object, in this case the authenticator, to prove whom you are. Nothing more, nothing less. The RSA device serves a completely different purpose.
The real problem is that given physical access to a security device, you are not *guaranteed* of it's security anymore.
(no subject)
Date: 2012-06-28 05:33 am (UTC)(no subject)
Date: 2012-06-28 06:24 am (UTC)(no subject)
Date: 2012-06-28 11:53 am (UTC)(no subject)
Date: 2012-06-28 12:11 pm (UTC)(no subject)
Date: 2012-06-28 06:50 pm (UTC)(no subject)
Date: 2012-06-28 07:43 pm (UTC)The code generation code is well known for the authenticator that is used by blizzard. Given a devices serial # and a reasonably accurate idea of what time it is, generate a key to hand to the server to prove whom you are.
The whole point of the blizzard authenticator is to require a physical object, in this case the authenticator, to prove whom you are. Nothing more, nothing less. The RSA device serves a completely different purpose.
The real problem is that given physical access to a security device, you are not *guaranteed* of it's security anymore.
(no subject)
Date: 2012-06-29 03:59 am (UTC)Blizzard's authenticator is from Vasco.