<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/crypto, branch v2.6.16</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v2.6.16</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v2.6.16'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2006-02-08T01:56:35Z</updated>
<entry>
<title>[PATCH] remove bogus asm/bug.h includes.</title>
<updated>2006-02-08T01:56:35Z</updated>
<author>
<name>Al Viro</name>
<email>viro@zeniv.linux.org.uk</email>
</author>
<published>2005-12-15T06:07:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1b8623545b42c03eb92e51b28c84acf4b8ba00a3'/>
<id>urn:sha1:1b8623545b42c03eb92e51b28c84acf4b8ba00a3</id>
<content type='text'>
A bunch of asm/bug.h includes are both not needed (since it will get
pulled anyway) and bogus (since they are done too early).  Removed.

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[CRYPTO] cipher: Set alignmask for multi-byte loads</title>
<updated>2006-01-09T22:16:00Z</updated>
<author>
<name>Herbert Xu</name>
<email>herbert@gondor.apana.org.au</email>
</author>
<published>2006-01-07T05:38:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a429d2609c153882c421b067ad5ae5a38851459e'/>
<id>urn:sha1:a429d2609c153882c421b067ad5ae5a38851459e</id>
<content type='text'>
Many cipher implementations use 4-byte/8-byte loads/stores which require
alignment on some architectures.  This patch explicitly sets the alignment
requirements for them.

Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>[CRYPTO] api: Require block size to be less than PAGE_SIZE/8</title>
<updated>2006-01-09T22:15:58Z</updated>
<author>
<name>Herbert Xu</name>
<email>herbert@gondor.apana.org.au</email>
</author>
<published>2006-01-07T05:24:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=7302533aac2df321b76e8a113e5cfa529c825b09'/>
<id>urn:sha1:7302533aac2df321b76e8a113e5cfa529c825b09</id>
<content type='text'>
The cipher code path may allocate up to two blocks of data on the stack.
Therefore we need to place limits on the maximum block size.

Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>[CRYPTO] sha1: Fixed off-by-64 bug in sha1_update</title>
<updated>2006-01-09T22:15:56Z</updated>
<author>
<name>Herbert Xu</name>
<email>herbert@gondor.apana.org.au</email>
</author>
<published>2005-12-21T11:01:58Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=bcb0ad2b34daade529ce1f38eede0ea8b7309535'/>
<id>urn:sha1:bcb0ad2b34daade529ce1f38eede0ea8b7309535</id>
<content type='text'>
After a partial update, the done pointer is off to the right by 64 bytes.

Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>[CRYPTO] cipher: Align temporary buffer in cbc_process_decrypt</title>
<updated>2006-01-09T22:15:49Z</updated>
<author>
<name>Herbert Xu</name>
<email>herbert@gondor.apana.org.au</email>
</author>
<published>2005-11-29T11:04:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=827c3911d8551842900f44c9a139382bcae68e6e'/>
<id>urn:sha1:827c3911d8551842900f44c9a139382bcae68e6e</id>
<content type='text'>
Since the temporary buffer is used as an argument to cia_decrypt, it must be
aligned by cra_alignmask.  This bug was found by linux@horizon.com.

Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>[CRYPTO] sha1: Avoid shifting count left and right</title>
<updated>2006-01-09T22:15:46Z</updated>
<author>
<name>Nicolas Pitre</name>
<email>nico@cam.org</email>
</author>
<published>2005-11-13T00:17:33Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=fa9b98fdab5b57ecb4dd3d6c2489e262af458c44'/>
<id>urn:sha1:fa9b98fdab5b57ecb4dd3d6c2489e262af458c44</id>
<content type='text'>
This patch avoids shifting the count left and right needlessly for each
call to sha1_update().  It instead can be done only once at the end in
sha1_final().

Keeping the previous test example (sha1_update() successively called with
len=64), a 1.3% performance increase can be observed on i386, or 0.2% on
ARM.  The generated code is also smaller on ARM.

Signed-off-by: Nicolas Pitre &lt;nico@cam.org&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>[CRYPTO] sha1: Rename i/j to done/partial</title>
<updated>2006-01-09T22:15:44Z</updated>
<author>
<name>Nicolas Pitre</name>
<email>nico@cam.org</email>
</author>
<published>2005-11-12T23:59:54Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=9d70a6c86cd86e111291bd0d506028ecb9649923'/>
<id>urn:sha1:9d70a6c86cd86e111291bd0d506028ecb9649923</id>
<content type='text'>
This patch gives more descriptive names to the variables i and j.

Signed-off-by: Nicolas Pitre &lt;nico@cam.org&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>[CRYPTO] sha1: Avoid useless memcpy()</title>
<updated>2006-01-09T22:15:41Z</updated>
<author>
<name>Nicolas Pitre</name>
<email>nico@cam.org</email>
</author>
<published>2005-11-12T23:47:20Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=cfa8d17cc836905ad174fd924701b352585d62f1'/>
<id>urn:sha1:cfa8d17cc836905ad174fd924701b352585d62f1</id>
<content type='text'>
The current code unconditionally copy the first block for every call to
sha1_update().  This can be avoided if there is no pending partial block.
This is always the case on the first call to sha1_update() (if the length
is &gt;= 64 of course.

Furthermore, temp does need to be called if sha_transform is never invoked.
Also consolidate the sha_transform calls into one to reduce code size.

Signed-off-by: Nicolas Pitre &lt;nico@cam.org&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>[CRYPTO] Allow AES C/ASM implementations to coexist</title>
<updated>2006-01-09T22:15:39Z</updated>
<author>
<name>Herbert Xu</name>
<email>herbert@gondor.apana.org.au</email>
</author>
<published>2005-11-05T07:06:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=c8a19c91b5b488fed8cce04200a84c6a35c0bf0c'/>
<id>urn:sha1:c8a19c91b5b488fed8cce04200a84c6a35c0bf0c</id>
<content type='text'>
As the Crypto API now allows multiple implementations to be registered
for the same algorithm, we no longer have to play tricks with Kconfig
to select the right AES implementation.

This patch sets the driver name and priority for all the AES
implementations and removes the Kconfig conditions on the C implementation
for AES.

Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>[CRYPTO] Allow multiple implementations of the same algorithm</title>
<updated>2006-01-09T22:15:37Z</updated>
<author>
<name>Herbert Xu</name>
<email>herbert@gondor.apana.org.au</email>
</author>
<published>2005-11-05T05:58:14Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=5cb1454b862ab3040b78364d58330262fea1ddba'/>
<id>urn:sha1:5cb1454b862ab3040b78364d58330262fea1ddba</id>
<content type='text'>
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 &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
</feed>
