What is the most accepted method for hiding password for 'connect.php' file? [duplicate]

This question already has answers here: How to secure database passwords in PHP? (17 answers) Closed 9 months ago.

As my server is getting a bit bigger, and more users are getting 开发者_C百科access to it, I don't want them to see the password that MySQL is using to connect to PHP, which is stored in my 'connect.php' file and required by every page. However, it is just sitting in the same directory as the rest of the php files.

I've considered using a second 'connect.php'-like file with access to only one table, that stores the encrypted passwords to connect to MySQL, but then I would have the problem of hiding the key to it.

Changing permissions won't work either, if you chmod o-r or something similar, nobody will be able to access the web application, obviously.

Is there an accepted method to get around this problem, or should I just solve it on my own? The problem is that I don't want it to be too convoluted if there is an accepted method.

---

I would strongly recommend moving connect.php in one directory above your DOCUMENT_ROOT so that it is not accessible from your web server.

Your php files can of course include connect.php with full or relative path eg:

require_once('../connect.php');

---

All the answers have good advice but fail to address the fact that any user with server access can just snoop around and open the config.php in an editor.

Set your config files in a directory outside of public webspace , the webserver should be the owner of this directory and it should have permissions set to 700. All files it contains should be 644. This way no one can even read the file contents apart from webserver user or root.

This is a common approach, but there is a lot more to the subject as security is a very vast topic, but is better than 90% of the setups out there.

---

Set $password, connect, then unset() $password. They should be never able to recover it. I don't think a PHP file can be downloaded anyway, neither seen. It is always compiled by the server before.

---

The content of server side files cannot be obtained by users, unless you show it to them willingly (or by mistake).

Most likely any compromise would come via FTP access in which case a hacker would have access to all files on the webserver anyway.

---

Move it to a folder after the root of www, such as www/includes. From there, you may use htaccess to block permission for viewing files under /includes.

After connected to the SQL database, use unset($username, $password) so that there is no security threat of someone echoing the username of password.

Finally, it's always best to have dedicated hosting so that nobody else with access to the web server can potentially view other user's files.

---

Alternatively, you could get rid of passwords altogether and configure the DB server that only connections from localhost are accepted. This'll only work on dedicated hosting though, it's a security risk if you're on shared hosting.