Using CGI-BOX and dealing with the SBOX protection

DTC is made so it's possible to use it for shared hosting purpose. That means that CGI-BIN has to be secured in some way. You might know that as-is, CGI-BIN are dangerous in shared hosting, because with it you could access to virtualy all the server files. That's why we use SBOX that does the chroot, chuid, and also cpu, memory and file-access limitations.

That means that if you want to run a perl script for a CGI that is hosted with DTC with SBOX activated, then you need to upload all the perl libraries inside that vhost chroot disk. In fact, you need to upload all the files and library that your CGI might use. It's a pain, but the counterpart is that it's possible to completly customize a CGI-BIN environement and be sure that it's TOTALY SAFE to use it. You could even run a different version of PHP than the system version (the cgi version) if you upload it (I did it and it worked pretty well).

That being said, if it's YOURS cgi-bin and that you trust yourself (of course you do), you can disable SBOX for a domain. Go in the domain configuration of an admin, and then click on the SBOX-Protection link to set it to "no". Once you done it for a domain, you can then disable it for all of it's subdomains. So once disabled for a particular domain, you need to go on the subdomain you want to disable SBOX for, and there a new radio button will appear that allows you to disable SBOX.

Editing this page means accepting its license.

Edit - History - Print - Recent Changes - Search

Page last modified on August 28, 2006, at 12:35 AM EST