From: “Perry E. Metzger” <pmetzger@lehman.com>
To: cypherpunks@toad.com
Message Hash: adbde352d214268040bbdca69dc3fbbec8f62f4353d3bf03fa6d521010579ec9
Message ID: <9403062009.AA17340@andria.lehman.com>
Reply To: <199403062000.UAA17352@an-teallach.com>
UTC Datetime: 1994-03-06 20:09:16 UTC
Raw Date: Sun, 6 Mar 94 12:09:16 PST
From: "Perry E. Metzger" <pmetzger@lehman.com>
Date: Sun, 6 Mar 94 12:09:16 PST
To: cypherpunks@toad.com
Subject: Re: Update on user-level hack to do telnet encryption posted recently
In-Reply-To: <199403062000.UAA17352@an-teallach.com>
Message-ID: <9403062009.AA17340@andria.lehman.com>
MIME-Version: 1.0
Content-Type: text/plain
Graham Toal says:
> Well if you have nothing useful to contribute but won't shut up anyway,
> I will. This conversation is over.
For the benefit of those who aren't being petulant, I will repeat:
The existing, already implemented and available, cryptographic
authentication (but not encrypted) version of the new BSD telnet is
available from:
ftp.cray.com(128.162.15.3):src/telnet/telnet.94.02.07.NE.tar.Z
This is not theoretical code; it really exists. See for yourself. No,
it doesn't just do kerberos.
The proposed telnet encryption and authentication RFCs are available
in the same directory.
The BSD 4.4 domestic distribution already has the encrypted version of
the code in it; perhaps someone should "liberate" it.
Those wishing to run an encrypted telnet to a remote machine that does
not support the new telnet options should ask the remote system
administrator to install the new telnet, which compiles on virtually
every architecture around, including SVR4 (or at least Solaris).
Failing that, you can run your own telnetd on the remote host.
Sorry if suggesting that people use already existing code is being a
"wet blanket".
Perry
Return to March 1994
Return to ““Perry E. Metzger” <pmetzger@lehman.com>”