On Thu, Feb 20, 2020 at 11:15 AM Akhil Goyal wrote:
> > The NIST test vectors use the string 'PTlen' to denote text lengths
> > in case of encrypt & decrypt operations. So the same string need to be
> > used while parsing PT and CT.
> >
> > Fixes: 2adb3b4e7e54 ("examples/fips_validation: fix AES-G
On Thu, Feb 20, 2020 at 11:15 AM Akhil Goyal wrote:
> > The NIST test vectors use the string 'PTlen' to denote text lengths
> > in case of encrypt & decrypt operations. So the same string need to be
> > used while parsing PT and CT.
> >
> > Fixes: 2adb3b4e7e54 ("examples/fips_validation: fix AES-G
>
> The NIST test vectors use the string 'PTlen' to denote text lengths
> in case of encrypt & decrypt operations. So the same string need to be
> used while parsing PT and CT.
>
> Fixes: 2adb3b4e7e54 ("examples/fips_validation: fix AES-GCM cipher length
> parsing")
>
> Signed-off-by: Anoob Jo
Hi Fan, Akhil,
Can you review this patch? Without this change, the app would not work for
AES-GCM decrypt.
Thanks,
Anoob
> -Original Message-
> From: Anoob Joseph
> Sent: Tuesday, February 18, 2020 4:01 PM
> To: Marko Kovacevic ; Akhil Goyal
> ; David Marchand
> Cc: Anoob Joseph ; Fan
The NIST test vectors use the string 'PTlen' to denote text lengths
in case of encrypt & decrypt operations. So the same string need to be
used while parsing PT and CT.
Fixes: 2adb3b4e7e54 ("examples/fips_validation: fix AES-GCM cipher length
parsing")
Signed-off-by: Anoob Joseph
---
v2:
* Fix
5 matches
Mail list logo
