1994-03-02 - Re: low-overhead encrypted telnet

Header Data

From: jpp@markv.com
To: cypherpunks@toad.com
Message Hash: 5939893e134f7e07ffdabd178be66a66e5d9a17c0ee074ab5f0ec1ddeab64048
Message ID: <9403021307.aa10907@hermix.markv.com>
Reply To: <Pine.3.88.9403021855.J1102-0100000@svme.er.sintef.no>
UTC Datetime: 1994-03-02 21:08:27 UTC
Raw Date: Wed, 2 Mar 94 13:08:27 PST

Raw message

From: jpp@markv.com
Date: Wed, 2 Mar 94 13:08:27 PST
To: cypherpunks@toad.com
Subject: Re: low-overhead encrypted telnet
In-Reply-To: <Pine.3.88.9403021855.J1102-0100000@svme.er.sintef.no>
Message-ID: <9403021307.aa10907@hermix.markv.com>
MIME-Version: 1.0
Content-Type: text/plain

The IP security program I have been working on (slowly) is a packet
redirector and cryptdec.  You ask it to encrypt packets comming in on
one socket, and pass them out to another socket (also to decrypt those
comming in on the second socket and pass them out the first socket).
Thus you can run one of these on the X server, and one on the X
client, and all the X trafic becomes encrypted over the net.  You can
telnet to the local redirector, to the forign redirector, and then to
the standard telnet port.  Or FTP, or whatever.

I am still learning about net software, and this vision may not be
easly implemented, or sockets may be the wrong level of interface to
the net, I dunno.  But I do know that my unix (SCO) and my X server
(WINDOWS) both support this stratagy.