From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 331 invoked by alias); 8 Dec 2008 15:46:25 -0000 Received: (qmail 321 invoked by uid 22791); 8 Dec 2008 15:46:24 -0000 X-Spam-Check-By: sourceware.org Received: from n2.bullet.mail.gq1.yahoo.com (HELO n2.bullet.mail.gq1.yahoo.com) (67.195.9.85) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Mon, 08 Dec 2008 15:45:23 +0000 Received: from [67.195.9.81] by n2.bullet.mail.gq1.yahoo.com with NNFMP; 08 Dec 2008 15:45:21 -0000 Received: from [67.195.9.108] by t1.bullet.mail.gq1.yahoo.com with NNFMP; 08 Dec 2008 15:45:21 -0000 Received: from [127.0.0.1] by omp112.mail.gq1.yahoo.com with NNFMP; 08 Dec 2008 15:45:21 -0000 Received: (qmail 47248 invoked by uid 60001); 8 Dec 2008 15:45:21 -0000 Received: from [38.106.153.14] by web110007.mail.gq1.yahoo.com via HTTP; Mon, 08 Dec 2008 07:45:20 PST References: <728947.59752.qm@web110014.mail.gq1.yahoo.com> <5FA959F1-B6A6-40C6-AB51-E5FEB4C71FD5@gmail.com> Date: Mon, 08 Dec 2008 15:46:00 -0000 From: Jary Grove Subject: Re: JESSIE - SSL BAD_CERTIFICATE Exception To: java@gcc.gnu.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <989867.47071.qm@web110007.mail.gq1.yahoo.com> X-IsSubscribed: yes Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org X-SW-Source: 2008-12/txt/msg00005.txt.bz2 Problem seems to be with the Active Directory Test Certificate that comes w= ith Windows 2003.=20 I purchased a domain certificate and no problem with it.=20 I will try to plugin the bounty castle and test with it.=20 Thanks __________________________________________________ Do You Yahoo!? Tired of spam?=A0 Yahoo! Mail has the best spam protection a= round=20 Active Directory Browser http://www.ldapsoft.com/activedirectoryadmintool.h= tml ----- Original Message ---- > From: Casey Marshall > To: Jary Grove > Cc: java@gcc.gnu.org > Sent: Tuesday, October 21, 2008 12:13:27 PM > Subject: Re: JESSIE - SSL BAD_CERTIFICATE Exception >=20 > On Oct 21, 2008, at 7:16 AM, Jary Grove wrote: >=20 > > Sorry, I was not very clear in my request. > >=20 > > I have extracted out the Jessie code from the classpath and compiling i= t as a=20 > seperate project. > > If you tell me which class to modify to ignore this error, it will be v= ery=20 > helpfull (atleast it will keep me going until this bug is permanently fix= ed). > >=20 >=20 > No, I understood that. I'm saying that the bug likely isn't even in the J= essie=20 > code, but in the generic certificate support, in the gnu.java.security.x5= 09=20 > package. My guess is that the parser is throwing an exception, and Jessie= can't=20 > setup a connection if there is no certificate. >=20 > If you've extracted that code, too, then you have a chance of fixing or w= orking=20 > around this issue. If it is a bug, it's in the class=20 > gnu.java.security.x509.ext.GeneralName. >=20 > But, I was also saying that you can plug-in a different certificate parse= r, and=20 > Jessie will use that one. >=20 > If you can send me the certificate it's choking on, I might be able to fi= gure=20 > out more precisely what the issue is.. >=20 > Thanks. >=20 > > Thanks > >=20 > >=20 > >=20 > >=20 > > ----- Original Message ---- > >> From: Casey Marshall=20 > >> To: Jary Grove=20 > >> Cc: java@gcc.gnu.org > >> Sent: Monday, October 20, 2008 5:44:03 PM > >> Subject: Re: JESSIE - SSL BAD_CERTIFICATE Exception > >>=20 > >> On Mon, Oct 20, 2008 at 3:08 PM, Jary Grove wrote: > >>> Any quick fix? > >>> I am compiling Jessie from the source and will be able to plug in the= =20 > changes > >> easily, if you can give me some pointers on how to ignore this error. > >>>=20 > >>=20 > >> This is actually a problem in the certificate parser, which are a part > >> of classpath/libgcj itself. You can plug in a different implementation > >> of this, via the standard security provider APIs. > >>=20 > >> Bouncycastle likely has an implementation which isn't as buggy as the > >> classpath one. > >=20 > >=20 > >=20 > >=20 > >=20