OpenSSLTest is not using the OpenSSL Provider#2219
OpenSSLTest is not using the OpenSSL Provider#2219reta wants to merge 1 commit intoopensearch-project:mainfrom
Conversation
Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2219 +/- ##
============================================
- Coverage 61.06% 61.03% -0.04%
+ Complexity 3269 3268 -1
============================================
Files 259 259
Lines 18335 18335
Branches 3248 3248
============================================
- Hits 11196 11190 -6
- Misses 5553 5559 +6
Partials 1586 1586 🚀 New features to boost your workflow:
|
|
Bwc tests are broken on main. Tracking issue here: #2221 |
|
@reta Any thoughts on this PR? Seems like this work has stalled |
@peternied I think we decided to drop support for OpenSSL (due to numerous limitations mentioned in description), the pull request in the current form will work only if OpenSSL 1.0.0 is present in the system (which is way outdated). The other options which some projects are doing is to prebuild |
|
I'm going to close this pull request. If anything changes we can reopen in the future. |
Signed-off-by: Andriy Redko andriy.redko@aiven.io
Description
OpenSSLTest should be using the OpenSSL Provider. There are few issues with
netty-tcnativeand OpenSSL:compat-openssl10Issues Resolved
Closes #2208
Is this a backport? If so, please add backport PR # and/or commits #
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.