Date: Tue, 16 Feb 1999 02:48:25 -0500 (EST) From: gene@cif.rochester.edu To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: conf/10115: /etc/login.conf still implies LOGIN_CAP_AUTH Message-ID: <199902160748.CAA28977@roundtable.cif.rochester.edu>
next in thread | raw e-mail | index | archive | help
>Number: 10115
>Category: conf
>Synopsis: /etc/login.conf still implies LOGIN_CAP_AUTH
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Mon Feb 15 23:50:01 PST 1999
>Closed-Date:
>Last-Modified:
>Originator: Gene Skonicki
>Release: FreeBSD 2.2.8-STABLE i386
>Organization:
University of Rochester
>Environment:
FreeBSD 2.2.8-RELEASE
However, I've confirmed my assertion with the CVS repository.
>Description:
The login.conf file as shipped under standard FreeBSD 3.1 (and 3.0)
still has all its examples involving auth-default and friends. In recent
memory, (around the inclusion of PAM) the support for login-auth methods was
completely deleted from login. So, these examples no longer make sense and
could be confusing.
Likewise, the manpage should probably be generally overhauled to reflect
the new world order.
>How-To-Repeat:
>Fix:
Update default login.conf file and associated manpage.
Probably cross-reference pam stuff on login.conf mp.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902160748.CAA28977>