Scripts Policy and Banned Scripts
Unfortunately, many good things are turned on us to be used for nefarious activities. Commonly used open source webscripts are frequently exploited to allow unauthorized access to the systems they are running on. Others just require more resources than is allocated on a shared server environment.
Consequently, in order to keep the Tedoc network and servers safe and reliable, we may need to take actions that inconvenience our good customers. Any time we find scripts or other commonly used tools that can become easily compromised or impact other users by using too many server resources, we may need to disable scripts or other tools installed and used by our customers.
Whenever possible, we will notify our customers in advance. We will also attempt to keep this page updated with current scripts which will require removal from our shared servers and/or our network.
However you should bear following in mind: You as the user of our service will ALWAYS be responsible for the scripts you use. If a server or a website gets compromised because of your script, then you will be held responsible and you will be billed for the damage. In short: everything you put on a server is your responsibility.
Nowadays many plugins in well-known CMS systems (e.g. WordPress, Joomla, Drupal) can get compromised by spam-abusers if nog updated regularly.
Wheneven this happens, you will be held responsible and will be billed for all damage done (including our time to fix all problems), without further notice.
Some general tips:
Make sure that you understand the scripts (and its programming language) you use.
Do not blindly install and/or test scripts. If you don’t use them, then remove it immediately.
A general very reliable source for info on this can be Securityfocus.com
Keep track of the Bugtraq archive and subscribe for the security mailinglist.
KEEP YOUR SCRIPTS UP-TO-DATE. IT IS YOUR RESPONSIBILITY TO PREVENT WEBSITE HACKS BASED ON SCRIPTING CODE (PHP, CGI, PERL, PYTHON, ETC).
Related links / articles:
- Safe mode http://www.php.net/features.safe-mode
- PHP: Security’s Low-Hanging Fruit http://www.securityfocus.com/columnists/427