Bug 10954 - samba4 ADS segfaults from auth methods usage by ADS SERVER / MEMBER
Summary: samba4 ADS segfaults from auth methods usage by ADS SERVER / MEMBER
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: libsmbclient (show other bugs)
Version: 4.1.13
Hardware: All All
: P5 critical (vote)
Target Milestone: 4.3
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
Depends on:
Reported: 2014-11-23 11:38 UTC by Remsnet (dead mail address)
Modified: 2021-01-13 18:47 UTC (History)
2 users (show)

See Also:

coredump sernet samba 4.1.3 (38.43 KB, text/plain)
2014-11-23 11:38 UTC, Remsnet (dead mail address)
no flags Details
gdb coredump (1.93 KB, text/plain)
2014-11-23 11:39 UTC, Remsnet (dead mail address)
no flags Details
smb.conf (4.49 KB, text/plain)
2014-11-23 11:40 UTC, Remsnet (dead mail address)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Remsnet (dead mail address) 2014-11-23 11:38:12 UTC
Created attachment 10452 [details]
coredump sernet samba 4.1.3

while usage at smb.conf 

 auth methods = guest sam winbind

symtoms :

- SAMBA4 stop clean working
- create coredumps at every client, allmost every second ..
- smbclient -L \\<server> -U Administrator stop working local and remote

samba docus don´t say  that set the allowed auth methods isn´t possible with in AD SERVER or MEMBER mode.

reason for set it : ldap clients ( php/perl/..)

Issue checked and reproducable with sernet samba4.1.x
 + bind 9.8.2( without spnego)
 as well with 9.9.5( with spnego )
Comment 1 Remsnet (dead mail address) 2014-11-23 11:39:11 UTC
Created attachment 10453 [details]
gdb coredump
Comment 2 Remsnet (dead mail address) 2014-11-23 11:40:54 UTC
Created attachment 10454 [details]
Comment 3 Amit Kumar 2018-09-21 05:41:03 UTC
Hello Remsnet LTD Support,
Option is deprecated.
# testparm 
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "auth methods" option is deprecated
Comment 4 Rowland Penny 2021-01-13 18:47:08 UTC
Doesn't anyone read the smb.conf if they are provided in a bug report ?

This so called bug was very probably caused by the very mangled AD DC smb.conf, which contained invalid parameters, lines that should only have been on a Unix domain member and even worse, it was using likewiseopen.

The bug reporters email is now dead, so we will probably never get any further updates. The reasons given to cause the problem have never caused Samba to crash for myself and if it was a real problem, I would have expected lots of reports on the samba mailing list and this just hasn't happened.

The bug reporter was using 4.1.3, so this would have been using the old 'winbind', this could also have had a bearing on the problem.

With all this in mind, I am closing this bug.