From: Emanuele Cesena <emanuele.cesena@gmail.com>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: Userspace API /dev/crypto
Date: Wed, 13 Jan 2010 09:16:08 +0100 [thread overview]
Message-ID: <1263370568.2981.16.camel@ec> (raw)
In-Reply-To: <63386a3d1001121237s3e7c4b19g82ead5dc9dc7f63c@mail.gmail.com>
On Tue, 2010-01-12 at 21:37 +0100, Linus Walleij wrote:
> Has there been some/any progress on the userspace API since, or
> is this up for grabs?
>
As far as I know the most recent advance is:
"Add CryptoAPI User Interface Support v8"
http://marc.info/?t=122696476500001&r=1&w=2
I recommend you to read the whole thread, since in the end it appears
that new versions may move to a socket-oriented interface.
Finally, for OpenSSL, we are working on a pkcs11 engine so that there
will be no need to apply patches (and further we expect it could be used
with other apps too, like firefox). We hope to submit it soon.
Best regards,
--
Emanuele Cesena <emanuele.cesena@gmail.com>
Il corpo non ha ideali
prev parent reply other threads:[~2010-01-13 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 20:37 Userspace API /dev/crypto Linus Walleij
2010-01-13 8:16 ` Emanuele Cesena [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=1263370568.2981.16.camel@ec \
--to=emanuele.cesena@gmail.com \
--cc=linus.ml.walleij@gmail.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.