With PerlApp it's much harder to recover source code than it is with other EXE creators (like pp) but it's not totally impossible. The theoretical method (which I've never tried, just had explained to me) is to load the perl-app created tool into an EXE debugger, run the program partway, dump out the memory contents and find where perl put the compiled opcode tree for the script, and then write a perl script that recreates that opcode tree and uses B::Deparse to rip it apart into perl code.
Unless you're implementing state secrets as CGI scripts, it's almost certainly easier for someone trying to obtain your source code to write whatever your script does themselves from scratch than it is for them to extract it out of a PerlApp executeable.
--
@/=map{[/./g]}qw/.h_nJ Xapou cets krht ele_ r_ra/;
map{y/X_/\n /;print}map{pop@$_}@/for@/
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|