On Wed, 2010-08-25 at 08:20 +0200, Pavel Machek wrote:
> Hi!
>
> > Motivations for the extensions: governments are asking for more security
> > features in the operating systems they procure, which make user-space
> > implementations impractical. A few examples:
> >
> > * Advanced crypto module
Hi!
> Motivations for the extensions: governments are asking for more security
> features in the operating systems they procure, which make user-space
> implementations impractical. A few examples:
>
> * Advanced crypto module for OSPP for Common Criteria requires OS services
> implementing se
Eliminiate sparse warning during usage of crypto_shash_* APIs
error: bad constant expression
Allocate memory for shash descriptors once, so that we do not kmalloc/kfree it
for every signature generation (shash descriptor for md5 hash).
>From ed753861981decc44b5660b52268077b74f3 Mon Se
Eliminiate sparse warning during usage of crypto_shash_* APIs
error: bad constant expression
>From 952f73a6813c119f78c657bdb40d1ee741efb3c2 Mon Sep 17 00:00:00 2001
From: Shirish Pargaonkar
Date: Tue, 24 Aug 2010 09:49:57 -0500
Subject: [PATCH] eliminate sparse warnings during crypto_sha
On Mon, Aug 23, 2010 at 5:39 PM, Miloslav Trmac wrote:
> - "Shirish Pargaonkar" wrote:
>> Instead of determining and allocating a char array for use during usage of
>> crypto_shash_* calls, would like to instead dynamically
>> allocate (and free) storage for the duration of crypto calculation
