Received: from bush.rutgersinsurance.com (rutgersinsurance.com [38.138.71.194]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2LLkvt55243 for ; Wed, 21 Mar 2001 16:46:57 -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 SAA16222 for ; Wed, 21 Mar 2001 18:01:01 -0500 Message-ID: <024801c0b250$c7114720$330a0a0a@rutgersinsurance.com> From: "Adam Lang" To: References: <01032018433400.01347@math.unl.edu.ar> <01032117414402.05421@math.unl.edu.ar> <021101c0b24e$a0b53fc0$330a0a0a@rutgersinsurance.com> <01032118385701.05822@math.unl.edu.ar> Subject: Re: php, postgres, ssl Date: Wed, 21 Mar 2001 16:49:17 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit 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/36 X-Sequence-Number: 220 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" To: "Adam Lang" ; 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 > -----------------------------------------------------------------