Hmm... I don't know. Very interesting question.
But unless you have some fear of someone sniffing the line between your
webserver and the database server, it isn't much of a concern I'd assume.
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 4:38 PM
Subject: Re: [PHP] php, postgres, ssl
> El Mié 21 Mar 2001 18:33, Adam Lang escribió:
> > 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?
>
> Well, I thought about this, because I was trying to build something like
it.
> A web server, and a database server, seperated! So I thought, if Postgres
> accepts hostssl connections (if compiled with ssl support), why doesn't
PHP
> use this powerfull feature?
> Would it be difficult to build a pg_connectssl function in PHP that would
do
> this?
>
> 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
> -----------------------------------------------------------------
