Security Token Battery Life?

[Obavijest]

i havent registered my token for fear that it would one day die and i get locked out. how would i even register a new one without a code from the dead one? o_o

[Soukyuu]

They can remove the token if you give them the code at the back of it, so running out of battery is not a problem, while physically losing it, is.

[Victor]

I've been using the same token since they were first released by SE ever back on FFXI. However many years that's been

[Laraul]

i think they should bring out an app for iphones and other phones like blizzard did with there tokens but safer and easyer to keep with u for as long as u need it.

I understand the appeal of this, this is what I do with my Blizzard account. But if you erase your iPhone or other device without unlinking it too your account it's as bad as loosing your token or phone.

I wouldn't worry about the battery life. It will last a long long time. All these fears are are unjustified about the short battery life.

[Antipika]

^ That should also explain why you have 30 seconds to enter a code, it's the tolerance of the system to prevent the token from desyncing. It also doesn't have any screws so I guess once it's dead, you need a new one.

You never had 30 seconds to enter the code, it could work even 10 minutes after on FF XI at least. (i just tried on XIV forum, worked after 4 minutes). As long as your one time password is not used within that time frame, then you can still type it. The grace period is somewhere between 10 and 15 minutes. Definitely -not- 30 seconds.

[Soukyuu]

30 seconds is what SE lists in their explanation. I know i "saved" 2-3 keys for an emergency in a txt file and they were all labeled as invalid the next day.

[Ryuko]

I don't think it's necessarily 30 seconds, or 10 minutes. Have you ever pressed the token and then pressed it again immediately after? The code is always unique, as though it follows an algorithm unique to YOUR token and will never use the same code twice.

I am in support of a phone-based app. I am so paranoid of losing my token, and despite being very careful, it has happened to me before. (I found it, but it was still a minor annoyance)... It is especially likely if you choose not to play for a few weeks. I do not believe there is a time limit for a code, even if SE says there is. The 'time limit' that is imposed by Blizzard is on the mobile app... a small bar runs out of time, and then generates a new code if you don't input it in time.

I don't think the code is necessarily generated based on time. Even the best watches sometimes fall out of speed and need to be synced. An isolated battery-operated clock inside a small plastic device isn't going to stay precise for years, and definitely not down to 30 seconds! Even computers, consoles and watches need to be adjusted every now and then. The tokens are far too cheap. I'm 99% positive that it works using an algorithm linked specifically to YOUR key.

[Coldfire]

It's probably just a list or algorithm that blocks all old codes when you enter a new one.

[Soukyuu]

I don't think it's necessarily 30 seconds, or 10 minutes. Have you ever pressed the token and then pressed it again immediately after? The code is always unique, as though it follows an algorithm unique to YOUR token and will never use the same code twice.

Actually, if you turn it off and immediately on again, you will see the old code. At least on mine.

It's probably just a list or algorithm that blocks all old codes when you enter a new one.

You'd have to save all the old codes then though, which seems unlikely to me

[Ryuko]

I believe the 'old' codes are saved on the token as well as the server. The server records it as 'used' and the token saves it as 'used' so that it never tries to use the same code again. I don't think it would take a lot of space... Let's assume you log on once a day... that's only 365 codes for one year. I'm sure the token could save thousands of codes with the smallest chip imaginable.

As far as it turning off/on with the same code... I've had it go both ways for me (give me the same code, give me a different code). I believe there is an internal timer giving you a certain amount to record down the code that was just generated, but I don't think it's timed on an external basis. Clocks fall off rhythm all the time. It just seems like a terrible thing to rely on.

The whole idea is... algorithms are hard to break, especially if someone has such a small sample size of codes to go by. So, even if someone could get a hold of a list of your old codes, I doubt they would put enough effort in to crack a person's individual algorithm.