-
Notifications
You must be signed in to change notification settings - Fork 1.6k
lws/mbedtls-client: Support loading default ca #3432
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
Conversation
The client based on mbedtls backend does not implement the loading certificate from the default path, but the client based on openssl backend does. Signed-off-by: makejian <makejian@xiaomi.com>
Support interfaces SSL_CTX_load_verify_file/SSL_CTX_load_verify_dir/SSL_CTX_load_verify_locations to align with openssl-client behavior Signed-off-by: makejian <makejian@xiaomi.com>
|
Thanks, it's pushed on main and v4.4-stable. |
|
This blew chunks in CI starting with This is against mbedtls-3.6.4 |
how can i run CI? |
|
You can see the results here The first part of that has more info on what it's building and how |
ok, let me check |
|
@lws-team or any other mistake in ci ? |
|
I can't event build it locally on rocky 10 with rocky's mbedtls 3.6.4 It seems wrong level of indirection (this is with your extra patch) |
I get it. I optimized the x509 structure before, did not use pointer types because I thought that too much dynamic memory was not in line with the advantages of mbedtls. I will fix my patch to rebase community's implementation. |
We used libwebsockets and found that mbedtls-client did not support loading the default certificate path. After careful observation, we found that openssl-client had a related implementation, so we made the following efforts to align the implementation between openssl-client and mbedtls-client.