Also on AOL
- Autos
- Technology
- Lifestyle
- Gaming
- Finance
- Entertainment on AOL
- Lifestyle on AOL
- Sports on AOL
- Travel on AOL
- More on AOL
Featured Galleries
Joystiq
© 2013 AOL Inc. All rights Reserved. Privacy Policy | Terms of Use | Trademarks | AOL A-Z HELP | About Our Ads

Reader Comments (Page 1 of 1)
2-09-2010 @ 3:21AM
Anjelle said...
"The code from the Authenticator is based off of the serial number of the device or app and a date/time stamp. Because of this, a code is only good for about 30 seconds."
That statement is 100% incorrect.
The authenticator app for iPhone MIGHT have a time limit, but I kind of doubt it. The original little keychain authenticator does NOT have a 30 second time limit, or any time limit, for that matter. Think about it.. it isn't connected to anything for Blizzard to know when a # was generated. The iPhone app is, but the original isn't. ;)
I have had more than a couple of experiences where I had to use a code that was generated from my keychain authenticator long after the so-called 30-second limit.
NOW, with that said... I have not tried to remove an authenticator. It is quite possible that yes, codes go in a certain order and one would need a certain number of them in sequential order in order to remove it. And THAT is where a 30-second Time Out may be in place.. to enter them within 30-seconds of each other.
Reply
2-09-2010 @ 4:12AM
Skrotus said...
The codes aren't just generated when you press the button, there is a new code every 30 seconds for the lifetime of the device, Blizzard has all these codes and the times they'll be active from when the device was activated.
The statement was in fact entirely correct, the bank security tokens work exactly the same way.
2-09-2010 @ 4:18AM
Aggrajag said...
@Anjelle "That statement is 100% incorrect"
That statement is 100% incorrect.