Thread Links			Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

P1619.1: Problems with current test vectors

To: "SISWG" <stds-p1619@xxxxxxxx>
Subject: P1619.1: Problems with current test vectors
From: "Matt Ball" <matt.ball@xxxxxxxxxxx>
Date: Fri, 2 Jun 2006 15:17:15 -0600
List-Help: <http://listserv.ieee.org/cgi-bin/wa?LIST=STDS-P1619>, <mailto:LISTSERV@LISTSERV.IEEE.ORG?body=INFO STDS-P1619>
List-Owner: <mailto:STDS-P1619-request@LISTSERV.IEEE.ORG>
List-Subscribe: <mailto:STDS-P1619-subscribe-request@LISTSERV.IEEE.ORG>
List-Unsubscribe: <mailto:STDS-P1619-unsubscribe-request@LISTSERV.IEEE.ORG>
Sender: stds-p1619@xxxxxxxx
Thread-Index: AcaGievtlxEll1zmQfeYDnJBW/rs5A==
Thread-Topic: P1619.1: Problems with current test vectors

Hi Everyone,

It looks like there may be a problem with the GCM test vector #10. Within this test vector, it appears that the GHASH operation is padding the IV with an extra 128 zeros. According to the GCM spec, there should not be any pad if the IV is a multiple of 128 bits. Can anyone else confirm this?

I'm also wondering if there is a problem with the CCM test vector #8. Can anyone confirm this vector?

Thanks,

-Matt

Prev by Date: P1619: how serious is the leak of K2?
Next by Date: RE: Minutes from the P1619/1619.1 meetings on May 23rd, 2006
Prev by thread: Re: Complaints, Particularly about the Reflector
Next by thread: P1619.1: Incompatibility of GHASH function between GCM spec and SP 800-38D
Index(es):
- Date
- Thread