[PATCH] doc: Official name of RIPE message digest is RIPEMD-160

[Sergey Matveev]

According to RIPEMD-160 digest specification:
http://homes.esat.kuleuven.be/~bosselae/ripemd160.html
and ECRYPT eHash wiki entry:
http://ehash.iaik.tugraz.at/wiki/RIPEMD-160
this function is known as "RIPEMD", not "RIPE-MD".

--
Signed-off-by: Sergey Matveev <stargrave at stargrave.org>
---
 configure.ac       | 2 +-
 doc/gpg-agent.texi | 2 +-
 g10/rmd160.c       | 6 +++---
 g10/sig-check.c    | 2 +-
 4 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/configure.ac b/configure.ac
index 003e509..61fd504 100644
--- a/configure.ac
+++ b/configure.ac
@@ -293,7 +293,7 @@ GNUPG_GPG_DISABLE_ALGO([camellia256],[CAMELLIA256 cipher])
 
 GNUPG_GPG_DISABLE_ALGO([md5],[MD5 hash])
 # SHA1 is a MUST algorithm
-GNUPG_GPG_DISABLE_ALGO([rmd160],[RIPE-MD160 hash])
+GNUPG_GPG_DISABLE_ALGO([rmd160],[RIPEMD-160 hash])
 GNUPG_GPG_DISABLE_ALGO([sha224],[SHA-224 hash])
 # SHA256 is a MUST algorithm for GnuPG.
 GNUPG_GPG_DISABLE_ALGO([sha384],[SHA-384 hash])
diff --git a/doc/gpg-agent.texi b/doc/gpg-agent.texi
index 5a387d4..fbddc3a 100644
--- a/doc/gpg-agent.texi
+++ b/doc/gpg-agent.texi
@@ -932,7 +932,7 @@ The SHA-1 hash algorithm
 @item sha256
 The SHA-256 hash algorithm
 @item rmd160
-The RIPE-MD160 hash algorithm
+The RIPEMD-160 hash algorithm
 @item md5
 The old and broken MD5 hash algorithm
 @item tls-md5sha1
diff --git a/g10/rmd160.c b/g10/rmd160.c
index 8eb005f..ca835d0 100644
--- a/g10/rmd160.c
+++ b/g10/rmd160.c
@@ -1,4 +1,4 @@
-/* rmd160.c  -	RIPE-MD160
+/* rmd160.c  -	RIPEMD-160
  * Copyright (C) 1998, 1999, 2000, 2001, 2008 Free Software Foundation, Inc.
  *
  * This file is part of GnuPG.
@@ -17,7 +17,7 @@
  * along with this program; if not, see <http://www.gnu.org/licenses/>.
  */
 
-/* For historic reasons gpg uses RIPE-MD160 to to identify names in
+/* For historic reasons gpg uses RIPEMD-160 to to identify names in
    the trustdb.  It would be better to change that to SHA-1, to take
    advantage of a SHA-1 hardware operation provided by some CPUs.
    This would break trustdb compatibility and thus we don't want to do
@@ -54,7 +54,7 @@ rol (u32 x, int n)
 #define rol(x,n) ( ((x) << (n)) | ((x) >> (32-(n))) )
 #endif
 
-/* Structure holding the context for the RIPE-MD160 computation.  */
+/* Structure holding the context for the RIPEMD-160 computation.  */
 typedef struct
 {
   u32 h0, h1, h2, h3, h4;
diff --git a/g10/sig-check.c b/g10/sig-check.c
index ee0ebcb..03e2ed9 100644
--- a/g10/sig-check.c
+++ b/g10/sig-check.c
@@ -179,7 +179,7 @@ check_signature2 (PKT_signature *sig, gcry_md_hd_t digest, u32 *r_expiredate,
 	 * one second.	Some remote batch processing applications might
 	 * like this feature here.
          *
-         * Note that before 2.0.10, we used RIPE-MD160 for the hash
+         * Note that before 2.0.10, we used RIPEMD-160 for the hash
          * and accidentally didn't include the timestamp and algorithm
          * information in the hash.  Given that this feature is not
          * commonly used and that a replay attacks detection should
-- 
2.6.4