linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: [PATCH v2 00/15] crypto user configuration api
Date: Wed, 17 Aug 2011 14:08:59 +0200	[thread overview]
Message-ID: <20110817120859.GX16877@secunet.com> (raw)

This patchset adds a netlink based user configuration API for the crypto
layer, similar to the configuration API of xfrm.

The patchset is based on the current cryptodev-2.6 tree and also available
at branch 'crypto-user-config-api' of

git://git.kernel.org/pub/scm/linux/kernel/git/klassert/linux-stk.git

A userspace tool that makes use of the configuration API is temporarily
available at

http://www.kernel.org/pub/linux/kernel/people/klassert/crconf/ 

With this it is possible to instantiate certain algorithms by doing

crconf add driver "cbc(aes-generic)" type 4

or

crconf add driver "cbc(aes-generic)" type 4 priority 100

To remove a (form templates build and unused) algorithm with all subsequent
algorithms do

crconf del driver "cbc(aes-generic)" type 4

Finally it is possible to print the instantiated crypto algorithms
similar to /proc/crypto by doing

crconf show all

This prints the algorithm informations of all instantiated algorithms
as long as the information fits into a netlink message.

Changes from v1:

- Removed the priority update functions.
- Fix algorithm information printing when build as module.
- Update the crconf tool according to the kernel changes.

Steffen

             reply	other threads:[~2011-08-17 12:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-17 12:08 Steffen Klassert [this message]
2011-08-17 12:09 ` [PATCH v2 01/15] crypto: Add a flag to identify crypto instances Steffen Klassert
2011-08-17 12:10 ` [PATCH v2 02/15] crypto: Add userspace configuration API Steffen Klassert
2011-08-22  6:59   ` Herbert Xu
2011-08-29  8:18     ` Steffen Klassert
2011-09-02  3:50       ` Herbert Xu
2011-08-17 12:10 ` [PATCH v2 03/15] crypto: Add a report function pointer to crypto_type Steffen Klassert
2011-08-17 12:11 ` [PATCH v2 04/15] crypto: Add userspace report for larval type algorithms Steffen Klassert
2011-08-17 12:12 ` [PATCH v2 05/15] crypto: Add userspace report for shash " Steffen Klassert
2011-08-17 12:12 ` [PATCH v2 06/15] crypto: Add userspace report for ahash " Steffen Klassert
2011-08-17 12:13 ` [PATCH v2 07/15] crypto: Add userspace report for blkcipher " Steffen Klassert
2011-08-17 12:13 ` [PATCH v2 08/15] crypto: Add userspace report for ablkcipher " Steffen Klassert
2011-08-17 12:14 ` [PATCH v2 09/15] crypto: Add userspace report for givcipher " Steffen Klassert
2011-08-17 12:15 ` [PATCH v2 10/15] crypto: Add userspace report for aead " Steffen Klassert
2011-08-17 12:15 ` [PATCH v2 11/15] crypto: Add userspace report for nivaead " Steffen Klassert
2011-08-17 12:16 ` [PATCH v2 12/15] crypto: Add userspace report for pcompress " Steffen Klassert
2011-08-17 12:16 ` [PATCH v2 13/15] crypto: Add userspace report for rng " Steffen Klassert
2011-08-17 12:17 ` [PATCH v2 14/15] crypto: Add userspace report for cipher " Steffen Klassert
2011-08-17 12:18 ` [PATCH v2 15/15] crypto: Add userspace report for compress " Steffen Klassert

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=20110817120859.GX16877@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=herbert@gondor.apana.org.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).