Bug 11314 - Prevent clashes between system and Samba SHA functions
Summary: Prevent clashes between system and Samba SHA functions
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Build (show other bugs)
Version: 4.2.2
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Björn Jacke
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-07 05:07 UTC by Emmanuel Dreyfus
Modified: 2017-01-03 03:31 UTC (History)
2 users (show)

See Also:

Attachments
Patch for v4-2-test to prevent SHA function clashes (1.90 KB, application/mbox)
2015-06-07 05:07 UTC, Emmanuel Dreyfus 		abartlet: review+
abartlet: review? (jra)
 Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Emmanuel Dreyfus 2015-06-07 05:07:55 UTC 
Created attachment 11126 [details]
Patch for v4-2-test to prevent SHA function clashes

Samba provides its own set of SHA function, which would replace
libc-provided flavors. This is a problem because while the prototypes
are the same, the context structure are different. As a result,
when connecting to a LDAP/SSL directory, we go through
libldap/libssl/libcrypto and there libcrypto expects to call libc
SHA functions, not Samba's.

The fix in attached patch is to check for SHA function presence 
and rename Samba's version to avoid a clash.

This is a backport of d5065ed2f4c6d9f4539297e9794a2b02adec4d12
from samba master branch.
Comment 1 Andrew Bartlett 2017-01-03 03:31:32 UTC 
Fixed in Samba 4.3 with your patch as d5065ed2f4c6d9f4539297e9794a2b02adec4d12

Sadly Samba 4.2 is no longer in support, so we can't fix it for 4.2.

Sorry,