Re: Questions, concerns about ANDF (Robert E. Novak)
11 May 89 20:18:13 GMT

          From comp.compilers

Related articles
Questions, concerns about ANDF (Dick Dunn) (1989-05-05)
Re: Questions, concerns about ANDF (Zalman Stern) (1989-05-08)
Re: Questions, concerns about ANDF (1989-05-10)
Re: Questions, concerns about ANDF (1989-05-11)
Re: Questions, concerns about ANDF (1989-05-12)
| List of all articles for this month |

Newsgroups: comp.compilers
Keywords: public key encryption
Date: 11 May 89 20:18:13 GMT
References: <> <>
From: (Robert E. Novak)
Organization: MIPS Computer Systems, Sunnyvale, CA

Why don't we just ship encrypted source code as the ANDF?

The main purpose of an ANDF is to allow vendors to ship some machine
independent form of their program that can be installed on a machine. Thus
we can have true shrink wrap software. The vendors have proprietary
algorthms locked up in their source code, hence the desire to not ship the
source. Yet, almost any ANDF would be in such a form that uncompiling an
ANDF back to source code would be fairly simple.

Sooo... let's ship the source using public key encryption where the
compilers are built by 'trusted' manufacturers that will decrypt and
compile the source code and install it, without ever revealing the source
code. Decryption or intercepting the compiler halfway through is
guaranteed to be more difficult than uncompiling an ANDF.
Robert E. Novak MIPS Computer Systems, Inc.
{ames,decwrl,pyramid}!mips!rnovak 928 E. Arques Ave. Sunnyvale, CA 94086
rnovak@admin.mips.COM ( +1 408 991-0402
[Seems to me that it's unlikely that you could create such a scheme that wasn't
fairly easy to reverse engineer. Public key encryption assumes that the
decryption key is not public, but in this case you'd be shipping it in every
copy of the compiler. -John]

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.