-
Notifications
You must be signed in to change notification settings - Fork 87
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
[Windows] OQS Provider Deployment #80
Comments
Thanks for giving this a try under Windows. Also glad to see so many tests pass. The error line in your screenshot unfortunately is too high level to let me get a definite idea what may be wrong. If you'd be willing to share the (Windows) build scripts that get you to this point I could try to set up a Windows VM somewhere to reproduce. Very important to see for me are path changes as well as changes to "oqs.cnf"... |
Thanks for your prompt response. I have set the env variable suggested by you and run the same test. This is the output:
Just to be sure I have run all OpenSSL tests and they all pass! How can I further troubleshoot or debug the failing tests? Thanks again. |
Thanks for sharing the logs: They already tell us the cause of the error: The NIDs ("type") for the algorithms are not properly set: value 0 is clearly wrong and causes the subsequent encode error ("encode result 0" should be 1). OQSPROV output at the start already shows the problem: It should be something like
This in turn is caused by errors calling into an OpenSSL provider core method. The reason for that should be found out by debugging into the function core_obj_create. Again, I would need to set up my own Windows environment (i.e., the Windows-equivalent of https://github.com/open-quantum-safe/oqs-provider/blob/main/scripts/fullbuild.sh) to get to that point. Any assistance with that would be very helpful & welcome. |
Hi again. I have not used any Windows specific build scripts. Just the same tools but on Windows. |
Which compiler/debugger setup, please? MSVC? Which version?
That confuses me: My understanding of the provider concept so far was that providers must be shared libs such as to be dynamically loaded at runtime into pre-installed/existing openssl(3) installations.
This certainly would make life easier for consumers.
Looking forward to that. Reading up on providers in the meantime.... |
Is the newly opened issue #82 meant to suggest that dynamic provider loading as discussed above just isn't "flying" under Windows? Allow me to re-iterate my request for a Windows script that builds and tests (and fails) as per your description. Alternatively, could you provide a written description along the lines of https://github.com/open-quantum-safe/liboqs/wiki/Platform-specific-notes-for-building-liboqs#building-on-windows how to reproduce the problems you see? Thanks in advance. |
Closing due to inactivity, also seems like a duplicate of #47. |
Hi.
We are trying to deploy OpenSSL, liboqs & OQS provider on Windows 10 x64 for the very first time.
When running the (unit) tests in oqs-provider, one of them fails.
D:\oqs-provider\bin>oqs_test_endecode.exe oqsprovider ..\etc\oqs.cnf
Due to our quite limited knowledge of this project, it is really hard for us to debug or troubleshoot this issue.
Any pointers are greatly appreciated.
Regards.
The text was updated successfully, but these errors were encountered: