Received: from bush.rutgersinsurance.com (rutgersinsurance.com [38.138.71.194]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2MDlUt62682 for ; Thu, 22 Mar 2001 08:47:30 -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 KAA17298 for ; Thu, 22 Mar 2001 10:01:32 -0500 Message-ID: <004201c0b2d6$f7b120e0$330a0a0a@rutgersinsurance.com> From: "Adam Lang" Cc: References: Subject: Re: php, postgres, ssl Date: Thu, 22 Mar 2001 08:49:51 -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/40 X-Sequence-Number: 224 I agree, something like that would be one of the better solutions. Have a separate layer worrying about the traffic being encrypted and have php and the database talk as if everything is standard. But I am mostly concerned why the PHP app would be connecting across the internet directly to the database. As far as the "requiressl", I have never seen it used with PHP. Maybe it falls under the "options" parameter. Be interesting if someone tried it. Adam Lang Systems Engineer Rutgers Casualty Insurance Company http://www.rutgersinsurance.com ----- Original Message ----- From: "Michael Fork" To: "Adam Lang" Cc: Sent: Wednesday, March 21, 2001 5:09 PM Subject: Re: [PHP] php, postgres, ssl > There are a couple of things you can do to establish a secure connection > between a remote postgres server and any other server. > > One is using SSH tunnels: > http://www.postgresql.org/users-lounge/docs/7.0/admin/security1530.htm > > Another is to establish your connection with "requiressl=true" as part of > the options strings under libpq -- which, since PHP uses libpq, I belive > should work under PHP as pg_Connect("host=server dbname=db user=me > password=pass requiressl=true") (and if it doesn't work, it should be able > to be added easily). > > I haven't actually done either of these, but I also don't see any reason > why these wouldn't work :)