Bug 3107 - Swat password check fails because of wrong crypt()
Summary: Swat password check fails because of wrong crypt()
Status: RESOLVED WONTFIX
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: SWAT (show other bugs)
Version: 3.0.20
Hardware: x86 Linux
: P3 minor
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-17 06:09 UTC by Godfried van Berkel
Modified: 2013-09-02 12:50 UTC (History)
0 users

See Also:

Attachments
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 Godfried van Berkel 2005-09-17 06:09:39 UTC 
Samba 3.0.20 builds fine with ./configure; make; make install on slackware 8.1
system.

Password authentication for Swat fails. It appears that the call to crypt() in
auth/pass_check.c:574 (or about) is not linked to the crypt() in libcrypt, but
to the one in libcrypto.

./configure finds both libraries, but the wrong one seems to get precedence. The
crypt() implementation in libcrypto.so doesn't handle the GNU MD5 extension right.

After removing -lcrypto from Makefile and recompiling, swat works fine.

My versions:
Slackware 8.1
libcrypt-2.2.5.so from glibc-2.2.5
libcrypto.so.0.9.6 from openssl-0.9.6d

Is this a bug in ./configure or is it a nasty feature?

Cheers, Godfried
Comment 1 Gerald (Jerry) Carter (dead mail address) 2006-01-18 08:41:42 UTC 
The problme is that cups requires libcrypto.
We get the library listr from 'cups-config --libs'.
So you can either disable cups or compile to include
--with-pam (does SLackware use PAM?)

Do you have a patch other than manually removing the 
libcrypto dependency?
Comment 2 Björn Jacke 2013-09-02 12:50:11 UTC 
cups is gone with 4.1