Error in running make all command patched OQS openssl fork about osp

[anhu]

Hello again @NomanNasirMinhas ,

the version of OQS's openSSL seems to be looking algorithms that are no longer supported in your version of liboqs. Root cause is likely the same as your other issue that you opened, your version of liboqs is too new. Please try release 0.8.0.

Warm regards, Anthony

[NomanNasirMinhas]

Nope! Still the same issue. I am using 0.8.0 liboqs. You can see the output of history command to verify

[anhu]

Hello @NomanNasirMinhas ,

It seems I will need to spend some time to update our code. Perhaps it has gotten stale.

In the meantime, can you please let me know a bit about your project and any kind of organizations or institutions that are associated with this work? Please let me know a bit about yourself such as where you are located and whether you are doing this project out of personal, academic or professional interest.

Warm regards, Anthony

[anhu]

In the meantime, can you please ...

Sorry about that, no need. You have already done so via different channels.

[shyamarshid]

I wanted to share my experience and a solution that worked for me regarding the issue with generating Post-Quantum Cryptography (PQC) certificates using wolfSSL with liboqs. Initially, following the wolfSSL instructions, I used liboqs version 0.8.0 but encountered errors similar to what Nasir mentioned.

I attempted to address this by downgrading wolfSSL to versions 5.5.2 and 5.5.4, but these changes didn't resolve the issue. However, I found a breakthrough in an older version of the README.md file in the wolfSSL osp repository. Specifically, this commit: 5ad16875, which referenced a specific commit in the liboqs repository. This commit corresponds to liboqs version 0.7.2-dev.

Using this specific version of liboqs (0.7.2-dev), along with the patch provided in the same commit (link to the patch: here), I successfully generated PQC certificates, including Dilithium, using the OpenSSL fork of wolfSSL.

It seems that, at least in my case, the specific combination of wolfSSL with liboqs version 0.7.2-dev and the mentioned patch was necessary to get things working correctly.

I hope this information is helpful for others facing similar issues!