KVC@engvax.UUCP (09/18/85)
> 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.