From owner-freebsd-bugs@FreeBSD.ORG  Thu Apr  2 17:08:33 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 3115C104
 for <freebsd-bugs@FreeBSD.org>; Thu,  2 Apr 2015 17:08:33 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 17023263
 for <freebsd-bugs@FreeBSD.org>; Thu,  2 Apr 2015 17:08:33 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t32H8W4A078114
 for <freebsd-bugs@FreeBSD.org>; Thu, 2 Apr 2015 17:08:32 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 199119] libmd conflicts with libcrypto
Date: Thu, 02 Apr 2015 17:08:33 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: thomas@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-199119-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 17:08:33 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199119

            Bug ID: 199119
           Summary: libmd conflicts with libcrypto
           Product: Base System
           Version: 10.1-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: thomas@FreeBSD.org

libmd provides symbols that have the same name, but (presumably) are not
compatible, with libcrypto.

As a result, a program linked against libmd cannot connect to an LDAP server
using SSL, because libldap will resolve symbols in libmd, whereas it expects
those from libcrypto.

An annoying collateral is that crontab(1) will hang when using nss_ldap,
because it is linked against libmd to get MD5.

Various solutions are possible:
  * link libmd statically in crontab(1)
  * add -lcrypto before -lmd when linking crontab(1)
  * make libmd symbols consistent (ABI-compatible) with those in libcrypto
  * use different syumbol names in libmd to avoid the clash
  * remove libmd symbols that duplicate functionality from libcrypto
  * deprecate libmd altogether and use other hash functions from libcrypto.

-- 
You are receiving this mail because:
You are the assignee for the bug.