From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16604 invoked by alias); 21 Oct 2008 17:14:15 -0000 Received: (qmail 16591 invoked by uid 22791); 21 Oct 2008 17:14:14 -0000 X-Spam-Check-By: sourceware.org Received: from rv-out-0708.google.com (HELO rv-out-0708.google.com) (209.85.198.249) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 21 Oct 2008 17:13:35 +0000 Received: by rv-out-0708.google.com with SMTP id c5so2211938rvf.56 for ; Tue, 21 Oct 2008 10:13:32 -0700 (PDT) Received: by 10.141.19.9 with SMTP id w9mr5797797rvi.202.1224609212201; Tue, 21 Oct 2008 10:13:32 -0700 (PDT) Received: from ?192.168.1.199? (dsl-63-249-108-128.cruzio.com [63.249.108.128]) by mx.google.com with ESMTPS id b8sm4837673rvf.9.2008.10.21.10.13.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 21 Oct 2008 10:13:30 -0700 (PDT) Cc: java@gcc.gnu.org Message-Id: <5FA959F1-B6A6-40C6-AB51-E5FEB4C71FD5@gmail.com> From: Casey Marshall To: Jary Grove In-Reply-To: <728947.59752.qm@web110014.mail.gq1.yahoo.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Subject: Re: JESSIE - SSL BAD_CERTIFICATE Exception Date: Tue, 21 Oct 2008 17:14:00 -0000 References: <728947.59752.qm@web110014.mail.gq1.yahoo.com> X-Mailer: Apple Mail (2.929.2) 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-10/txt/msg00023.txt.bz2 On Oct 21, 2008, at 7:16 AM, Jary Grove wrote: > Sorry, I was not very clear in my request. > > I have extracted out the Jessie code from the classpath and > compiling it as a seperate project. > If you tell me which class to modify to ignore this error, it will > be very helpfull (atleast it will keep me going until this bug is > permanently fixed). > No, I understood that. I'm saying that the bug likely isn't even in the Jessie code, but in the generic certificate support, in the gnu.java.security.x509 package. My guess is that the parser is throwing an exception, and Jessie can't setup a connection if there is no certificate. If you've extracted that code, too, then you have a chance of fixing or working around this issue. If it is a bug, it's in the class gnu.java.security.x509.ext.GeneralName. But, I was also saying that you can plug-in a different certificate parser, and Jessie will use that one. If you can send me the certificate it's choking on, I might be able to figure out more precisely what the issue is. Thanks. > Thanks > > > > > ----- Original Message ---- >> From: Casey Marshall >> To: Jary Grove >> Cc: java@gcc.gnu.org >> Sent: Monday, October 20, 2008 5:44:03 PM >> Subject: Re: JESSIE - SSL BAD_CERTIFICATE Exception >> >> 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 changes >> easily, if you can give me some pointers on how to ignore this error. >>> >> >> 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. >> >> Bouncycastle likely has an implementation which isn't as buggy as the >> classpath one. > > > > >