Path: utzoo!attcan!uunet!unsvax!jimi!duke!greg
From: greg@duke.cs.unlv.edu (Greg Wohletz)
Newsgroups: comp.sys.next
Subject: Re: kerberized login authentication
Message-ID: <1951@jimi.cs.unlv.edu>
Date: 7 Sep 90 18:40:54 GMT
References: <1950@jimi.cs.unlv.edu>
Sender: news@jimi.cs.unlv.edu
Reply-To: greg@jimi.cs.unlv.edu (Greg Wohletz)
Organization: The Cave
Lines: 29

In article <1950@jimi.cs.unlv.edu> jay@unlv.edu (Jay Nietling) writes:
)we'd like to start using kerberos for login authentication on our next
)machines just like we  do on  all our  normal  workstations.   i don't
)think    that  loginwindow  runs    /bin/login  but     does  its  own
)authentication.  is there a magic flag to  loginwindow that will cause
)it to use some other program for authentication?

)failing that --  we  have the nice nextlogin.tiff  file and  there are
)apparently a lot of nice alternative  tiff files in the next archives.
)but,    i'd  like to    get my  hands  on  some   code that works like
)/usr/lib/NextStep/loginwindow to put in ttys.  i'd really like to just
)get  the code to  loginwindow.  can such a  program be built  with the
)interface builder?  although i'd rather not mess with  objective-c and
)the interface builder could someone point  me in  the right direction?
)is everything you need to know to build such a program  (not really an
)application) documented?

well so far this article generated one message from a poor soul who
actually thinks yellowpages is gods gift to system administration, and
another (deservidly) flaming him.  But, nobody has come forth with any
information.

Apparently nobody has yet bitten the bullet and written a replacement
loginwindow application, so...  How about at least a description of the
functional requirements of such a beast?  i.e. how does it signal the
system that the login was sucessfull?  Is it responcible for execing
another program after the login succeeds?  etc.

						--Greg