Muzzii has asked for the wisdom of the Perl Monks concerning the following question:
|
---|
Replies are listed 'Best First'. | ||
---|---|---|
Re: Decompile PerlApp
by diotalevi (Canon) on Jan 31, 2003 at 08:16 UTC | ||
You probably ought to post some more information like the version of PerlApp that was used. Perhaps also the encoded script. Make a judgement call on whether it's too big to post or not and be sure to encode it somehow. A normal hex-encoding might be nice I suppose. Or just a first K maybe. | [reply] | |
Re: Decompile PerlApp
by PodMaster (Abbot) on Jan 31, 2003 at 08:31 UTC | ||
you may not modify, reverse engineer, decompile, decrypt, extract or otherwise disassemble the Software.update: I'm not a lawyer. It is food for thought. If you have a copy of the perlapp license, great, read it and post the relevant passage here, otherwise, i think it still applies.
| [reply] | |
by theorbtwo (Prior) on Jan 31, 2003 at 09:04 UTC | ||
Note that "Software" there is defined as "ActiveState Perl Dev Kit, the License Key (as hereinafter defined) and other applicable software". I do not think that includes the output of the program -- though, arguably, it may be "other applicable software", esp as those are later explicitly covered under "works". In any case, there's an old Roman saying "where there are no police, there are no laws" (presumably, it sounds better in Latin). You're probably fine, on a legal basis. Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node). | [reply] | |
by Muzzii (Initiate) on Jan 31, 2003 at 16:10 UTC | ||
The liscencing issue was covered in another post in regards to the previous link i posted and it was determined that the EULA or applicable federal laws did not apply to a person decompiling a perlapp program for the sole purpose of recovering a program legitamtly written by that person. I am not trying to pirate or steal anything here, i am merely wanting to recover my own intellectual property. The total encoded file would be to big to post here, but i would be happy to email any information to anyone who would help. Here is the first 100 lines of the encoded program:
Here is a 'control file that i made. The control file consists of:
I looked at this code before running it through PerlApp and it looks like this:
Then i ran this 'control' file through perlapp and extracted the encoded script out of it and it looks like this:
As you can see there is a 343:356 ratio to this file. It does not seem to be merely a XOR operation against the string "Copyright © 2000 ActiveState Tool Corp." witch is:
This is about as much as i have now, i can also post a encode and unencoded snippit of another 'control' file that contains just a repeating string '#A'. If anyone can help, it would deeply appreciated. Many Thanks Muzzii | [reply] [d/l] [select] | |
Re: Decompile PerlApp
by Anonymous Monk on Jan 31, 2003 at 13:51 UTC | ||
| [reply] | |
by Muzzii (Initiate) on Jan 31, 2003 at 16:27 UTC | ||
Ok gang, NM on the post, i figured it all out. It is a XOR againt the ActiveState Copyright string. For future reference to others who may have this problem, my version of perlapp is 2.0, and i have discovered that the current version (5.0) does not use the simple XOR against the key string algorithm. 5.0 seems to be using a random key that is encoded into the code itself and it also stuffs the script with alot of other information that may obscure the script itself. Many thanks to those who helped out and special thanks to all those who participated in A real challenge.<\p> | [reply] |