-
Notifications
You must be signed in to change notification settings - Fork 836
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help Needed: wolfSSL Build Issue with Latest Version and Runtime Error with Dilithium Certificates #8239
Comments
Second one got resolved as I updated liboqs to 0.10.0. I will really appreciate any suggestion for first one. Please let me know if any additional info is required. |
Hello @SanzidaH
can you please try using Warm regards, Anthony |
Here at wolfSSL we love learning about how the academic community is using our source code. Can you please tells more about yourself and your project?
If you are hesitant to share this information on a public platform, you can send me email at [email protected]. Warm regards, Anthony |
I'm encountering similar issues (problem 2). While I can compile wolfSSL v5.7.0-stable with liboqs 0.12.0, this wolfSSL version yields problems with Dilithium 2 and Dilithium 3 certificates in my libcoap application (the problem relates to |
Version
6af54d3
Description
I am stuck on the following issues with wolfSSL, and I would greatly appreciate any guidance or suggestions to resolve them.
It seems wolfSSL does not recognize the OID for dilithium2.
For configure this is what I run: ./configure --enable-certreq --enable-certgen --enable-certext --enable-keygen --enable-cryptocb --with-liboqs --disable-psk --disable-shared --enable-intelasm --enable-aesni --enable-sp-math-all --enable-sp-asm --enable-experimental --enable-kyber CFLAGS="-Os"
It seems that some macros, such as OQS_SIG_ml_dsa_87_ipd_length_public_key, are undefined. Is this a compatibility issue between liboqs and wolfSSL, or am I missing some configuration steps?
I will really appreciate any suggestion/guidance to resolve these issues.
The text was updated successfully, but these errors were encountered: