From owner-freebsd-hackers  Sun Jul 14 17:38:27 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA19562
          for hackers-outgoing; Sun, 14 Jul 1996 17:38:27 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA19553
          for <hackers@FreeBSD.org>; Sun, 14 Jul 1996 17:38:25 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA07346; Sun, 14 Jul 1996 17:31:43 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199607150031.RAA07346@phaeton.artisoft.com>
Subject: Re: "login classes"
To: sef@kithrup.com (Sean Eric Fagan)
Date: Sun, 14 Jul 1996 17:31:43 -0700 (MST)
Cc: hackers@FreeBSD.org
In-Reply-To: <199607140659.XAA02107@kithrup.com> from "Sean Eric Fagan" at Jul 13, 96 11:59:36 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-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> There are three sides to the login classes -- the library functions,
> modified utilities, and some new utilities to provide authentication.  I
> don't know that I can do the login et al modifications, and I *know* I don't
> know about about kerberos and S/Key to write that.

Have you looked at the PAM (Pluggable Authentication Modules) RFC?

Also, you may want to contact authentication third party vendors
as used by BSDI, to duplicate that interface.

It looks like there are several existing standards to consider
in this area...


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.