Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!decwrl!shelby!BBN.COM!rsalz
From: rsalz@BBN.COM (Rich Salz)
Newsgroups: comp.protocols.kerberos
Subject: Re:  Proposal for long-lived revocable tickets.
Message-ID: <8907241833.AA04113@prune.bbn.com>
Date: 24 Jul 89 18:33:50 GMT
Sender: daemon@shelby.Stanford.EDU
Organization: The Internet
Lines: 13

>Since getting a very long ticket is a big security risk, it should be
>brought to the user's or to the administrator's attention.
Perhaps.  But not as a feature of the protocol.  In a large, automated
distributed system such things as mail to bring to attention are bad.

I can imagine a database application where the DB server has enough
state so that a ticket is used only once, or a number-cruncher where
I wanna factor a 500-digit possible prime, or run a simulation of a
complex chemical reaction...  whatever.

I understand that things like long tickets are scarey, but then so
is the ability to be able to do "cat >/vmunix".
	/r$