Topic: implement wolfssl 2.4.0 to lighttpd 1.4.32

Hi,
I try to implement wolfssl embedded ssl 2.4.0 to lighttpd 1.4.32.

When i run lighttpd
it show
2012-11-27 17:53:02: (network.c.400) SSL: ssl requested but openssl support is not compiled in

I go back check config.log in lighttpd directory
I found 
cyassl-2.4.0/cyassl/openssl/ssl.h:31:24: cyassl/ssl.h: No such file or directory
Then i go cyassl directory make symbol link to cyassl header directory and compile again,
system show compile error

buffer.h:19: warning: shadowed declaration is here
response.c: In function `htps_add_ssl_entries':
response.c:138: error: `X509_NAME_ENTRY' undeclared (first use in this function)
response.c:138: error: (Each undeclared identifier is reported only once
response.c:138: error: for each function it appears in.)
response.c:138: error: `xe' undeclared (first use in this function)
response.c:142: warning: implicit declaration of function `SSL_get_verify_result'
response.c:149: warning: implicit declaration of function `X509_NAME_entry_count'
response.c:154: warning: implicit declaration of function `X509_NAME_get_entry'
response.c:157: warning: implicit declaration of function `OBJ_obj2nid'
response.c:157: warning: implicit declaration of function `X509_NAME_ENTRY_get_object'
response.c:158: warning: implicit declaration of function `OBJ_nid2sn'
response.c:158: warning: assignment makes pointer from integer without a cast
response.c:186: warning: implicit declaration of function `PEM_write_bio_X509'
make[4]: *** [response.o] Error 1

attached file is complete compile console log

wolfssl configure with
        --disable-static \
        --disable-debug \
        --enable-opensslExtra \
        --enable-fastmath

please help

Post's attachments

log 96.76 kb, file has never been downloaded. 

You don't have the permssions to download the attachments of this post.

Share

Re: implement wolfssl 2.4.0 to lighttpd 1.4.32

Hi Kevin,

wolfSSL currently only supports lighttpd version 1.4.23.  A wolfSSL port to the most recent version of lighttpd is on our list of things that we want to get done, but due to other commitments, we haven't been able to get to it yet.  The newer versions of lighttpd added a more extensive use of OpenSSL, and as such will require an expansion of the wolfSSL OpenSSL compatibility layer (the missing functions you stated above).

We also offer the wolfSSL Embedded Web Server (http://yassl.com/yaSSL/Products-yassl-e … erver.html), which could work as a replacement for lighttpd depending on your project requirements.  This fully supports TLS 1.2 with the most recent version of wolfSSL.  Like wolfSSL, it is dual licensed under GPLv2 and commercial licensing.  Have you taken a look at it?

Best Regards,
Chris