All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arturas K <arturas@cerberis.soften.ktu.lt>
To: linux-crypto <linux-crypto@vger.kernel.org>
Subject: Ideas about Linux CryptoAPI userspace interface
Date: Thu, 10 Jul 2008 11:56:20 +0300	[thread overview]
Message-ID: <4875CEB4.0@cerberis.soften.ktu.lt> (raw)

Hi,

I run trough mailing list archives back to "ancient times" and from time 
to time there is a noise about the lack of cryptoapi userspace 
interface. There were just wining ( like me :D ), there were some 
attempts to do something reasonable/usable - but nothing reached 
mainline kernel...

I am not good at C or C++, so I will limit my contribution to some 
observations/ideas:

* in user space, openssl is the defacto cryptography provider. it even 
supports some hardware accelerators.

* the biggest desire for cryptoapi userspace interface comes from corner 
cases there kernel supports hardware acceleration, while openssl does 
not (like geode aes engine).

* for this interface to achieve reasonable adoption (succeed),
it must be exposed to openssl (aka some sort of openssl engine)

* there were attempts to port cryptodev, but filed due some gurus don't 
like the interface or the implementation or both.

* despite cryptodev is far from ideal interface - it already has support 
in openssl.

* unless there are willing ones to code on both (kernel and openssl), 
why not to properly implement cryptodev, mark it as highly experimental 
and add a fat warning what it will be tiered apart once someone comes 
with something better?

* I beleve, there will be more willing ones to create proper interface 
once there is actual user base instead of targeted one :)

---
teaser: I dream about cheap stock vga card acting as cryptography 
accelerator to feed 10G ethernet links at no cost :D
---
ArturasK.

                 reply	other threads:[~2008-07-10  9:18 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=4875CEB4.0@cerberis.soften.ktu.lt \
    --to=arturas@cerberis.soften.ktu.lt \
    --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.