From: Ray Stell <stellr@cns.vt.edu>
To: Carol Walter <walterc@indiana.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: ssl database connection problems...
Date: Wed, 21 Jan 2009 17:59:03 -0500
Message-ID: <20090121225903.GA2040@cns.vt.edu> (raw)
In-Reply-To: <1C72704B-AC59-4B54-A383-06530E0F88CF@indiana.edu>
References: <752F2E74-9F28-4E3D-869C-93357751AFA0@indiana.edu>
<20081230023630.GA19239@cns.vt.edu>
<E0C8B5AA-621F-45A0-83C9-20A3AC4AFD5B@indiana.edu>
<20090121212450.GA14677@cns.vt.edu>
<1C72704B-AC59-4B54-A383-06530E0F88CF@indiana.edu>
On Wed, Jan 21, 2009 at 05:01:08PM -0500, Carol Walter wrote:
>
> On Jan 21, 2009, at 4:24 PM, Ray Stell wrote:
>
>> On Wed, Jan 21, 2009 at 12:50:23PM -0500, Carol Walter wrote:
> Also, in the second part of my message there are lines relating to the
> encryption. I'm not sure what needs to be in my postgresql.conf file to
> handle this. I'm using the MD5 method.
sorry, I didn't read that far and I didn't keep the post, so if I put
something stupid here, well, there it is.
The last time I played with this was 8.2.something, so 8.3.x may
not worky the same way:
I used the following in pg_hba.conf:
hostssl all all CIDR-address md5
with my specific notation for the CIDR.
http://www.postgresql.org/docs/8.3/interactive/auth-pg-hba-conf.html
looks like you can use host and it will allow either ssl or not, so
chose hostssl if you want to keep the clear text guys out.
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: stellr@cns.vt.edu, walterc@indiana.edu
Subject: Re: ssl database connection problems...
In-Reply-To: <20090121225903.GA2040@cns.vt.edu>
* 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