Re: Writing spaghetti code for obfuscation/encryption
- From: "f0dder" <spamtrap@xxxxxxxxxx>
- Date: Wed, 31 Aug 2005 00:19:15 +0000 (UTC)
spamtrap@xxxxxxxxxx wrote:
> Hi all,
>
> I'm considering writing some convoluted and confusing code in order to
> hide the access/decryption of some important data in an app. I don't
> really want to be dependent on any particular OS at the moment.
>
> The problem is how to generate this code without becoming confused
> myself, and how to make sure it is orthogonal, or always produces the
> same result with the same input.
>
> I would like for it to be similar to the copy protection schemes of
> old, that make tracing difficult and unpredictable.
>
> Can anyone offer any suggestions on how this might be done, besides
> undocumented opcodes and simple encryption?
Don't do this at a source level (ie, don't *write* obfuscated source).
Either run your source code to an obfuscating pre-processor before you
compile/assemble, or run your binaries through an obfuscator...
.
- References:
- Writing spaghetti code for obfuscation/encryption
- From: spamtrap
- Writing spaghetti code for obfuscation/encryption
- Prev by Date: Re: Writing spaghetti code for obfuscation/encryption
- Next by Date: Re: Simple program cwitching thru all video-modes craps-out ...
- Previous by thread: Re: Writing spaghetti code for obfuscation/encryption
- Next by thread: Re: Writing spaghetti code for obfuscation/encryption
- Index(es):
Relevant Pages
|
|