Replies: 3 comments
-
You should enable KEM decoders/encoders explicitly |
Beta Was this translation helpful? Give feedback.
0 replies
-
Many thanks for your respond. I'm going to recompile the oqs ... hope that can resolve our issue. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Transforming to discussion to find this easier as an FAQ. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi
Using OpenSSL 3.3.0 with OQS provider 0.6.1-dev
I tried to generate PQ keys and Certificate Signing Request (CSR) using MLKEM public key algorithm e.g.:
$ openssl req -new -newkey mlkem512 -nodes -keyout mlkem512.key -out mlkem512.csr -subj "/CN=mlkem512 EE/C=BE"
but I faced the following exception:
Using the "genpkey" option, also returns the same error:
$ openssl genpkey -algorithm mlkem512 -out mlkem512.key
It looks like these openssl commands work only with signature-algorithms e.g. Dilithium, ML-DSA.
Are there other openssl functions to generate keys and certrequest for kem-algorithms (kyber, mlkem..) ?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions