Correct, all it does is connect straight to the database. It doesn't have
anything to involve encryption... it doesn't care. So, you'll probably need
to secure the path yourself, ie IPSEC.
Someone else may have a better idea, but this is all I can think of.
Typically though, you shouldn't have PHP connect to a database over a
connection that is insecure/public.
Any reason this is a concern?
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Martin A. Marques" <martin@math.unl.edu.ar>
To: "Adam Lang" <aalang@rutgersinsurance.com>; <pgsql-php@postgresql.org>
Sent: Wednesday, March 21, 2001 3:41 PM
Subject: Re: [PHP] php, postgres, ssl
> El Mié 21 Mar 2001 10:46, escribiste:
> > I'd assume that would be totally independent of PHP. You'd probably
have
> > to setup your webserver to connect to the postgres server over an
encrypted
> > line... like using IPSEC or something. Then have PHP connect as
normal...
> > the IPSEC layer would encrypt all transmissions.
>
> Well, then I'm even more confused.
> Lets see if I'm lost, or not.
>
> Browser A conects to Server (Apache with PHP). The page (say index.php)
has a
> pg_connect("host=hostname dbname=dbname password=dpass"). As far as I can
> see, PHP is doing the conection stuff here, and apache has nothing to do
with
> it.
>
> Any comments?
>
> Saludos... ;-)
>
> --
> System Administration: It's a dirty job,
> but someone told me I had to do it.
> -----------------------------------------------------------------
> Martín Marqués email: martin@math.unl.edu.ar
> Santa Fe - Argentina http://math.unl.edu.ar/~martin/
> Administrador de sistemas en math.unl.edu.ar
> -----------------------------------------------------------------