> > -----Message d'origine----- > De : Amos Jeffries > > On Mon, 15 Nov 2010 21:33:40 +0000, SÃbastien WENSKE wrote: >> Thanks for your support Dean, but I'm definitively a n00b :) I had >> compile many times (without error) with some ssl paths, but no result >> I got the same result on the scan... >> >> I compiled openssl with no particular option (no make install) >> >> ./configure --localstatedir=/var --prefix=/usr >> --includedir=/usr/include --datadir=/usr/share --bindir=/usr/sbin >> --libexecdir=/usr/lib/squid --exec-prefix=/usr --sysconfdir=/etc/squid >> --enable-x-accelerator-vary --with-default-user=proxy --enable-ssl >> --enable-follow-x-forwarded-for --enable-underscores >> --enable-delay-pools --enable-cache-digests --enable-auth="basic" >> --enable-ecap >> --with-openssl=/usr/src/openssl/openssl-1.0.0a/include/openssl > > I think this should be > --with-openssl=/usr/src/openssl/openssl-1.0.0a/ > >> >> I'm lost ... I need to fix this issue before implementing this in my >> company ... >> >> Cheers, >> >> Sebastian >> On Mon, 15 Nov 2010 23:39:31 +0000, SÃbastien WENSKE wrote: > Hi Amos, > > Glad to hear you, I have already try and retry this one, but no changes... > this is freaky and I'm tired :) > > I will continue tomorrow, I think I need to find a guide to compile squid > with "non-system" ssl libraries/headers. > > Otherwise, is there a way to know with wich openssl squid is compiled??? > Because à every time squid will run correctly in ssl mode... :-/ The config.log file will show which openssl libraries are searched for and found. Along with any problems in the detection. A dump of stdout from a new "make" will contain the full set of things linked to the "squid" binary. Including the full-path of any custom libraries. There should also be tools around to show which libraries any given pre-built binary loads. I can't think of any off the top of my head right now though. HTH Amos
