Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!wuarchive!uunet!unsvax!jimi!lightnin.cs.unlv.edu!jay
From: jay@lightnin.cs.unlv.edu (Jay Nietling)
Newsgroups: comp.sys.next
Subject: kerberized login authentication
Message-ID: <1950@jimi.cs.unlv.edu>
Date: 29 Aug 90 23:52:17 GMT
Sender: news@jimi.cs.unlv.edu
Reply-To: jay@unlv.edu (Jay Nietling)
Organization: UNLV Computer Science and Electrical Engineering
Lines: 19


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?

-jay
jay@cs.unlv.edu