mirror of
https://github.com/open-quantum-safe/liboqs.git
synced 2025-12-12 00:04:16 -05:00
* fix compiler warning/error in aes256_armv8.c * pull pqclean+paches * pull pqclean+paches * remove old patches & update algorithm md/yml * add new patches * add patch with fixes for arm/kyber768+kyber1024 * update licenses in yamls and mds * update kyber/dil suppression files * removes superfluous pqclean Makefiles & updates copy_from_upstream script to handle this case * update license infos
3.8 KiB
3.8 KiB
Falcon
- Algorithm type: Digital signature scheme.
- Main cryptographic assumption: hardness of NTRU lattice problems.
- Principal submitters: Thomas Prest.
- Auxiliary submitters: Pierre-Alain Fouque, Jeffrey Hoffstein, Paul Kirchner, Vadim Lyubashevsky, Thomas Pornin, Thomas Prest, Thomas Ricosset, Gregor Seiler, William Whyte, Zhenfei Zhang.
- Authors' website: https://falcon-sign.info
- Specification version: 20211101.
- Primary Source:
- Source:
66e5017205 - Implementation license (SPDX-Identifier): MIT
- Source:
Parameter set summary
| Parameter set | Security model | Claimed NIST Level | Public key size (bytes) | Secret key size (bytes) | Signature size (bytes) |
|---|---|---|---|---|---|
| Falcon-512 | EUF-CMA | 1 | 897 | 1281 | 666 |
| Falcon-1024 | EUF-CMA | 5 | 1793 | 2305 | 1280 |
Falcon-512 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.
‡For an explanation of what this denotes, consult the Explanation of Terms section at the end of this file.
Falcon-1024 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.