Installation security hints/en - Revision history

C schmitz: Text replacement - " enclose="div"" to ""

2022-02-16T13:03:23Z

Text replacement - " enclose="div"" to ""

← Older revision		Revision as of 15:03, 16 February 2022
Line 94:		Line 94:
	This avoids having to change all the other files that include /application/config/config.php, since config.php 're-directs them' towards the configuration file that is located in a non-web directory which includes all the real configuration information. However, you will need to edit configreal.php and change the follow parameters to use absolute directory paths to work properly:		This avoids having to change all the other files that include /application/config/config.php, since config.php 're-directs them' towards the configuration file that is located in a non-web directory which includes all the real configuration information. However, you will need to edit configreal.php and change the follow parameters to use absolute directory paths to work properly:

	<syntaxhighlight lang="php~~" enclose="div~~">		<syntaxhighlight lang="php">

	'basePath' => dirname(dirname('''FILE''')),		'basePath' => dirname(dirname('''FILE''')),
Line 109:		Line 109:
	Example:		Example:

	<syntaxhighlight lang="php~~" enclose="div~~">		<syntaxhighlight lang="php">
	'basePath' => '/var/www/htdocs/limesurvey',		'basePath' => '/var/www/htdocs/limesurvey',
	'runtimePath' => '/var/www/htdocs/limesurvey/tmp/runtime',		'runtimePath' => '/var/www/htdocs/limesurvey/tmp/runtime',

FuzzyBot: Updating to match new version of source page

2021-03-09T10:21:21Z

Updating to match new version of source page

@@ Line 5: / Line 5: @@
 LimeSurvey relies on its own security, which is activated by default. The authors of this software take no responsibility and makes no claims regarding the appropriateness or security level of this software. However, we take security issues very seriously and react quickly. Therefore, if you know of any security problems within LimeSurvey, please let us know either by sending us an email to [mailto:info@limesurvey.org info@limesurvey.org] or by opening a bug report in our [http://bugs.limesurvey.org bug tracker] (please mark it as private).
 ==Linux file permissions==
@@ Line 110: / Line 122: @@
 Also, '''don't use "admin" as the default user'''. Go to your MySQL database (or the one in which you installed LimeSurvey) and change default user name "admin" to whatever you prefer (e.g. "admin_xyz"). It will now be much harder to guess the administrator's new user name. Remember, this is one of the two variables intruders can use to gain access. The admin password is the other variable. So choose both of them with extreme caution.

FuzzyBot: Updating to match new version of source page

2017-10-19T11:30:06Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2017-09-11T09:05:07Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2017-08-14T11:00:02Z

Updating to match new version of source page

← Older revision		Revision as of 13:00, 14 August 2017
Line 8:		Line 8:
	==Linux file permissions==		==Linux file permissions==

	If you are using a Linux server, setting ~~according~~ file permissions is required to secure your LimeSurey installation.		If you are using a Linux server, setting accordingly file permissions is required to secure your LimeSurey installation.

	===Basic facts about Linux/*nix file permissions===		===Basic facts about Linux/*nix file permissions===
Line 30:		Line 30:
	For the script to work properly, the write access to some directories is needed:		For the script to work properly, the write access to some directories is needed:
	*The /limesurvey/application/config directory requires ''Read & Write'' for saving the application configuration settings.		*The /limesurvey/application/config directory requires ''Read & Write'' for saving the application configuration settings.
	*The "/limesurvey/tmp" directory and its sub-directories are used for imports/uploads and should be set to ''Read & Write'' for your web server.		*The '/limesurvey/tmp' directory and its sub-directories are used for imports/uploads and should be set to ''Read & Write'' for your web server.
	*The upload/directory and all its sub-directories must also have set ''Read & Write'' permissions in order to enable pictures and media files upload.		*The upload/directory and all its sub-directories must also have set ''Read & Write'' permissions in order to enable pictures and media files upload.
	* All other directories and files can be set to ''Read Only''.		* All other directories and files can be set to ''Read Only''.
Line 70:		Line 70:

	===SSL usage===		===SSL usage===
	We generally recommend the usage of SSL for sensitive survey data. You usually enable SSL by configuring your web server correctly and using a SSQL certificate. If you have enabled SSL, you should enforce SSL all the time ~~via~~ the [~~Global~~ settings] ~~option~~ of LimeSurvey. Additionally, you could set ~~only~~ to use 'secure' cookies by editing~~/adding~~ the [[Optional_settings#Session_settings\|~~related~~ option]] in config.php.		We generally recommend the usage of SSL for sensitive survey data. You usually enable SSL by configuring your web server correctly and using a SSQL certificate. If you have enabled SSL, you should enforce SSL all the time from the [[Global_settings\|global settings]] of LimeSurvey. Additionally, you could only set to use 'secure' cookies by editing the [[Optional_settings#Session_settings\|respective option]] in config.php.

	=== The access to the config.php file ===		=== The access to the config.php file ===
Line 109:		Line 109:
	</syntaxhighlight>		</syntaxhighlight>

	Also, don't use "admin" as the default user. Go to your MySQL database (or the one in which you installed LimeSurvey on different database) and change default user name "admin" to whatever you prefer (e.g. "admin_xyz"). It will be now much harder to guess administrator's new user name. Remember, this is one of the two variables intruders can use to gain access. The admin password is the other variable. So choose both of them with extreme care.		Also, '''don't use "admin" as the default user'''. Go to your MySQL database (or the one in which you installed LimeSurvey on different database) and change default user name "admin" to whatever you prefer (e.g. "admin_xyz"). It will be now much harder to guess administrator's new user name. Remember, this is one of the two variables intruders can use to gain access. The admin password is the other variable. So choose both of them with extreme care.

FuzzyBot: Updating to match new version of source page

2017-08-07T15:05:03Z

Updating to match new version of source page

Show changes

FuzzyBot: Importing a new version from external source

2017-01-25T10:43:32Z

Importing a new version from external source

← Older revision		Revision as of 12:43, 25 January 2017
Line 47:		Line 47:
	$ chmod -R -w limesurvey/		$ chmod -R -w limesurvey/

	$ chmod -R 770 limesurvey/~~tmp~~		$ chmod -R 770 limesurvey/application/config

	$ chmod -R 770 limesurvey/tmp		$ chmod -R 770 limesurvey/tmp

FuzzyBot: Importing a new version from external source

2017-01-25T10:37:27Z

Importing a new version from external source

← Older revision		Revision as of 12:37, 25 January 2017
Line 37:		Line 37:

	For the script to work properly it needs write access to some directories:		For the script to work properly it needs write access to some directories:
	* The application/config directory requires ''Read & Write'' for saving the application configuration settings.
	*The "/limesurvey/tmp" directory and its subdirectories are used for imports/uploads and should be set to ''Read & Write'' for your webserver.		*The "/limesurvey/tmp" directory and its subdirectories are used for imports/uploads and should be set to ''Read & Write'' for your webserver.
	*The upload/ directory and all its subdirectories must also have ''Read & Write'' for your webserver in order to enable picture and media files upload.		*The upload/ directory and all its subdirectories must also have ''Read & Write'' for your webserver in order to enable picture and media files upload.

FuzzyBot: Importing a new version from external source

2017-01-25T10:27:21Z

Importing a new version from external source

← Older revision		Revision as of 12:27, 25 January 2017
Line 37:		Line 37:

	For the script to work properly it needs write access to some directories:		For the script to work properly it needs write access to some directories:
			* The application/config directory requires ''Read & Write'' for saving the application configuration settings.
	*The "/limesurvey/tmp" directory and its subdirectories are used for imports/uploads and should be set to ''Read & Write'' for your webserver.		*The "/limesurvey/tmp" directory and its subdirectories are used for imports/uploads and should be set to ''Read & Write'' for your webserver.
	*The upload/ directory and all its subdirectories must also have ''Read & Write'' for your webserver in order to enable picture and media files upload.		*The upload/ directory and all its subdirectories must also have ''Read & Write'' for your webserver in order to enable picture and media files upload.

FuzzyBot: Updating to match new version of source page

2017-01-25T10:04:34Z

Updating to match new version of source page

← Older revision		Revision as of 12:04, 25 January 2017
Line 46:		Line 46:

	$ chmod -R -w limesurvey/		$ chmod -R -w limesurvey/

			$ chmod -R 770 limesurvey/tmp

	$ chmod -R 770 limesurvey/tmp		$ chmod -R 770 limesurvey/tmp
Line 73:		Line 75:

	The following are recommendations only. LimeSurvey in general is very safe without these additional measure. If you however collect extremely sensitive data a little additional security can help:		The following are recommendations only. LimeSurvey in general is very safe without these additional measure. If you however collect extremely sensitive data a little additional security can help:

			===SSL usage===
			In general we recommend the usage of SSL for sensitive survey data.
			You usually enable SSL by configuring your webserver correctly and using a SSQL certificate.
			If you have enabled SSL you should enforce SSL at all time in the global settings of LimeSurvey. Additionally you should set only to used 'secure' cookies by using the [[Optional_settings#Session_settings\|related option]] in config.php.


	=== Access of config.php file ===		=== Access of config.php file ===

← Older revision		Revision as of 13:30, 19 October 2017
Line 4:		Line 4:
	==General==		==General==

	LimeSurvey relies on its own security, which is activated by default. The authors of this software ~~takes~~ no responsibility and makes no claims ~~in relation to~~ the appropriateness or ~~the~~ security level of this software. However, we take security issues very ~~serious~~ and react quickly. Therefore, if you know of any security problems ~~with~~ LimeSurvey, please let us know either by sending us an ~~e-mail at~~ [mailto:info@limesurvey.org info@limesurvey.org] or by opening a bug report in our [http://bugs.limesurvey.org bug tracker] (please mark it as private).		LimeSurvey relies on its own security, which is activated by default. The authors of this software take no responsibility and makes no claims regarding the appropriateness or security level of this software. However, we take security issues very seriously and react quickly. Therefore, if you know of any security problems within LimeSurvey, please let us know either by sending us an email to [mailto:info@limesurvey.org info@limesurvey.org] or by opening a bug report in our [http://bugs.limesurvey.org bug tracker] (please mark it as private).

	==Linux file permissions==		==Linux file permissions==

	If you are using a Linux server, setting ~~accordingly~~ file permissions is required to secure your LimeSurey installation.		If you are using a Linux server, setting file permissions accordingly is required to secure your LimeSurey installation.

	===Basic facts about Linux/*nix file permissions===		===Basic facts about Linux/*nix file permissions===
Line 14:		Line 14:
	A Linux/*nix operating system is multi-user. This means that, apart from your personal account, other user accounts may exist on the system and you should take care of what permissions you give to other users.		A Linux/*nix operating system is multi-user. This means that, apart from your personal account, other user accounts may exist on the system and you should take care of what permissions you give to other users.

	<div class="simplebox">[[File:help.png]] '''Hint:''' ~~Setting~~ file permissions is especially important in order to secure configuration files holding critical data such as passwords.</div>		<div class="simplebox">[[File:help.png]] '''Hint:''' setting file permissions is especially important in order to secure configuration files holding critical data such as passwords.</div>

	'''Bear in mind that the 'root' account will always be granted permission to access your files (no matter what file permissions you set) as it is the super-admin user.'''		'''Bear in mind that the 'root' account will always be granted permission to access your files (no matter what file permissions you set) as it is the super-admin user.'''

	The web server (which runs LimeSurvey) is also running under a given identity (user). On Linux, this is usually the 'www', 'www-data' (on Debian/Ubuntu), 'apache' or 'nobody' user. However, some hosting companies use systems (such as suexec) that make possible ~~the running of~~ LimeSurvey scripts with your personal user. Of course, the web server user must have the right to read LimeSurvey files. However, only a small subset of LimeSurvey sub-directories must be writable by the web server user.		The web server (which runs LimeSurvey) is also running under a given identity (user). On Linux, this is usually the 'www', 'www-data' (on Debian/Ubuntu), 'apache' or 'nobody' user. However, some hosting companies use systems (such as suexec) that make it possible to run LimeSurvey scripts with your personal user. Of course, the web server user must have the right to read LimeSurvey files. However, only a small subset of LimeSurvey sub-directories must be writable by the web server user.

	<div class="simplebox">[[File:help.png]] '''Hint''': It is very valuable to revoke write permission for the web server user to these LimeSurvey sub-directories that do not require it. Indeed, even if a LimeSurvey vulnerability might be discovered, the main files will still be protected from an illicit modification thanks to the file system permissions.</div>		<div class="simplebox">[[File:help.png]] '''Hint''': it is very valuable to revoke write permission for the web server user to these LimeSurvey sub-directories that do not require it. Indeed, even if a LimeSurvey vulnerability might be discovered, the main files will still be protected from an illicit modification thanks to the file system permissions.</div>

	===Setting file permissions on a self-managed Linux system===		===Setting file permissions on a self-managed Linux system===

	If you're managing your web server and operating system configuration (you are the owner of the physical server or are renting a virtual server on which you have root access), you ~~can follow~~ the following recommendations from below.		If you're managing your web server and operating system configuration (you are the owner of the physical server or are renting a virtual server on which you have root access), you may consider the following recommendations from below.

	You can first set the owner and group of your LimeSurvey files so that it will ease the file permissions setup. A possible strategy is to set the owner of the LimeSurvey files to your personal username, and the group of the LimeSurvey files to the web server group. Usually, this web server group only contains the web server account (and possibly another webmaster account). For instance, if your username is 'myaccount' and the webserver user is 'apache' in the 'apache' group, then, from a shell access, you can use the following command: <code>$ chown -R myaccount:apache limesurvey/</code>. ~~Then~~, set the file and sub-directories permissions.		You can first set the owner and group of your LimeSurvey files so that it will ease the file permissions setup. A possible strategy is to set the owner of the LimeSurvey files to your personal username, and the group of the LimeSurvey files to the web server group. Usually, this web server group only contains the web server account (and possibly another webmaster account). For instance, if your username is 'myaccount' and the webserver user is 'apache' in the 'apache' group, then, from a shell access, you can use the following command: <code>$ chown -R myaccount:apache limesurvey/</code>. Subsequently, set the file and sub-directories permissions.

	For the script to work properly, the write access to some directories is needed:		For the script to work properly, the write access to some directories is needed:
	*The /limesurvey/application/config directory requires ''Read & Write'' for saving the application configuration settings.		*The /limesurvey/application/config directory requires ''Read & Write'' for saving the application configuration settings
	*The '/limesurvey/tmp' directory and its sub-directories are used for imports/uploads and should be set to ''Read & Write'' for your web server.		*The /limesurvey/tmp directory and its sub-directories are used for imports/uploads and should be set to ''Read & Write'' for your web server
	*The upload/directory and all its sub-directories must also have set ''Read & Write'' permissions in order to enable pictures and media files upload.		*The upload/directory and all its sub-directories must also have set ''Read & Write'' permissions in order to enable pictures and media files upload
	* All other directories and files can be set to ''Read Only''.		* All other directories and files can be set to ''Read Only''

	<div class="simplebox">[[File:help.png]] '''Hint:''' ~~Supposing~~ you've followed the above ~~recommendations~~ on owner/group, these settings can be applied by the following commands:		<div class="simplebox">[[File:help.png]] '''Hint:''' supposing you've followed the recommendations above on owner/group, these settings can be applied by the following commands:

	<code>$ chmod -R o-r-w-x limesurvey/</code>		<code>$ chmod -R o-r-w-x limesurvey/</code>
Line 53:		Line 53:

	In the managed server case, the server needs write access to some directories in order for the script to work properly:		In the managed server case, the server needs write access to some directories in order for the script to work properly:
	*The "/limesurvey/tmp" directory is used for imports/uploads and should be set to ''Read & Write'' for your web server.		*The /limesurvey/tmp directory is used for imports/uploads and should be set to ''Read & Write'' for your web server
	*The upload/directory and all its sub-directories must also have ''Read & Write'' for your web server in order to enable pictures and media files upload.		*The upload/directory and all its sub-directories must also have ''Read & Write'' for your web server in order to enable pictures and media files upload
	* The other directories and files should be set to ''Read Only''.		* The other directories and files should be set to ''Read Only''

	<div class="simplebox">[[File:help.png]] '''Hint:'''		<div class="simplebox">[[File:help.png]] '''Hint:'''
	* Depending on your web server configuration, you will have to chmod the rights on the writable folders to 755 or 777 to make it writable for the web server. Try 755 first, if it does not work, 'upgrade' to 777.		* Depending on your web server configuration, you will have to chmod the rights on the writable folders to 755 or 777 to make it writable for the web server. Try 755 first, if it does not work, 'upgrade' to 777
	* You can also try to remove other users' read access to config.php by setting this file's permissions to 750 - if it does not work, 'upgrade' to 755.</div>		* You can also try to remove other users' read access to config.php by setting this file's permissions to 750 - if it does not work, 'upgrade' to 755</div>

	==Windows file permissions==		==Windows file permissions==
Line 67:		Line 67:
	==Other security issues==		==Other security issues==

	The following are recommendations only. LimeSurvey in general is very safe without these additional ~~measure~~. If you however collect extremely sensitive data a little additional security can help:		The following are recommendations only. LimeSurvey in general is very safe without these additional measures. If you however collect extremely sensitive data, a little additional security can help:

	===SSL usage===		===SSL usage===
Line 78:		Line 78:
	The /application/config/config.php file contains a user name and password for your database server. This poses certain security issues, particularly if you are using a login that has high level administrative access to your database. In the event of some error returning the content of this PHP file to a user's browser, your database password and other details could be compromised (however, this is a very unlikely scenario). The best way to minimize risk is to set up a specific login that has specific rights only to your LimeSurvey database.		The /application/config/config.php file contains a user name and password for your database server. This poses certain security issues, particularly if you are using a login that has high level administrative access to your database. In the event of some error returning the content of this PHP file to a user's browser, your database password and other details could be compromised (however, this is a very unlikely scenario). The best way to minimize risk is to set up a specific login that has specific rights only to your LimeSurvey database.

	Another way to secure this information can be to put the ~~certain~~ information from the /application/config/config.php file in a non-web directory, i.e. for Apache users this is the directory above the htdocs (also known as public_html or www) folder. Basically, you will use config.php, but have one line in it - a line that includes the file with ACTUAL configuration information (ex: <code><?php return include("/home/hostfolder/safedata/configreal.php"); ?></code>). Remove all actual configuration information from /application/config/config.php and paste it into the other file (configreal.php) that is mentioned in the /application/config/'''config.php''' file. This other file should be located in a non-web directory. Then /application/config/config.php will not contain database passwords, etc. - just the name of the file that '''DOES''' contain the database info.		Another way to secure this information can be to put the information from the /application/config/config.php file in a non-web directory, i.e. for Apache users this is the directory above the htdocs (also known as public_html or www) folder. Basically, you will use config.php, but have one line in it - a line that includes the file with ACTUAL configuration information (ex: <code><?php return include("/home/hostfolder/safedata/configreal.php"); ?></code>). Remove all actual configuration information from /application/config/config.php and paste it into the other file (configreal.php) that is mentioned in the /application/config/'''config.php''' file. This other file should be located in a non-web directory. Then, /application/config/config.php will not contain database passwords etc. - just the name of the file that '''DOES''' contain the database info.

	This avoids having to change all the other files that include /application/config/config.php, since config.php 're-directs them' towards the configuration file that is located in a non-web directory ~~that~~ includes all the real configuration information. However, you will need to edit configreal.php and change the follow parameters to use absolute directory paths to work properly:		This avoids having to change all the other files that include /application/config/config.php, since config.php 're-directs them' towards the configuration file that is located in a non-web directory which includes all the real configuration information. However, you will need to edit configreal.php and change the follow parameters to use absolute directory paths to work properly:

	<syntaxhighlight lang="php" enclose="div">		<syntaxhighlight lang="php" enclose="div">
Line 109:		Line 109:
	</syntaxhighlight>		</syntaxhighlight>

	Also, '''don't use "admin" as the default user'''. Go to your MySQL database (or the one in which you installed LimeSurvey ~~on different database~~) and change default user name "admin" to whatever you prefer (e.g. "admin_xyz"). It will be ~~now~~ much harder to guess administrator's new user name. Remember, this is one of the two variables intruders can use to gain access. The admin password is the other variable. So choose both of them with extreme ~~care~~.		Also, '''don't use "admin" as the default user'''. Go to your MySQL database (or the one in which you installed LimeSurvey) and change default user name "admin" to whatever you prefer (e.g. "admin_xyz"). It will now be much harder to guess the administrator's new user name. Remember, this is one of the two variables intruders can use to gain access. The admin password is the other variable. So choose both of them with extreme caution.

← Older revision		Revision as of 11:05, 11 September 2017
Line 4:		Line 4:
	==General==		==General==

	LimeSurvey relies on its own security, which is activated by default. The authors of this software takes no responsibility and makes no claims in relation to the appropriateness or the security level of this software. However, we take security issues very serious and react quickly - if you know of any security problems with LimeSurvey, please let us know either by sending us an e-mail at [mailto:info@limesurvey.org info@limesurvey.org] or by opening a bug report in our [http://bugs.limesurvey.org bug tracker] (please mark it as private).		LimeSurvey relies on its own security, which is activated by default. The authors of this software takes no responsibility and makes no claims in relation to the appropriateness or the security level of this software. However, we take security issues very serious and react quickly. Therefore, if you know of any security problems with LimeSurvey, please let us know either by sending us an e-mail at [mailto:info@limesurvey.org info@limesurvey.org] or by opening a bug report in our [http://bugs.limesurvey.org bug tracker] (please mark it as private).

	==Linux file permissions==		==Linux file permissions==
Line 16:		Line 16:
	<div class="simplebox">[[File:help.png]] '''Hint:''' Setting file permissions is especially important in order to secure configuration files holding critical data such as passwords.</div>		<div class="simplebox">[[File:help.png]] '''Hint:''' Setting file permissions is especially important in order to secure configuration files holding critical data such as passwords.</div>

	''Bear in mind that the 'root' account will always be granted permission to access your files (no matter what file permissions you set) as it is the super-admin user.''		'''Bear in mind that the 'root' account will always be granted permission to access your files (no matter what file permissions you set) as it is the super-admin user.'''

	The web server (which runs LimeSurvey) is also running under a given identity (user). On Linux, this is usually the 'www', 'www-data' (on Debian/Ubuntu), 'apache' or 'nobody' user. However, some hosting companies use systems (such as suexec) that make possible the running of LimeSurvey scripts with your personal user. Of course, the web server user must have the right to read LimeSurvey files. However, only a small subset of LimeSurvey sub-directories must be writable by the web server user.		The web server (which runs LimeSurvey) is also running under a given identity (user). On Linux, this is usually the 'www', 'www-data' (on Debian/Ubuntu), 'apache' or 'nobody' user. However, some hosting companies use systems (such as suexec) that make possible the running of LimeSurvey scripts with your personal user. Of course, the web server user must have the right to read LimeSurvey files. However, only a small subset of LimeSurvey sub-directories must be writable by the web server user.
Line 24:		Line 24:
	===Setting file permissions on a self-managed Linux system===		===Setting file permissions on a self-managed Linux system===

	If you're managing your web server and operating system configuration (you are the owner of the physical server or are renting a virtual server on which you have root access), you can follow the following ~~the~~ recommendations from below.		If you're managing your web server and operating system configuration (you are the owner of the physical server or are renting a virtual server on which you have root access), you can follow the following recommendations from below.

	You can first set the owner and group of your LimeSurvey files so that it will ease the file permissions setup. A possible strategy is to set the owner of the LimeSurvey files to your personal username, and the group of the LimeSurvey files to the web server group. Usually, this web server group only contains the web server account (and possibly another webmaster account). For instance, if your username is 'myaccount' and the webserver user is 'apache' in the 'apache' group, then, from a shell access, you can use the following command: <code>$ chown -R myaccount:apache limesurvey/</code>. Then set the file and sub-directories permissions.		You can first set the owner and group of your LimeSurvey files so that it will ease the file permissions setup. A possible strategy is to set the owner of the LimeSurvey files to your personal username, and the group of the LimeSurvey files to the web server group. Usually, this web server group only contains the web server account (and possibly another webmaster account). For instance, if your username is 'myaccount' and the webserver user is 'apache' in the 'apache' group, then, from a shell access, you can use the following command: <code>$ chown -R myaccount:apache limesurvey/</code>. Then, set the file and sub-directories permissions.

	For the script to work properly, the write access to some directories is needed:		For the script to work properly, the write access to some directories is needed:
Line 50:		Line 50:
	===Setting file permissions on a hosted web server===		===Setting file permissions on a hosted web server===

	Giving the difficulty of a standard procedure to secure a web application on a hosted environment, it is rather difficult because hosted environments differ in so many ways.		Giving the difficulty of a standard procedure to secure a web application on a hosted environment, it is rather difficult because hosted environments differ in many ways.

	In the managed server case, the server needs write access to some directories in order for the script to work properly:		In the managed server case, the server needs write access to some directories in order for the script to work properly:
Line 70:		Line 70:

	===SSL usage===		===SSL usage===
	We generally recommend the usage of SSL for sensitive survey data. You usually enable SSL by configuring your web server correctly and using a SSQL certificate. If you have enabled SSL, you should enforce SSL all the time from the [[Global_settings\|global settings]] of LimeSurvey. Additionally, you could only set to use 'secure' cookies by editing the [[Optional_settings~~#Session_settings~~\|respective option]] in config.php.		We generally recommend the usage of SSL for sensitive survey data. You usually enable SSL by configuring your web server correctly and using a SSQL certificate. If you have enabled SSL, you should enforce SSL all the time from the [[Global_settings\|global settings]] of LimeSurvey. Additionally, you could only set to use 'secure' cookies by editing the [[Optional_settings\|respective option]] in config.php.

	=== The access to the config.php file ===		=== The access to the config.php file ===
Line 76:		Line 76:
	{{Alert\| You must update application/config/'''config.php''' only after the first installation is done and it works.}}		{{Alert\| You must update application/config/'''config.php''' only after the first installation is done and it works.}}

	The /application/config/config.php file contains a user name and password for your database server. This poses certain security issues, particularly if you are using a login that has high level administrative access to your database. In the event of some error returning the content of this PHP file to a user's browser, your database password and other details could be compromised (~~please note~~, ~~that~~ this is a very unlikely scenario). The best way to minimize risk is to set up a specific login that has specific rights only to your LimeSurvey database.		The /application/config/config.php file contains a user name and password for your database server. This poses certain security issues, particularly if you are using a login that has high level administrative access to your database. In the event of some error returning the content of this PHP file to a user's browser, your database password and other details could be compromised (however, this is a very unlikely scenario). The best way to minimize risk is to set up a specific login that has specific rights only to your LimeSurvey database.

	Another way to secure this information can be to put the certain information from the /application/config/config.php file in a non-web directory, i.e. for Apache users this is the directory above the htdocs (also known as public_html or www) folder. Basically, you will use config.php, but have one line in it - a line that includes the file with ACTUAL configuration information (ex: <code><?php return include("/home/hostfolder/safedata/configreal.php"); ?></code>). Remove all actual configuration information from /application/config/config.php and paste it into the other file (configreal.php) that is mentioned in the /application/config/'''config.php''' file. This other file should be located in a non-web directory. Then /application/config/config.php will not contain database passwords, etc. - just the name of the file that '''DOES''' contain the database info.		Another way to secure this information can be to put the certain information from the /application/config/config.php file in a non-web directory, i.e. for Apache users this is the directory above the htdocs (also known as public_html or www) folder. Basically, you will use config.php, but have one line in it - a line that includes the file with ACTUAL configuration information (ex: <code><?php return include("/home/hostfolder/safedata/configreal.php"); ?></code>). Remove all actual configuration information from /application/config/config.php and paste it into the other file (configreal.php) that is mentioned in the /application/config/'''config.php''' file. This other file should be located in a non-web directory. Then /application/config/config.php will not contain database passwords, etc. - just the name of the file that '''DOES''' contain the database info.