From owner-freebsd-current  Sun Feb  2 19:08:30 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA03679
          for current-outgoing; Sun, 2 Feb 1997 19:08:30 -0800 (PST)
Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA03667
          for <freebsd-current@FreeBSD.ORG>; Sun, 2 Feb 1997 19:08:22 -0800 (PST)
Received: (from davidn@localhost)
	by labs.usn.blaze.net.au (8.8.5/8.8.5) id OAA15227;
	Mon, 3 Feb 1997 14:07:25 +1100 (EST)
Message-ID: <19970203140724.QM50066@usn.blaze.net.au>
Date: Mon, 3 Feb 1997 14:07:24 +1100
From: davidn@unique.usn.blaze.net.au (David Nugent)
To: terry@lambert.org (Terry Lambert)
Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.ORG
Subject: Re: getty patches
References: <Mutt.19970202221224.j@uriah.heep.sax.de> <199702030034.RAA09929@phaeton.artisoft.com>
X-Mailer: Mutt 0.59.1
Mime-Version: 1.0
In-Reply-To: <199702030034.RAA09929@phaeton.artisoft.com>; from Terry Lambert on Feb 2, 1997 17:34:19 -0700
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Terry Lambert writes:
> > 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.

Authentication is only one aspect of login.conf.


> I'm not aware that the current login.conf code is capable of running
> the commercial authenticators... I'd be happy to be corrected.

You're quite correct. The reason that authentication is not
available is lack of information, pure and simple. I'm still
waiting for information from either/both sef and BSDI on it,
and how the API is intended to work. There are quite a few
ambiguities to resolve. Currently login(1) includes the 
relevant code to support them, but it is not compiled in.


> 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.

No, that's an 'motd' file. The issue file is sent before login.conf
can be used since there is no user logged in when getty starts.


Regards,

David Nugent - Unique Computing Pty Ltd - Melbourne, Australia
Voice +61-3-9791-9547  Data/BBS +61-3-9792-3507  3:632/348@fidonet
davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/