Updating Samba to 4.3.11_1

Karl Denninger karl at denninger.net
Sun Jul 24 20:57:07 UTC 2016

On 7/24/2016 15:13, Don Lewis wrote:
> My best guess at this point is that one of the samba dependencies on
> your machine is linked to the base version of libcrypto.so, and that is
> preventing libcrypto.so from the ports version of openssl from being
> loaded to resolve the BIO_dgram_is_sctp and BIO_dgram_sctp_wait_for_dry
> symbols.
Your suspicion was correct; it was libarchive, which was linked against
the base ssl libraries.

I know this has had a package update applied to it in the past due to
being flagged in the nightly security run.  That in turn is probably
what broke it, since that would have been built without openssl as a port.

This may be a generalized problem that just happened to manifest in this
situation; I've believed that pkgng made the use of ports and packages
on an interchangeable basis "mostly safe", but in the case of anything
that includes openssl (or potentially any other system service library)
and the base and port libraries are not compatible (even though they
have the same minor version numbers, and thus the linker would expect
they *are*) you're at risk of getting bit by this.

Karl Denninger
karl at denninger.net <mailto:karl at denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2996 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20160724/5427c123/attachment.bin>

More information about the freebsd-ports mailing list