Skip site navigation (1) Skip section navigation (2)

Re: BUG #1321: SSL error: sslv3 alert handshake failure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: "T(dot)J(dot) Ferraro" <tjtoocool(at)phreaker(dot)net>,pgsql-bugs(at)postgresql(dot)org, Magnus Hagander <mha(at)sollentuna(dot)net>
Subject: Re: BUG #1321: SSL error: sslv3 alert handshake failure
Date: 2004-11-16 20:33:49
Message-ID: 2074.1100637229@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Michael Fuhr <mike(at)fuhr(dot)org> writes:
> Sounds like a problem due to the backend in recent betas demanding
> a client certificate if $PGDATA/root.crt exists, but the client
> certificate doesn't exist in ~/.postgresql/postgresql.{crt,key}.

If that is the problem, it's still broken because the error message
is so unhelpful.  (I'm quite certain I tested that case last time
I touched the SSL code, and it said something reasonable then.)

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Michael FuhrDate: 2004-11-16 20:41:56
Subject: Re: BUG #1321: SSL error: sslv3 alert handshake failure
Previous:From: Michael FuhrDate: 2004-11-16 20:30:33
Subject: Re: BUG #1321: SSL error: sslv3 alert handshake failure

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group