Closed (won't fix)
Project:
Drupal core
Version:
5.3
Component:
other
Priority:
Critical
Category:
Feature request
Assigned:
Reporter:
Created:
22 Nov 2007 at 20:48 UTC
Updated:
10 Jan 2008 at 10:58 UTC
This week I had some problems and suddenly the .htaccess file became downloadable and readable by webusers.
After changing things back to normal I noticed that the main .htaccess file in the root of drupal has a filesmatch but one of the most important files: settings.php is not in the list.
Should we change this to the following so it the risc will be less?:
# Protect files and directories from prying eyes.
Order allow,deny
Comments
Comment #1
drummDirectly requesting settings.php will be interpreted as a PHP file. Since settings.php does not actually do anything on its own, the user would get a blank page.
Comment #2
laurenwestenberg commentedofcourse, but I think this is not logic. People should get an unforbidden. Also I had a problem that I could download the whole file and open it and watch the password.
With the settings.php in the .htaccess list this wouldn't be possible, I think this would improve security, even if it is only with 0,1%