[870] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: Proposed Kerberos V5 Password Changing Algorithm

daemon@ATHENA.MIT.EDU (Marc Horowitz)
Sat Feb 25 20:59:34 1995

To: eichin@MIT.EDU
Cc: rsalz@osf.org, krbdev@MIT.EDU, tytso@MIT.EDU
Date: Sat, 25 Feb 1995 20:59:16 EST
From: Marc Horowitz <marc@MIT.EDU>

I'm willing to submit on binary, although I still think it's Morally
Wrong :-)

However, I'd like to see a version flag at the head of the protocol.
if we decide later we need to change the protocol, it would be good if
the client and server both knew what the other side was trying to do.
It would be fine if both sides piggybacked the protocol vno in the
first message they sent, so that the peer could bail if necessary
(where "bail" might mean "close the socket and forget it", but I'd
like to see an error response at every point in the protocol, in case
the peer did something actually wrong, like mangle a message.

		Marc

home help back first fref pref prev next nref lref last post