-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Wolfssl #17965
base: master
Are you sure you want to change the base?
Wolfssl #17965
Conversation
37cf389
to
2fb62b7
Compare
@Ferroin, I remember you mentioned having a unique variable in the CMakeLists.txt for both libraries, but I can't recall the exact details. Please feel free to push a commit or leave a comment so I can make the necessary changes. |
@thiagoftsm check the conflict please |
I fixed the conflict and I retest. Everything is working on my environment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only three comments on the CMake code, but otherwise looks good to me.
930b5e1
to
d2fff24
Compare
CMakeLists.txt
Outdated
set(ENABLE_OPENSSL True) | ||
set(ENABLE_WOLFSSL False) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My meaning here was that ENABLE_WOLFSSL should be an option, but ENABLE_OPENSSL should be set to true or false based on the value of that option.
Framed a bit differently, exactly one of these variables must be True. We can’t build if both are False (because we decided to have a hard dependency on a TLS implementation) or both are True (because that would break the abstraction layer). The original implementation you had here ensured that it wasn’t possible for both to be True, but not that it wasn’t possible for both to be False.
What I’m suggesting is essentially this:
set(ENABLE_OPENSSL True) | |
set(ENABLE_WOLFSSL False) | |
option(ENABLE_WOLFSSL "Use WolfSSL in place of OpenSSL for TLS and crypto support" False) | |
if(ENABLE_WOLFSSL) | |
set(ENABLE_OPENSSL False) | |
else() | |
set(ENABLE_OPENSSL True) | |
endif() |
Summary
Fixes #6509
This PR is also fixing some issues when we compile netdata disabling
ACLK
.Test Plan
wolfssl
on your system. The default compilation of the library won't allow everything necessary to haveACLK debug messages
andcloud
, to fix this I compiled it using the following options:info
endpoint, because you can test both SSL and streaming with it.Additional Information
To support ACLK and cloud, it will be necessary to do more changes in the source code. So this is the first step to bring the library.
This PR was tested on scenarios:
For users: How does this change affect me?