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.so.4. These have the same SHLIB_MAJOR, and so ldconfig builds a hint for '-lcrypto.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 causes 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 create a bit of OpenSSL chaos. Who else has run into this? What's the resolution? Bill -- CONFIDENTIALITY NOTICE -- Information transmitted by this e-mail is proprietary to MphasiS and/or its Customers and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please notify us immediately at [EMAIL PROTECTED] and delete this mail from your records. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
