Add EAs for LMS & XMSS Sig Generation

Author: robertmclemons

input/gpcp.xml

@@ -4116,7 +4116,12 @@
 						ensure that hash-based signature algorithms do not reuse private keys</TSS>
 					<Guidance/>
 					<Tests>
-						Boilerplate text goes here <h:p/>
+						The following tests are conditional based upon the selections made in the SFR. The evaluator
+						shall perform the following test or witness respective tests executed by the developer. The tests
+						must be executed on a platform that is as close as practically possible to the operational platform
+						(but which may be instrumented in terms of, for example, use of a debug mode). Where the test
+						is not carried out on the TOE itself, the test platform shall be identified and the differences
+						between test environment and TOE execution environment shall be described.<h:p/>
 
 						<!-- RSA-PKCS Signature Generation   -->
 						<h:br/><h:b>RSA-PKCS Signature Generation </h:b><h:p/>
@@ -4214,6 +4219,37 @@
 						generate 10 test cases using random data. The evaluator shall compare the results against those
 						from a known-good implementation.<h:p/>
 
+						<!-- LMS Signature Genration  -->
+						<h:br/><h:b>LMS Signature Gneration </h:b><h:p/>
+						<h:table border="1">
+							<h:tr class="header" bgcolor="#cccccc">
+								<h:td valign="top">Identifier</h:td>
+								<h:td valign="top">Cryptogrphic Algorithm Parameters</h:td>
+								<h:td valign="top">Cryptographic Key Sizes</h:td>
+								<h:td valign="top">List of Standards</h:td>
+							</h:tr>
+							<h:tr>
+								<h:td valign="top">LMS</h:td>
+								<h:td valign="top">LMS</h:td>
+								<h:td valign="top">Private key size = [<h:b>selection:</h:b>
+									192 bits with [<h:b>selection:</h:b> SHA256/192, SHAKE256/192], 
+									256 bits with [<h:b>selection:</h:b> SHA-256, SHAKE256]] , 
+									Winternitz parameter = [<h:b>selection:</h:b> 1, 2, 4, 8], 
+									and tree height = [<h:b>selection:</h:b> 5, 10, 15, 20, 25]</h:td>
+								<h:td valign="top">RFC 8554 [LMS]<h:p/>
+										NIST SP 800-208 [parameters] </h:td>
+							</h:tr>
+						</h:table><h:p/>	
+						To test the TOE’s ability to generate cryptographic digital signature using LMS, the
+						evaluator shall perform the Algorithm Functional Test using the following input parameters:<h:ul>
+						<h:li>Hash algorithm [SHA-256/192, SHAKE256/192, SHA-256, SHAKE256]</h:li>
+						<h:li>Winterlitz [1, 2, 4, 8]</h:li>
+						<h:li>Tree height [5, 10, 15, 20, 25]</h:li></h:ul><h:p/>
+						<h:br/><h:b>Algorithm Functional Test</h:b><h:p/>
+						For each supported combination of the above parameters, the evaluator shall generate 10
+						signatures. The evaluator shall verify the correctness of the implementation by comparing values
+						generated by the TOE with those generated by a known good implementation using the same
+						input parameters.<h:p/>
 
 						<!-- ML-DSA Signature Generation  -->
 						<h:br/><h:b>ML-DSA Signature Generation</h:b><h:p/>
@@ -4249,8 +4285,9 @@
 						<h:br/><h:b>Known Answer Test for Rejection Cases</h:b><h:p/>
 						For each supported parameter set, the evaluator shall cause the TOE to generate signatures using
 						the data below and a deterministic seed of all 0’s. Correctness is determined by
-						comparing the hash of the resulting signature with the hash of the signature.<h:p/>
-						The values are defined as follows:<h:ul>
+						comparing the hash of the resulting signature with the hash in the fourth row 
+						for each corresponding test case below.<h:p/>
+						The test values are defined as follows:<h:ul>
 						<h:li><h:i>Seed</h:i> is the seed to generate the key pair (<h:i>pk, sk</h:i>)</h:li>
 						<h:li><h:i>Hash of keys</h:i> is computed by SHA-256(<h:i>pk</h:i>||<h:i>sk</h:i>)</h:li>
 						<h:li><h:i>Message</h:i> is the message to be signed</h:li>
@@ -4321,7 +4358,8 @@
 						<h:br/><h:b>Known Answer Test for Large Number of Rejection Cases (Total Rejection Count)</h:b><h:p/>
 						For each supported parameter set, the evaluator shall cause the TOE to generate signatures using
 						the data below and a deterministic seed of all 0’s. Correctness is determined by
-						comparing the hash of the resulting signature with the hash of the signature.<h:p/>
+						comparing the hash of the resulting signature with the hash in the fourth row
+						of the corresponding test case below.<h:p/>
 						<h:p/><h:b>ML-DSA-87 Test Cases for Total Rejection Count</h:b><h:p/>
 						<h:pre>
 		Test case 87-LN-01
@@ -4384,6 +4422,37 @@
 		Message: 		9831A830231A160B9847203341A5F30BF3E87A2A482AEEA6886315C92B5C4E4C
 		Hash of sig: 	46C669D2FEB643A38E54FF87B790CC33F44043A1B6B31DB9474D301328CA2A7F
 						</h:pre>
+						
+						<!-- XMSS Signature Gneration  -->
+						<h:br/><h:b>XMSS Signature Gneration</h:b><h:p/>
+						<h:table border="1">
+							<h:tr class="header" bgcolor="#cccccc">
+								<h:td valign="top">Identifier</h:td>
+								<h:td valign="top">Cryptogrphic Algorithm Parameters</h:td>
+								<h:td valign="top">Cryptographic Key Sizes</h:td>
+								<h:td valign="top">List of Standards</h:td>
+							</h:tr>
+							<h:tr>
+								<h:td valign="top">XMSS</h:td>
+								<h:td valign="top">XMSS</h:td>
+								<h:td valign="top">Private key size = [<h:b>selection:</h:b>
+									192 bits with [<h:b>selection:</h:b> SHA256/192, SHAKE256/192], 
+									256 bits with [<h:b>selection:</h:b> SHA-256, SHAKE256]] , 
+									and tree height = [<h:b>selection:</h:b> 10, 16, 20] </h:td>
+								<h:td valign="top">RFC 8391 [XMSS] <h:p/>
+										NIST SP 800-208 [parameters]</h:td>
+							</h:tr>
+						</h:table><h:p/>	
+						To test the TOE’s ability to generate digital signatures using XMSS, the evaluator
+						shall perform the XMSS Key Generation Test using the following input parameters:<h:ul>
+						<h:li>Hash algorithm [SHA-256/192, SHAKE256/192, SHA-256, SHAKE256]</h:li>
+						<h:li>Tree height [10, 16, 20]</h:li></h:ul><h:p/>
+						<h:br/><h:b>XMSS Key Generation Test</h:b><h:p/>
+						For each supported combination of the above parameters, the evaluator shall generate 10
+						signatures. The evaluator shall verify the correctness of the implementation by comparing values
+						generated by the TOE with those generated by a known-good implementation using the same
+						input parameters.<h:p/>
+												
 					</Tests>
 				</aactivity>
 			</f-element>