You know, the current structure of how one sets up MediaWiki is just begging for trouble security wise,
"You should probably change your database password, since you just posted it for the world to see." http://www.mediawiki.org/w/index.php?title=Manual_talk:Preventing_access#Dos...
I mean I can't think of hardly any other components here on my Linux system that encourages one to toss passwords right into the same file with the rest of ones settings. It's like we're still at day one when the program was first baked.
Indeed there is even /etc/shadow etc. Yes, the idea is there are two levels of security for /etc files... That way when we send one in for repairs, we don't have to worry if our house keys are still in it somewhere, usually.
Yes the user could easily include() the passwords from a separate file, and indeed I remember there was an Adim*.php.
However putting the passwords in a separate file should be the default way mediawiki sets up, not something the user must do especially.
great job at lecturing, yet completely missing quite a few important points. you give examples of password files that are used to verify user's password, not to supply it, and those files are accessed with suid privileges. separate file would be as world-readable as LocalSettings - because web server software would have to read it (or you'd have to do setuid trickery) maybe putting outside the webroot would make sense for certain improperly configured environments, but unfortunately there's no way to auto-detect such environments and their settings, not without crystal ball at least.
there's enough of privilege separation - you can use superuser password to change user password after each maintenance :)
oh well, I already wrote too much text to reply to your lunacy ;-)
On May 23, 2011, at 7:20 PM, jidanni@jidanni.org wrote:
You know, the current structure of how one sets up MediaWiki is just begging for trouble security wise,
"You should probably change your database password, since you just posted it for the world to see." http://www.mediawiki.org/w/index.php?title=Manual_talk:Preventing_access#Dos...
I mean I can't think of hardly any other components here on my Linux system that encourages one to toss passwords right into the same file with the rest of ones settings. It's like we're still at day one when the program was first baked.
Indeed there is even /etc/shadow etc. Yes, the idea is there are two levels of security for /etc files... That way when we send one in for repairs, we don't have to worry if our house keys are still in it somewhere, usually.
Yes the user could easily include() the passwords from a separate file, and indeed I remember there was an Adim*.php.
However putting the passwords in a separate file should be the default way mediawiki sets up, not something the user must do especially.
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
I'm just saying it would be safer each time a WikiSysop posts his LocalSettings.php to some bulletin board to ask somebody to debug it for him, if by default passwords were not stored in it.
On Mon, May 23, 2011 at 8:03 PM, jidanni@jidanni.org wrote:
I'm just saying it would be safer each time a WikiSysop posts his LocalSettings.php to some bulletin board to ask somebody to debug it for him, if by default passwords were not stored in it.
Well configuration is going out of LocalSettings anyway, so you won't have any reason to post it.
-Chad
On 11-05-23 09:20 AM, jidanni@jidanni.org wrote:
You know, the current structure of how one sets up MediaWiki is just begging for trouble security wise,
"You should probably change your database password, since you just posted it for the world to see." http://www.mediawiki.org/w/index.php?title=Manual_talk:Preventing_access#Dos...
I mean I can't think of hardly any other components here on my Linux system that encourages one to toss passwords right into the same file with the rest of ones settings. It's like we're still at day one when the program was first baked.
- WordPress, Drupal, OSCommerce, etc... basically every php, perl, etc... web software. - php, if you configure mysql globally using defaults - Postfix mysql integration - Nagios and other server monitoring; For when storing things in the database, and when you need to interact with a mysql server to monitor stats, etc... (unless you go and add a user that doesn't require a password; just don't tell me that's a valid solution based on the fact there is no password in the config *rolls eyes*) - PowerDNS' database storage - Puppet, if you use storeconfigs with anything other than SQLite - Apache, if you want to use MySQL based logging or auth - Sphinx
Is this what the term 'Fallacy' would refer to? Indeed there is even /etc/shadow etc.
Yes, the idea is there are two levels of security for /etc files... That way when we send one in for repairs, we don't have to worry if our house keys are still in it somewhere, usually.
Yes the user could easily include() the passwords from a separate file, and indeed I remember there was an Adim*.php.
However putting the passwords in a separate file should be the default way mediawiki sets up, not something the user must do especially.
I leave this rhetoric to Domas' reply.
mediawiki-l@lists.wikimedia.org