From: David McCullough <davidm@snapgear.com>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: ocf-linux-20050922 - Asynchronous Crypto support for linux
Date: Mon, 26 Sep 2005 10:14:59 +1000 [thread overview]
Message-ID: <20050926001459.GE10157@beast> (raw)
In-Reply-To: <20050630134806.GA30067@beast>
Hi all,
A new release of the ocf-linux package is up:
http://ocf-linux.sourceforge.net/
Mostly fixes in this release. I had been sitting on sme tof this for
too long. Best to check the Changelog below for some of the specifics.
At least some 2.6 testing was done for this release :-)
Changes:
* Much improved 2.6 support in OCF
* Openswan patch has full ESP/AH acceleration
* Updated crypto-tools with many fixes/additions
* Much more reliable (will not exhaust system resources under heavy load)
Cheers,
Davidm
--
David McCullough, davidm@cyberguard.com.au, Custom Embedded Solutions + Security
Ph:+61 734352815 Fx:+61 738913630 http://www.uCdot.org http://www.cyberguard.com
prev parent reply other threads:[~2005-09-26 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 13:57 ocf-linux-20050520 - Asynchronous Crypto support for linux David McCullough
2005-06-30 13:48 ` ocf-linux-200506300 " David McCullough
2005-09-26 0:14 ` David McCullough [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=20050926001459.GE10157@beast \
--to=davidm@snapgear.com \
--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