On 29-abr-09, at 12:38, Leonel Nunez wrote: >> On 29-abr-09, at 04:17, Leonel Nunez wrote: >> >>> downloaded , compiled and installed cherokee 0.99.12 all went fine >>> >>> When I want to start cherokee I get this error : >>> >>> plugin_loader.c:194: ERROR: dlopen(/usr/lib/cherokee/ >>> libplugin_libssl.so): >>> /usr/lib/cherokee/libplugin_libssl.so: symbol SSL_get_servername, >>> version >>> OPENSSL_0.9.8 not defined in file libssl.so.0.9.8 with link time >>> reference >>> plugin_loader.c:363: ERROR: Can't open "libssl" module >>> Couldn't read the config file: /etc/cherokee/cherokee.conf >>> >>> Am I missing any configuration missing from 0.99.11 to 0.99.12?? >> >> >> No. It looks like a compilation issue, actually. >> >> The OpenSSL package of Debian doesn't support TLS extensions. That's >> fair enough, although Cherokee won't support TLS SNI. >> >> The problem seems to be related to the TLSEXT detection. According to >> the error message you sent, Cherokee is calling the >> SSL_get_servername() function, even if your libssl doesn't include >> it. Of course, that shouldn't happen. The most strange thing is >> that >> the source code is ready to deal with old libssl libraries. If you >> take a look at it, you'll see that all the calls to extended >> functions >> are located inside #ifndef OPENSSL_NO_TLSEXT blocks. >> >> Leonel, could you please check whether the following macro variables >> are defined when you compile the server? >> >> SSL_CTRL_SET_TLSEXT_HOSTNAME >> OPENSSL_NO_TLSEXT >> > > after a ./configure : > > leo...@hardy-server:/tmp/cherokee-0.99.12$ grep -ry > SSL_CTRL_SET_TLSEXT_HOSTNAME *
No, SSL_CTRL_SET_TLSEXT_HOSTNAME is supposed to be defined within the OpenSSL headers. Try this insteaad: grep -r SSL_CTRL_SET_TLSEXT_HOSTNAME /usr/include/openssl/ -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
