All of lore.kernel.org
 help / color / mirror / Atom feed
From: David McCullough <David_Mccullough@securecomputing.com>
To: linux-crypto@vger.kernel.org
Subject: ocf-linux-20070727 - Asynchronous Crypto support for linux
Date: Fri, 27 Jul 2007 23:36:41 +1000	[thread overview]
Message-ID: <20070727133641.GA29614@securecomputing.com> (raw)


Hi all,

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

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

This is really a test release for some people developing drivers on
newer kernels and I didn't want to hold them out any longer.  It's
stable but not everything I want to do has been included yet.  I expect
to do another release within a week or so with some small extras and
fixups.  The high level changes from the previous release:

    * sync up with latest FreeBSD API Changes.
    * pull in quite a few changes from the OpenSwan OCF version (more coming).
    * 2.6 kernel support up to and including 2.6.22.
    * 2.4 kernel support up to and including 2.4.35.
    * full cryptosoft support for new kernel crypto API.
    * updated openswan patch to 2.4.9 (with additional support for above
      kernels).

Tested under 2.4.35 and 2.6.22 across multiple architectures.
Also,  join up the mailing list if you are interested/working on this:

    http://lists.sourceforge.net/mailman/listinfo/ocf-linux-users

Cheers,
Davidm

-- 
David McCullough,  david_mccullough@securecomputing.com,   Ph:+61 734352815
Secure Computing - SnapGear  http://www.uCdot.org http://www.cyberguard.com

             reply	other threads:[~2007-07-27 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 13:36 David McCullough [this message]
2007-12-15 12:40 ` ocf-linux-20071215 - Asynchronous Crypto support for linux 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=20070727133641.GA29614@securecomputing.com \
    --to=david_mccullough@securecomputing.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.