[14203] in Athena Bugs
Re: telnetd: spurious "You must use the encryption option"
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Feb 20 12:45:22 1996
To: brlewis@MIT.EDU
Cc: Greg Hudson <ghudson@MIT.EDU>, bugs@MIT.EDU
In-Reply-To: Your message of "Tue, 20 Feb 1996 10:23:41 EST."
<9602201523.AA29836@joy.MIT.EDU>
Date: Tue, 20 Feb 1996 12:45:17 EST
From: Greg Hudson <ghudson@MIT.EDU>
>>Please explain what's wrong with the protocol such that timeouts are
>>needed before forking login. Shouldn't telnetd simply initiate
>>request for authentication and encryption, and wait for the response?
> I don't know whether to call this a problem with the protocol. If
> one were to augment the protocl to get around this problem, one
> would need to add something like "ENCRYPT WONT START". If a client
> supports encryption, there's no way to know when/if it will actually
> begin encrypting its output (telnetd's input).
What happens if the server sends "DO ENCRYPT" to the client?
