Not for 'how-to' coding questions but PHP theory instead, this forum is here for those of us who wish to learn about design aspects of programming with PHP.
Where do you store that? Obviously you can't hash it. And storing it in the database itself would be bad.
EDIT| I guess it doesn't make much sense to store such details in a database. Lol, I don't know what I was thinking. Where would such details go?
Set Search Time - A google chrome extension. When you search only results from the past year (or set time period) are displayed. Helps tremendously when using new technologies to avoid outdated results.
Is that really necessary? As long as the script doesn't output the password to the screen it should be pretty protected from the world.
If I've got lots of different apps & databases on one box, I store the credentials in an include file.
If I've got a box dedicated to one system, I store the credentials right in the DB abstraction constructor function. That eliminates it from any variable space so I can print_r() to my hearts content without worrying about the credentials being dumped to the screen.
Real programmers don't comment their code. If it was hard to write, it should be hard to understand.
It is possible for php scripts to be displayed and not parsed on screen, so people can view the code. I don't know how, but I know that it can happen. So keeping it below the webroot protects against that being a security risk.
It is possible for php scripts to be displayed and not parsed on screen, so people can view the code. I don't know how, but I know that it can happen. So keeping it below the webroot protects against that being a security risk.
The php parser on the site could go down, that would then just display all php code to the screen including your password. I prefer to put my db connect information one level above webroot as well.