All of lore.kernel.org
 help / color / mirror / Atom feed
From: David McCullough <david_mccullough@au.securecomputing.com>
To: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: ocf-linux-20060301 - Asynchronous Crypto support for linux
Date: Wed, 1 Mar 2006 14:26:32 +1000	[thread overview]
Message-ID: <20060301042632.GA17290@beast> (raw)


Hi all,

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

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

Mostly Openswan updates/cleanups and fixes in this release.

* Well tested on 2.4.32 and 2.6.15 with OpenSwan.
* hold locks for less time which improves
  the cryptosoft (software driver) interaction
  with the system.
* fix cryptodev to handle CRIOGET requests when
  application is chrooted.
* Bug fixes and improvements by Ronen Shitrit
  md5/sha processing in cryptosoft
  other typo/ordering problems in cryptosoft
  more error reporting to make debugging easier.
* updated openswan patch for 2.4.5rc5
* openswan support no longer requires any other crypto
  code (other than OCF) to be configured in.
* openswan code Q's state machine when in interrupt context
  and calls immediately when not (previously compile time
  determined)
* openssh uses OCF appropriately now if it supports required   
  algs
* updated ssl patch to openssl-0.9.8a
* no patch required for openssh anymore
* openssl md5/sha support by Ronen Shitrit

Cheers,
Davidm

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

             reply	other threads:[~2006-03-01  4:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-01  4:26 David McCullough [this message]
2006-03-31 13:36 ` ocf-linux-20060331 - 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=20060301042632.GA17290@beast \
    --to=david_mccullough@au.securecomputing.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 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.