From owner-freebsd-stable Tue Jan 26 10:07:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08864 for freebsd-stable-outgoing; Tue, 26 Jan 1999 10:07:35 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08838 for ; Tue, 26 Jan 1999 10:07:24 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id NAA06907; Tue, 26 Jan 1999 13:07:04 -0500 (EST) Date: Tue, 26 Jan 1999 13:07:04 -0500 (EST) From: John Fieber To: Matt Behrens 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 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.) -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message