You need to find anything you've linked to ports OpenSSL, remove the DEFAULT_VERSIONS+=ssl=openssl from /etc/make.conf (if you've still got it), and rebuild those ports that you built linked to the ports OpenSSL.
To find the ports (if any) linked to the ports OpenSSL, I think this will do the trick:
So that's the list of ports you've built linked to ports OpenSSL. Double check your /etc/make.conf doesn't have any openssl line in it.
Then rebuild those ports (how you do so depends on what tool(s) you've been building with so far.) You seem to be using make directly (in your git example) so you might have to go to each of the ports you've built and do some sort of make clean and then make reinstall dance (I'm not a ports or make expert so can't tell you exactly what will work.) It's good to have another machine or VM to experiment on!
Might also be an idea to remove the OpenSSL port after that, to make sure you are 100% base.
Note: /usr/bin/openssl is the base OpenSSL, /usr/
local/bin/openssl is the ports OpenSSL. And something like this shows you the binary files they are linked to:
Code:
% ldd /usr/bin/openssl
/usr/bin/openssl:
libssl.so.111 => /usr/lib/libssl.so.111 (0x8002dd000)
libcrypto.so.111 => /lib/libcrypto.so.111 (0x800375000)
libc.so.7 => /lib/libc.so.7 (0x800664000)
libthr.so.3 => /lib/libthr.so.3 (0x800a5d000)
% ldd /usr/local/bin/openssl
/usr/local/bin/openssl:
libssl.so.11 => /usr/local/lib/libssl.so.11 (0x8002dc000)
libcrypto.so.11 => /usr/local/lib/libcrypto.so.11 (0x800372000)
libthr.so.3 => /lib/libthr.so.3 (0x8005f9000)
libc.so.7 => /lib/libc.so.7 (0x800626000)
So my base openssl program is linked to /usr/lib/libssl.so.111
My ports openssl program is linked to /usr/local/lib/libssl.so.11
Or looking at mod_ssl for Apache:
Code:
% ldd /usr/local/libexec/apache24/mod_ssl.so
/usr/local/libexec/apache24/mod_ssl.so:
libssl.so.11 => /usr/local/lib/libssl.so.11 (0x8006ab000)
libcrypto.so.11 => /usr/local/lib/libcrypto.so.11 (0x800e00000)
libcrypt.so.5 => /lib/libcrypt.so.5 (0x800741000)
libthr.so.3 => /lib/libthr.so.3 (0x800762000)
libc.so.7 => /lib/libc.so.7 (0x80024a000)
You can see libssl.so.11 is located at /usr/local/lib/libssl.so.11 - so my mod_ssl is linked to the ports OpenSSL.
Same for MySQL:
Code:
% ldd /usr/local/libexec/mysqld
/usr/local/libexec/mysqld:
libz.so.6 => /lib/libz.so.6 (0x800d6e000)
libm.so.5 => /lib/libm.so.5 (0x800d88000)
libexecinfo.so.1 => /usr/lib/libexecinfo.so.1 (0x800dba000)
libcrypt.so.5 => /lib/libcrypt.so.5 (0x800dbf000)
libssl.so.11 => /usr/local/lib/libssl.so.11 (0x800de0000)
libcrypto.so.11 => /usr/local/lib/libcrypto.so.11 (0x800e76000)
libc++.so.1 => /usr/lib/libc++.so.1 (0x8010fd000)
libcxxrt.so.1 => /lib/libcxxrt.so.1 (0x8011cd000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x8011ef000)
libthr.so.3 => /lib/libthr.so.3 (0x801209000)
libc.so.7 => /lib/libc.so.7 (0x801236000)
libelf.so.2 => /lib/libelf.so.2 (0x80162f000)
You can see libssl is pointing to /usr/
local/lib/libssl.so.11 - the ports OpenSSL.
You've said "I most certainly want to avoid future problems on this server build" - but what I've recommended doesn't guarantee that. Like I said if an OpenSSL 2.x (or whatever) came out with whizzy new features and you wanted to use them in e.g. Apache - then using the base OpenSSL will mean you can't. You are making a choice - the base OpenSSL should be fine and it should be easier to build ports using it but it is a choice! It's your system, so you have to make the choice.
I'm pretty sure you don't want to mix & match the versions.
