Path: utzoo!attcan!uunet!cs.utexas.edu!usc!apple!sun-barr!decwrl!shelby!SRC.DEC.COM!saltzer
From: saltzer@SRC.DEC.COM (Jerry Saltzer)
Newsgroups: comp.protocols.kerberos
Subject: Re: Proposal for long-lived revocable tickets.
Message-ID: <8907211826.AA19325@jumbo.pa.dec.com>
Date: 21 Jul 89 18:26:00 GMT
References: <8907051758.AA00754@LYCUS.MIT.EDU>
Sender: daemon@shelby.Stanford.EDU
Organization: The Internet
Lines: 19

John suggests,

"1) an entry in the hot list need only be maintained in that list until
the maximum site "life" has passed.  After this point, any hot-listed
ticket will no longer be valid for obtaining a replacement, as it will
have expired.

2) The hot list should be short and easy to maintain." 

The initial, zero-order implementation could be just to hold the
user's name and refuse to renew any tickets for that user
until LIFE has passed.  That would be a little inconvenient for
the user, but on the other hand, the use of revocation and
hot lists would probably be a very rare event; polishing to
improve the granularity of revocation is something that can
be left as a future exercise.

                                Jerry