Replies: 1 comment
-
If anyone else comes across my post above, my solution was to compile boringssl from google's git repository, which gave me what I needed in a few minutes w/o any hassle using -curves X25519MLKEM768. |
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
-
I'm on Linux debian 6.1.0-26-arm64 w/ openssl 3.3.2 and OQS Provider 0.7.1-dev. I am trying to replicate the perftest.sh script in the /oqs-demos/curl repository. I wasn't able to get the curl docker image to build successfully on aarch64, so I've just built everything by manually.
Everything seems, to my untrained eye, to be working normally (openssl list shows the algorithms from the OQS provider), except when I pass a -groups mlkem768 or -groups kyber768 to openssl s_server. The server starts up w/o complaints, but once my s_time instance connects, s_server gives "SSL routines:final_key_share:no suitable key share" to STDERR.
Everything works as expected if I pass -groups x25519 to s_server. Which is great, as that is half of the benchmark data I would like to collect, but the other half would be MLKEM768 w/ X25519 in hybrid mode.
openssl s_server -cert server.crt -key server.key -groups mlkem768 -www -tls1_3 -accept localhost:4433
openssl s_time -connect :4433 -new -time 5 -verify 1
Any help would be appreciated in helping me collect this data.
Beta Was this translation helpful? Give feedback.
All reactions