On Fri, Apr 08, 2011 at 03:44:01PM -0500, Kim Phillips wrote:
> the following conditions in a driver setkey fail:
>
> if (!RTA_OK(rta, keylen))
> goto badkey;
>
> if (rta->rta_type != CRYPTO_AUTHENC_KEYA_PARAM)
> goto badkey;
>
> because testmgr ke
On Fri, 8 Apr 2011 08:55:33 +0800
Herbert Xu wrote:
> Kim Phillips wrote:
> >
> > I started to add test vectors from [1] to crypto/testmgr.c, but it
> > required that drivers not assume associated data, iv, and cipher data
> > were contiguous in memory, and since some of them do, I don't know if
Kim Phillips wrote:
>
> I started to add test vectors from [1] to crypto/testmgr.c, but it
> required that drivers not assume associated data, iv, and cipher data
> were contiguous in memory, and since some of them do, I don't know if
> such a contribution would be acceptable upstream.
Such drive
On Tue, 5 Apr 2011 15:04:35 +0200
Phil Sutter wrote:
> Hi,
>
> On Mon, Apr 04, 2011 at 08:35:43PM -0500, Kim Phillips wrote:
> > On Mon, 4 Apr 2011 19:03:37 +0200
> > Phil Sutter wrote:
> >
> > > I would like to enhance drivers/crypto/mv_cesa.c by an AEAD algorithm
> > > (at least authenc(hmac
Hi,
On Mon, Apr 04, 2011 at 08:35:43PM -0500, Kim Phillips wrote:
> On Mon, 4 Apr 2011 19:03:37 +0200
> Phil Sutter wrote:
>
> > I would like to enhance drivers/crypto/mv_cesa.c by an AEAD algorithm
> > (at least authenc(hmac(sha1),cbc(aes))), since the driver is able to do
> > both operations i
On Mon, 4 Apr 2011 19:03:37 +0200
Phil Sutter wrote:
> I would like to enhance drivers/crypto/mv_cesa.c by an AEAD algorithm
> (at least authenc(hmac(sha1),cbc(aes))), since the driver is able to do
> both operations in one go.
>
> Unfortunately, I have found little information about this task i
Dear list,
I would like to enhance drivers/crypto/mv_cesa.c by an AEAD algorithm
(at least authenc(hmac(sha1),cbc(aes))), since the driver is able to do
both operations in one go.
Unfortunately, I have found little information about this task in
Documentation/ or the web. Am I missing something?
