The bitter Truth

[Zodiac]

i gave them a full description some time ago. The answer was that the acc, i send the reported from, was immediately banned.

I got the hint, and i will contact the gms never again. Dont wont to another banned acc.

-.- Just like them to take a helping hand and punish him for trying to get them to realize the error in there own security oi.....

[iDerrick]

-.- Just like them to take a helping hand and punish him for trying to get them to realize the error in there own security oi.....

Seriously.

@MaxOff: But in any case, what you did was still wrong, and how the GMs saw it, even if it was for good intentions.

[MaxOff]

I tried the nice way, and got rejected. So i waited to see if they would fix it non the less. They did not. So im showing the public what was ignored.

My only aim is to see that something like that will not be possible anymore.

[Laifun]

SedaLia.. i recognise that name.. I was reading and hoping my name didn't pop up D:

[Hyper]

SedaLia.. i recognise that name.. I was reading and hoping my name didn't pop up D:

LOL me too. >.>;;

[NotMyWay]

I still think you should not disconnect players who might be afk vending or trying to get titles which require them to remain online for long periods of time...

[MaxOff]

the timeframe was 2minutes, and the ticker was that the person logged into a server. So the chance being on that list is really low.

[AngellicDiety]

There was a security researcher, Antonio or someone whose name started with "A". He posts up all security related flawes on the internet. He emails the affected companies with the site, and tells them they need to correct it.

Otherwise the method is completely public. Perhaps a similar stance may help you?

Although many people here would yell at me for proposing such a thing, this security researcher proved it works.

Companies are a little more complaint when the method is out in the open, and your telling them to fix it.

[Hessah]

Well if u're really considering to post it out in public.. ithink u should 1st wait and see if Outspark is planning to do anything about it..

have u worked out a way to stop this weakness?? have u told outspark wat they could possibly do? if u dont hv a solution for the problem u should wait longer

i personally dont recommend u (obviously) to post it in public coz that'll just ruin the whole thing for everyone... as it will be more than likely land in MANY bad hands...

a problem could probably be fixed without making it worst for everyone... it'll be very much appreciated if u dont take the dangerous approach.

just because one method "works" doesnt mean its the best way to deal with the problem.