1. This is bad. Worse than I knew... which was plenty bad already.
2.
The character-name question is not going to protect GW accounts when the NCSoft account is compromised because of the old support tickets that contain character names.
The best quick fix would be to delete all the old support tickets ASAP. Since that requires NCSoft to cooperate, it probably won't happen.
Plan B. Change the GW security question so that the user may specify ONE particular character name as the only correct answer. (Presumably everyone has an obscure character that's never been used in a support ticket.)
3.
Read #2. It's important.
4. Again, I want to call for EITHER
Let us sever our GW accounts from the NCSoft account
OR
Remove the NCSoft account's ability to reset the GW password (from the GW side).
5.
Quote:
Originally Posted by genofreek
I'm not sure how I feel about this massive exploit being highlighted and broken down on a high-traffic area of a high-traffic forum.
|
Since it's already known to the bad guys, there's not much more harm to do. If this were a first release, I'd feel a little more miffed that NCSoft wasn't given a private warning first. Since the info has already been available for 4 months elsewhere, I'm not terribly upset.
Hopefully the knowledge that ANYONE can now hack any account, might pressure NCSoft into finally acting.
6.
Quote:
Originally Posted by zwei2stein
I do not want to sound like an anet defender, but can anyone confirm this? I mean, anyone trustworthy (say, guru regular?) can confirm that he did manage to log in to someone else plaync by chance?
|
Perhaps not a regular, but not a brand new Guru account either:
Quote:
Originally Posted by niek2004
After about 60 tries I logged into someone else's account. Too bad it didnt have guildwars.
|
Quote:
Originally Posted by zwei2stein
Because I am not aware of technology that would allow this. I can not even concieve bug where someone would randomly end getting logged to another account ... there is just no magical code fairy that could sometimes, randomly, say "nah, lets log him to completelly random different account".
|
Here's one possibility: Improper pointer to a memory address that is not properly allocated and preserved for the duration of the pointer. When the number indexing that account in the database is calculated, it gets stored at that address. Then the memory gets released. Then the pointer comes by and references it. If the system doesn't happen to reuse that memory address for anything in the meantime, the correct value is still there, and the pointer returns the correct value exactly as planned. If the system has reused it, the value is essentially random, and the pointer returns a random value. Hard bug to catch and fix, since sometimes -- even usually -- it works just fine, and the condition that triggers incorrect behavior is wholly external to the program or its inputs.
I'm sure there's thousands of other programming errors that could produce a similar result. That's just the one that came to my mind.
Quote:
Originally Posted by YunSooJin
I know the guru population isnt exactly made up of adult professionals, but is there anyone well-versed in context of the law who can comment on this?
Possible that there can be class-action type lawsuits?
|
More jurisdictions than you can count, more legal frameworks than you can count. Some jurisdictions consider the EULA a binding addition to your purchase agreement. Some jurisdictions consider the EULA mere toilet paper. All jurisdictions are going to have trouble quantifying players' losses. Did you lose the purchase price of the game? The e-bay value of your best items? Some sort of emotional harm? It's a relatively new issue, and courts are universally bad at dealing with new issues. My guess is that the most favorable jurisdiction to try something like would be somewhere in the EU. And that's out of my area of expertise.
Well, I guess I have one more thought to add: You'll never get a judge or jury to understand how accounts are getting hacked and how exactly that fails to live up to the level of care a reasonable and prudent game company would use. But, "you knew there was a big hole in your security and you just sat there and denied it while doing nothing to fix it" is something that everyone understands. As is often the case, the coverup is more damning than the negligence.