[1515] in Kerberos_V5_Development
Re: rlogin -x --> rlogin -noencryption
daemon@ATHENA.MIT.EDU (Sam Hartman)
Wed Aug 7 14:51:16 1996
To: "Barry Jaspan" <bjaspan@MIT.EDU>
Cc: Sam Hartman <hartmans@MIT.EDU>, krbdev@MIT.EDU
From: Sam Hartman <hartmans@MIT.EDU>
Date: 07 Aug 1996 14:48:33 -0400
In-Reply-To: "Barry Jaspan"'s message of Wed, 7 Aug 1996 14:32:04 -0400
>>>>> ""Barry" == "Barry Jaspan" <bjaspan@MIT.EDU> writes:
"Barry> It is important to realize that kshd can't work this
"Barry> way.
You could do that. Richard didn't. He encodes whether the
session will be encrypted as part of the command line to kshd that is
sent over. If the command line is checksummed (as it is without the
-i option to kshd), this is secure. So, there is only one port for
kshell, where as there are two ports for klogin.
"Barry> Ummm.. I didn't realize that. Why not? It seems to me
"Barry> you can just set up kshell and ekshell like klogin and
"Barry> eklogin. What am I missing?
"Barry> Barry
