public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "ovidr at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/19728] New: libgcj Gnu.java missing SHA-160
Date: Mon, 31 Jan 2005 20:50:00 -0000	[thread overview]
Message-ID: <20050131205008.19728.ovidr@users.sourceforge.net> (raw)

Index: Gnu.java
===================================================================
RCS file: /cvsroot/gcc/gcc/libjava/gnu/java/security/provider/Gnu.java,v
retrieving revision 1.7
diff -u -r1.7 Gnu.java
--- Gnu.java  15 Nov 2004 20:02:04 -0000  1.7
+++ Gnu.java  31 Jan 2005 20:47:01 -0000
@@ -129,6 +129,7 @@
         // Format "Alias", "Actual Name"
         put("Alg.Alias.MessageDigest.SHA1", "SHA");
         put("Alg.Alias.MessageDigest.SHA-1", "SHA");
+        put("Alg.Alias.MessageDigest.SHA-160", "SHA");

         // Algorithm Parameters
         put("AlgorithmParameters.DSA",

-- 
           Summary: libgcj Gnu.java missing SHA-160
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ovidr at users dot sourceforge dot net
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19728


             reply	other threads:[~2005-01-31 20:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-31 20:50 ovidr at users dot sourceforge dot net [this message]
2005-01-31 22:17 ` [Bug libgcj/19728] " pinskia at gcc dot gnu dot org
2005-02-21  0:13 ` cvs-commit at gcc dot gnu dot org
2005-02-21  0:13 ` tromey at gcc dot gnu dot org
2005-02-21  0:35 ` pinskia at gcc dot gnu dot org

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=20050131205008.19728.ovidr@users.sourceforge.net \
    --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).