Michael Baentsch

Also hit this bug. Further confirmed via CI: https://github.com/openssl/openssl/runs/7190875851?check_suite_focus=true

ACK. The patching was introduced to allow `oqsprovider` to be tested independently of openssl (test) code. But as this is _openssl_ testing, I'd suggest dropping this "test independence" property for...

@mattcaswell You may want to run CI again: The `oqsprovider` test should now pass again (assuming this PR doesn't change the "helpers" test API too drastically).

Thanks for the bug report. Indeed I'm not sure we have someone in the team using an ARM-based Windows. Is there a specific test (ideally CI) environment that you could...

Thanks for your contribution! It's a very good goal to have `liboqs` be more easily "embeddable" into other `cmake` driven projects. The "OQS_" namespacing prefixing also makes sense. Will you...

> Yes, I plan to update the CMakeLists.txt under the tests directory. Thanks in advance! > However, I am not sure if I can modify the CMakeLists.txts related to kem...

> They also do development at different paces And also seem to have different goals (integrations of more/different PQ algs into different apps, say). But 4 months difference (judging for...

@claucece Thanks for that update and your interest to look into this issue. In case you didn't find them yet, here's pointers to some interop test scripts we already have...

If you'd like us to look into this, please point to information how to install all required tooling for this sample build script to work? Are there docker images containing...

> Are there any configuration switches to bypass the assembly code and replace it with its C equivalent code No, a single such [liboqs build option](https://github.com/open-quantum-safe/liboqs/wiki/Customizing-liboqs) does not exist "out...