public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David McCullough <davidm@snapgear.com>
To: cryptoapi@lists.logix.cz, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org
Subject: ocf-linux-20050324 - Asynchronous Crypto support for linux
Date: Thu, 24 Mar 2005 14:38:38 +1000	[thread overview]
Message-ID: <20050324043838.GA3124@beast> (raw)


Hi all,

The latest release of ocf-linux (20050324) is available for download
from the project page:

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

This release includes the following changes:

  * Added random number generator support for the hifn and safenet drivers.

  * Added patch for 2.4/2.6 kernels to allow RNG code to add entropy easily,
    implements add_true_randomness in both kernels.

  * First working version of the Public Key routines on the safenet.

  * Fixed a couple of nasty bugs in the existing key framework/driver support.

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-03-24  4:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050324043838.GA3124@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