It looks as though Limbic~Region has already done much of the legwork I was about to do, and has assembled his results in this thread, which I now list here in hopes that some of the ideas therein might prove helpful.
Alternatively, Super Searching for all the reasons why Hiding your Script is nearly impossible with interpreted languages such as Perl, might also give you some ideas on how to undo what has been done by Perl2Exe.
The good news is, once you've written a program, even though much time has elapsed since then and now, the re-write is usually substantially improved.
Good luck.
| [reply] |
Surely the perl script is in your CVS repository, and you can just check out another copy
... and if not, it must be on a backup tape somewhere
@_=qw; ask f00li5h to appear and remain for a moment of pretend better than a lifetime;;s;;@_[map hex,split'',B204316D8C2A4516DE];;y/05/os/&print;
| [reply]
[d/l] |
if you can recall how you constructed your script once you maybe better re-write it. on the other hand, if you find a tool which disassembles your exe to assembler code the B::Deparse module should be helpful. you won't get commented code, however, but it will be readable at least. | [reply] |
Unfortunately what you want to do is entirely dependent on the version of perl2exe, by both version number and platform. Once upon a time, perl2exe basically packaged your script and a perl interpreter and dumped it all to a temporary directory. Then, you could just find that temporary directory and you'd have your script. It's not quite that simple anymore.
Recode it. You'll be better off, and you'll find a newer/better/faster way to do what your old script did. | [reply] |