1994-09-17 - Re: if this is RC4

Header Data

From: rarachel@prism.poly.edu (Arsen Ray Arachelian)
To: perry@imsi.com
Message Hash: 1203e6ad079bccfa30032653d0f783985bb95694634c2a1f67ffca649575ecd4
Message ID: <9409171312.AA24429@prism.poly.edu>
Reply To: <9409161318.AA06070@snark.imsi.com>
UTC Datetime: 1994-09-17 13:25:13 UTC
Raw Date: Sat, 17 Sep 94 06:25:13 PDT

Raw message

From: rarachel@prism.poly.edu (Arsen Ray Arachelian)
Date: Sat, 17 Sep 94 06:25:13 PDT
To: perry@imsi.com
Subject: Re: if this is RC4
In-Reply-To: <9409161318.AA06070@snark.imsi.com>
Message-ID: <9409171312.AA24429@prism.poly.edu>
MIME-Version: 1.0
Content-Type: text


> One possibility is that the author may have simply decompiled the
> original code...

This might explain the char % 255's in the code.  Normally such a 
construct is dangerous if the machine/compiler you use uses 2 byte
"chars" and there's the slightest posibility of having your "char"
hold more than 255.  I would normally use char & 255, however it
may surprise some of us that some machines can do a MOD faster than
an AND and the compiler used might have exploited that feature.

However, reconstructing C code out of binaries is a pain and I
doubt that you'd see a header file as well as a main .c file...
Anyone have experience with decompilers?




Thread