On Oct 27 10:00, Matthew D. Fuller wrote:
On Thu, Oct 27, 2016 at 03:05:03PM +0200 I heard the voice of
Mathieu Arnold, and lo! it spake thus:
Once you install openssl from ports, the ports framework will use
it, always.
That is absolutely not the case since OpenSSL in base was updated to
.so.8 and ports wasn't re-bumped past it. Everything gets confused
all the time.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209582
Even in an e.g. net/ntp rebuilt just now:
% ldd /usr/local/sbin/ntpd | grep -E '(crypto|ssl)'
libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x800cea000)
libssl.so.8 => /usr/lib/libssl.so.8 (0x801ae6000)
Just looking at a ldd through /usr/local I'm finding tons of things
that are still linking to base libcrypto. STuff from ldns, nginx,
Virtualbox, libwww, lots of X pieces...
This makes me *EXTREMELY* nervous about upgrading _any_ systems where
I'm using ports OpenSSL to stable/11.
I don't see this on my system which is FreeBSD 11.0-STABLE #0 r307132
$ ldd /usr/local/sbin/ntpd | grep -E '(crypto|ssl)'
libcrypto.so.38 => /usr/local/lib/libcrypto.so.38 (0x800cee000)
libssl.so.39 => /usr/local/lib/libssl.so.39 (0x801aca000)
Most likely because I have correctly declared the default version of the
SSL library by putting DEFAULT_VERSIONS=ssl=libressl-devel in make.conf.
Without declaring it specifically like that I wouldn't trust the system
to do it automatically either.
--
Matt
_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
