Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!uunet!shelby!SNLL-ARPAGW.LLNL.GOV!hilary
From: hilary@SNLL-ARPAGW.LLNL.GOV (Hilary Jones)
Newsgroups: comp.protocols.kerberos
Subject: Re: Storing tickets safely
Message-ID: <9103041655.AA17383@snll-arpagw.llnl.gov>
Date: 4 Mar 91 16:55:41 GMT
Sender: news@shelby.stanford.edu (USENET News System)
Organization: Internet-USENET Gateway at Stanford University
Lines: 12

>We already have a commitment from elsewhere to do a shared-memory
>credentials cache implementation, but if you were interested in a
>different model, we would welcome help with it.
	
OK, I will see what I can come up with.
	
>If you discover a ticket theft, you can instruct the KDC to refuse to
>replace that ticket when a renewal is requested.

I gather from this that version 5 of Kerberos is no longer stateless.  
Is that correct?  Otherwise, a renewable ticket isn't really any 
different that any other kind of ticket.