public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "david at jpackage dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug crypto/27228] java.security.InvalidAlgorithmParameterException
Date: Sat, 22 Apr 2006 19:18:00 -0000 [thread overview]
Message-ID: <20060422191803.1731.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27228-7936@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from david at jpackage dot org 2006-04-22 19:18 -------
Maybe we can consider moving these class before closing this bug? I am also
wondering why the are Diffie Hellman classes in the `sig' package. DH is not a
digital signature algorithm, unless we are accounting for the obvious
similarities between DH and DSA (but then, ElGamal is similar as well). But
then there are ElGamal classes are in javax.crypto.key.dh. How confusing can we
get?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27228
next prev parent reply other threads:[~2006-04-22 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 20:53 [Bug libgcj/27228] New: java.security.InvalidAlgorithmParameterException r_ovidius at eml dot cc
2006-04-20 22:16 ` [Bug libgcj/27228] java.security.InvalidAlgorithmParameterException tromey at gcc dot gnu dot org
2006-04-20 22:16 ` tromey at gcc dot gnu dot org
2006-04-20 23:08 ` tromey at gcc dot gnu dot org
2006-04-20 23:14 ` [Bug crypto/27228] java.security.InvalidAlgorithmParameterException tromey at gcc dot gnu dot org
2006-04-21 2:30 ` csm at gnu dot org
2006-04-21 5:02 ` r_ovidius at eml dot cc
2006-04-21 6:37 ` csm at gnu dot org
2006-04-22 18:11 ` cvs-commit at developer dot classpath dot org
2006-04-22 19:18 ` david at jpackage dot org [this message]
2006-04-22 19:26 ` csm at gnu dot org
2006-07-22 0:31 ` raif at swiftdsl dot com dot au
2006-07-22 5:23 ` csm at gnu dot org
2006-07-24 10:58 ` raif at swiftdsl dot com dot au
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=20060422191803.1731.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).