From owner-freebsd-current Wed Jan 30 11:24: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 82EB037B402; Wed, 30 Jan 2002 11:23:58 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 1755B5341; Wed, 30 Jan 2002 20:23:55 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: current@freebsd.org Subject: HEADS UP: login(1) PAMified References: <200201301910.g0UJAMp60199@freefall.freebsd.org> From: Dag-Erling Smorgrav Date: 30 Jan 2002 20:23:55 +0100 In-Reply-To: <200201301910.g0UJAMp60199@freefall.freebsd.org> Message-ID: Lines: 21 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 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 Dag-Erling Smorgrav writes: > Log: > Still with asbestos longjohns on, completely PAMify login(1) and remove > code made redundant by various PAM modules (primarily pam_unix(8)). > > Sponsored by: DARPA, NAI Labs This commit and the ones immediately preceding and following it strip most of the authentication logic out of login(1) and moves it into various PAM modules. Provided that your PAM library is up to date and you have etc/pam.d/login rev 1.7 (mergemaster is your friend!), login(1) should behave just like it used to. There's still a chance that something will crop up, though, so I'd recommend against upgrading systems you can't easily boot into single-user mode to fix a broken PAM config. If you run into trouble you can't get out of on your own, contact me by mail or on IRC (EvilDES on EFNet) and I'll try to figure it out ASAP. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message