Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site harvard.ARPA
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!sasaki
From: sasaki@harvard.ARPA (Marty Sasaki)
Newsgroups: net.crypt
Subject: encryption algorithms for software distribution
Message-ID: <78@harvard.ARPA>
Date: Wed, 24-Apr-85 22:47:09 EST
Article-I.D.: harvard.78
Posted: Wed Apr 24 22:47:09 1985
Date-Received: Sat, 27-Apr-85 00:11:28 EST
Distribution: net
Organization: Harvard Science Center
Lines: 30

Please forgive me if this is a topic covered before. I have just started
to read this group.

I have gotten involved with software distribution. Much of the software
requires that a copy of a UNIX source licence be sent before I can send
the software out. When I get the software, I then copy things to tape
and mail the stuff out. When there is an update, I have to send tapes
out again, or possibly mail the diff's.

It would be very convenient if I could just use electronic mail to send
things out (when the code is small, I'm not about to send multi-megabyte
messages). To get around the problem with illicit reading of
information, I thought that encrypting the code before mailing would be
a good idea. When someone sent me a copy of their UNIX license, they
could also send me the key to use in the encryption. When updates
occured, I would merely encrypt the update and mail it off, secure in
the knowledge that only the authorized party could read it.

Is this approach a reasonable one? If it is, could someone send me
either a pointer to an algorithm, an algorithm, or better yet, a program
to do the encryption/decryption?

Crypt(1) is not really feasible since many of the machines are not UNIX
machines and the code for Crypt(1) belongs to AT&T.
-- 
----------------
  Marty Sasaki				net:   sasaki@harvard.{arpa,uucp}
  Havard University Science Center	phone: 617-495-1270
  One Oxford Street
  Cambridge, MA 02138