On Fri, Mar 20, 2015 at 07:13:53PM -0400, Wietse Venema wrote:
> Viktor Dukhovni:
> > I am curious what:
> >
> > ldd /usr/local/lib/libssl.so.8
> >
> > reports and whether there are headers and or shared objects for
> > libz in ports?
>
> In a FreeBSD 10.1 testvm:
>
> # ldd -a /usr/local/lib/libssl.so.8
> /usr/local/lib/libssl.so.8:
> libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x801668000)
> libthr.so.3 => /lib/libthr.so.3 (0x801a6c000)
> libc.so.7 => /lib/libc.so.7 (0x80081f000)
> /usr/local/lib/libcrypto.so.8:
> libthr.so.3 => /lib/libthr.so.3 (0x801a6c000)
> libc.so.7 => /lib/libc.so.7 (0x80081f000)
> /lib/libthr.so.3:
> libc.so.7 => /lib/libc.so.7 (0x80081f000)
>
> Fascinating: no libz dependency. See below for build options.
Perhaps the OP built OpenSSL and explicitly enabled the optional libz
compression support. Also, OpenSSL can be built to support dynamic
loading of libz:
Configure ... [[no-]zlib|zlib-dynamic] ...
# [no-]zlib [don't] compile support for zlib compression.
# zlib-dynamic Like "zlib", but the zlib library is expected to be a
shared
# library and will be loaded in run-time by the OpenSSL
library.
Lots of opportunities for things to go wrong. I've always built
OpenSSL without compression support.
--
Viktor.
