Greetings -

I seem to run into this sort of problem with some frequency with
Redhat, so I'm hoping someone can offer a general suggestion on how to
proceed.

Redhat Enterprise WS comes with  openSSL 0.9.7.a, as indicated by rpm
-q openssl. However, the current version of openssl is 0.9.7e, which
I'd like to upgrade to.

Fine - an easy build from the openssl tarball, compile into apache
using the --enable-ssl option,  and we're done, right?
Nope. As seems to often be the case, Redhat has decided to install
openssl in non-standard directories. For example, the normal openssl
config from sources puts everything relative to /usr/bin/ssl, wheras
the Redhat RPM seems to put *most things* relative to /usr/bin. This
is a pain. I tried making a symbolic link for openssl in /usr/bin to
point to the 0.9.7e files in /usr/bin/ssl, but that doesn't seem to
work (i.e., when I compile an app - say, apache - using openssl - say,
Apache - it
still uses the 0.9.7a defaults).

I'd rather not unload the openssl RPM and then install from the
tarball, since every other time I;ve tried that something has broken
along the way. Moreoever, I'd rather not try to overwrite the 0.9.7a
files with the 0.9.7e files, since I'm not sure there is an obvious
way to match the Redhat  directory structure using the openssl
configure script.

Any suggestions?  I really wish RH would not deviate from default
directories - makes doing updates a real pain. Basically, all I want
to do is figure out how to install openssl 0.9.7e, and compile it into
apache - is there a way to 'tell' apache to look at a specific
location for ssl?

Thanks...

[ Post a follow-up to this message ]