-
Notifications
You must be signed in to change notification settings - Fork 7
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
Help! need support for TLS v1.3 #9
Comments
Hi @houssam84 , Thanks for reaching out to us here at wolfSSL. May I ask, how do you configure and build wolfSSL. Do you use configure or do you have a user_settings.h ? In either case, can you let us know what options you enable/disable? Here at wolfSSL, we love it when the community uses our code and we love to learn how they are using it. Can you please let me know a bit about yourself and your project? What are you trying to achieve? Where are you geographically located? Is this question out of personal, academic or professional interest? Are there any organizations associated with this work? Any information is useful in helping us prioritize your request. Warm regards, Anthony |
Thank u for your response. i appreciate your support.
This work is part of an IOT exploring secure communication protocols and is not currently tied to an organization or specific personal interest. Any guidance you can provide to resolve the issue would be greatly appreciated. Thank you for your support. Best regards, |
Hi, |
hi, I have compiled project with TLS v1.2. It is OK. but the following test results (undefined reference to `wolfTLSv1_3_server_method'):
#include <wolfssl.h>
#include <wolfssl/options.h>
#include <wolfssl/ssl.h>
void setup() {
Serial.begin(115200);
wolfSSL_Init();
WOLFSSL_CTX* ctx = wolfSSL_CTX_new(wolfTLSv1_3_server_method());
if (ctx) {
Serial.println("TLS 1.3 is supported and context created successfully!");
wolfSSL_CTX_free(ctx);
} else {
Serial.println("Failed to initialize TLS 1.3 context.");
}
}
void loop() {
// Nothing to do here
}
The text was updated successfully, but these errors were encountered: