|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #37000 Suggestion for improving Database Security chapter
Submitted: 2006-04-06 16:19 UTC Modified: 2009-05-08 17:27 UTC
Avg. Score:3.0 ± 0.0
Reproduced:0 of 0 (0.0%)
From: david at acz dot org Assigned:
Status: Wont fix Package: Documentation problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
33 - 15 = ?
Subscribe to this entry?

 [2006-04-06 16:19 UTC] david at acz dot org
It would be helpful for the Database Security chapter to discuss security in a shared hosting environment.  Under a typical Apache / mod_php setup where PHP scripts all run as the Apache user, any user can read any other user's PHP scripts and thus capture any database authentication information.  It may be possible to mitigate this with safe mode, but not if the server allows running other types of CGIs.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2009-05-08 17:27 UTC]
This isn't so much a database issue as it is a permissions issue.  As 
such, the permissions and security are inherited by the operating 
system's own security (or lack thereof), and thus goes beyond the scope 
of the PHP manual.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Apr 18 11:01:28 2024 UTC