Kris, the information I base my statements on is from the mail-list:
http://www.mail-archive.com/pgsql-bugs@postgresql.org/msg10008.html
I can confirm that Jboss does not requested a keystore, and that it is the driver which is having a problem with the format of the certificate. I can confirm that server.key, server.crt, and root.crt need to be placed in the root of data:
/usr/local/pgsql/data
If you remove any of those files from the directory , postgreSQl does not startup. This is based on requesting ssl with -l.
The options left are to create an SSLv3 specific certificate, if that can be done?? or build version 7.4.* of postgreSQL
Any ideas
regards
Andrew
On 6 Dec 2004, at 19:53, Kris Jurka wrote:
On Mon, 6 Dec 2004, Andrew M wrote:
after much research to various mail-lists, it seems that there is a bug
in the beta versions of postgreSQL 8 which is causing the problem. Is
there anyway to create a SSLv3 specific certificate?
How about sharing a little of that research with us. The whole JDBC
and SSL setup worked fine for me last time I tested it (mid-October) and I
have little reason to believe it is broken now. What "bug" are you
seeing?
Kris Jurka
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
