On Wed, 1 Nov 2000, Lutz Jaenicke wrote:
>
> If you are using shared libraries, you either have to recompile your
> application or must make sure, that the correct shared library is being
> used. This is typically assured by including the version number into
> the shared library name: "libssl.so.0.9.6" etc.
>
Which means that the soname as defined in the tope level Makefile
should change from lib$$i.so.${SHLIB_MAJOR}
to lib$$i.so.${SHLIB_MAJOR}.${SHLIB_MINOR}
Not sure if this fixes the problem, but the soname should in principle
be pumped every time binary compatibility is lost.
Then you have this little problem of makin the rpm system not delete
the old version of libssl when upgrading to the next version but keep
both on the system
Otherwise it might be a better idea to link against libssl.a, at least
until the ABI is stabilized.
> So if you run an openssh that was compiled against version 0.9.5a of
> OpenSSL, the 0.9.5a version of the shared library is obligatory. You
> cannot use the 0.9.6 shared library instead.
>
This could be reflected in the openssh rpm package as being dependend
on openssl version 0.9.5a, which will raise a complint when you later
upgrade to 0.9.6 of openssl.
You have the same issue with stunnel and apache-mod_ssl.
Villy
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
