Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!lll-winken!taco!eos.ncsu.edu!kctreima
From: kctreima@eos.ncsu.edu (Kenneth C. Treimann)
Newsgroups: comp.protocols.kerberos
Subject: Re: Verifying passwords without getting new tickets
Keywords: password, ticket, KRBTKFILE
Message-ID: <1991May21.011156.20773@ncsu.edu>
Date: 21 May 91 01:11:56 GMT
References: <9105180827.AA13470@steve-dallas.MIT.EDU> <9105201808.AA10941@ATHENA.MIT.EDU>
Sender: news@ncsu.edu (USENET News System)
Followup-To: comp.protocols.kerberos
Organization: North Carolina State University
Lines: 17

Thanks once again to all those who responded to my question.  I suppose my 
real concern about getting tickets for one user was that in doing so, the 
tickets for another user were destroyed.  This meant I had to type in a
password to verify one user, then type in another password to get the original 
user's tickets back.  But thanks to the miracle of KRBTKFILE (and some helpful 
people from MIT and elsewhere), this is no longer a problem.  My program now 
only asks for one password and leaves the original user's tickets alone.

I can always tell when a problem has a simple if not obvious solution.  It's
just finding it is the hard part...
-- 
Kenneth C. Treimann (The Bean) 
Obligatory quote: "F*** you, a******." - The Terminator
Meaningless song lyrics: I'm so bad 
                         I should be in detention.
                               - Anthrax (Stolen from the film Easy Money)
Optional disclaimer: See obligatory quote above.