Date: Thu, 02 Apr 2015 17:08:33 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 199119] libmd conflicts with libcrypto Message-ID: <bug-199119-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199119-8>