mirror of https://github.com/open-quantum-safe/liboqs.git synced 2025-10-04 00:02:01 -04:00

Adding multiple upstream support to doc generation (#1123 )

* Fix an issue where run_tests tried to run tests from upstream. Fix by @DStebila

* No longer checking spdx on files copied from upstream

* Added compiler checking for gcc. Must be at least 9.4.0.

* Added pqclean's aarch64 optimized kyber implementation to liboqs

* stripping asimd flag for ARM64_V8 as it isn't needed and will cause errors when trying to specify it during compilation

* Updated kyber docs

* Updated kyber markdown so that no-secret-dependent-branching-checked-by-valgrind correctly says false for the new aarch64 implementation

* Added automated updating of legacy yaml format, and added some yaml files which don't get automatically updated

* Fixed a bug where optimized upstreams would use the primary upstream's supported platform

* Fixed a bug with copy_from_upstream.py's verify function where it would always use the default upstream location when comparing with diff

* Added reporting for implementations that are in upstream but aren't yet integrated into liboqs

* Added support to ignore implementations from upstream in copy_from_upstream.yml. This is to prevent implementations that haven't been integrated into LIBOQS yet from being pulled in by copy_from_upstream.py. It also silences the warning when verifying.

* Adding updated ymls and md files for docs

* copy_from_upstream.py now also calls update_docs_from_yaml.py

2021-11-18 06:56:19 +01:00

9.2 KiB

Raw Blame History

Rainbow

Algorithm type: Digital signature scheme.
Main cryptographic assumption: multivariable polynomials, unbalanced oil and vinegar.
Principal submitters: Jintai Ding.
Auxiliary submitters: Ming-Shing Chen, Matthias Kannwischer, Jacques Patarin, Albrecht Petzoldt, Dieter Schmidt, Bo-Yin Yang.
Authors' website: https://www.pqcrainbow.org/
Specification version: NIST Round 3 submission.
Implementation source: 7eb978b4a7, which takes it from:
- 173ada0e07
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)
Rainbow-I-Classic	EUF-CMA	1	161600	103648	66
Rainbow-I-Circumzenithal	EUF-CMA	1	60192	103648	66
Rainbow-I-Compressed	EUF-CMA	1	60192	64	66
Rainbow-III-Classic	EUF-CMA	3	882080	626048	164
Rainbow-III-Circumzenithal	EUF-CMA	3	264608	626048	164
Rainbow-III-Compressed	EUF-CMA	3	264608	64	164
Rainbow-V-Classic	EUF-CMA	5	1930600	1408736	212
Rainbow-V-Circumzenithal	EUF-CMA	5	536136	1408736	212
Rainbow-V-Compressed	EUF-CMA	5	536136	64	212

Rainbow-I-Classic implementation characteristics

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?‡
clean	All	All	None	True	True	False

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

Rainbow-I-Circumzenithal implementation characteristics

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?
clean	All	All	None	True	True	False

Rainbow-I-Compressed implementation characteristics

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?
clean	All	All	None	True	True	False

Rainbow-III-Classic implementation characteristics

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?
clean	All	All	None	True	True	True

Rainbow-III-Circumzenithal implementation characteristics

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?
clean	All	All	None	True	True	True

Rainbow-III-Compressed implementation characteristics

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?
clean	All	All	None	True	True	True

Rainbow-V-Classic implementation characteristics

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?
clean	All	All	None	True	True	True

Rainbow-V-Circumzenithal implementation characteristics

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?
clean	All	All	None	True	True	True

Rainbow-V-Compressed implementation characteristics

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?
clean	All	All	None	True	True	True

Explanation of Terms

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

9.2 KiB Raw Blame History