Heads up multiboxers. Authenticator change incoming.

[Lindline]

To help keep Battle.net accounts as secure as possible, we've recently changed how Battle.net authenticators can be used. Going forward, Battle.net authenticators can now only be associated with one Battle.net account at a time. No changes are being made to how many game licenses a single Battle.net account can support. You can still have multiple World of Warcraft accounts under a single Battle.net account, for instance, and all game licenses linked with a Battle.net account will still be protected if an authenticator is in use.

Those of you who currently have more than one Battle.net account associated with a single authenticator will be able to maintain your existing setup without needing to do anything. This change will only affect new authenticator attachments. But, if at some point you decide to detach the authenticator from any of your Battle.net accounts for any reason, you won't be able to reattach it if it's already associated with another Battle.net account.

http://us.battle.net/sc2/en/blog/882513

Just be aware if you're adding Bnet accounts under your wing or if you make changes to which Bnet accounts you have authenticators on.

[ebony]

am going to kill em!

[Tim]

Silly Blizzard, yet again making changes that deteriorate the game without a justifiable reason.

[Ualaa]

Hopefully the battery in the authenticator lasts a long time then. Kind of sucks, to have a delay (for a new code) after one account enters, before you can enter a new code for another account.

Not a huge deal really, but 2 extra minutes for log in... is nice to avoid.

Once the change goes into effect, there won't be an advantage for having a single warcraft game on each battle net account. At that point, five boxers might as well amalgamate their accounts onto a single battle.net.


*Edit*
It's a slight security upgrade; as a hacker cannot use your current valid authenticator code, for another of your accounts which is not simultaneously being logged in, during that 30 second window.

Either that, or a rather slight cash grab.

[ebony]

Originally Posted by Ualaa

Once the change goes into effect, there won't be an advantage for having a single warcraft game on each battle net account. At that point, five boxers might as well amalgamate their accounts onto a single battle.net.

one PTR & beta

[Lindline]

Originally Posted by Tim

Silly Blizzard, yet again making changes that deteriorate the game without a justifiable reason.

You mean besides the fact that accounts were being compromised by someone adding a single authenticator to an unlimited number of accounts? Its actually been a known issue for a long while. I'm surprised that it took this long for them to make the change.

[ebony]

Originally Posted by Lindline

You mean besides the fact that accounts were being compromised by someone adding a single authenticator to an unlimited number of accounts? Its actually been a known issue for a long while. I'm surprised that it took this long for them to make the change.

ya this is ture you got hacked they was adding a authenticator they fixed that though by sending a email before you can add one but that must of not worked they know we do it like this even when i phoned up they said is it to login in the same code.

when i changed i changed i lost a pet that was B.net wide so might change back but i do like dualboxing on ptr/beta so not sure what am doing am ok as long as my keyfod does not die if it does then ill have to older 5

[EaTCarbS]

Thanks for the inconvenience blizz. Might have to downsize to 2 b.net accounts.

[Kalyse]

I would be really annoyed if you created all your accounts accross multiple BNets.

I would message Blizzard and ask them to merge the accounts cause you are now just under a big inconvenience, and they have changed thigns.

[Tim]

Originally Posted by Lindline

You mean besides the fact that accounts were being compromised by someone adding a single authenticator to an unlimited number of accounts? Its actually been a known issue for a long while. I'm surprised that it took this long for them to make the change.

Actually that is not a valid reason for this change. If an authenticator code is being used on compromised accounts, Blizzard simply has to add the auth key's code to what is called a Token Revocation List. This makes that authenticator completely invalid and will not function again.

So it simply becomes standard operating procedure. Upon ruling that an account was compromised with an auth code that was attached to it, remove the auth key and add it to the revocation list.

This is a super basic concept that is over SIX DECADES old and yet Blizzard can't get a handle on how token-based authentication for two factor security works? Ugg....