davo176 / sphincsplus Goto Github PK

Running python3 createAddRandom.py python3 createAddSign.py

will build the new test cases

For interoperability testing you will have to change between java and csharp in the files: ref/createSigned.c ref/checkSigned.c you will also have to swap between robust and simple in the following files: createSigned.py, checkSigned.py and ref/createSigned.c ref/checkSigned.c (add to output files basically making sure filenames are unique. currently createSigned has simple and checkSigned has robust so you can see examples there)

So you will end up running createSigned.py, checkSigned.py 4 times:

• java, simple
• java, robust
• csharp, simple
• csharp, robust

This repository contains the software that accompanies the SPHINCS+ submission to NIST's Post-Quantum Cryptography project.

The SPHINCS+ specification proposed a set of 36 named instances, specifying hash functions and concrete parameters for the security level, tree dimensions, WOTS+ and FORS. This reference implementation allows for more flexibility, as parameters can be specified in a params.h file. The proposed parameter sets have been predefined in ref/params/params-*.h, and the hash function can be varied by linking with the different implementations of hash.h, i.e., hash_haraka.c, hash_sha2.c and hash_shake.c, as well as different implementations of thash.h, i.e., *_robust.c and *_simple.c. This is demonstrated in the Makefile. See the table below for a summary of the parameter sets. These parameters target the NIST security categories 1, 3 and 5; for each category, there is a parameter set geared towards either small signatures or fast signature generation.

All included code is available under the CC0 1.0 Universal Public Domain Dedication, with the exception of rng.c, rng.h and PQCgenKAT_sign.c, which were provided by NIST.