From 43a97878ce14b72f0981164f87f2e35e14151312 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 11:22:09 +0200 Subject: Adding upstream version 110.0.1. Signed-off-by: Daniel Baumann --- security/nss/cmd/pk11gcmtest/tests/README | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 security/nss/cmd/pk11gcmtest/tests/README (limited to 'security/nss/cmd/pk11gcmtest/tests/README') diff --git a/security/nss/cmd/pk11gcmtest/tests/README b/security/nss/cmd/pk11gcmtest/tests/README new file mode 100644 index 0000000000..9131b52314 --- /dev/null +++ b/security/nss/cmd/pk11gcmtest/tests/README @@ -0,0 +1,14 @@ +The GCM test vectors in this directory were downloaded from the NIST +Cryptographic Algorithm Validation Program (CAVP) website +(http://csrc.nist.gov/groups/STM/cavp/) on Mar 29, 2013 using the URL +http://csrc.nist.gov/groups/STM/cavp/documents/mac/gcmtestvectors.zip. + +The original test files are about 3 MB each, which are too big to +include in the NSS source tree. I observed the following patterns in +the test vectors: +1. Taglen changes in a cycle of 7: 128, 120, 112, 104, 96, 64, 32. +2. Then, AADlen changes in a cycle of 5: 0, 128, 160, 384, 720. + +To reduce the number of test vectors, I kept Taglen = 128, 96 from +each cycle of 7, and kept AADlen = 0, 720, 160 from each two cycles +of 10. -- cgit v1.2.3