Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Herbert Xu 5cb1454b86 [CRYPTO] Allow multiple implementations of the same algorithm ... This is the first step on the road towards asynchronous support in the Crypto API. It adds support for having multiple crypto_alg objects for the same algorithm registered in the system. For example, each device driver would register a crypto_alg object for each algorithm that it supports. While at the same time the user may load software implementations of those same algorithms. Users of the Crypto API may then select a specific implementation by name, or choose any implementation for a given algorithm with the highest priority. The priority field is a 32-bit signed integer. In future it will be possible to modify it from user-space. This also provides a solution to the problem of selecting amongst various AES implementations, that is, aes vs. aes-i586 vs. aes-padlock. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>		2006-01-09 14:15:37 -08:00
..
aes.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
anubis.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
api.c	[CRYPTO] Allow multiple implementations of the same algorithm	2006-01-09 14:15:37 -08:00
arc4.c
blowfish.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
cast5.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
cast6.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
cipher.c	[CRYPTO] Fix boundary check in standard multi-block cipher processors	2005-09-06 14:49:44 -07:00
compress.c
crc32c.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
crypto_null.c
deflate.c
des.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
digest.c
hmac.c	[PATCH] Use sg_set_buf/sg_init_one where applicable	2005-10-30 11:19:43 +11:00
internal.h	[CRYPTO] Allow multiple implementations of the same algorithm	2006-01-09 14:15:37 -08:00
Kconfig	[PATCH] s390: cleanup Kconfig	2006-01-06 08:33:53 -08:00
khazad.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
Makefile
md4.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
md5.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
michael_mic.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
proc.c	[CRYPTO] Allow multiple implementations of the same algorithm	2006-01-09 14:15:37 -08:00
scatterwalk.c	[CRYPTO] Add plumbing for multi-block operations	2005-07-06 13:51:31 -07:00
scatterwalk.h	[CRYPTO] Add alignmask for low-level cipher implementations	2005-07-06 13:52:09 -07:00
serpent.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
sha1.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
sha256.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
sha512.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
tcrypt.c	[PATCH] s390: in-kernel crypto test vectors	2006-01-06 08:33:51 -08:00
tcrypt.h	[PATCH] s390: in-kernel crypto test vectors	2006-01-06 08:33:51 -08:00
tea.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
tgr192.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
twofish.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00
wp512.c	[CRYPTO] Use standard byte order macros wherever possible	2006-01-09 14:15:34 -08:00