Hi Williams I understand your argument. But in my case I would like to compile libssl into the httpd because of the criticial SSL/TLS vulnerability. Why that? The answer is easy: Because I can only control the installed httpd but not the installation of the debian boxes itself in the production enviroment. So the only way to enforce that the right libssl is in place is to compile it into httpd. So maybe the reason for my a little bit strange question is now much clearer. So, can anybody help me how I can compile the libssl and libz into httpd? cheers mike > -----Ursprüngliche Nachricht----- > Von: William A. Rowe, Jr. [mailto:wrowe@xxxxxxxxxxxxx] > Gesendet: Freitag, 2. Januar 2009 15:48 > An: users@xxxxxxxxxxxxxxxx > Betreff: Re: Can't compile libssl and libz into httpd > 2.2.11 > > > xPostings wrote: > > > > I really don't know if it's only a config problem on my side or > > if it's a change from apache 2.2.8 to 2.2.11: > > How can I compile httpd WITHOUT any linkings to libssl and libz > > (that means compile it into httpd). Also the httpd 2.2.8 is bigger > > in filesize than 2.2.11 (bacause libz and libssl is not > compiled into...) > > > > My box is a debian etch only basic netinstall with > > There were libz security flaws back in the early 1.1 and 1.2 > series and > periodic security updates to libssl. If you have the debian > folks offering > you updated / patched / secured flavor, why on earth would > you want to lock > into the flavor of the day and deprive yourself of the fixes > to criticial > SSL/TLS vulnerability fixes as more are discovered in the future? > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP > Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > >