You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 8, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,6 +77,7 @@ The following quantum-safe algorithms from liboqs are supported (assuming they h
77
77
-`oqs_kem_default` (see [here](https://github.com/open-quantum-safe/openssl/wiki/Using-liboqs-algorithms-that-are-not-in-the-forks#oqsdefault) for what this denotes)
@@ -93,6 +94,8 @@ If ``<KEX>`` is any of the algorithms listed above, the following hybrid algorit
93
94
94
95
For example, since `kyber768` claims L3 security, the hybrid `p384_kyber768` is available.
95
96
97
+
Note that algorithms marked with a dagger (†) have large stack usage and may cause failures when run on threads or in constrained environments.
98
+
96
99
#### Authentication
97
100
98
101
The following digital signature algorithms from liboqs are supported by the fork. **Note that not all variants of all algorithms are enabled by default; algorithms that are enabled by default are marked with an asterisk, and should you wish to enable additional variants, consult [the "Code Generation" section of the documentation in the wiki](https://github.com/open-quantum-safe/openssl/wiki/Using-liboqs-algorithms-not-in-the-fork#code-generation)**.
0 commit comments