Received: from bush.rutgersinsurance.com (rutgersinsurance.com [38.138.71.194]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2MDh7t62014 for ; Thu, 22 Mar 2001 08:43:07 -0500 (EST) (envelope-from aalang@rutgersinsurance.com) Received: from 6014cwpza006 (adam.rutgersinsurance.com [10.10.10.51]) by bush.rutgersinsurance.com (8.9.3/8.9.3) with SMTP id JAA17274 for ; Thu, 22 Mar 2001 09:57:05 -0500 Message-ID: <003901c0b2d6$58647d20$330a0a0a@rutgersinsurance.com> From: "Adam Lang" To: References: <01032018433400.01347@math.unl.edu.ar> <01032118385701.05822@math.unl.edu.ar> <024801c0b250$c7114720$330a0a0a@rutgersinsurance.com> <01032118565603.05822@math.unl.edu.ar> Subject: Re: php, postgres, ssl Date: Thu, 22 Mar 2001 08:45:24 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200103/39 X-Sequence-Number: 223 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" To: 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... ;-)