sharpetronics/liboqs
1
0
Fork 0
mirror of https://github.com/open-quantum-safe/liboqs.git synced 2025-12-11 00:04:48 -05:00
Code Issues Projects Releases Wiki Activity
liboqs/docs/algorithms/sig/falcon.md
Douglas Stebila 30fbfd826f
Sync with PQClean (#1061) 
* Sync with PQClean 6c1ea921ee4a06a6b50c742ca540bb9b5e51aee2

* Update documentation YML from PQClean

* Update documentation from PQClean
2021-08-01 17:02:22 -04:00

3.6 KiB
Raw Blame History

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 Ricosset, Gregor Seiler, William Whyte, Zhenfei Zhang.
  • Authors' website: https://falcon-sign.info
  • Specification version: v1.2.
  • Implementation source: 6c1ea921ee, which takes it from:
  • 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)
Falcon-512 EUF-CMA 1 897 1281 690
Falcon-1024 EUF-CMA 5 1793 2305 1330

Falcon-512 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
avx2 x86_64 Linux,Darwin 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

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
avx2 x86_64 Linux,Darwin 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.