From: David McCullough <davidm@snapgear.com>
To: James Morris <jmorris@redhat.com>
Cc: Fruhwirth Clemens <clemens@endorphin.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, cryptoapi@lists.logix.cz,
Michal Ludvig <michal@logix.cz>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 1/2] CryptoAPI: prepare for processing multiple buffers at a time
Date: Thu, 20 Jan 2005 13:30:19 +1000 [thread overview]
Message-ID: <20050120033019.GD9407@beast> (raw)
In-Reply-To: <Xine.LNX.4.44.0501181147490.24891-100000@thoron.boston.redhat.com>
Jivin James Morris lays it down ...
> On Sat, 15 Jan 2005, Fruhwirth Clemens wrote:
>
> > However, developing two different APIs isn't particular efficient. I
> > know, at the moment there isn't much choice, as J.Morris hasn't commited
> > to acrypto in anyway.
>
> There is also the OCF port (OpenBSD crypto framework) to consider, if
> permission to dual license from the original authors can be obtained.
For anyone looking for the OCF port for linux, you can find the latest
release here:
http://lists.logix.cz/pipermail/cryptoapi/2004/000261.html
One of the drivers uses the existing kernel crypto API to implement
a SW crypto engine for OCF.
As for permission to use a dual license, I will gladly approach the
authors if others feel it is important to know the possibility of it at this
point,
Cheers,
Davidm
--
David McCullough, davidm@snapgear.com Ph:+61 7 34352815 http://www.SnapGear.com
Custom Embedded Solutions + Security Fx:+61 7 38913630 http://www.uCdot.org
next prev parent reply other threads:[~2005-01-20 3:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Xine.LNX.4.44.0411301009560.11945-100000@thoron.boston.redhat.com>
[not found] ` <Pine.LNX.4.61.0411301722270.4409@maxipes.logix.cz>
[not found] ` <20041130222442.7b0f4f67.davem@davemloft.net>
2005-01-11 17:03 ` PadLock processing multiple blocks at a time Michal Ludvig
2005-01-11 17:08 ` [PATCH 1/2] " Michal Ludvig
2005-01-14 13:10 ` [PATCH 1/2] CryptoAPI: prepare for processing multiple buffers " Michal Ludvig
2005-01-14 14:20 ` Fruhwirth Clemens
2005-01-14 16:40 ` Michal Ludvig
2005-01-15 12:45 ` Fruhwirth Clemens
2005-01-18 16:49 ` James Morris
2005-01-20 3:30 ` David McCullough [this message]
2005-01-20 13:47 ` James Morris
2005-03-03 10:50 ` David McCullough
2005-01-11 17:08 ` [PATCH 2/2] PadLock processing multiple blocks " Michal Ludvig
2005-01-14 3:05 ` Andrew Morton
2005-01-14 13:15 ` [PATCH 2/2] CryptoAPI: Update PadLock to process multiple blocks at once Michal Ludvig
2005-01-14 22:31 Fw: [PATCH 1/2] CryptoAPI: prepare for processing multiple buffers at a time Evgeniy Polyakov
2005-01-14 22:31 ` Evgeniy Polyakov
2005-01-14 22:32 ` Evgeniy Polyakov
2005-01-14 22:33 ` Evgeniy Polyakov
2005-01-14 22:34 ` Evgeniy Polyakov
2005-01-14 22:41 ` Evgeniy Polyakov
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=20050120033019.GD9407@beast \
--to=davidm@snapgear.com \
--cc=akpm@osdl.org \
--cc=clemens@endorphin.org \
--cc=cryptoapi@lists.logix.cz \
--cc=davem@davemloft.net \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@logix.cz \
/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