Hi, http://redmine.lighttpd.net/issues/2306 was a duplicate of http://redmine.lighttpd.net/issues/2269, which is now the correct upstream bug.
I found and fixed the problem in commit 2788: http://cgit.lighttpd.net/lighttpd/lighttpd-1.x/commit/?h=lighttpd-1.4.x&id=328043caf395e40c8f544162de8965853bb0393a The problem was that we export our own md5 functions, and the symbol names conflict with those from ssl/crypt. Don't ask me why it didn't trigger when i compiled lighttpd with -O0 instead of -O2, but prefixing our functions with li_ fixed it. On 04/14/2011 01:52 PM, Arno Töll wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > tags: 622733 +upstream > forwarded: 622733 http://redmine.lighttpd.net/issues/2306 > owner: 622733 ! > thanks > >> It looks like lighttpd is not really compatible with new openssl. > > Agreed, can confirm this for the Lighttpd package as well as for > upstream's trunk. The issue is tracked upstream as > http://redmine.lighttpd.net/issues/2306, but might correlate with > http://redmine.lighttpd.net/issues/2255 and > http://redmine.lighttpd.net/issues/2246 > > I will keep track. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
