linux-toradex.git/crypto/ablkcipher.c, branch v2.6.34

crypto: ablkcipher - Fix checkpatch errors

2010-02-16T12:23:37+00:00

Signed-off-by: Richard Hartmann 
Signed-off-by: Herbert Xu

crypto: blkcipher - Do not use eseqiv on stream ciphers

2009-08-14T12:58:18+00:00

Recently we switched to using eseqiv on SMP machines in preference
over chainiv.  However, eseqiv does not support stream ciphers so
they should still default to chainiv.

This patch applies the same check as done by eseqiv to weed out
the stream ciphers.  In particular, all algorithms where the IV
size is not equal to the block size will now default to chainiv.

Signed-off-by: Herbert Xu

crypto: skcipher - Change default sync geniv on SMP to eseqiv

2009-06-25T10:43:48+00:00

As it stands we use chainiv for sync algorithms and eseqiv for
async algorithms.  However, when there is more than one CPU
chainiv forces all processing to be serialised which is usually
not what you want.  Also, the added overhead of eseqiv isn't that
great.

Therefore this patch changes the default sync geniv on SMP machines
to eseqiv.  For the odd situation where the overhead is unacceptable
then chainiv is still available as an option.

Note that on UP machines chainiv is still preferred over eseqiv
for sync algorithms.

Signed-off-by: Herbert Xu

crypto: skcipher - Fix request for sync algorithms

2009-06-25T06:46:31+00:00

When a sync givcipher algorithm is requested, if an async version
of the same algorithm already exists, then we will loop forever
without ever constructing the sync version based on a blkcipher.

This is because we did not include the requested type/mask when
getting a larval for the geniv algorithm that is to be constructed.

Signed-off-by: Herbert Xu

crypto: skcipher - Avoid infinite loop when cipher fails selftest

2009-02-18T13:20:06+00:00

When an skcipher constructed through crypto_givcipher_default fails
its selftest, we'll loop forever trying to construct new skcipher
objects but failing because it already exists.

The crux of the issue is that once a givcipher fails the selftest,
we'll ignore it on the next run through crypto_skcipher_lookup and
attempt to construct a new givcipher.

We should instead return an error to the caller if we find a
givcipher that has failed the test.

Signed-off-by: Herbert Xu

[CRYPTO] skcipher: Move chainiv/seqiv into crypto_blkcipher module

2008-02-23T03:12:06+00:00

For compatibility with dm-crypt initramfs setups it is useful to merge
chainiv/seqiv into the crypto_blkcipher module.  Since they're required
by most algorithms anyway this is an acceptable trade-off.

Signed-off-by: Herbert Xu

[CRYPTO] api: Show async type

2008-01-10T21:16:56+00:00

This patch adds an async field to /proc/crypto for ablkcipher and aead
algorithms.

Signed-off-by: Herbert Xu

[CRYPTO] skcipher: Create default givcipher instances

2008-01-10T21:16:46+00:00

This patch makes crypto_alloc_ablkcipher/crypto_grab_skcipher always
return algorithms that are capable of generating their own IVs through
givencrypt and givdecrypt.  Each algorithm may specify its default IV
generator through the geniv field.

For algorithms that do not set the geniv field, the blkcipher layer will
pick a default.  Currently it's chainiv for synchronous algorithms and
eseqiv for asynchronous algorithms.  Note that if these wrappers do not
work on an algorithm then that algorithm must specify its own geniv or
it can't be used at all.

Signed-off-by: Herbert Xu

[CRYPTO] skcipher: Add skcipher_geniv_alloc/skcipher_geniv_free

2008-01-10T21:16:44+00:00

This patch creates the infrastructure to help the construction of givcipher
templates that wrap around existing blkcipher/ablkcipher algorithms by adding
an IV generator to them.

Signed-off-by: Herbert Xu

[CRYPTO] skcipher: Added geniv field

2008-01-10T21:16:43+00:00

This patch introduces the geniv field which indicates the default IV
generator for each algorithm.  It should point to a string that is not
freed as long as the algorithm is registered.

Signed-off-by: Herbert Xu