Serbot - Badass

Commits

1. https://github.com/dotcppfile/Serbot/commit/806e4a4987cb7e8c72844b577fbe24707ee21e60 2. https://github.com/dotcppfile/Serbot/commit/180e85f66dec6ea66885dd225f0189937400a22c

Updates

1. Backdooring. Now this is what matters the most in this Update because in linux, creating a service or running something on startup for all users requires root privileges, now you can always work it around by editing .xinitrc or .bashrc or whatever but this is related to the current user only and it doesn't always work so screw it. Since Serbot is mostly used on Servers that web hosts, its backdooring fuction will identify every PHP page in the Web Directory, infect them all with Malicious Code that can bypass most WAFs and Protection Systems like Suhosin, now, the Malicious Code checks wither the Serbot client is running or not and if it's not then it will go ahead and start it again, as simple as that. This simple technique will make sure that you'll never lose your Serbot Client even if the Main Server Restarts since any Web Visitor will get it up and running again. 2. Self updating has been added; if you send the `selfupdateall` command then all your clients will create a random `.py` file that will download the new `Client.py` from Github, kill the current running Serbot Client, edit its code and run it again. 3. One liners, this is your happy day Lol. Serbot now handles all commands more properly; a command like "mkdir whatever; cd whatever" will work perfectly. 4. You can now simply identify the source of the Message you receive by looking at the keywords: [SERVER], [CLIENT] and [CONTROLLER]. 5. The Flooders now use 20 threads instead of 10. 6. A lot of bug fixes. 7. A Serbot Client is now only meant to run on Linux servers.

Serbot - 12/24/2014

Change Log:

1. Commands/Subprocesses have now a 30 seconds timeout. (This is a must because commands like 'ping google.com' have no timeout which will get the client stuck.)
2. Server now logs Errors in 'serbot-logs.txt'