pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adam Lang <aalang@rutgersinsurance.com>
Cc: pgsql-php@postgresql.org
Subject: Re: php, postgres, ssl
Date: Thu, 22 Mar 2001 08:49:51 -0500
Message-ID: <004201c0b2d6$f7b120e0$330a0a0a@rutgersinsurance.com> (raw)
References: <Pine.BSI.4.21.0103211657100.22836-100000@glass.toledolink.com>

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" <mfork@toledolink.com>
To: "Adam Lang" <aalang@rutgersinsurance.com>
Cc: <pgsql-php@postgresql.org>
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 :)





view thread (14+ messages)  latest in thread

Message-ID: <004201c0b2d6$f7b120e0$330a0a0a@rutgersinsurance.com>
Permalink:  ../004201c0b2d6$f7b120e0$330a0a0a@rutgersinsurance.com/
Also on:    postgresql.org/message-id/004201c0b2d6$f7b120e0$330a0a0a@rutgersinsurance.com

 · 

reply

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: <004201c0b2d6$f7b120e0$330a0a0a@rutgersinsurance.com>
  References: <Pine.BSI.4.21.0103211657100.22836-100000@glass.toledolink.com> <004201c0b2d6$f7b120e0$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