pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Luke Woollard <luke@taborvision.com>
To: pgsql-php@postgresql.org
Subject: Re: Securing PHP scripts
Date: Tue, 19 Aug 2003 13:04:55 +1000
Message-ID: <NHBBLDDBILGIHKOBAGFNKENECDAA.luke@taborvision.com> (raw)
In-Reply-To: <Pine.BSF.4.44.0308182252530.81707-100000@themode.com>

I don't know of any..

Luke Woollard
HPAD.com



-----Original Message-----
From: pgsql-php-owner@postgresql.org
[mailto:pgsql-php-owner@postgresql.org]On Behalf Of brew@themode.com
Sent: Tuesday, August 19, 2003 12:55 PM
To: pgsql-php@postgresql.org
Subject: Re: [PHP] Securing PHP scripts



Cody.....

> Now to connect to the DB via PHP, I have the password hard coded (which is
in clear text).
>
> Here is my question: Is there a way around storing the password in clear
text?

But no user can ever read that clear text, right?  They should only get
the PHP script output which normally wouldn't contain the user name and
password.....

There can be a danger of other users on the machine being able see the
clear text password if it's a shared machine and if they are able to read
the script, though!

Of course that didn't answer your question...... maybe somebody else knows
a way around storing it in clear text.

BTW, for the best security you should be sure and run PHP with
register_globals off in the php.ini config file, read about it at

http://us4.php.net/register_globals

Sorry if I'm telling you a bunch of stuff you already know anyway.......

brew






---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)




view thread (8+ messages)  latest in thread

Message-ID: <NHBBLDDBILGIHKOBAGFNKENECDAA.luke@taborvision.com>
Permalink:  ../NHBBLDDBILGIHKOBAGFNKENECDAA.luke@taborvision.com/
Also on:    postgresql.org/message-id/NHBBLDDBILGIHKOBAGFNKENECDAA.luke@taborvision.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: luke@taborvision.com
  Subject: Re: Securing PHP scripts
  In-Reply-To: <NHBBLDDBILGIHKOBAGFNKENECDAA.luke@taborvision.com>
  References: <Pine.BSF.4.44.0308182252530.81707-100000@themode.com> <NHBBLDDBILGIHKOBAGFNKENECDAA.luke@taborvision.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox