Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site jc3b21.UUCP
Path: utzoo!linus!decvax!bellcore!petrus!sabre!zeta!epsilon!gamma!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!akguc!codas!peora!ucf-cs!usfvax2!3b2bame!jc3b21!jra
From: jra@jc3b21.UUCP (Jay R. Ashworth)
Newsgroups: net.unix,net.micro.pc,net.crypt
Subject: Re: Non-ATT 'crypt(3)'
Message-ID: <132@jc3b21.UUCP>
Date: Wed, 25-Dec-85 19:08:33 EST
Article-I.D.: jc3b21.132
Posted: Wed Dec 25 19:08:33 1985
Date-Received: Sat, 28-Dec-85 23:36:07 EST
References: <357@ho95e.UUCP>
Organization: Proma Corp., Seminole, FL
Lines: 22
Xref: linus net.unix:6151 net.micro.pc:6111 net.crypt:461

In article <357@ho95e.uucp>, Bill Stewart discusses the lack of need to
make a substitute crypt(3) program produce cyphertext which an at&t
crypt program can decipher. (or, at least, that's what I *thought* he was
talking about...)  
	His point seems to be well taken, for the only problem caused would 
be the inability to decrypt something which another site has sent you, to 
which you know the key.  However, if you *have* source code for a crypt 
program, you can just send them a copy (assuming legalities permit), and
ask them to use *it*, instead of the 'standard' version.  A small logistics
prolem, maybe, but no other ones that I can see.  Of course, by legalities
above, I meant copyrights, etc., not legal restrictions on encryption
technology.  I refuse to comment on that, the NSA might be listening :-).
-- jra
-- 
Jay R. Ashworth    	Proma Software   	jra@jc3b22.UUCP  
Programmer/Analyst	9189 Park Blvd.		(813) 399-1045
Boy Genius (:-)		Seminole FL 33544	(So they tell me)

Disclaimer: The opinions, if any, expressed in this article, if any, 
	    are not those of my employer, if any, or anybody else,
	    and probably resulted from Coca-Cola (Coca-Cola is a reg. tm
	    of Coca-Cola USA) dripping down my keyboard.