![]() ![]() In that second link this was posted (not by a blue). Just did a quick search on forums found these 2 posts also Something broke, or someone changed something to no longer allow this. You could be right, but the issue here is this WAS working. Where as when the accounts were seperate they got a single FOB time of Day Update on each account accross your Five acounts, and then they where keeping up a seperate Drift calculation on each account. The drift calculation may not like Zero time difference from the last log on. I am thinking that when you log into one Battle.NET account 5 times, it does not like five different FOB time of Day updates in a row with the same TOD, and rejects them. On the Servers they are keeping up with the drift from real time for each Fob on each account in their system, other wise your FOB would stop working when the internal clock drifted too far off real time. When the servers decript the code they get the Time of Day on your Fob. I suspect it is the Time of Day tracking on the Server side that is issue. (there is probably also some tracking server side for the previous and next valid numbers to account for the timebase drift that likely happens on the keychain unit, since it is bound to be significant and would vary with temperature and such) Pushing the button just causes the Display to turn on, the code that is displayed is an encription of the Time of Day (likely rounded to 30 sec) and the Fob serial number. I have a similar unit to this for my etrade account and it does't bother with the button, it just always shows the current valid number, and a little countdown bar showing how much longer until it changes. ![]() They could make both sides change numbers more frequently, but then you would have less time to type in the correct number before it expires. Since the server has no way of knowing if you pressed the button, there is no way it can be made to accept a different number until the 30 seconds go by and it moves on to the next one. This key is valid for a try made in that 30 second block and is based on the authenticator serial number and the time/day plus some other constant numbers no one else is likely to know. The way (i'm fairly sure) the authentication works is that the keychain unit and the auth server create a new valid agreed upon key every 30 seconds. The move to a proper one-time key is a Good Thing, but to make it more bearable for us, they really do need to improve the authenticator to generate a new code every time it's cycled! until you get all of your accounts logged in.Īnyone else experiencing this with their account + blizzard authenticator this evening? ![]() This means you can no longer log in all five (or 10) at the same time, but now must log in one, wait for about 8 seconds for the authenticator key to generate a new number, then log in the next, etc. After some experimentation it is revealed that EACH individual login instance now requires its OWN DIFFERENT authenticator number (not the physical key, but the numbers it generates). Tonight, after the login servers became "unbusy", now only one specific account is logged in, the other four fail with a message something like "account credentials failed". This has worked flawlessly for a long time now. After that I'm logged in on all five simultaneously. I use keyclone, and have it set up (with workaround) to enter my account info, and the specific individual accounts are saved from the last usage, so all I have to do is enter my password, and then enter my blizzard authenticator key at the next prompt. After they became available again, I was unable to log in my normal way. ![]() Login servers were "busy" for a short bit this evening. So, anyone else seeing this behavior starting this evening? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |