>> >>Who are these "other webpage maintainers" and why do they have access >>to your PHP source code? This isn't a PHP issue. The MySQL password >>has to be in a file as plain text; there's no getting around that (as >>recently discussed on here). Your issue is controlling access to the >>machine and the files, so is an OS/policy/trust issue, imo. > John is right. And from what you say in your response I think that sharing database passwords isn't really the problem. It seems that John's answer was right on - you have an OS/policy/trust issue. If you are trying to limit access to what files the PHP user can read, you might find this message from the archives quite useful... http://marc.theaimsgroup.com/?l=php-general&m=109066460609993&w=2 -- Teach a man to fish... NEW? | http://www.catb.org/~esr/faqs/smart-questions.html STFA | http://marc.theaimsgroup.com/?l=php-general&w=2 STFM | http://php.net/manual/en/index.php STFW | http://www.google.com/search?q=php LAZY | http://mycroft.mozdev.org/download.html?name=PHP&submitform=Find+search+plugins
Attachment:
signature.asc
Description: OpenPGP digital signature
