1994-07-11 - Re: Request: tamper-proofing executables

Header Data

From: Roger Bryner <bryner@atlas.chem.utah.edu>
To: N/A
Message Hash: 9673da779c3de8cfbc8ce336370e02a03a13140f15c5f90be0a03ea36f0603f5
Message ID: <Pine.3.89.9407101928.A14068-0100000@atlas.chem.utah.edu>
Reply To: <199407102309.AA17740@laurel.ocs.mq.edu.au>
UTC Datetime: 1994-07-11 01:06:19 UTC
Raw Date: Sun, 10 Jul 94 18:06:19 PDT

Raw message

From: Roger Bryner <bryner@atlas.chem.utah.edu>
Date: Sun, 10 Jul 94 18:06:19 PDT
Subject: Re: Request: tamper-proofing executables
In-Reply-To: <199407102309.AA17740@laurel.ocs.mq.edu.au>
Message-ID: <Pine.3.89.9407101928.A14068-0100000@atlas.chem.utah.edu>
MIME-Version: 1.0
Content-Type: text/plain


How about a different tack, having all branch instructions feed in some 
number from the program, generated from the state of the program, to a 
lookup hard-key.  The program then branches to the appropriate site.

If the number of branches/states of program  was great enough, this might be 
secure(of cource, they can just watch it and recode, but they could 
probably re-write the code for this ammount.)

Roger.

Thread

• Return to July 1994

• Return to “Ian Farquhar <ifarqhar@laurel.ocs.mq.edu.au>”
• Return to “rarachel@prism.poly.edu (Arsen Ray Arachelian)”
• Return to “Roger Bryner <bryner@atlas.chem.utah.edu>”

• Return to “wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)”

• 1994-07-10 (Sun, 10 Jul 94 00:08:36 PDT) - Re: Request: tamper-proofing executables - wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)
  • 1994-07-10 (Sun, 10 Jul 94 16:09:27 PDT) - Re: Request: tamper-proofing executables - Ian Farquhar <ifarqhar@laurel.ocs.mq.edu.au>
    • 1994-07-11 (Sun, 10 Jul 94 18:01:08 PDT) - Re: Request: tamper-proofing executables - rarachel@prism.poly.edu (Arsen Ray Arachelian)
    • 1994-07-11 (Sun, 10 Jul 94 18:06:19 PDT) - Re: Request: tamper-proofing executables - Roger Bryner <bryner@atlas.chem.utah.edu>