-
Notifications
You must be signed in to change notification settings - Fork 68
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
replace oqs-openssl111 #182
Comments
Question thus: Would anyone mind we drop |
Given today's decision to keep supporting oqs-openssl111 work on this topic is put on the backburner. I personally would very much welcome other's contributions regarding maintenance of oqs-openssl111. |
@dr7ana @igorbarshteyn @Keelan10 @chiachin2686 @ryndia You all kindly contributed oqs-openssl111 integrations to Background: With the EOL notice by OpenSSL we're now also bringing support for |
I would love to help! I will also take another look at the image size issue we had discussed previously. I've had a lot on my plate starting a new position (as I'm sure you do as well normally), but I will prioritize this for July without issue, thank you for your patience |
@dr7ana Thank you very much! By all means, prioritize your new job! Your contribution will be very welcome any time! |
OpenSSL111 has gone end of life. The demos not yet moved off OpenSSL111 should be sunset, too. Until someone finds time to do the upgrade of |
@baentsch I know I'm apologizing for the umpteenth time for not getting this done, but I will do it soon I promise! I will also fix the oversize binary issue |
Absolutely no reason to apologize. We all do this on our spare time and voluntarily -- and at least I am grateful for any contribution, regardless of timing. All I want to achieve with the above is set proper user expectations. |
Tagging @johnma14 fyi |
@baentsch I just got to see this message now. For some reason, I never got any notification. I will work on updating the HAProxy demo. |
@johnma14 in case @ajbozarth didn't notify you as per #273 (comment), consider work on |
Hey there folks! I have been working on integrating OPENSSLv3 (in-place of openssl1.1.1) with liboqs-python with the help of oqs-provider. I could build and install the liboqs-python module and it is working fine with the Should I take this to a discussion or this is the right place for this? @baentsch Thanks! |
This is a good place to have the conversation. What's the exact problem/error message? |
Folder Structure on my machine (I am trying to set it up on my machine for a specific purpose which is out of scope of this issue is regarded)
As discussed here - open-quantum-safe/oqs-provider#507 (comment) that There are multiple error factors, it would be great if you could point-out the priority of those error factors which I must re-check in-order to rectify it. Factors I think could cause issues:
|
With openssl/openssl#19312 merged, oqs-provider together with OpenSSL3 (master) now deliver the same level of functionality as oqs-openssl111.
This issue is to propose replacing oqs-openssl111 with openssl3+oqs-provider where possible in the demos.
Applicable integrations (tick if done) -- suggested order of importance
- [ ] haproxy(available upstream)Not applicable: Wireshark, Chromium, openssh, openlitespeed
The text was updated successfully, but these errors were encountered: