0 użytkowników i 1 Gość przegląda ten wątek.
The only communication has been through the MOTD.It said something about an emergency shut-down of the SQL server.
<&Sharkbait> one of the db admins got hit with keylogger<&Sharkbait> used an authorized account to shift spawn tables by one row<&Sharkbait> meta 6 gear was being dropped from standard spawns of the affected npc group<&Sharkbait> maintenance pruning returned 6539 officer items on one account, so the servers were shut down, forums are integrated and are also shut down<&Sharkbait> not that long, we have full weekly backups<&Sharkbait> unfortunately tracing all damage done manually is impossible, we have no tools designed to read transactions when the db itself is skewed<&Sharkbait> yes, no billing or account status was affected, thats part of the billing dept
Najlepsze, co znalazłem, to info na IRC-u.Serwer: irc.coldfront.netKanal: #eve-announce
Chyba przeoczyłem ten wpis wcześniej.O co chodzi z tą 'Karmą' mam + i - przy Twojej
At 10:25 GMT today we discovered an anomaly in the EVE Online Database indicating a potential exploit. Our policy in such cases is to mobilize a taskforce of internal and external experts to evaluate the situation. At 12:57 that group concluded that our best course of action was to go completely dark while an exhaustive scan of our entire infrastructure was executed.What we discovered was an indication that one of our databases was being accessed through a security breach. While some may feel that such a drastic reaction was not warranted, it is always our approach to err on the side of caution in order to protect the players.We of course understand the effect and disruption this has had for our players and apologize for not having been able to explain to the community what was going on. In these cases it can often be counterproductive to containment to give out information while we are in the process of evaluating the scope of the problem. Our taskforce quickly found the security breach and prevented that from being used. We subsequently found three cases of database actions being performed through the security breach but none of those affected other users than the one doing the actions. We can also confirm that no personal details such as users’ credentials or credit card numbers were exposed through this incident.The servers were brought back online at 22:00 GMT and we will of course continue to monitor the situation closely over the weekend and the following week. Again we sincerely apologize for this disruption.
