From: Jary Grove <jarygrove@yahoo.com>
To: Casey Marshall <casey.s.marshall@gmail.com>
Cc: java@gcc.gnu.org
Subject: Re: JESSIE - SSL BAD_CERTIFICATE Exception
Date: Tue, 21 Oct 2008 14:17:00 -0000 [thread overview]
Message-ID: <728947.59752.qm@web110014.mail.gq1.yahoo.com> (raw)
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).
Thanks
----- Original Message ----
> From: Casey Marshall <casey.s.marshall@gmail.com>
> To: Jary Grove <jarygrove@yahoo.com>
> 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 reply other threads:[~2008-10-21 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 14:17 Jary Grove [this message]
2008-10-21 17:14 ` Casey Marshall
2008-12-08 15:46 ` Jary Grove
-- 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=728947.59752.qm@web110014.mail.gq1.yahoo.com \
--to=jarygrove@yahoo.com \
--cc=casey.s.marshall@gmail.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).