From: Herbert Valerio Riedel <hvr@hvrlab.org>
To: "David S. Miller" <davem@rth.ninka.net>
Cc: Sandy Harris <sandy@storm.ca>, Mitsuru KANDA <mk@linux-ipv6.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
cryptoapi-devel@kerneli.org, design@lists.freeswan.org,
usagi@linux-ipv6.org
Subject: Re: [CryptoAPI-devel] Re: [Design] [PATCH] USAGI IPsec
Date: 21 Oct 2002 09:34:14 +0200 [thread overview]
Message-ID: <1035185654.21824.11.camel@janus.txd.hvrlab.org> (raw)
In-Reply-To: <1035168066.4817.1.camel@rth.ninka.net>
On Mon, 2002-10-21 at 04:41, David S. Miller wrote:
> A completely new CryptoAPI subsystem has been implemented so that
> full lists of page vectors can be passed into the ciphers, which is
> necessary for a clean IPSEC implementation.
oh... nice to learn about your plans (so late) at all ;-)
well, it would be cool if you'd cooperate (or at least share
information) with us (the official cryptoapi project ;-), as we're open
for the design requirements of the next generation cryptoapi...
...otherwise this may render the kerneli.org/cryptoapi effort completely
useless :-/ ...of course, if it's your long term goal to take the
cryptoapi development away from kerneli.org, I'd like to know too ;-)
regards,
--
Herbert Valerio Riedel / Phone: (EUROPE) +43-1-58801-18840
Email: hvr@hvrlab.org / Finger hvr@gnu.org for GnuPG Public Key
GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748 5F65 4981 E064 883F
4142
next prev parent reply other threads:[~2002-10-21 7:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 8:05 [PATCH] USAGI IPsec Mitsuru KANDA
2002-10-21 14:46 ` [Design] " Sandy Harris
2002-10-21 2:41 ` David S. Miller
2002-10-21 3:42 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-21 7:34 ` Herbert Valerio Riedel [this message]
2002-10-22 2:27 ` [CryptoAPI-devel] " Sandy Harris
2002-10-22 5:02 ` Jari Ruusu
2002-10-24 14:50 ` Jean-Luc Cooke
2002-10-28 13:55 ` JuanJo Ciarlante
2002-10-21 4:22 ` Andre Hedrick
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=1035185654.21824.11.camel@janus.txd.hvrlab.org \
--to=hvr@hvrlab.org \
--cc=cryptoapi-devel@kerneli.org \
--cc=davem@rth.ninka.net \
--cc=design@lists.freeswan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mk@linux-ipv6.org \
--cc=netdev@oss.sgi.com \
--cc=sandy@storm.ca \
--cc=usagi@linux-ipv6.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 NNTP newsgroup(s).