Phat Looser

This would be for the MTA team then: http://wolffiles.de/index.php?forum-showposts-20 : The problem they solved it was to only answer those requests once per 4 seconds. Else, it seems that you already checked your connections (vnstat -l), didn't you? It would be interesting how much DDoS affects the map download.

Adding a resource as admin is always a good idea. Enable "function.callRemote" in your default, or add a special ACL for that resource (thats what I did).

This is the server section, but it seems its a client side problem here. Yes, install the newest drivers.

WARNING! You are trying to run the server as root, don't! Get your own user for MTA and replace the "root" in the following lines with that username! chown -R root:root * chmod u+x mta-server

apt-get install screen screen -S $SCREEN_NAME -d -m $GAME_PATH$SERVER_FILE Your server runs in a virtual console now. Re-attach to that console with screen -r $SCREEN_NAME get out of it with ctrl+D A Send commands to it with screen -D -r $SCREEN_NAME -p 0 -X stuff "$COMMAND"`echo -ne '\015'` original author: Dragonshadow (for minecraft, don't wanna be stealing the last line of code) sorry to say it that bluntly, but nohub doesn't let you control your servers rite.

I must be blind, since I cannot see the "shutdown" part.

Issue not closed. I tried a bit, and found out that a few servers are prone to this problem. Most of them non-"professional", of course, but hacking a server is a bad habit. I think we should think of a way to explain the ACL better.

Its the "spawn" script. Just remove that "while(not playerspawn)" thingy.

Stealth was upgraded and has minimodes now, Normal, VIP and WALLHACK(Teamdeathmatch-style). You can respawn in VIP and WALLHACK mode, unless of course you are the VIP.

1) get a car 2) tune it with NOS 3) get a stopwatch 4) trigger the nitro 5) write down the time 6) create another bar in the "race" resource 7) set this bar to "1" if the car has nitro, else don't if the car has nitro and "fire" is pressed, activate a timer which triggers each 200 ms and reduces the bar (1-(maxNitroTime - timercalls*200)/maxNitroTime) 9) if (maxNitroTime - timercalls*200) <= 0 then set the bar to 0 10) if another nitro is ready (measure that time, too maybe) or a nitro was picked up, set the bar to 1 again 11) ??? 12) PROFIT

outputChatBox("Mode test");

By "no real administrator" I mean: I need to run stuff with elevated rights before it has admin access. When I auto-update MTA it doesn't start elevated, so I need to stop it and start it again. An account named "administrator" does not exist, and there is only one account, which happens to be "Adolf". But to start administrative tasks on that account, I need to accept the Windows-Sudo-Window A.K.A "Benutzerkontensteuerung". Nuff said: 1) there is only one account. 2) this account CAN have admin rights, but without right elevation I can't do shit. 2.1) MTA can be installed on that account with elevated rights. The Auto-Updater doesn't elevate. 3) MTA does not start with elevated rights, finds out it can't do shit and asks me for a different account, even though the one account is already registered as admin. It doesn't even try to elevate.

Its Windows 7's "run as" window, and the account is no administrator, also, there is no real administrator account on that computer.

Thats what I was talking about. If I choose "STAUDE\Adolf", it doesn't work, and there is no "administrator" on my gamer laptop (why should I have one?)

Actually its the server admin's fault. Putting all resources on admin is a very, very bad idea.

Currently I am trying to analyze what was going on, but it wasn't a malformed packet for sure. Looking through the "runcode" resource I managed to find stuff that explains a LOT.

Were you able to find out how they did it, so that they can't do it again?

Another one is reporting crashes: #0 0xf7480d7f in raise () from /lib32/libc.so.6 #1 0xf7482788 in abort () from /lib32/libc.so.6 #2 0xf74bd6f5 in ?? () from /lib32/libc.so.6 #3 0x0000002e in ?? () #4 0xf2443e84 in ?? () #5 0x00000400 in ?? () #6 0xf0900000 in ?? () #7 0xf75a3ff4 in ?? () from /lib32/libc.so.6 #8 0xf758acf8 in ?? () from /lib32/libc.so.6 #9 0x00000017 in ?? () #10 0xff84fb20 in ?? () #11 0x00000031 in ?? () #12 0xf758ad11 in ?? () from /lib32/libc.so.6 #13 0x00000002 in ?? () #14 0xf758add0 in ?? () from /lib32/libc.so.6 #15 0x0000001f in ?? () #16 0xf758ad15 in ?? () from /lib32/libc.so.6 #17 0x00000004 in ?? () #18 0xf24443b3 in ?? () #19 0x00000008 in ?? () #20 0xf758ad1b in ?? () from /lib32/libc.so.6 #21 0x00000005 in ?? () #22 0x0ac023c0 in ?? () I dunno, but it COULD be someone is shutting down his server, so I don't know if its an MTA bug. Only thing I know that his logfile is 1.8 GB of scripting errors. €dit: It happens over and over, even though I blocked the contact to that server. It seems the mass of "illegal object" errors it throws crashes the server over and over, always with the same error (above). I'll force the scripts deactivated and I'll restart the server. #0 0xf746bd7f in raise () from /lib32/libc.so.6 #1 0xf746d788 in abort () from /lib32/libc.so.6 #2 0xf74a86f5 in ?? () from /lib32/libc.so.6 #3 0x00000030 in ?? () #4 0xf1efde84 in ?? () #5 0x00000400 in ?? () #6 0x00000031 in ?? () #7 0x0a5e8ab0 in ?? () #8 0xf7575cf8 in ?? () from /lib32/libc.so.6 #9 0x00000017 in ?? () #10 0xfffcab20 in ?? () #11 0x00000031 in ?? () #12 0xf7575d11 in ?? () from /lib32/libc.so.6 #13 0x00000002 in ?? () #14 0xf7575dd0 in ?? () from /lib32/libc.so.6 #15 0x0000001f in ?? () #16 0xf7575d15 in ?? () from /lib32/libc.so.6 #17 0x00000004 in ?? () #18 0xf1efe3b3 in ?? () #19 0x00000008 in ?? () #20 0xf7575d1b in ?? () from /lib32/libc.so.6 #21 0x00000005 in ?? () #22 0x0a6accf0 in ?? () Its a "sigabort" that was sent. If its a bug, I'll make it a mantis report. €dit2: Its a bug. Not a feature.

Yes, in "play" one of the scriptlines can cause an endless loop.

The hackers gained admin rights on that server and messed with the ACL, from what I've heard.

I don't get whats going on, maybe you should explain. For everyone.

First off, I switched from nohub to screen and I like it better, since I can open the console now. Second, there was something like "gdb". It is used for debugging a program and can give back the crash reason. Third, there is different kinds of "crashing". Normally when the server crashes, the system ends the process and thats it. If the server goes to 100% on (only one) core, it could be that one of your scripts loops endlessly (then it should stop after 30 seconds afaik).

There is several things you need to know about MTA. 1) Don't bother with scripting an anti-cheat. I have made one about 2 years ago, and disabled it step by step since MTA's anticheat made it obsolete. 2) If somebody actually manages to be banned, a serial ban will ban his hardware. It is hard to avoid the serial ban, and up to now I haven't had the time to crack it. If I would be able to crack it I'd tell the developers 3) It was some time ago you were able to detect even s0beit with scripts only. This is not necessairy any more, but it shows how powerful MTA's scripts are. 4) Every time a new MTA version is out, I am trying to crash the server or to find an exploit. There were bugs, of course, but I know of no security-relevant exploits or crashes.

Did you try the description how to get the mta-server running on debian lenny? It seems you didn't install the 32 bit libraries.

Its a problem to make it go alive again. Looking at it: as soon as a normal player joins stealth he is bashed to death by elite players who already waited for someone to join the game. Result: Insta-Ragequit.