1997-10-28 - Re: Source code obfuscation

Header Data

From: Adam Back <aba@dcs.ex.ac.uk>
To: shamrock@cypherpunks.to
Message Hash: 667c301bc534b55c2ccb5a76e387d0e2f532fafad3ae999cb0bb0576aa82aebd
Message ID: <199710282253.WAA02826@server.test.net>
Reply To: <Pine.BSF.3.96.971028165130.13198F-100000@pakastelohi.cypherpunks.to>
UTC Datetime: 1997-10-28 23:09:05 UTC
Raw Date: Wed, 29 Oct 1997 07:09:05 +0800

Raw message

From: Adam Back <aba@dcs.ex.ac.uk>
Date: Wed, 29 Oct 1997 07:09:05 +0800
To: shamrock@cypherpunks.to
Subject: Re: Source code obfuscation
In-Reply-To: <Pine.BSF.3.96.971028165130.13198F-100000@pakastelohi.cypherpunks.to>
Message-ID: <199710282253.WAA02826@server.test.net>
MIME-Version: 1.0
Content-Type: text/plain




Lucky Green <shamrock@cypherpunks.to> writes:
> Is anyone familiar with tools that can be used to obscure source
> code so that it builds, but no longer contains comments or useful
> variable or procedure names?

Do a search on ANDF -- not sure of the acronym's meaning anymore, but
I think there is a GNU version, so perhaps there is a working system
that can be had.

I think it's for architecturally independent distribution -- "compile"
or mangle your source with the ANDF system, and then finish the
compile (compile the garbled C code) on the target system.

(Odd thing for GNU to get involved in what with their source
availability theme.)

Adam
-- 
Now officially an EAR violation...
Have *you* exported RSA today? --> http://www.dcs.ex.ac.uk/~aba/rsa/

print pack"C*",split/\D+/,`echo "16iII*o\U@{$/=$z;[(pop,pop,unpack"H*",<>
)]}\EsMsKsN0[lN*1lK[d2%Sa2/d0<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<J]dsJxp"|dc`






Thread