On Thursday 25 November 2004 17:43, Olaf van der Spek wrote:
I'm more worried about the data (in MySQL), not the code.
By protecting the MySQL password from being read by scripts directly and
only allowing access based on the current vhost, only this vhost can
access it's own database and not
Raditha Dissanayake wrote:
Olaf van der Spek wrote:
Hi,
Is there a way to store MySQL (or other sensitive data) that will be
It should read MySQL passwords.
passed to a library in such a way that scripts itself can't access this?
A per-vhost store would be ideal.
If not, would this be a good idea
Jason Wong wrote:
On Thursday 25 November 2004 17:43, Olaf van der Spek wrote:
I'm more worried about the data (in MySQL), not the code.
By protecting the MySQL password from being read by scripts directly and
only allowing access based on the current vhost, only this vhost can
access it's own
On Friday 26 November 2004 05:52, Olaf van der Spek wrote:
That's a reasonable solution, but what if multiple SQL users per vhost
are needed?
Frankly, if that vhost is going to require that level of 'complexity' then
that vhost would be better off on a dedicated server. A dedicated server
Hi,
Is there a way to store MySQL (or other sensitive data) that will be
passed to a library in such a way that scripts itself can't access this?
A per-vhost store would be ideal.
If not, would this be a good idea to implement?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe,
Olaf van der Spek wrote:
Hi,
Is there a way to store MySQL (or other sensitive data) that will be
passed to a library in such a way that scripts itself can't access this?
A per-vhost store would be ideal.
If not, would this be a good idea to implement?
Your question is not very clear but if you
6 matches
Mail list logo
