From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: [PATCH 00/16] crypto user configuration api
Date: Thu, 11 Aug 2011 13:26:03 +0200 [thread overview]
Message-ID: <20110811112603.GD16877@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
It is possible to update the priority of an algorithm by doing
crconf update driver "cbc(aes-generic)" type 4 priority 200
this updates the priority of this and all subsequent algorithms.
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.
Steffen
next reply other threads:[~2011-08-11 11:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 11:26 Steffen Klassert [this message]
2011-08-11 11:26 ` [PATCH 01/16] crypto: authenc - Don't multiply priorities Steffen Klassert
2011-08-15 7:19 ` Herbert Xu
2011-08-15 8:02 ` Steffen Klassert
2011-08-15 8:55 ` Herbert Xu
2011-08-15 10:08 ` Steffen Klassert
2011-08-16 12:30 ` Herbert Xu
2011-08-16 12:37 ` Steffen Klassert
2011-09-21 8:32 ` Steffen Klassert
2011-09-21 11:19 ` Herbert Xu
2011-08-11 11:27 ` [PATCH 02/16] crypto: Add a flag to identify crypto instances Steffen Klassert
2011-08-11 11:27 ` [PATCH 03/16] crypto: Add userspace configuration API Steffen Klassert
2011-08-11 11:28 ` [PATCH 04/16] crypto: Add a report function pointer to crypto_type Steffen Klassert
2011-08-11 11:29 ` [PATCH 05/16] crypto: Add userspace report for larval type algorithms Steffen Klassert
2011-08-11 11:29 ` [PATCH 06/16] crypto: Add userspace report for shash " Steffen Klassert
2011-08-11 11:30 ` [PATCH 07/16] crypto: Add userspace report for ahash " Steffen Klassert
2011-08-11 11:31 ` [PATCH 08/16] crypto: Add userspace report for blkcipher " Steffen Klassert
2011-08-11 11:31 ` [PATCH 09/16] crypto: Add userspace report for ablkcipher " Steffen Klassert
2011-08-11 11:32 ` [PATCH 10/16] crypto: Add userspace report for givcipher " Steffen Klassert
2011-08-11 11:32 ` [PATCH 11/16] crypto: Add userspace report for aead " Steffen Klassert
2011-08-11 11:33 ` [PATCH 12/16] crypto: Add userspace report for nivaead " Steffen Klassert
2011-08-11 11:34 ` [PATCH 13/16] crypto: Add userspace report for pcompress " Steffen Klassert
2011-08-11 11:34 ` [PATCH 14/16] crypto: Add userspace report for rng " Steffen Klassert
2011-08-11 11:35 ` [PATCH 15/16] crypto: Add userspace report for cipher " Steffen Klassert
2011-08-11 11:35 ` [PATCH 16/16] 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=20110811112603.GD16877@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).