From: David McCullough <David_Mccullough@securecomputing.com>
To: Leo Yan <leoy@marvell.com>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: Questions For Linux Crypto API
Date: Wed, 14 Oct 2009 21:44:04 +1000 [thread overview]
Message-ID: <20091014114404.GA4435@securecomputing.com> (raw)
In-Reply-To: <EC64E4604C8024438259B683BB2514E1077BB35162@SC-VEXCH1.marvell.com>
Jivin Leo Yan lays it down ...
>
> Hi, all
>
> I am a newbie for Linux crypto.
> Recently I am warming up on Linux Crypto APIs and have some questions.
> Would you kindly give me some hints about it J ?
>
> 1. Does Linux Crypto API now support user space or not?
> I have googled the mailing list, and find some guys have committed some patches for it.
> But so far, in the Linux mainline (2.6.31) do not merge it.
> So Linux Crypto API will support user space or not?
Someone else will know more about this. People are working on it I think
but it's not there yet.
> 2. OCF has been ported to Linux, so will OCF integrate with Linux Crypto API or not?
OCF has a driver called cryptosoft that uses the linux crypto API.
> If Linux Crypto API will support the user space and provide the user space APIs, then OpenBSD Cryptographics Framework
> will directly use the Linux Crypto APIs or not? Otherwise
Once linux has it's own user space API you will not need OCF to provide one,
but you will need to add/wait for support for applications like openssl etc
to use the linux API.
Cheers,
Davidm
--
David McCullough, david_mccullough@securecomputing.com, Ph:+61 734352815
McAfee - SnapGear http://www.snapgear.com http://www.uCdot.org
next prev parent reply other threads:[~2009-10-14 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 7:51 Questions For Linux Crypto API Leo Yan
2009-10-14 11:44 ` David McCullough [this message]
2009-10-15 1:46 ` Leo Yan
2009-10-15 3:02 ` David McCullough
2009-10-15 5:12 ` Leo Yan
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=20091014114404.GA4435@securecomputing.com \
--to=david_mccullough@securecomputing.com \
--cc=leoy@marvell.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.