I actually did install it with the prefix=/usr. I only have one
openssl binary, but I think I have a lot of the old libraries on the
server. I couldn't do RPM erase or update because of all these
conflicts (and I'm new to this). Do you know if it is possible to
point apache2 to a specific openssl library, or something like that?
I see files like this:
/lib/libssl.so.0.9.6b /lib/libssl.so.2 /lib/libss.so.2
/lib/libss.so.2.0
So those are the old openssl. Not sure how to clean that out and make
it use the new openssl?
> Could it be because OpenSSL was originally installed w/ an RPM but
> when upgraded it was with source? I couldn't get an RPM upgrade to
> work so I did a source recompile....
> > I've noticed this one my boxes as well. I have a version of Apache 2.0 on
> > RedHat 8.0 that is not vulnerable but I compiled and installed OpenSSL9.6h
> > anyway and openssl version still tells me that the OpenSSL9.6b engine is
> > installed.
> > --
> > Jeff Umbach
> > > I'm pretty new to this, so go easy :) I've detected the apache slapper
> > > in my /tmp dir. I removed all those processes owned by apache. I
> > > upgraded to OpenSSL 0.9.6h
> > > #/usr/bin/openssl version
> > > OpenSSL 0.9.6h 5 Dec 2002
> > > I downloaded Apache 2.0.43, compiled, and installed.
> > > But it is still showing this:
> > > Apache/2.0.43 (Unix) mod_ssl/2.0.43 OpenSSL/0.9.6b on Linux
> > > Why is that 0.9.6b still on there? What step did I miss?
> > > Thanks a lot!!