Bug #10005 | RFE - security patch, to prevent plaintext passwords in config files from leaki | ||
---|---|---|---|
Submitted: | 19 Apr 2005 17:40 | Modified: | 9 Jan 2006 14:46 |
Reporter: | R Herrold | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Eventum | Severity: | S3 (Non-critical) |
Version: | current | OS: | Any (All) |
Assigned to: | CPU Architecture: | Any |
[19 Apr 2005 17:40]
R Herrold
[22 Apr 2005 13:35]
Mike Schroll
How about just making the upgrade scripts rename the configs to a filename ending in .php? That would prevent leakage of sensitive information when someone upgrades, and it leaves behind the config information, easily accessible from the web -- at well defined filenames -- ala http://site.eventum/config.inc.php_pre_1_5_3
[2 May 2005 20:02]
R Herrold
Date: Sat, 23 Apr 2005 14:54:50 -0400 (EDT) From: R P Herrold <herrold@owlriver.com> To: Bug Database <dev-bugs@mysql.com> Subject: Re: Bug #10005 [Com]: RFE - security patch, to prevent plaintext passwords in config files from leaki > How about just making the upgrade scripts rename the configs to a > filename ending in .php? > > That would prevent leakage of sensitive information when someone > upgrades, and it leaves behind the config information, easily > accessible from the web -- at well defined filenames -- > ala > http://site.eventum/config.inc.php_pre_1_5_3 The issue is not so much a leak during upgrades; a local user can craft a local PHP script to sourhe and read the vaiables set in a local script. It is the rather changes to remove the ability to REMOTELY access the configs file by getting them out of a path which is served 'to the world' and restricting them into a path accesible (through webserver ACL enfircement) only to 127.0.0.1 -- Russ Herrold
[2 May 2005 20:03]
R Herrold
> Just a quick note here, I was reading this page > http://www.dwheeler.com/secure-programs/Secure-Programs-HOWTO/php.html > And found the below.. This to me means that Eventum and other such programs > should expect to have a top level public dir, and an includes that is not > public. So the question is, do you eventum guys consider this to be > we
[9 Jan 2006 13:46]
Aleksey Kishkin
unassign it, because jpm has left mysql ab?
[9 Jan 2006 14:46]
Bryan Alsdorf
The config files are not placed in a seperate directory now, but all sensitive files do now end in .php so their contents are no longer readable by the outside world.