From owner-freebsd-current Fri Apr 26 10: 4:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from client.paymentonline.com (client.paymentonline.com [63.236.115.2]) by hub.freebsd.org (Postfix) with ESMTP id 9223137B400 for ; Fri, 26 Apr 2002 10:04:27 -0700 (PDT) Received: from localhost (bsd@localhost) by client.paymentonline.com (8.11.2/8.11.2) with ESMTP id g3QH1UT61532 for ; Fri, 26 Apr 2002 10:01:30 -0700 (PDT) Date: Fri, 26 Apr 2002 10:01:30 -0700 (PDT) From: bsd To: current@freebsd.org Subject: passwd and PAM Message-ID: <20020426095423.X61186-100000@client.paymentonline.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I realize this probably isn't a -current issue, but since I don't have any experience with PAM I don't know for sure if it's just me or not. My problem is that the passwd command isn't doing anything, at all. I have the stock pam setup (/etc/pam.d, /etc/pam.conf deleted after running mergemaster). Running adduser will add a user with a password in master.passwd, but running passwd will not change the password, regardless if a password exists or is null. Also, if a user does have a password, with the stock setup not even root can change it without providing the correct previous password. This wasn't intentional was it? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message