From owner-freebsd-security  Fri Jan 19 12:32:43 2001
Delivered-To: freebsd-security@freebsd.org
Received: from jenkins.web.us.uu.net (jenkins.web.us.uu.net [208.240.88.32])
	by hub.freebsd.org (Postfix) with ESMTP id 4C36537B402
	for <freebsd-security@FreeBSD.ORG>; Fri, 19 Jan 2001 12:32:26 -0800 (PST)
Received: from jenkins.web.us.uu.net (localhost.web.us.uu.net [127.0.0.1])
	by jenkins.web.us.uu.net (Postfix) with ESMTP
	id E79A912686; Fri, 19 Jan 2001 15:32:18 -0500 (EST)
To: freebsd-security@FreeBSD.ORG
Cc: djm@web.us.uu.net
Subject: login_access()
Date: Fri, 19 Jan 2001 15:32:18 -0500
From: "David J. MacKenzie" <djm@web.us.uu.net>
Message-Id: <20010119203218.E79A912686@jenkins.web.us.uu.net>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

login.c in -stable is compiled by default with login_access(),
which is in the login source directory.  It reads /etc/login.access
to restrict who can login.  sshd also uses that source file.

However, rshd and the MIT krb5 port don't check that file,
so relying on it for authorization is risky.
I suggest that login_access() be removed from the login source directory
and turned into a PAM module account management function so it can be
used uniformly without specially hacking each program that needs it.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message