-
Notifications
You must be signed in to change notification settings - Fork 84
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
Broken LibreSSL tls_conn_change_cert implementation #1135
Comments
Maybe |
So the allocation of the It would be possible to create a new context for each such a configuration and saving these contexts as hash_list instead of the certificate path. Then using the |
|
"not very documented" points it out. |
Is v3.14.0 okay for this issue? Today we planned to release v3.13.0. |
Looks like there are some broken LibreSSL implementations #1127.
Let's start with
test_tls_cli_conn_change_cert
andtls_conn_change_cert
, this does not work within libressl sinceSSL_certs_clear
is not supported (There is usually a good reason why LibreSSL drops some APIs, mostly for security maintenance reasons).re/src/tls/openssl/tls_tcp.c
Lines 331 to 333 in b41f503
After studying the usage, I wonder why the ssl object is changed and not the ssl ctx before (or a new one used)? Since within
tls_start_tcp
a new ssl object is created from ctx. This waySSL_certs_clear
can be avoided, I think.re/src/sip/transp.c
Lines 827 to 843 in b41f503
We should keep all SSL implementations very generic.
@cHuberCoffee
The text was updated successfully, but these errors were encountered: