sharpetronics/liboqs
1
0
Fork 0
mirror of https://github.com/open-quantum-safe/liboqs.git synced 2025-10-04 00:02:01 -04:00
Code Issues Projects Releases Wiki Activity
liboqs/docs/algorithms/kem/classic_mceliece.md
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

15 KiB
Raw Blame History

Classic McEliece

  • Algorithm type: Key encapsulation mechanism.
  • Main cryptographic assumption: Niederreiter's dual version of McEliece's public key encryption using binary Goppa codes.
  • Principal submitters: Daniel J. Bernstein, Tung Chou, Tanja Lange, Ingo von Maurich, Rafael Misoczki, Ruben Niederhagen, Edoardo Persichetti, Christiane Peters, Peter Schwabe, Nicolas Sendrier, Jakub Szefer, Wen Wang.
  • Authors' website: https://classic.mceliece.org
  • Specification version: SUPERCOP-20191221.
  • Primary Source:
    • Source: 4c9e5a3aa7
    • Implementation license (SPDX-Identifier): Public domain , which takes it from:
    • SUPERCOP-20191221 "vec" and "avx" implementations

Parameter set summary

Parameter set Security model Claimed NIST Level Public key size (bytes) Secret key size (bytes) Ciphertext size (bytes) Shared secret size (bytes)
Classic-McEliece-348864 IND-CCA2 1 261120 6452 128 32
Classic-McEliece-348864f IND-CCA2 1 261120 6452 128 32
Classic-McEliece-460896 IND-CCA2 3 524160 13568 188 32
Classic-McEliece-460896f IND-CCA2 3 524160 13568 188 32
Classic-McEliece-6688128 IND-CCA2 5 1044992 13892 240 32
Classic-McEliece-6688128f IND-CCA2 5 1044992 13892 240 32
Classic-McEliece-6960119 IND-CCA2 5 1047319 13908 226 32
Classic-McEliece-6960119f IND-CCA2 5 1047319 13908 226 32
Classic-McEliece-8192128 IND-CCA2 5 1357824 14080 240 32
Classic-McEliece-8192128f IND-CCA2 5 1357824 14080 240 32

Classic-McEliece-348864 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 vec All All None True True True
Primary Source avx x86_64 Linux,Darwin AVX2,POPCNT False True True

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.

Classic-McEliece-348864f 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 vec All All None True True True
Primary Source avx x86_64 Linux,Darwin AVX2,POPCNT,BMI1 False True True

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

Classic-McEliece-460896 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 vec All All None True True True
Primary Source avx x86_64 Linux,Darwin AVX2,POPCNT False True True

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

Classic-McEliece-460896f 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 vec All All None True True True
Primary Source avx x86_64 Linux,Darwin AVX2,BMI1,POPCNT False True True

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

Classic-McEliece-6688128 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 vec All All None True True True
Primary Source avx x86_64 Linux,Darwin AVX2,POPCNT False True True

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

Classic-McEliece-6688128f 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 vec All All None True True True
Primary Source avx x86_64 Linux,Darwin AVX2,BMI1,POPCNT False True True

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

Classic-McEliece-6960119 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 vec All All None True True True
Primary Source avx x86_64 Linux,Darwin AVX2,POPCNT False True True

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

Classic-McEliece-6960119f 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 vec All All None True True True
Primary Source avx x86_64 Linux,Darwin AVX2,BMI1,POPCNT False True True

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

Classic-McEliece-8192128 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 vec All All None True True True
Primary Source avx x86_64 Linux,Darwin AVX2,POPCNT False True True

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

Classic-McEliece-8192128f 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 vec All All None True True True
Primary Source avx x86_64 Linux,Darwin AVX2,POPCNT,BMI1 False True True

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.