Repository navigation
Releases
RELEASE/v1.1.0.43
Demo: 2026-7-20
Prod: 2026-8-12
- New Algorithms (Demo only):
- ctrDRBG / SP800-90Ar1, hashDRBG / SP800-90Ar1, and hmacDRBG / SP800-90Ar1 (Algo / Revision) - The new ctrDRBG, hashDRBG, and hmacDRBG SP800-90Ar1 testing revisions differ from their 1.0 counterparts in the following ways:
- the returnedBitsLen registration is changed from being an integer type to being a domain type
- the ctrDRBG / 1.0 testing does not support variable length counter fields. Variable length counter fields were introduced in SP 800-90Ar1. The new ctrDRBG SP800-90Ar1 testing revision adds the new counterFieldLen registration property.
- requested in usnistgov/ACVP#1622
- ML-KEM / encapDecap / FIPS203-tr1 and ML-DSA / sigGen / FIPS204-tr1 (Algo / Mode / Revision) - The new ML-KEM encapDecap and ML-DSA sigGen testing revisions add the possibility to use the seed, expanded private key format, or both in testing. This is accomplished by a new registration property: keyFormats.
- LMS / sigGen / SP800-208 and LMS / sigVer / SP800-208 (Algo / Mode / Revision) - The new LMS sigGen and LMS sigVer testing revisions add the messageLength registration property and allow IUTs to specify supported message lengths.
- The new LMS sigGen testing revision also adds checks for
Quniqueness across signatures generated from the same tree.
- The new LMS sigGen testing revision also adds checks for
- ctrDRBG / SP800-90Ar1, hashDRBG / SP800-90Ar1, and hmacDRBG / SP800-90Ar1 (Algo / Revision) - The new ctrDRBG, hashDRBG, and hmacDRBG SP800-90Ar1 testing revisions differ from their 1.0 counterparts in the following ways:
- RSA keyGen FIPS186-5
- Addresses an issue where the validation incorrectly specified test case failures when
"isSample" : trueand"infoGeneratedByServer" : false. - #450
- Addresses an issue where the validation incorrectly specified test case failures when
- KDF SPDM 1.0
- Removes the thLen registration property and fixes an issue with the v1.3 SPDM testing.
- usnistgov/ACVP#1631
- ConditioningComponents / BlockCipher_DF / v1.0 - corrects an issue where
outputLengthwas missing from the prompt. - ML-DSA sigGen FIPS204 and ML-DSA sigVer FIPS204 - resolves an issue where registrations that used incorrect casing for the externalMu property were not rejected by the ACVTS.
- ML-DSA sigVer FIPS204 - Fixes the
ModifyZdisposition so that the modification matches the disposition. The issue was that the location being modified was not within z. - ML-KEM / encapDecap / FIPS203 - Fixes a bug where test cases for the
encapsulationKeyCheckfunction includedekthat were longer than intended. - ctrDRBG / 1.0 - addresses an issue with the implementation of CTR_DRBG_Update() that was present in the ctrDRBG / 1.0 testing where
V = (V+1) mod 2^blocklenwould be calculated incorrectly with a probability of 1 in 2^128. - LMS sigGen 1.0 - Adds checks for
Quniqueness across signatures generated from the same tree. - XECDH / keyVer / RFC7748 - removes a test scenario from the X448 testing that only applies to X25519
Prod Update: 2026-08-17
- The ML-KEM / encapDecap / FIPS203-tr1 and ML-DSA / sigGen / FIPS204-tr1 algorithms are enabled on ACVTS Prod.
Prod Update: 2026-08-20
- The KDF SPDM, ctrDRBG / SP800-90Ar1, hashDRBG / SP800-90Ar1, hmacDRBG / SP800-90Ar1, LMS / sigGen / SP800-208 and LMS / sigVer / SP800-208 algorithms are enabled on ACVTS Prod.
v1.1.0.42
Demo: 2026-4-16
Prod: 2026-6-1
- New Algorithms (Demo only):
- KDF / SPDM / 1.0 (Algo / Mode / Revision) - testing for the SPDM KDF as described in DSP0274, section 12 (see https://www.dmtf.org/dsp/dsp0274).
- The CAVP would like to thank Thomas Bowen for providing the following Pull Request which was instrumental in adding SPDM testing to ACVTS: #405.
- NOTE: Until the KDF SPDM 1.0 documentation becomes available and is posted to https://pages.nist.gov/ACVP/#supported, please consult the sample JSON files located at https://github.com/usnistgov/ACVP-Server/tree/master/gen-val/json-files/KDF-SPDM-1.0/
- XECDH / keyGen / RFC7748, XECDH / keyVer / RFC7748, and XECDH / SSC / RFC7748 (Algo / Mode / Revision) - testing for the curve25519 and curve448 elliptic curves as defined in RFC 7748.
- The CAVP would like to thank Joachim Vandersmissen who contributed the XECDH / RFC7748 testing. See #391.
- KDF / SPDM / 1.0 (Algo / Mode / Revision) - testing for the SPDM KDF as described in DSP0274, section 12 (see https://www.dmtf.org/dsp/dsp0274).
- Ascon AEAD128 SP800-232
- Fixes bit-oriented tags on Ascon AEAD128 by reversing the bit order on incomplete bytes in the tag.
- Adds encryption and decryption tests to Ascon AEAD128 for tags that are not the minimum or maximum of the domain.
- Addresses #434
- HMAC-SHA* 1.0 algorithms - Fixes HMAC 1.0 MAC validation for the scenario where the
macsupplied result is a different length than expected. Previously, if the suppliedmacwas longer than the requestedmacLen, assuming the full value was still correct, this was accepted by ACVTS. Now it will be rejected. The suppliedmacmust be exactly themacLenrequested. - RSA keyGen FIPS186-5
- Improves error handling for when missing or invalid values are supplied for bitLens in the response.
- Fixes "General exception. Contact service provider" error that occurs when
infoGeneratedByServer = false, isSample = false, randPQ = ProbableWithProvableAux
- RSA signaturePrimitive 1.0 - fixes a Null Reference Exception that occurs when validating a response where the supplied value for "testPassed" is "true", but "false" is expected.
- Improves error handling for the scenario where a Domain type is expected, but omitted from a registration.
v1.1.0.41
Demo: 2025-10-31
Prod: 2025-11-12
- New Algorithms (Demo only):
- SHAKE-128 FIPS202 and SHAKE-256 FIPS202 - This new testing revision for the SHAKE algorithms adds support for IUTs to supply their supported messageLengths. The FIPS202 testing revision omits MCT tests, combines AFT and VOT tests, and, if supported by the IUT, tests message lengths where the bitlength of the trailer (4-bits) appended to the message exceeds the block size.
- NOTE: SHAKE-128 FIPS202 and SHAKE-256 FIPS202 will initially only be enabled on ACVTS Demo. SHAKE-128 FIPS202 and SHAKE-256 FIPS202 will not be enabled on ACVTS Prod initially. SHAKE-128 FIPS202 and SHAKE-256 FIPS202 will be enabled on ACVTS Prod only after they have been tested sufficiently on ACVTS Demo.
- SHAKE-128 FIPS202 and SHAKE-256 FIPS202 - This new testing revision for the SHAKE algorithms adds support for IUTs to supply their supported messageLengths. The FIPS202 testing revision omits MCT tests, combines AFT and VOT tests, and, if supported by the IUT, tests message lengths where the bitlength of the trailer (4-bits) appended to the message exceeds the block size.
- SHAKE-128 1.0 and SHAKE-256 1.0 - Updates SHAKE 1.0 testing to honor "inEmpty": false, i.e., to not include a test for 0-bit messages when "inEmpty": false.
- ACVP-AES-CCM 1.0 - Updates testing to record the correct value for ivLen in the prompt, i.e., 104 bits, when the "ECMA" conformance is tested.
- KAS-ECC Sp800-56Ar3 and KAS-FFC Sp800-56Ar3 - Fixes bug where, when different KAS schemes used different
Lvalues, there was a chance that theLvalue from one scheme would be applied to the other schemes. - RSA keyGen FIPS186-5
- Addresses issues related to
pMod8andqMod8- Fixes issue where
pMod8andqMod8values supplied in the registration were not being used in probable-based prime generation tests. - Adds parameter validation to ensure
pMod8andqMod8are in {0, 1, 3, 5, 7}. - Adds
pMod8andqMod8to the prompt files for groups where it is relevant. - #411
- Fixes issue where
- Updates testing to provide a meaningful error message when randPQ is probable and primeTest is missing from the registration.
- Addresses issues related to
- RSA sigVer FIPS186-5 - improves error handling to provide a meaningful error message when maskFunction is omitted.
- ACVP-AES-KW 1.0, ACVP-AES-KWP 1.0, and ACVP-TDES-KW 1.0 - Addresses issue where the maximum payload length of 4096 was not being enforced.
- ACVP-AES-XTS 2.0
- Fixes bug around not allowing payload sizes that are exact multiples of data unit sizes and another around not allowing payload sizes that are smaller than the data unit size
- Fixes an issue where the values supplied for dataUnitLength were not being displaying on the csrc.nist.gov algorithm certificates.
- SHA3-* 2.0, SHAKE-128 1.0, SHAKE-256 1.0 - resolves issue where the invalid registration property "digestSize" was being accepted.
- SHA3-* 2.0 - adds tests for message lengths where the bitlength of the trailer (2-bits) appended to the message exceeds the block size.
- EDDSA sigGen 1.0 - corrects typo in error message.
- /health endpoint - Addresses issue where the health endpoint would sometimes omit the "status" key and value.
- ML-DSA sigGen FIPS204
- Reduces the number of test cases for ML-DSA sigGen corner cases. This change is in support of a fix for a bug affecting
ML-DSA-65andML-DSA-87sigGen corner cases. The actual fix for theML-DSA-65andML-DSA-87sigGen corner cases will be applied separately from this release. It involves an update to the test "pool" data that is used to create theML-DSA-65andML-DSA-87sigGen corner test cases. - https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/6U34L4ISYzk
- Reduces the number of test cases for ML-DSA sigGen corner cases. This change is in support of a fix for a bug affecting
- Sample JSON files
2025-12-12 Prod Update
On 2025-12-12 the following algorithms were enabled on ACVTS Prod:
- SHAKE-128 / FIPS202 (Algo / Revision)
- SHAKE-256 / FIPS202
v1.1.0.40
Demo: 2025-6-11
Prod: 2025-6-23
IMPORTANT: PLEASE NOTE THE IMPACT OF THIS RELEASE'S DEPLOYMENT TO THE ACVTS DEMO ENVIRONMENT FOR ML-KEM / encapDecap / FIPS203 TEST VECTORS THAT WERE GENERATED BY RELEASES PRIOR TO RELEASE V1.1.0.40 WITH "isSample": false. SEE THE ML-KEM / encapDecap / FIPS203 BULLET BELOW FOR THIS INFORMATION.
- New Algorithms:
- Adds HMAC revision 2.0 testing, e.g., HMAC-SHA-1 / 2.0, HMAC-SHA2-224 / 2.0, HMAC-SHA2-256 / 2.0, etc. (Algo / Revision) - Adds a new revision 2.0 to HMAC that adds
msgLenas a registration property and moves themsgLen,keyLenandmacLenproperties into the test case instead of the test group for the prompt. This reduces the number of test groups and test cases.
- Adds HMAC revision 2.0 testing, e.g., HMAC-SHA-1 / 2.0, HMAC-SHA2-224 / 2.0, HMAC-SHA2-256 / 2.0, etc. (Algo / Revision) - Adds a new revision 2.0 to HMAC that adds
- ACVP-AES-XTS / "2.0" (Algo / Revision) - Updates the testing to reverse the assumption that "all lengths listed by the payloadLen property are also valid data unit lengths." The updated assumption is that "all lengths listed by the dataUnitLen property are also valid payload lengths. As such, the values for the payloadLen property MUST include all dataUnitLen values."
- KMAC-128 and KMAC-256 - Updates testing to ensure both block-aligned and non-block-aligned key sizes are tested.
- ML-KEM / encapDecap / FIPS203 (Algo / Mode / Revision)
- Adds "encapsulationKeyCheck" and "decapsulationKeyCheck" as functions for ML-KEM Encap/Decap FIPS203 to exercise an implementation's capability to perform the Encapsulation Key Check in FIPS 203 Section 7.2 and the Decapsulation Key Check in FIPS 203 Section 7.3. These tests are only included if the appropriate function is present in the registration. They operate by providing a valid or invalid key and expecting the IUT to return a
truefor a valid key orfalsefor an invalid key. - The test group and test case formats for decapsulation test groups and test cases are updated so that
dkis provided at the test case level rather than at the test group level.- IMPLICATIONS FOR ACVTS DEMO RELEASE: test vectors that were generated by releases prior to v1.1.0.40 with "isSample": false will fail on validation as a result of this update and will need to be regenerated using ACVTS release v1.1.0.40 or higher. CAVP will implement a workaround as part of the v1.1.0.40 release's deployment to Prod so that test vectors will not need to be regenerated on Prod.
- Adds "encapsulationKeyCheck" and "decapsulationKeyCheck" as functions for ML-KEM Encap/Decap FIPS203 to exercise an implementation's capability to perform the Encapsulation Key Check in FIPS 203 Section 7.2 and the Decapsulation Key Check in FIPS 203 Section 7.3. These tests are only included if the appropriate function is present in the registration. They operate by providing a valid or invalid key and expecting the IUT to return a
- Ascon / AEAD128 / SP800-232, Ascon / Hash256 / SP800-232, Ascon / XOF128 / SP800-232, and Ascon / CXOF128 / SP800-232 (Algo / Mode / Revision)
- Updates property names to more closely match those of other algorithms supported by ACVTS.
- Fixes issues with domains not being respected by increment.
- Adds decryption failure test cases to check the authentication element of the AEAD128 mode.
- Updates the minimum tag length for Ascon / AEAD128 / SP800-232 from 64 bits to 32 bits
- Fixes a bug in the Ascon / AEAD128 / SP800-232 nonceMasking encrypt tests
- Addresses: #1568, usnistgov/ACVP#1570, usnistgov/ACVP#1571, usnistgov/ACVP#1572, usnistgov/ACVP#1573, usnistgov/ACVP#1574, usnistgov/ACVP#1575, usnistgov/ACVP#1576, and usnistgov/ACVP#1577
- Updates ACVTS to provide a meaningful error message when an ACVTS Prod registration contains
"isSample" : true. NOTE: the only valid value for "isSample" for an ACVTS Prod registration isfalse.- Addresses #393
2025-7-25 Prod Update
On 2025-7-25 the following algorithms were enabled on ACVTS Prod:
- HMAC-SHA-1 / 2.0 (Algo / Revision)
- HMAC-SHA2-224 / 2.0
- HMAC-SHA2-256 / 2.0
- HMAC-SHA2-384 / 2.0
- HMAC-SHA2-512 / 2.0
- HMAC-SHA2-512/224 / 2.0
- HMAC-SHA2-512/256/ 2.0
- HMAC-SHA3-224 / 2.0
- HMAC-SHA3-256 / 2.0
- HMAC-SHA3-384 / 2.0
- HMAC-SHA3-512 / 2.0
2025-8-13 Prod Update
On 2025-8-13 the following algorithms were enabled on ACVTS Prod:
- Ascon / AEAD128 / SP800-232 (Algo / Mode / Revision)
- Ascon / Hash256 / SP800-232
- Ascon / XOF128 / SP800-232
- Ascon / CXOF128 / SP800-232
v1.1.0.39
Demo: 2025-4-23
Prod: 2025-5-9
- New Algorithms (Demo only):
- Ascon / AEAD128 / SP800-232, Ascon / Hash256 / SP800-232, Ascon / XOF128 / SP800-232, and Ascon / CXOF128 / SP800-232 - (Algo / Mode / Revision) - testing for Ascon-based family of algorithms based on the SP 800-232 Initial Public Draft.
- ML-DSA sigGen FIPS204 - Adds two ML-DSA Signature Generation corner cases. The first corner case assumes an implementation strictly adheres to the pseudocode in FIPS 204 and tests the four defined rejection paths. The second corner case tests whether an IUT is able to compute a signature when a significant number of rejections, specifically, 64, have occurred. See https://pages.nist.gov/ACVP/draft-celi-acvp-ml-dsa.html#name-ml-dsa-siggen-test-types for more information. These corner case tests are only available for IUTs that advertise support for: 1) testing the internal signature interface; 2) being able to compute mu internal to the algorithm implementation (some implementations may not be able to compute mu internally. They may require mu to be pre-computed and passed as an argument to the implementation.); 3) deterministic signature generation; and 4) must support computing signatures of messages that are 256 bits in length.
- Sample JSON files
- Updates the LMS keyGen 1.0, LMS sigGen 1.0, and LMS sigVer 1.0 sample JSON files to include test cases for all LMS modes instead of for a representative subset of the modes.
- DetECDSA sigGen FIPS186-5
- addresses an issue where the signature values recorded in the sample json files were incorrect. The per-message secret numbers used to create the signatures were being generated incorrectly.
- adds extra tests to the sample JSON files that purposefully use small values for the private key. The use of small values for the private keys forces implementations to demonstrate that the private keys are being converted to octet strings and padded to the correct lengths as part of computing the per-message secret number.
- #377
- ECDSA sigGen 1.0, ECDSA sigGen FIPS186-5, and DetECDSA sigGen FIPS186-5 - Addresses issue where values used for k were not included in the InternalProjection json files
- Adds two new implementation/module types: softwarehybrid and firmwarehybrid. See https://pages.nist.gov/ACVP/draft-fussell-acvp-spec.html#name-modules.
v1.1.0.38
Demo: 2025-01-14
Prod: 2025-01-31
ATTENTION: THIS RELEASE INTRODUCES SEVERAL IMPORTANT CHANGES AND INCOMPATIBILITIES RELATED TO THE EDDSA sigGen 1.0, SLH-DSA, ML-DSA, AND ML-KEM ALGORITHM TESTING. PLEASE READ THE RELEASE NOTES THAT FOLLOW CAREFULLY. IF YOU HAVE ANY QUESTIONS, FEEL FREE TO OPEN A NEW ISSUE AT https://github.com/usnistgov/ACVP/issues OR https://github.com/usnistgov/ACVP-Server/issues.
- EDDSA sigGen 1.0
- Testing is updated to make the contextLength registration property mandatory, when applicable, i.e., when curve contains ED-448 or preHash == true. contextLength is now also disallowed when not applicable, i.e., when curve == ED-25519 and preHash == false.
- Addresses #359
- Fixes an issue where test cases could include contexts with lengths that are unsupported as per the supplied registration.
- Testing is updated to make the contextLength registration property mandatory, when applicable, i.e., when curve contains ED-448 or preHash == true. contextLength is now also disallowed when not applicable, i.e., when curve == ED-25519 and preHash == false.
- ML-DSA sigGen FIPS204, ML-DSA sigVer FIPS204, SLH-DSA sigGen FIPS205, and SLH-DSA sigVer FIPS205 - Updates ML-DSA and SLH-DSA sign and verify testing to include tests for the external interfaces defined in FIPS 204 Section 5 and FIPS 205 Section 10. Also updates the ML-DSA sign and verify testing to support externally computed mu as allowed in the FIPS 204 comments for Algorithm 7 Line 6 and Algorithm 8 Line 7.
- Please note that adding support for ML-DSA and SLH-DSA external interface testing changes the format of ML-DSA and SLH-DSA sigGen and sigVer registrations significantly. Please consult the ML-DSA and SLH-DSA algorithm specifications at https://pages.nist.gov/ACVP/#supported and the sample test vectors at https://github.com/usnistgov/ACVP-Server/tree/master/gen-val/json-files for the updated formats for ML-DSA and SLH-DSA sigGen and sigVer registrations.
- Please also note that any ML-DSA and SLH-DSA sigGen and sigVer test vectors that were generated on an ACVTS release prior to v1.1.0.38 cannot have their responses submitted for validation using an ACVTS release >= v1.1.0.38. Any such test vectors will need to be abandoned and new test vectors created.
- ML-KEM encapDecap FIPS203 - ML-KEM encapDecap FIPS203 decapsulation test vectors that were generated on an ACVTS release prior to v1.1.0.38 cannot have their responses submitted for validation using an ACVTS release >= v1.1.0.38. Any such test vectors will need to be abandoned and new test vectors created.
- SHAKE-128 1.0 and SHAKE-256 1.0 - Corrects issue where message digest values were computed incorrectly for non-byte-aligned outputLens. (Note that the completeness of this fix is still being investigating relative to some recent feedback.)
v1.1.0.37
Demo: 2024-11-5
Prod: 2024-11-16
- KDA HKDF SP800-56Cr1 and KDA HKDF SP800-56Cr2 - Updates testing to provide an error message when a registration is missing the required macSaltMethods property.
- TupleHash-128 and TupleHash-256 - Updates testing to include the hexCustomization property in the prompt
- sample JSON files:
- Removes sample SHA3-224-1.0 JSON files as the SHA3 1.0 testing is deprecated.
- Updates the SLH-DSA keyGen FIPS205, SLH-DSA sigGen FIPS205, and SLH-DSA sigVer FIPS205 sample JSON files to include test cases for all SLH-DSA parameter sets instead of for a representative subset of the parameter sets.
v1.1.0.36
Demo: 2024-10-7
Prod: 2024-10-11
- ECDSA sigGen FIPS186-5 and ECDSA sigVer FIPS186-5 - updates testing to use the correct output lengths when SHAKE128 and SHAKE256 are used.
- ECDSA sigGen 1.0 and ECDSA sigGen FIPS186-5 - improves error handling to provide error messages that are more descriptive.
- ECDSA sigVer 1.0 and ECDSA sigVer FIPS186-5 - removes support for the componentTest registration property.
- EDDSA sigGen FIPS186-5 - fixes an issue where test cases with non-zero length contexts were provided for IUTs that indicated support for "contextLength": [0].
- sample JSON files - corrects an issue where the SHA2-384, SHA2-512, SHA2-512-224, and SHA2-512-256 sample JSON files were computed using the SHA2-256 algorithm.
- KDA HKDF Sp800-56Cr2 and KDA TwoStep Sp800-56Cr2 - updates error messages to use the correct casing when referring to the usesSharedHybridSecret and auxSharedSecretLen registration properties.
- ACVP-AES-CCM - updates testing to allow 96-bit nonce lengths.
- ACVP-AES-XTS 2.0 - Addresses issue where test cases sometimes used an invalid Data Unit Sequence Number or sequenceNumber.
- RSA sigGen FIPS186-5 and RSA sigVer FIPS186-5 - updates testing to reject registrations that include maskFunction or saltLen for pkcs1v1.5.
- RSA sigGen FIPS186-5 - updates testing to no longer include the maskFunction and saltLen properties for the pkcs1v1.5 tests.
v1.1.0.35
Demo: 2024-6-14
Prod: 2024-7-23
- New Algorithms:
- SLH-DSA keyGen FIPS205, SLH-DSA sigGen FIPS205 and SLH-DSA sigVer FIPS205 - adds testing for Stateless Hash-Based Digital Signature Standard algorithms.
- ML-KEM keyGen FIPS 203 - updates testing to include domain separation. Domain separation for key generation did not appear in the FIPS 203 Initial Public Draft, but was added in the final published version of FIPS 203. See FIPS 203 Appendix C.2. (https://csrc.nist.gov/pubs/fips/203/final)
- ML-DSA keyGen FIPS 204 - updates testing to include domain separation. Domain separation for key generation did not appear in the FIPS 204 Initial Public Draft, but was added in the final published version of FIPS 204. See FIPS 204 Appendix D.3. (https://csrc.nist.gov/pubs/fips/204/final)
- ECDSA sigVer FIPS186-5 - addresses issue where test groups using SHAKE were incorrectly identified as being component tests.
- EDDSA sigGen FIPS186-5 - Adds a check to enforce the requirement that at least one of the the "pure" or "preHash" registration properties must be set to "true."
- RSA keyGen FIPS186-5
- addresses an issue where submitting the response resulted in "General exception. Contact service provider."
- updates testing to indicate which hash algorithm is used for probableWithProvableAux
- GenValAppRunner sample application - changes the flag used to specify the "answer" file from "-a" to "-n" as .NET now uses "-a" to specify architecture.
2024-8-13 Prod Update
On 2024-8-13 the following algorithms were enabled on ACVTS Prod:
- SLH-DSA keyGen FIPS205, SLH-DSA sigGen FIPS205 and SLH-DSA sigVer FIPS205
- ML-DSA keyGen FIPS204, ML-DSA sigGen FIPS204 and ML-DSA sigVer FIPS204
- ML-KEM keyGen FIPS203 andML-KEM encapDecap FIPS203
v1.1.0.34
Demo: 2024-4-1
Prod: 2024-6-6
- New Algorithms (Demo only):
- ML-DSA keyGen FIPS204, ML-DSA sigGen FIPS204 and ML-DSA sigVer FIPS204 - testing for Module-Lattice-Based Digital Signature Standard based on the FIPS 204 Initial Public Draft.
- NOTE: The ML-DSA testing was updated on 5/23/24 to incorporate updates to the FIPS 204 draft and to add the messageLength registration property to ML-DSA sigGen FIPS204. For more information, refer to the comments included in the following discussion: #332.
- ML-KEM encapDecap FIPS203 and ML-KEM keyGen FIPS203 - testing for Module-Lattice-Based Key-Encapsulation Mechanism based on the FIPS 203 Initial Public Draft
- ML-DSA keyGen FIPS204, ML-DSA sigGen FIPS204 and ML-DSA sigVer FIPS204 - testing for Module-Lattice-Based Digital Signature Standard based on the FIPS 204 Initial Public Draft.
- AES-GCM-SIV - addresses an issue where, when an IUT reports that a decryption operation which should fail has failed, the server marks the IUT's result as being incorrect. Fix provided by jvdsn at #308.
- ECDSA keyGen FIPS186-5, ECDSA keyVer FIPS186-5, ECDSA sigGen FIPS186-5, ECDSA sigVer FIPS186-5, DetECDSA sigGen FIPS186-5 - adds testing for the B and K curves
- ECDSA sigGen FIPS186-5 and ECDSA sigVer FIPS186-5 - updates testing to use the correct output lengths for SHAKE-128 and SHAKE-256
- EDDSA sigGen 1.0 - Adds support for custom contextLength based on support outlined in sections 7.6 and 7.8 of FIPS 186-5
- RSA keyGen FIPS186-5 - removes support for testing the 15360 modulus. The runtimes involved in testing this modulus are too high.