[Whosat]

Thanks ghosty!

[ducky93]

I was doing some testing and found a few commands you may not know of to lag/crash a server.

groundlist
report_entities
ListServerUserMessages

Hope this helps

[thetwistedpanda]

Originally Posted by ducky93 I was doing some testing and found a few commands you may not know of to lag/crash a server. groundlist report_entities ListServerUserMessages Hope this helps

Only groundlist is something to be worried about; the other two not so much. report_entities shouldn't function unless sv_cheats is on, and listserverusermessage doesn't seem to affect any cpu/server load.

[johns3]

I have just put the rcon locker on my server. However, the hacker still managed to introduce "Client dropped" error, whereby, nobody can join the server after the "Client dropped" message appeared. Can anyone advice any counter for this?

[SooStoked]

Thanks
good stuff

[Hollanda]

sourcebans integration would be welcome!

[devicenull]

Originally Posted by Hollanda sourcebans integration would be welcome!

I can't tell with 100% certainty that some of these things are on purpose. Some can possibly occur accidentally, and I'd rather have someone kicked from the server rather then being banned forever or w/e. If you want to ban people like that, all the exploits are logged to the SourceMod logs, so it should be trivial to grab people's info from those.

[Hollanda]

Originally Posted by devicenull I can't tell with 100% certainty that some of these things are on purpose. Some can possibly occur accidentally, and I'd rather have someone kicked from the server rather then being banned forever or w/e. If you want to ban people like that, all the exploits are logged to the SourceMod logs, so it should be trivial to grab people's info from those.

L 09/18/2009 - 16:234: rcon from "82.168.99.148:21898": Bad Password L 09/18/2009 - 16:234: rcon from "82.168.99.148:21898": Bad Password L 09/18/2009 - 16:23:48: rcon from "unknown": Bad Password L 09/18/2009 - 16:23:51: rcon from "unknown": Bad Password L 09/18/2009 - 16:23:51: rcon from "unknown": Bad Password L 09/18/2009 - 16:23:53: rcon from "unknown": Bad Password L 09/18/2009 - 16:23:53: rcon from "unknown": Bad Password L 09/18/2009 - 16:23:54: rcon from "unknown": Bad Password L 09/18/2009 - 16:23:54: rcon from "unknown": Bad Password L 09/18/2009 - 16:23:55: rcon from "unknown": Bad Password L 09/18/2009 - 16:23:55: rcon from "unknown": Bad Password L 09/18/2009 - 16:23:56: rcon from "unknown": Bad Password

At the above example the server crashed about every 2 rounds.

Running multiple servers it's not easy to check all logs...

Some exploits like above, I think, are obvious enough to ban into sourcebans?

[toString]

13:40:39 L 09/22/2009 - 13:42:01: [SM] Native "RegConsoleCmd" reported: Cannot override "sm" command
13:40:39 L 09/22/2009 - 13:42:01: [SM] Displaying call stack trace for plugin "rcon_lock.smx":
13:40:39 L 09/22/2009 - 13:42:01: [SM]   [0]  Line 95, /home/groups/alliedmodders/forums/files/7/2/43224.attach::OnPluginStart()

Is this not supported in 1.3.0?

sourcemod-1.3.0-hg2805

[devicenull]

Originally Posted by Hollanda At the above example the server crashed about every 2 rounds. Running multiple servers it's not easy to check all logs... Some exploits like above, I think, are obvious enough to ban into sourcebans?

That exploit can't be fixed from a sourcemod plugin. Nor will banning the user's steamid/ip have any real effect. You would need to add firewall rules to prevent this.