Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!cbosgd!ucbvax!cit-vax.arpa!engvax!KVC
From: KVC@engvax.UUCP
Newsgroups: fa.info-vax
Subject: Re: execute-only images
Message-ID: <8509180220.AA09953@cit-vax.ARPA>
Date: Tue, 17-Sep-85 22:20:09 EDT
Article-I.D.: cit-vax.8509180220.AA09953
Posted: Tue Sep 17 22:20:09 1985
Date-Received: Fri, 20-Sep-85 05:19:15 EDT
Sender: daemon@ucbvax.ARPA
Reply-To: info-vax@ucb-vax.arpa
Organization: The ARPA Internet
Lines: 15

> What you describe sounds like a BUG FIX to me.  If you have an image which
> you don't want a user to be able to copy, and you allow him to link with an
> arbitrary sharable image, he could put stuff in that sharable image to
> copy the otherwise "execute-only" image.  That bug has now been fixed.

This is a good point that I hadn't thought of.  Seems like it may be
very difficult, on the other hand if you are going to provide "execute-only"
protection, it had best be foolproof.

I still contend that A)  we need a more usable execute-only (likely not
possible given that "foolproofness" is a requirement) and B) some
documentation would've been nice...

	/Kevin Carosso            engvax!kvc @ CIT-VAX.ARPA
	 Hughes Aircraft Co.