From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Nov 9 06:30:22 2004 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24C9916A4CE for ; Tue, 9 Nov 2004 06:30:22 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7A1843D45 for ; Tue, 9 Nov 2004 06:30:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) iA96ULYW002756 for ; Tue, 9 Nov 2004 06:30:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA96ULDt002752; Tue, 9 Nov 2004 06:30:21 GMT (envelope-from gnats) Resent-Date: Tue, 9 Nov 2004 06:30:21 GMT Resent-Message-Id: <200411090630.iA96ULDt002752@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-ports-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, bob frazier Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8623816A4CE for ; Tue, 9 Nov 2004 06:28:22 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72EE543D1F for ; Tue, 9 Nov 2004 06:28:22 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id iA96SM7C093556 for ; Tue, 9 Nov 2004 06:28:22 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id iA96SM6P093555; Tue, 9 Nov 2004 06:28:22 GMT (envelope-from nobody) Message-Id: <200411090628.iA96SM6P093555@www.freebsd.org> Date: Tue, 9 Nov 2004 06:28:22 GMT From: bob frazier To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: ports/73703: Samba 'obey pam restrictions' causes PANIC in Samba 3 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2004 06:30:22 -0000 >Number: 73703 >Category: ports >Synopsis: Samba 'obey pam restrictions' causes PANIC in Samba 3 >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 09 06:30:21 GMT 2004 >Closed-Date: >Last-Modified: >Originator: bob frazier >Release: RELENG_5 (5.3-STABLE #1) >Organization: SFT Inc. >Environment: FreeBSD BSDServer.SFT.local 5.3-STABLE FreeBSD 5.3-STABLE #1: Tue Oct 26 20:13:16 PDT 2004 root@:/usr/obj/usr/src/sys/GENERIC i386 >Description: When attempting to use the latest Samba 3 port (3.0.7), following a portupgrade of all ports (using cvs tag RELEASE_5_3_0), I noticed that all users that had a login without a blank password were unable to list or access any shares. Blank password users (such as a 'guest' type user without a password) worked ok. Domain logins still worked properly. Only access to the shares was affected. When I commented out the "obey pam restrictions = yes" line in smb.conf, the problem went away. Rebuilding the port via portupgrade -f (as well as 'make deinstall' / 'make reinstall'), restoring tdb's from backup, etc. had no effect. >How-To-Repeat: using FBSD RELENG_5, Samba 3.0.7 and latest ports a) set up Samba 3 as a domain controller b) add some shares and users c) add the line "obey pam restrictions = yes" to the global section of smb.conf d) attempt to list shares without a user (smbclient -U% -L localhost) and with a user (smbclient -U username -L localhost) where 'username' is a valid user with a password (and not 'root'). e) remove the line "obey pam restrictions = yes" from the global section of smb.conf f) repeat step d. >Fix: remove the line "obey pam restrictions = yes" from the global section of smb.conf to work around the problem. >Release-Note: >Audit-Trail: >Unformatted: