-
Notifications
You must be signed in to change notification settings - Fork 42
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
SSL init #154
Comments
I am running into the same issue on a Debian stretch system. Your diagnostic seems better than mine. :) Could you make any progress on this since you posted the issue? |
The function SSL_library_init is not available anymore in libssl 1.0 and onwards. The library uses another mechanism to initialise itself. It does not seem that there is an easy way to determine the version of libssl we have loaded, we therefore rely on the presence of a SSL_library_init foreign symbol to determine wether that function must be called or not. While libssl documentation claims the function SSL_load_error_strings should be present in libssl 1.0 and onwards, it is not, at least on Debian Stretch. We use the same strategy as for SSL_library_init to avoid a spurious call. Reference: https://www.openssl.org/docs/man1.1.0/ssl/OPENSSL_init_ssl.html
The function SSL_library_init is not available anymore in libssl 1.0 and onwards. The library uses another mechanism to initialise itself. It does not seem that there is an easy way to determine the version of libssl we have loaded, we therefore rely on the presence of a SSL_library_init foreign symbol to determine wether that function must be called or not. While libssl documentation claims the function SSL_load_error_strings should be present in libssl 1.0 and onwards, it is not, at least on Debian Stretch. We use the same strategy as for SSL_library_init to avoid a spurious call. Reference: https://www.openssl.org/docs/man1.1.0/ssl/OPENSSL_init_ssl.html
@orthecreedence @mmontone Juste a gentle ping on this. :-) |
Hi, sorry for the lag, I've merged #155 so this should be ready to test now. Cl-async makes the FFI calls directly so you shouldn't need to load any other deps (just do a pull on cl-async#master) and hopefully this will be fixed. Thanks, @michipili for your work on this. |
I have a problem loading cl-async-ssl:
I guess that's because I have libssl-1.0.0 installed, but SSL_library_init does not have that function:
Am I correct?
Strange thing is cl-async-ssl seems to support libssl-1.0.0 in linux, which is what I'm using:
To "fix" the load I changed:
to:
(it had problems loading SSL_load_error_strings too)
But I havent' tested if this runs correctly yet. In any case, my "fix" is not good.
The text was updated successfully, but these errors were encountered: