public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David McCullough <davidm@snapgear.com>
To: linux-crypto@vger.kernel.org
Cc: cryptoapi@lists.logix.cz, linux-kernel@vger.kernel.org
Subject: ocf-linux-20050520 - Asynchronous Crypto support for linux
Date: Fri, 20 May 2005 23:57:23 +1000	[thread overview]
Message-ID: <20050520135723.GB26883@beast> (raw)


Hi all,

A new release of the ocf-linux package is up:

	http://ocf-linux.sourceforge.net/

A lot of changes in this release.  Best to check the Changelog below
for the specifics.  Most of the changes have centered around RNG, PKE
or getting Openswan running with OCF.

No 2.6 testing was done for this release,  but it should be close
if it doesn't work.

The OpenSwan 2.3.0 patch of accelerates receive packets only
at this point.  This is just to get the basics out there for comment
while the transmit side is coded.

Changes:
* Mostly complete SKB processing for all drivers
* Numerous fixes to all drivers (esp. cryptosoft)
* All drivers can now do ESP/AH processing on buffers, skb's
  or iovecs.
* Re-work of the ixp4xx driver (multiple  outstanding requests)
* PKE support working in safenet
* New demand driven RNG support with optional FIPS140 testing of data
* Openswan RX-only support for comment
* Fixed race condition in ocf driver startup

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

             reply	other threads:[~2005-05-20 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20 13:57 David McCullough [this message]
2005-06-30 13:48 ` ocf-linux-200506300 - Asynchronous Crypto support for linux David McCullough
2005-09-26  0:14   ` ocf-linux-20050922 " David McCullough

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=20050520135723.GB26883@beast \
    --to=davidm@snapgear.com \
    --cc=cryptoapi@lists.logix.cz \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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