home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.m68k
- Path: sparky!uunet!munnari.oz.au!newsroom.utas.edu.au!bruny.cc.utas.edu.au!u882453
- From: u882453@bruny.cc.utas.edu.au (Andrew King)
- Subject: Re: 4 byte fetch...
- Message-ID: <u882453.711698745@bruny>
- Sender: news@newsroom.utas.edu.au
- Organization: University of Tasmania, Australia.
- References: <1992Jul8.160456.22056@col.hp.com> <0ZqoNB1w164w@PDaXcess.techbook.com> <ERIC.92Jul10143833@iceland.telebit.com>
- Date: Tue, 21 Jul 1992 06:05:45 GMT
- Lines: 21
-
- eric@telebit.com (Eric Smith) writes:
-
- >If the intent is to obfuscate the code, wouldn't it be better to modify the
- >code as far away from the modified code as possible?
-
- >Instead of:
- > move.w d0,(a0)
- > jmp (a6)
-
- >You would use:
- > move.w d0,(a0)
- >... do lots of stuff here...
- > jmp (a6)
-
- Another trick is to use:
- move.l a6,(a7)
- .... do lots of code here
- rts
-
- Trace vector-decoders are often used to protect code too..
-
-