Printable View
The only thing I see changing is the amount of time we have to spend putting in authenticator codes. If you observe the history of wow account hackers, you will see that they always find a way around the security measures that blizzard puts in place.
For me this is a good thing. Because of this I gonna protect my other Battle.net too with a authenticator. (Yes I am a lazy person and hate to type the security code over and over again)
I stopped using the authenticator when they made the codes single use - I'm not going to spend 2.5m every time I want to log in.
This change is great for us multiboxers and I've slapped the hardware authenticator back onto my battle.net account.
I was asked for my code on the first login, Friday morning, then not again all day Friday and Saturday.
I played this morning and then happened to update my ATI graphics drivers (11.6 gives a definite FPS boost for me!) and my next login requested the code, so it's obviously doing some sort of hardware/software configuration check, which is nice.
Quote:
Originally Posted by moog
Actually, no it isn't. I have logged into my accounts from 4 completely different machines in my household and the last time it asked for a code was on Friday. The only thing in common is the router and cable modem. I imagine the next time I am asked for a code will be when my dynamic IP is refreshed with the service provider, but that is only a guess.
I kind of like not having to put in my code for every single little disconnect that I have, but it doesn't make me feel as safe as putting in a code every single time.
Better avoid playing playing from a cyber café then (I know this not something really recommended but many people do this thinking their authenticator adds an additional security layer, I hope Blizzard communicates clearly about this situation).
I haven't been asked to enter any authenticator code since last Friday even when I logged to the battle.net website. As my IP address is supposed to be fixed, I'm curious to know how long I'll be exempted from having to use my authenticator ...
Lax, you're right my argument about the man-in-the-middle attack using a tunnel isn't really valid.
I travel alot and thus play from different locations, sometimes as many as 12 in a month. There are times when I get the "Your account has been locked due to suspicious activity" and I have thru go process of waiting on the email exchange of verifying my info and changing passwords. This is a pain in the ass when trying to box on the road.
Other times it just asks for my authenticator code and I'm on my way.
My issue here is that I DO use the mobile authenticator, yet even after entering the proper code I still have to do the email thing sometimes.
I think I'll like this new system when playing from my home PC :)
I posted my comment to blizzard on the thread number 4, page 19 or something like that.
Basically, I sided with another user who stated, all be it, the authenticator isnt a 100% guarantee, it is a measurable protection that some of us are used to. Even if it is intelligent now, the lack of doing it, is at a minimum, kicking in placebo. A simple solution would be, as the "connecting" "success" "authentication" splash screens are being flashed, throw up the number being used just under the word "authenticating".
At least then I feel better knowing this security measure is still being used, even if it isnt. (conspiracy?)
Dunno. Im a creature of habit and rules. This change, is poorly explained IMO, and poorly executed. As a consumer, I need to feel better about this.
They should just make this change optional.
For most people, like me, who don't play at any other location outside of their home where no one else plays WoW, it's awesome. I can login in about a third of the time.
However, I understand, especially in this community how much people travel for work/business, school, etc and how being able to login with out the authenticator at those locations would be a scary situation.
Only time will tell. I'm sure if enough people get screwed over by this they will revert it. I do see how it could be an issue, but for my own greediness, I love the change.
Unless the new method is equal to, or exceeds, the authenticator in security, it should be optional.
I bet if it were optional, half the people that are currently saying they don't like it would eventually try and stick with it. They just don't like being forced.
- Souca -
When I run my wow traffic through a proxy as expected I get prompted for my authenticator key, but not again until I change proxy servers, or disconnect from the proxy.
Some testing I did:
If I login from my home network first time I get prompted for a key.
Any other logins are straight logins no key required.
Switch to a proxy first time I get prompted for a key.
Any other logins are straight logins no key required.
Disconnect the proxy.
Sign in from home network... I get prompted for a key.
I think blizzard is caching last authenticated IP. Similar to the dialup authenticator. I could be way off, but above is what I did to make me conclude this.