The earlier version was PHPsuExec but that is quickly being replaced by suPHP and the two do basically the same thing.

suPHP provides an additional layer of protection on servers. It causes php scripts to run under the account username instead of the user ‘nobody’ which is the user that apache/php would run under on a server that is not running suPHP. This feature allows us to more easily track any potential security breaches that come in via insecure php script(s) that a user is running.

suPHP also does away with the requirement of using 777 permissions on directories/files that need write permission. In fact if a directory and/or file has the permission set to (CHMOD) 777 and it is access via a browser, then an internal server error 500 will be generated. The highest level of permissions that a user can use on a suPHP enabled server is 755. This permission setting is sufficient enough for any directories/files that needs to be written to.

The benefit of using suPHP besides better security, is that it will make any PHP applications (most often CMS systems) such as Mambo more user friendly. Case in point: If you upload/install anything via Mambo such as a template on a non-suphp server, then those template files will be owned by ‘nobody’ and you will not be able to edit them manually or even delete them from your account. This ownership issue is done away with suPHP. On a suPHP enabled server, those same template files will be owned by the account username and the account holder will be able to manipulate those files as he sees fit.

No longer do you need to use (chmod) the dangerous file permission of 666 or the folder permission of 777 to make things writable.

The correct permissions should be:

• Writable Folders: 755
• Writable Files: 644
• Files that need to be un-writable: 444

By default, SourceGuardian is not installed on any of our web hosting packages. However, that does not mean that you are not able to host any scripts that are encoded with SourceGuardian!

SourceGuardian does tell you to upload there encoders to the scripts folder and it will load the files as long the php function dl() is enabled as part of the installation. And unfortunately we have to dissapoint you once again, dl() is disabled for security reasons on all web hosting packages.

Below we will explain you how to get the scripts to run properly, this is possible since we run suPHP.

First you need to create a new .htaccess file in your public_html folder if you haven’t done already. Otherwise you need to edit your current .htaccess file.

In your .htaccess file under your public_html folder, add the following:

suPHP_ConfigPath /home/user/public_html
<Files php.ini>
order allow,deny
deny from all
</Files>

Note: Make sure to change the user text above to your account user name.

Then create a php.ini file under your public_html folder and add the following (or edit the current file if you have a php.ini file):

extension_dir=/home/user/public_html/extensions

[Zend]
zend_extension=/usr/local/ioncube/ioncube_loader_lin_5.2.so
zend_optimizer.optimization_level=15
zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer-3.3.3
zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS-3.3.3
zend_extension=/usr/local/Zend/lib/ZendExtensionManager.so
zend_extension_ts=/usr/local/Zend/lib/ZendExtensionManager_TS.so
extension=/home/user/public_html/extensions/ixed.5.2.lin

Note: Make sure to change the user text above to your account user name.

Zend Optimizer and IonCube loaders are added as well so you won’t drop the support for them with your new php.ini file.

Now create a new folder called "extensions" in your public_html folder and download the required loader at http://www.sourceguardian.com/ixeds/ixed4.lin.x86-64.zip

Then extract the zip file and upload the file "ixed.5.2.lin" to your created folder "extensions"

You may choose another folder to upload the SourceGuardian loader to but remember to have the folder name reflect the one you typed within your php.ini file.

Full details about SourceGuardian can be found at there website, located here:

http://www.sourceguardian.com

Congratulations, you have just installed SourceGuardian in your web hosting account and your script should now run properly!

Any request made to the server is considered a "hit". A request can be for any object, an html page, a graphic image, an audio file, a CGI script, etc. So, "hits" are the total number of requests that were received during the specified report period.

A "visit", on the other hand, is a series of "hits" that are deemed to have come from the same browser within a certain amount of time. A "visit", therefore, represents a browser that came to your site for a while and then left.

Each "visit" is composed of many more "hits".

For example, when a browser requests one page on your site, webalizer will report one hit for the page request, plus one more hit for each image or other object (flash object, javascript file, etc) that was referenced on that page. That is why hits are always greater than visits.

Visits are also grouped by time. Webalizer does this by looking at the IP address of the browser and calculates the amount of time since a visitor’s last requested a page/file (if any). If the time difference is greater than a pre-configured ‘visit timeout’ value (or has never made a request before), it is considered a ‘new visit’.

We deliver our web hosting accounts with detailed statistics to keep track of your websites visitors.

Addon domain:

Addon domains allow you to have more than one independent website sharing the resources of your hosting account. Addon domains hosting is similar to virtualization. You can host multiple domains or multiple websites on a single account which are basically setup as sub domains on the main domain but the domains you add as a addon domain gets parked on top of the subdomain. You can see website of the sub domain when you type your addon domain in your browser but the URL never changes as it continues with your addon domain in the browser.

Parked domain:

You can have multiple domain names pointing to your site. This is a great way to increase your online visibility. Parked domain on main domain shows the website of the main domain. Similarly parked domain on the subdomain would show the website of subdomain.

Examples of parked domains are:

• ds-hostingsolutions.com/kb/differences-addon-and-parked-domains-explained/
• ds-hostingsolutions.biz/kb/differences-addon-and-parked-domains-explained/

Apache configuration needs to know what directory to call when someone opens a particular website in the browser and in case of addon domains, it will load the subdomain. Your addon domain is added as an alias for that subdomain.

From a user perspective, an addon domain functions just like any other domain. You can register and set up an addon domain under your existing web hosting account. So when your visitors type “http://www.yourdomain.com” in their browser, they will be transported to the new site. The difference between a parked domain and an addon domain from a web user’s perspective is that with a parked domain the URL in the address bar will change to the physical location of the page as the page loads.

For example, if you type http://www.abc.com, that domain won’t remain in the browser address bar, but will change to “http://www.domain.com/abc/index.html” as soon as the page is displayed.

DS-Hosting Solutions allows you to add or park as many domains on your web hosting account you need.