From: Tarun Ahuja <tarun.ahuja@cavium.com>
To: linux-crypto@vger.kernel.org
Subject: RFC 4868 support for Linux IPsec stack
Date: Mon, 19 Jan 2009 11:27:44 -0800 [thread overview]
Message-ID: <4974D430.9000504@cavium.com> (raw)
In-Reply-To: <4974D343.3010302@cavium.com>
Does anybody know the status of support for RFC 4868 (SHA256/384/512
with iv length of 16/24/32) to
Linux IPsec stack?sending mail as text I believe, as of kernel 2.6.28,
only SHA256 is supported and that
too only 12 bytes for the icv (instead of 16).
-Tarun
prev parent reply other threads:[~2009-01-19 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 22:48 crypto: libcrc32c should select crc32c Jan Engelhardt
2009-01-18 5:37 ` Herbert Xu
2009-01-18 8:14 ` Jan Engelhardt
2009-01-18 20:45 ` Sam Ravnborg
2009-01-19 19:51 ` Jan Engelhardt
2009-01-19 21:08 ` Herbert Xu
[not found] ` <4974D343.3010302@cavium.com>
2009-01-19 19:27 ` Tarun Ahuja [this message]
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=4974D430.9000504@cavium.com \
--to=tarun.ahuja@cavium.com \
--cc=linux-crypto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.