Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: linux-crypto@vger.kernel.org
Cc: Nico Erfurth <nico.erfurth@viprinet.com>,
	Simon Kissel <simon.kissel@viprinet.com>,
	Sebastian Siewior <bigeasy@breakpoint.cc>
Subject: RFC: kcrypto - (yet another) user space interface
Date: Thu, 10 Jun 2010 20:22:29 +0200	[thread overview]
Message-ID: <20100610182237.1B48E4CD45@orbit.nwl.cc> (raw)

Hello everyone,

my employer wants to have a lightweight, zero-copy user space interface
to the Crypto-API and I *think* I'm on the right way to realising this.

What I've got so far is just a proof-of-concept, tested only with
cbc(aes), merely as generic as I'd like it to be, but with zero-copy of
the actual data buffers (which reside in user space) and asynchronous
operation.

You can check it out via git://nwl.cc/~n0-1/kcrypto.git or simply have a
look at http://nwl.cc/cgi-bin/git/gitweb.cgi?p=kcrypto.git;a=summary. If
you do so, you may in return flame me as much as you like to. :)

I know that it's far from being ready for use as the sole crypto API
user space interface, but I'm convinced as well that it will never be
unless someone with Crypto-API skills points out at least the very basic
design flaws I've already created.

As this is not yet being used in production (of course), I'm totally
open to changes. So taking this as start of a collaborative project
would be perfect for me, too.

Greetings (and sorry for yet another interface approach),
Phil

             reply	other threads:[~2010-06-10 18:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 18:22 Phil Sutter [this message]
2010-06-10 21:14 ` RFC: kcrypto - (yet another) user space interface Sebastian Andrzej Siewior
2010-06-11  7:47   ` Nikos Mavrogiannopoulos
2010-06-11  9:08     ` Sebastian Andrzej Siewior
2010-06-11 10:51       ` Phil Sutter
2010-06-11 17:00   ` Phil Sutter
2010-06-11 17:00   ` Phil Sutter
2010-06-12 16:40 ` Uri Simchoni

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=20100610182237.1B48E4CD45@orbit.nwl.cc \
    --to=phil@nwl.cc \
    --cc=bigeasy@breakpoint.cc \
    --cc=linux-crypto@vger.kernel.org \
    --cc=nico.erfurth@viprinet.com \
    --cc=simon.kissel@viprinet.com \
    /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