[367] in Kerberos
daemon@TELECOM.MIT.EDU (steiner@ATHENA.MIT.EDU)
Tue Apr 19 16:34:52 1988
From: steiner@ATHENA.MIT.EDU
To: kerberos@ATHENA.MIT.EDU, sdsu!vinge@UCSD.EDU
(Please copy Vernor on any replies as he is not on
the mailing list.)
Jennifer
------- Forwarded Message
Received: by E40-PO.MIT.EDU (5.45/4.7) id AA21587; Sat, 16 Apr 88 23:17:58 EST
Received: by ATHENA.MIT.EDU (5.45/4.7) id AA20583; Sat, 16 Apr 88 23:17:22 EST
Received: from sdsu by ucsd.edu (5.58/UCSD-1.0) via UUCP;
Sat, 16 Apr 88 21:18:15 PDT id AA06696 for steiner@ATHENA.MIT.EDU
Received: by sdsu.SDSU.EDU (5.51/SDSU-ROOT)
id AA28587 for delivery to ucsd!steiner@athena.mit.edu; Sat, 16 Apr 88 21:15:24 PDT
From: sdsu!vinge@ucsd.edu (Vernor Vinge)
Message-Id: <8804170415.AA28587@sdsu.SDSU.EDU>
To: steiner@ATHENA.MIT.EDU
Subject: kerberos question
Date: Sat, 16 Apr 88 21:15:19 PDT
Jennifer --
I just read "Kerberos: An Authentication Service for Open Network
Systems". Thanks for showing me how to get it.
I have a question (2.5 actually):
Why is it necessary to include the client's IP address in the tickets
and authenticators? Wouldn't the client's name suffice?
Why is it necessary to include the server's name in the ticket?
Thanks,
- -- Vernor
Vernor Vinge
Dept Math Sci
San Diego State University
San Diego, CA 92182
------- End of Forwarded Message
