pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Carol Walter <walterc@indiana.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: ssl database connection problems...
Date: Tue, 30 Dec 2008 15:53:37 -0500
Message-ID: <4D15E432-79CD-4D0E-ACDD-BC1ABCC5BAFD@indiana.edu> (raw)
In-Reply-To: <20081230023630.GA19239@cns.vt.edu>
References: <752F2E74-9F28-4E3D-869C-93357751AFA0@indiana.edu>
	<20081230023630.GA19239@cns.vt.edu>

Thanks to all of you.  Many of my problems have been fixed.  My  
"listening_addresses" was not set correctly.  After I fixed that  
problem, I started getting an SSL error.  I'm now getting this error  
as follows:

walterc@fac-staff:~$ psql -U walterc -d walterc -h db -p 5433
psql: SSL SYSCALL error: EOF detected

I've poked around a lot in my system.  OpenSSL is telling me that ssl  
is not properly configured.  I don't know if the error is accurate of  
it's describing differences between its configuration and Postgres'.   
Since ssl on my database box has never been used, there's a very good  
chance it's not configured properly.  I've decided the best tact would  
be to get a new version of OpenSSL.  The most current version on the  
Sun Freeware site, is 0.9.8i.
Are there any issues with compatibility that I should know about.

I'm running Solaris 10 and version 8.3.4 of postgres.

Thanks,

Carol
On Dec 29, 2008, at 9:36 PM, Ray Stell wrote:

> On Mon, Dec 29, 2008 at 04:23:30PM -0500, Carol Walter wrote:
>> "with openssl" when I initially configured the server.  Are there  
>> other
>> things that need to be done to get openssl started on the database  
>> server?
>> How can I diagnose this problem?
>>
>
> The files server.key, server.crt, root.crt, and root.crl are only  
> examined
> during server start; so you must restart the server for changes in  
> them
> to take effect.
>
> http://www.postgresql.org/docs/8.3/interactive/ssl-tcp.html
>
> It's been awhile since I played with this, but there's something  
> about an
> environment var, PGSSLMODE.
>
> You can use openssl to verify the server/root ca correctness like
> this:
>
> openssl  verify -CAfile ./root.crt testcert.pem
>
> assuming openssl in the mix.
>
> -- 
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin




view thread (22+ messages)  latest in thread

Message-ID: <4D15E432-79CD-4D0E-ACDD-BC1ABCC5BAFD@indiana.edu>
Permalink:  ../4D15E432-79CD-4D0E-ACDD-BC1ABCC5BAFD@indiana.edu/
Also on:    postgresql.org/message-id/4D15E432-79CD-4D0E-ACDD-BC1ABCC5BAFD@indiana.edu

 · 

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-admin@postgresql.org
  Cc: walterc@indiana.edu
  Subject: Re: ssl database connection problems...
  In-Reply-To: <4D15E432-79CD-4D0E-ACDD-BC1ABCC5BAFD@indiana.edu>
  References: <752F2E74-9F28-4E3D-869C-93357751AFA0@indiana.edu> <20081230023630.GA19239@cns.vt.edu> <4D15E432-79CD-4D0E-ACDD-BC1ABCC5BAFD@indiana.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