1. At least ban the account which took the LGG and bought things with. That's how I see it. This combines with 2. as well. At least banning the account in question would be enough. Even if he came back, oh well. People do that. But you should at least rid of damages in question, even if they are small, it still looks as if users can take advantage of a mistake, and cause harm with it.
3. Indeed, so do you. Flareboy may have made this mistake, but regardless, the user could have have self control to warn Flare about it. But even if he didn't, sure he tried the password. I admit, whuldn't at least try it? It takes an active thought to cause harm, such as stealing the LGG on Flare's account. Flare should take it as a lesson, we all make mistakes. But Bunneyz should, honestly, have this current account perm banned. If he so chooses to come back, that's on him, you can't really stop someone persistent. But you do have to lie down controls. The account in question, bunneyz, should honestly be banned, mainly because it's the account that has benefited from the issue.
One could bring up the argument "We can just reverse the transactions and gain."
But why would you create more overhead for your staff, that was caused by the malicious intent of a uses? Especially when they had the audacity to post about it, bragging of their chao items afterwards?
Results 1 to 29 of 29
Thread: ARE YOU KIDDING ME?!?/21
Hybrid View
- 02 Jul. 2013 07:04pm #1You can't capture what this kid spits with kismet
each packet i send is encrypted with 3DES
And I'll keep flowin til the light goes off
you get a virus-cough, you kids are microsoft
And I'm hard like openbsd internals
excuse me, I need to make a call to the kernel
- 02 Jul. 2013 07:33pm #2
- 02 Jul. 2013 07:57pm #3You can't capture what this kid spits with kismet
each packet i send is encrypted with 3DES
And I'll keep flowin til the light goes off
you get a virus-cough, you kids are microsoft
And I'm hard like openbsd internals
excuse me, I need to make a call to the kernel