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
#define FREERTOS implies NO_DH #28
Comments
toddouska
added a commit
that referenced
this issue
Mar 7, 2015
Thanks for the request. If you define HAVE_DH in user_settings.h (or in some other way) the FREERTOS in settings.h will no longer automatically disable DH. I added the same for SHA-512 with HAVE_SHA512. |
abrahamsonn
pushed a commit
to abrahamsonn/wolfssl
that referenced
this issue
Oct 9, 2017
Add further instructions to README
hicksjacobp
pushed a commit
to hicksjacobp/wolfssl
that referenced
this issue
Mar 29, 2021
[GIV-94219] Revert Ubuntu Lib Effort
kojo1
pushed a commit
to kojo1/wolfssl
that referenced
this issue
Mar 4, 2022
Update a few debugging strings were copied and pasted.
lealem47
pushed a commit
to lealem47/wolfssl
that referenced
this issue
Mar 29, 2023
Octeon III (CN7300) build instructions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We'd like to use TLS_DHE* cipher suites, but since we are using FREERTOS settings.h inside WolfSSL sees FREERTOS and then defines NO_DH.
The text was updated successfully, but these errors were encountered: