From: "Casey Marshall" <casey.s.marshall@gmail.com>
To: "Jary Grove" <jarygrove@yahoo.com>
Cc: java@gcc.gnu.org
Subject: Re: JESSIE - SSL BAD_CERTIFICATE Exception
Date: Mon, 20 Oct 2008 22:44:00 -0000 [thread overview]
Message-ID: <20024fdf0810201544h6fe13c01ya311ead9163ca946@mail.gmail.com> (raw)
In-Reply-To: <266224.30114.qm@web110007.mail.gq1.yahoo.com>
On Mon, Oct 20, 2008 at 3:08 PM, Jary Grove <jarygrove@yahoo.com> 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-10-20 22:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 22:09 Jary Grove
2008-10-20 22:44 ` Casey Marshall [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-21 14:17 Jary Grove
2008-10-21 17:14 ` Casey Marshall
2008-12-08 15:46 ` Jary Grove
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=20024fdf0810201544h6fe13c01ya311ead9163ca946@mail.gmail.com \
--to=casey.s.marshall@gmail.com \
--cc=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).