From: Adam Lang <aalang@rutgersinsurance.com>
To: pgsql-php@postgresql.org
Subject: Re: php, postgres, ssl
Date: Wed, 21 Mar 2001 16:33:53 -0500
Message-ID: <021101c0b24e$a0b53fc0$330a0a0a@rutgersinsurance.com> (raw)
References: <01032018433400.01347@math.unl.edu.ar>
<004b01c0b20d$60c1b380$330a0a0a@rutgersinsurance.com>
<01032117414402.05421@math.unl.edu.ar>
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
> -----------------------------------------------------------------
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: aalang@rutgersinsurance.com
Subject: Re: php, postgres, ssl
In-Reply-To: <021101c0b24e$a0b53fc0$330a0a0a@rutgersinsurance.com>
References: <01032018433400.01347@math.unl.edu.ar> <004b01c0b20d$60c1b380$330a0a0a@rutgersinsurance.com> <01032117414402.05421@math.unl.edu.ar> <021101c0b24e$a0b53fc0$330a0a0a@rutgersinsurance.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