From owner-freebsd-current Sun Feb 2 16:36:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA25030 for current-outgoing; Sun, 2 Feb 1997 16:36:03 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA25014 for ; Sun, 2 Feb 1997 16:35:59 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA09929; Sun, 2 Feb 1997 17:34:19 -0700 From: Terry Lambert Message-Id: <199702030034.RAA09929@phaeton.artisoft.com> Subject: Re: getty patches To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 2 Feb 1997 17:34:19 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: from "J Wunsch" at Feb 2, 97 10:12:24 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > There are a number of people who have been working on login.conf > > changes; at the very least, your /etc/issue capability probably > > conflicts with this. > > Funny you should notice that FreeBSD's login.conf implementation has > been brought in by David Nugent. :-)) I was only aware of the work by SEF, with the goal toward being able to use commercial authenticators, like those supported in BSDI, by running the BSDI binaries. I'm not aware that the current login.conf code is capable of running the commercial authenticators... I'd be happy to be corrected. As to the login.conf/issue conflict, if the same person is doing both code sets, one would expect them to avoid conflicts like this. There is a well define issue file interface in BSDI's login.conf. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.