1. Shrouded code...
Just how secure is shrouded code? How difficult would it be for
someone to reverse-engineer small sections of shrouded code, to try
and determine an algorithm used?
--
MrTrick
-------------------------------------------------------------------------------------
magnae clunes mihi placent, nec possum de hac re mentiri.
2. Re: Shrouded code...
On Mon, 8 Nov 2004 11:53:51 +1100, Patrick Barnes <mrtrick at gmail.com> wrote:
> Just how secure is shrouded code? How difficult would it be for
> someone to reverse-engineer small sections of shrouded code, to try
> and determine an algorithm used?
Oh, and this has nothing to do with any contest idea... I highly doubt
Rob would be happy with people actively and publically attempting to
circumvent shrouding.
--
MrTrick
3. Re: Shrouded code...
On Mon, 8 Nov 2004 11:53:51 +1100, Patrick Barnes <mrtrick at gmail.com>
wrote:
>
>Just how secure is shrouded code? How difficult would it be for
>someone to reverse-engineer small sections of shrouded code, to try
>and determine an algorithm used?
I imagine it is pretty difficult.
I shrouded the simplest program I could think of, "?1" and got this:
00000000 FE6D3E54 5E240A6E FA6A58E8 6EFE22EF *.m>T^$.n.jX.n.".*
00000010 B254C384 AFBB *.T.... *
I shrouded it again, and got this:
00000000 FE286554 5E240A85 ECFDC6C0 4D78577A *.(eT^$......MxWz*
00000010 EAF70F73 BC67 *...s.g *
So as you can see almost every byte is scrambled differently each
time. Plus, as Rob is fond of saying, any code you (or someone else)
did manage to recover would have short, meaningless names.
Pete
