From: Jary Grove <jarygrove@yahoo.com>
To: java@gcc.gnu.org
Subject: Re: JESSIE - SSL BAD_CERTIFICATE Exception
Date: Mon, 08 Dec 2008 15:46:00 -0000 [thread overview]
Message-ID: <989867.47071.qm@web110007.mail.gq1.yahoo.com> (raw)
In-Reply-To: <5FA959F1-B6A6-40C6-AB51-E5FEB4C71FD5@gmail.com>
Problem seems to be with the Active Directory Test Certificate that comes with Windows 2003.
I purchased a domain certificate and no problem with it.
I will try to plugin the bounty castle and test with it.
Thanks
__________________________________________________
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around
Active Directory Browser http://www.ldapsoft.com/activedirectoryadmintool.html
----- Original Message ----
> From: Casey Marshall <casey.s.marshall@gmail.com>
> To: Jary Grove <jarygrove@yahoo.com>
> Cc: java@gcc.gnu.org
> Sent: Tuesday, October 21, 2008 12:13:27 PM
> Subject: Re: JESSIE - SSL BAD_CERTIFICATE Exception
>
> 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.
> >
> >
> >
> >
> >
next prev parent reply other threads:[~2008-12-08 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 14:17 Jary Grove
2008-10-21 17:14 ` Casey Marshall
2008-12-08 15:46 ` Jary Grove [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-20 22:09 Jary Grove
2008-10-20 22:44 ` Casey Marshall
2008-10-18 21:17 Jary Grove
2008-10-20 20:03 ` Casey Marshall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=989867.47071.qm@web110007.mail.gq1.yahoo.com \
--to=jarygrove@yahoo.com \
--cc=java@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).