Re: SSL confirmation - (could not accept SSL connection: sslv3 alert certificate unknown )

From: Andrew M <andrew(at)jibeya(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: SSL confirmation - (could not accept SSL connection: sslv3 alert certificate unknown )
Date: 2004-12-06 19:33:59
Message-ID: C721A366-47BD-11D9-8DF8-0003938366A4@jibeya.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-jdbc

Hi,
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?

regards

Andrew
On 6 Dec 2004, at 12:28, Kris Jurka wrote:

>
>
> On Mon, 6 Dec 2004, Andrew M wrote:
>
>> jdbc:postgresql://localhost:5432/mydatabase?ssl
>>
>> When I launch Jboss, which handles the connection to postgresql, I get
>> the following error:
>>
>> javax.net.ssl.SSLHandshakeException:
>> sun.security.validator.ValidatorException: No trusted certificate
>> found
>>
>
> Difficult to say. Perhaps JBoss is deciding to use an alternate
> truststore? Perhaps it doesn't like your cert setup. I would suggest
> first running a simple client program to test that it's working first.
> Also adding -Djavax.net.debug=ssl to the java command will help
> debugging
> ssl problems.
>
> Further the 8.0 JDBC driver can create SSL connnections without doing
> authentication by adding using an additional url parameter:
>
> sslfactory=org.postgresql.ssl.NonValidatingFactory
>
> You should try to get it to authenticate correctly, but this is another
> useful test point.
>
> Kris Jurka
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message alex 2004-12-06 19:34:33 Re: DBD::PgSPI 0.02
Previous Message Michael Fuhr 2004-12-06 19:28:53 Re: DBD::PgSPI 0.02

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2004-12-06 19:53:13 Re: SSL confirmation - (could not accept SSL connection:
Previous Message Kris Jurka 2004-12-06 13:24:39 Re: Patch for jdbc escaped functions