, March 26, 2013 4:16 PM
To: Chaoxing Lin
Cc: linux-crypto@vger.kernel.org
Subject: Re: potential bug in GMAC implementation. not work in ESN mode
On 25.03.2013 18:12, Chaoxing Lin wrote:
> 2nd ping
>
> Nobody is maintaining crypto/gcm.c?
>
>
>
> -Original Message-----
Thanks Jussi, the patch fixes the problem.
You may commit it officially.
-Original Message-
From: Jussi Kivilinna [mailto:jussi.kivili...@iki.fi]
Sent: Tuesday, March 26, 2013 4:16 PM
To: Chaoxing Lin
Cc: linux-crypto@vger.kernel.org
Subject: Re: potential bug in GMAC implementation
2nd ping
Nobody is maintaining crypto/gcm.c?
-Original Message-
From: Chaoxing Lin
Sent: Friday, March 08, 2013 11:38 AM
To: 'linux-crypto@vger.kernel.org'
Subject: potential bug in GMAC implementation. not work in ESN mode
I was testing ipsec with GMAC and found that t
Ping Is there anyone looking at this potential bug??
-Original Message-
From: Chaoxing Lin
Sent: Friday, March 08, 2013 11:38 AM
To: 'linux-crypto@vger.kernel.org'
Subject: potential bug in GMAC implementation. not work in ESN mode
I was testing ipsec with GMAC and foun
> Seems that somehow I got confused, considering the "one/single-pass over
> data" description the same as "combined mode algorithm".
> I will post a fix or revert the patch if HW does not allow the correct
> behaviour.
Horia,
Do you plan to fix talitos driver to make it ESN capable in the nea
I was testing ipsec with GMAC and found that the rfc4543 GMAC implementation in
kernel software crypto work in "esp=aes256gmac-noesn!" mode.
It does not work in in "esp=aes256gmac-esn!" mode. The tunnel was established
but no data traffic is possible.
Looking at source code, I found this piece o
1. Can any one point me which RFC describe how exactly authencesn should work?
2. I test Ipsec with "esp=aes256-sha512-esn!" options and found compatibility
issue between kernel software crypto and talitos driver.
Talitos <>talitos Good
Soft crypto<>soft crypto
