From: Adrian-Ken Rueegsegger <rueegsegger@swiss-it.ch>
To: davem@davemloft.net
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org,
linux-crypto@vger.kernel.org,
Adrian-Ken Rueegsegger <rueegsegger@swiss-it.ch>
Subject: [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
Date: Mon, 2 Jun 2008 11:33:09 +0200 [thread overview]
Message-ID: <12123991893044-git-send-email-rueegsegger@swiss-it.ch> (raw)
In-Reply-To: <1212399189188-git-send-email-rueegsegger@swiss-it.ch>
This patch fixes the usage of RIPEMD-160 in xfrm_algo which in turn
allows hmac(rmd160) to be used as authentication mechanism in IPsec
ESP and AH (see RFC 2857).
Signed-off-by: Adrian-Ken Rueegsegger <rueegsegger@swiss-it.ch>
---
net/xfrm/xfrm_algo.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/xfrm/xfrm_algo.c b/net/xfrm/xfrm_algo.c
index ac765dd..23a2cc0 100644
--- a/net/xfrm/xfrm_algo.c
+++ b/net/xfrm/xfrm_algo.c
@@ -200,8 +200,8 @@ static struct xfrm_algo_desc aalg_list[] = {
}
},
{
- .name = "hmac(ripemd160)",
- .compat = "ripemd160",
+ .name = "hmac(rmd160)",
+ .compat = "rmd160",
.uinfo = {
.auth = {
--
1.5.2.5
next prev parent reply other threads:[~2008-06-02 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 9:33 [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160 Adrian-Ken Rueegsegger
2008-06-02 9:33 ` Adrian-Ken Rueegsegger [this message]
2008-06-02 10:41 ` Herbert Xu
2008-06-04 19:05 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-06-01 17:16 Adrian-Ken Rueegsegger
2008-06-01 17:16 ` Adrian-Ken Rueegsegger
2008-06-02 5:49 ` Herbert Xu
2008-06-02 6:51 ` Sebastian Siewior
2008-06-02 7:02 ` Adrian-Ken Rueegsegger
2008-06-02 7:04 ` Herbert Xu
2008-06-02 7:09 ` Adrian-Ken Rueegsegger
2008-06-02 7:11 ` Herbert Xu
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=12123991893044-git-send-email-rueegsegger@swiss-it.ch \
--to=rueegsegger@swiss-it.ch \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.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