From owner-freebsd-stable Tue Jan 26 11:48:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20886 for freebsd-stable-outgoing; Tue, 26 Jan 1999 11:48:21 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20876 for ; Tue, 26 Jan 1999 11:48:16 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.2/8.9.2) with ESMTP id OAA16282; Tue, 26 Jan 1999 14:44:18 -0500 (EST) (envelope-from matt@zigg.com) Date: Tue, 26 Jan 1999 14:44:17 -0500 (EST) From: Matt Behrens To: John Fieber cc: Chris Stenton , stable@FreeBSD.ORG Subject: Re: old version of PAM in 3.0-stable stopping Samba working? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry. I jumped to an unfounded conclusion. Actually, I read your message, John, shortly after mine, and oopsed privately. Now I can oops publicly. On Tue, 26 Jan 1999, John Fieber wrote: : On Tue, 26 Jan 1999, Matt Behrens wrote: : : > It looks to me that PAM isn't quite "Linux-compatible", and Samba : > was definitely written for Linux PAM. : : How so? It looked to me like the original poster was just trying : to use pam modules for a services they don't implement: : : > : samba account requisite pam_cleartext_pass_ok.so : > : samba account required pam_unix.so try_first_pass : : That doesn't mean the library is broken or incompatible, just : that our modules are different. (And as I said, somewhat : minimalist at this point in time.) - Matt Behrens Network Administrator, zigg.com Engineer, Nameless IRC Network To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message