Only someone falsely using his name/password could explain that, but then the IPA would tell the truth.
Quote from: Ax2Grind on November 07, 2008, 01:20:22 PMOnly someone falsely using his name/password could explain that, but then the IPA would tell the truth.Unfortunately, the admin.log file provided by the old versions of jumpmod was utterly useless. No IP information, hardly any commands even logged at all, the commands that were logged showed the player name but not the actual admin account name that was being used by the player, etc. Just abjectly abysmally unhelpful for doing any kind of forensic detective work.Thankfully, Lohmatiy has improved the admin.log in the recent jumpmod builds he's provided us. As we discovered the other day, there are unfortunately still a number of admin commands that do not get logged at all. But it's better than it used to be, and at least now, for the commands that are logged, we get, player name, admin account name, and IP.Regards,
Yo kingy, that's the reason why I am trusted: Lohmatiy: If I ever wanted, I would easily get the server down just by using one of the bugsLohmatiy: or get a 15 lvl accessDo I need to point out the word "wanted"? The ts and wp (and crikey and whatever runs 1.07 and higher) servers are still running and everything goes fine, what's your problem there?
I only wish I had condumped the conversation with Lohmatiy when he first started coming to jump and was explaining his attitude towards hacking. It went something along the lines of: "I love hacking. I see it as a personal challenge between me and the admins."
Now he gets to see all of our IP's
As far as I know, jumpmod admins don't have privileges to see IPs on our server. (If I'm incorrect, someone please correct me.)
I would also add that it would seem preferrable to fix them, hadn't it been for the architecture of Q2 itself: none of the bugs I'm aware of, are just malformed commands or whatever, all of them are actually multiple-step attacks (oh well, I will not desribe those anywhere).