1992-11-13 - Datalink encryption

Header Data

From: pmetzger@shearson.com (Perry E. Metzger)
To: avalon@coombs.anu.edu.au
Message Hash: 0fab5ef197d33444949b19d889b161a7350ea3077f27dd00cc0320c0e15a07c8
Message ID: <9211131640.AA23728@newsu.shearson.com>
Reply To: <9211131022.AA20601@coombs.anu.edu.au>
UTC Datetime: 1992-11-13 16:47:19 UTC
Raw Date: Fri, 13 Nov 92 08:47:19 PST

Raw message

From: pmetzger@shearson.com (Perry E. Metzger)
Date: Fri, 13 Nov 92 08:47:19 PST
To: avalon@coombs.anu.edu.au
Subject: Datalink encryption
In-Reply-To: <9211131022.AA20601@coombs.anu.edu.au>
Message-ID: <9211131640.AA23728@newsu.shearson.com>
MIME-Version: 1.0
Content-Type: text/plain


>From: avalon@coombs.anu.edu.au (Darren Reed)

>Hi, I've started playing around with doing encryption with telnet/telnetd
>again (I'm cheating and using the rsa/prime number code from pgp-2.0)
>and I'm stuck on what to use as the encryption for the actual flow of data.
>(hmm...if it works for telnet/telnetd, it can probably be made to work for
> the other r-daemons too :-)

>The idea is telnet and telnetd each choose an rsa pub & sec key, then use
>rsa to encode a key for the encryption scheme which both ends send and
>then use that for the base of the link encryption.

Use IDEA; its sitting right in the PGP code.

Perry





Thread