sharpetronics/liboqs

mirror of https://github.com/open-quantum-safe/liboqs.git synced 2025-11-30 00:02:38 -05:00

Jason Goertzen 55bc8cb38d

ARMv8 optimized Dilithium (#1194 )

* Updated sig templates to add support for arch specific upstreams. Currently behaves as expected, but still need to test (and integrate) dilithium

* Fixed a couple of build errors, and started work on dilithium integration from pqclean. Currently failing kat tests

* Updated templating for both sig and kem to make them look a little better

* Renamed dilithium folders so they are consistent across pqclean and pqcrystals so that copy_from_upstream script will function correctly

* Added arm optimized version of dilithium[2|3|5]

* Updating other signature schemes CMakeLists.txt to be the output of the updated templates

* Arm optimized implementation of dilithium is added, with randomized signing patched into it. copy_from_upstream script is working properly. Still need to update the update_docs scripts before ready to merge

* Finished updating docs scripts and yml files. Builds pass, so should be ready for a merge

* Fixed template issue with multiple compile flags

* Updated doc generation scripts so that all '_' in scheme names are replaced with '\_'

2022-03-09 15:17:42 -05:00

49 KiB

Raw Blame History

SPHINCS+

Algorithm type: Digital signature scheme.
Main cryptographic assumption: hash-based signatures.
Principal submitters: Andreas Hülsing.
Auxiliary submitters: Jean-Philippe Aumasson, Daniel J. Bernstein,, Christoph Dobraunig, Maria Eichlseder, Scott Fluhrer, Stefan-Lukas Gazdag, Panos Kampanakis, Stefan Kölbl, Tanja Lange, Martin M. Lauridsen, Florian Mendel, Ruben Niederhagen, Christian Rechberger, Joost Rijneveld, Peter Schwabe.
Authors' website: https://sphincs.org/
Specification version: NIST Round 3 submission.
Primary Source:
- Source: 4c9e5a3aa7 with copy_from_upstream patches
- Implementation license (SPDX-Identifier): CC0-1.0

Parameter set summary

Parameter set	Security model	Claimed NIST Level	Public key size (bytes)	Secret key size (bytes)	Signature size (bytes)
SPHINCS+-Haraka-128f-robust	EUF-CMA	1	32	64	17088
SPHINCS+-Haraka-128f-simple	EUF-CMA	1	32	64	17088
SPHINCS+-Haraka-128s-robust	EUF-CMA	1	32	64	7856
SPHINCS+-Haraka-128s-simple	EUF-CMA	1	32	64	7856
SPHINCS+-Haraka-192f-robust	EUF-CMA	3	48	96	35664
SPHINCS+-Haraka-192f-simple	EUF-CMA	3	48	96	35664
SPHINCS+-Haraka-192s-robust	EUF-CMA	3	48	96	16224
SPHINCS+-Haraka-192s-simple	EUF-CMA	3	48	96	16224
SPHINCS+-Haraka-256f-robust	EUF-CMA	5	64	128	49856
SPHINCS+-Haraka-256f-simple	EUF-CMA	5	64	128	49856
SPHINCS+-Haraka-256s-robust	EUF-CMA	5	64	128	29792
SPHINCS+-Haraka-256s-simple	EUF-CMA	5	64	128	29792
SPHINCS+-SHA256-128f-robust	EUF-CMA	1	32	64	17088
SPHINCS+-SHA256-128f-simple	EUF-CMA	1	32	64	17088
SPHINCS+-SHA256-128s-robust	EUF-CMA	1	32	64	7856
SPHINCS+-SHA256-128s-simple	EUF-CMA	1	32	64	7856
SPHINCS+-SHA256-192f-robust	EUF-CMA	3	48	96	35664
SPHINCS+-SHA256-192f-simple	EUF-CMA	3	48	96	35664
SPHINCS+-SHA256-192s-robust	EUF-CMA	3	48	96	16224
SPHINCS+-SHA256-192s-simple	EUF-CMA	3	48	96	16224
SPHINCS+-SHA256-256f-robust	EUF-CMA	5	64	128	49856
SPHINCS+-SHA256-256f-simple	EUF-CMA	5	64	128	49856
SPHINCS+-SHA256-256s-robust	EUF-CMA	5	64	128	29792
SPHINCS+-SHA256-256s-simple	EUF-CMA	5	64	128	29792
SPHINCS+-SHAKE256-128f-robust	EUF-CMA	1	32	64	17088
SPHINCS+-SHAKE256-128f-simple	EUF-CMA	1	32	64	17088
SPHINCS+-SHAKE256-128s-robust	EUF-CMA	1	32	64	7856
SPHINCS+-SHAKE256-128s-simple	EUF-CMA	1	32	64	7856
SPHINCS+-SHAKE256-192f-robust	EUF-CMA	3	48	96	35664
SPHINCS+-SHAKE256-192f-simple	EUF-CMA	3	48	96	35664
SPHINCS+-SHAKE256-192s-robust	EUF-CMA	3	48	96	16224
SPHINCS+-SHAKE256-192s-simple	EUF-CMA	3	48	96	16224
SPHINCS+-SHAKE256-256f-robust	EUF-CMA	5	64	128	49856
SPHINCS+-SHAKE256-256f-simple	EUF-CMA	5	64	128	49856
SPHINCS+-SHAKE256-256s-robust	EUF-CMA	5	64	128	29792
SPHINCS+-SHAKE256-256s-simple	EUF-CMA	5	64	128	29792

SPHINCS+-Haraka-128f-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?‡
Primary Source	clean	All	All	None	True	True	False
Primary Source	aesni	x86_64	All	AES	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

‡For an explanation of what this denotes, consult the Explanation of Terms section at the end of this file.

SPHINCS+-Haraka-128f-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	aesni	x86_64	All	AES	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-Haraka-128s-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	aesni	x86_64	All	AES	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-Haraka-128s-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	aesni	x86_64	All	AES	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-Haraka-192f-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	aesni	x86_64	All	AES	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-Haraka-192f-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	aesni	x86_64	All	AES	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-Haraka-192s-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	aesni	x86_64	All	AES	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-Haraka-192s-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	aesni	x86_64	All	AES	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-Haraka-256f-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	aesni	x86_64	All	AES	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-Haraka-256f-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	aesni	x86_64	All	AES	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-Haraka-256s-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	aesni	x86_64	All	AES	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-Haraka-256s-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	aesni	x86_64	All	AES	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHA256-128f-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHA256-128f-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHA256-128s-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHA256-128s-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHA256-192f-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHA256-192f-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHA256-192s-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHA256-192s-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHA256-256f-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHA256-256f-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHA256-256s-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHA256-256s-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHAKE256-128f-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHAKE256-128f-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHAKE256-128s-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHAKE256-128s-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHAKE256-192f-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHAKE256-192f-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHAKE256-192s-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHAKE256-192s-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHAKE256-256f-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHAKE256-256f-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHAKE256-256s-robust implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

SPHINCS+-SHAKE256-256s-simple implementation characteristics

Implementation source	Identifier in upstream	Supported architecture(s)	Supported operating system(s)	CPU extension(s) used	No branching-on-secrets claimed?	No branching-on-secrets checked by valgrind?	Large stack usage?
Primary Source	clean	All	All	None	True	True	False
Primary Source	avx2	x86_64	All	AVX2	True	True	False

Are implementations chosen based on runtime CPU feature detection? Yes.

Explanation of Terms

Large Stack Usage: Implementations identified as having such may cause failures when running in threads or in constrained environments.