[no subject]

[...]

    Geoffrey> I recall a perl compiler a while back.  Wouldn't
    Geoffrey> converting it to a binary be an even better obfuscation
    Geoffrey> solution?

The Perl compiler's really more of a proof of concept thing (see
perldoc -q 'compile my Perl').  Not to mention most of the
perl-to-binary packages really just package up the source with a
speciallized perl interpreter in one single file.

Granted this will change with Perl 6 and Parrot when *cough* it comes
out and you'll be able to just ship Parrot bytecode.

-- 
Fletch                | "If you find my answers frightening,       __`'/|
fletch at phydeaux.org|  Vincent, you should cease askin'          \ o.O'
                      |  scary questions." -- Jules                =(___)=
                      |                                               U


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00481" href="msg00481.html">[ale] Perl Obfuscation</a></strong>
<ul><li><em>From:</em> cfowler at outpostsentinel.com (Christopher Fowler)</li></ul></li>
<li><strong><a name="00489" href="msg00489.html">[ale] Perl Obfuscation</a></strong>
<ul><li><em>From:</em> esoteric at 3times25.net (Geoffrey)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00502.html">[ale] SSH Woes</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00504.html">[ale] SSH Woes</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00489.html">[ale] Perl Obfuscation</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00492.html">[ale] Perl Obfuscation</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00503"><strong>Date</strong></a></li>
<li><a href="threads.html#00503"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>