From: Adam Lang <aalang@rutgersinsurance.com>
To: pgsql-php@postgresql.org
Subject: Re: php, postgres, ssl
Date: Thu, 22 Mar 2001 08:45:24 -0500
Message-ID: <003901c0b2d6$58647d20$330a0a0a@rutgersinsurance.com> (raw)
References: <01032018433400.01347@math.unl.edu.ar>
<01032118385701.05822@math.unl.edu.ar>
<024801c0b250$c7114720$330a0a0a@rutgersinsurance.com>
<01032118565603.05822@math.unl.edu.ar>
The argument then would probably be, "why is your web app connecting to a
database across the public Internet"?
I'd assume that is not the safest, nor smartest, thing to do. There are a
lot of problems with that setup.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Martin A. Marques" <martin@math.unl.edu.ar>
To: <pgsql-php@postgresql.org>
Sent: Wednesday, March 21, 2001 4:56 PM
Subject: Re: [PHP] php, postgres, ssl
> Well, I would say that, if I use ssh and not telnet, I am concerned about
> sniffers on the net. We had one about 3 years ago.
>
> Saludos... ;-)
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: <003901c0b2d6$58647d20$330a0a0a@rutgersinsurance.com>
References: <01032018433400.01347@math.unl.edu.ar> <01032118385701.05822@math.unl.edu.ar> <024801c0b250$c7114720$330a0a0a@rutgersinsurance.com> <01032118565603.05822@math.unl.edu.ar> <003901c0b2d6$58647d20$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