View Issue Details

IDProjectCategoryView StatusLast Update
0008089mantisbtsecuritypublic2014-01-21 16:13
Reporterdeboutv Assigned To 
PrioritynormalSeverityminorReproducibilityN/A
Status confirmedResolutionopen 
Product Version1.1.0a3 
Summary0008089: Make the location of config_inc.php relocatable outside htdocs
Description

Sometimes webserver sends not interpreted PHP file to the client (because of a bug in the webserver, a misconfiguration, the PHP engine is unavailable...).
In this case, you can request the config_inc.php file and see the password...

To prevent this behaviour (see directly the config_inc.php file), I recommend to move the config file into a directory protected by a .htaccess file (deny from all) or (better) move the config file out of the document_root directory.

TagsNo tags attached.

Relationships

related to 0016850 closedvboctor Add config folder for customization files 

Activities

vboctor

vboctor

2007-06-22 00:37

manager   ~0014797

I wonder if we can add an .htaccess file to block serving specific files. We should also add one to block other folders like core/. I am not very familiar with the htaccess format, so people are welcome to contribute their suggestions.

giallu

giallu

2007-06-28 18:48

reporter   ~0014829

AFAIK, the packaged versions in linux already move config_inc.php out of the webroot extacly for the reasons you are stating

Since this affects only those installing manually from sources, I think it would be enough to note this issue (with possible workarounds) in the installation instructions.

dhx

dhx

2010-09-19 02:25

reporter   ~0026778

Agreed with the need to make the location of config_inc.php relocatable outside of the web root. I already do the same thing (hard coded changes) when installing MantisBT from source.

vboctor

vboctor

2013-10-09 00:19

manager   ~0038230

I believe we support having an env variable point to the config_inc.php We could add a check to admin/check/ page which would direct admins to move config_inc.php out of htdocs and include it in a local one or point to it using the env variable.