Date: Wed, 3 May 2006 20:21:40 -0700 From: William Bloom <wbloom@eldocomp.com> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: OpenSSL Version Conflict Message-ID: <44597344.90604@eldocomp.com>
next in thread | raw e-mail | index | archive | help
I very recently (last weekend) upgraded my 5.4 system to 6.1-RC1 and soon discovered a conflict between the base OpenSSL version and the ports OpenSSL version. The base version is 0.9.7e-p1 and installs /lib/libcrypto.so.4. The ports version (security/openssl) is 0.9.8a and installs /usr/local/lib/libcrypto.s= o.4. =20These have the same SHLIB_MAJOR, and so ldconfig builds a hint for '-lcry= pto.4' that points to the library in /usr/local/lib. Also, /usr/bin/ssh (which is linked against libcrypto.so.4) finds the library in /usr/local/lib. This ca= uses scp and ssh to choke and die since they do a sanity check on the library version. I've worked around this for the time being, but two completely different release levels of OpenSSL using the same SHLIB_MAJOR tends to crea= te a bit of OpenSSL chaos. Who else has run into this? What's the resolution? Bill -- CONFIDENTIALITY NOTICE -- Information transmitted by this=A0e-mail is proprietary to MphasiS and/or it= s Customers and is intended for use only by the individual or entity to whic= h it is addressed, and may contain information that is=A0privileged, confide= ntial or exempt from disclosure under applicable law. If you are not the int= ended recipient or it appears that this mail has been forwarded to you witho= ut proper authority, you are notified that any use or dissemination of this = information in any manner is strictly prohibited. In such cases, please noti= fy us immediately at mailmaster@mphasis.com and delete this mail from your r= ecords.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44597344.90604>