| Newsgroups |
perl.cvs.perlfaq |
| Message-ID |
<[email protected]> |
cvsuser 02/07/07 20:39:42
Modified: . perlfaq3.pod
Log:
* changed Mac OS to MacOS
* How can I hide the source for my Perl program?
+ mentioned B::Deparse and how easy it is to recover
'compiled' source
Revision Changes Path
1.24 +9 -3 perlfaq/perlfaq3.pod
Index: perlfaq3.pod
===================================================================
RCS file: /cvs/public/perlfaq/perlfaq3.pod,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -w -r1.23 -r1.24
--- perlfaq3.pod 21 Jun 2002 05:05:05 -0000 1.23
+++ perlfaq3.pod 8 Jul 2002 03:39:42 -0000 1.24
@@ -1,6 +1,6 @@
=head1 NAME
-perlfaq3 - Programming Tools ($Revision: 1.23 $, $Date: 2002/06/21 05:05:05 $)
+perlfaq3 - Programming Tools ($Revision: 1.24 $, $Date: 2002/07/08 03:39:42 $)
=head1 DESCRIPTION
@@ -704,6 +704,12 @@
crackers might be able to disassemble it. These pose varying degrees
of difficulty to people wanting to get at your code, but none can
definitively conceal it (true of every language, not just Perl).
+
+It is very easy to recover the source of Perl programs. You simply
+feed the program to the perl interpreter and use the modules in
+the B:: hierarchy. The B::Deparse module should be able to
+defeat most attempts to hide source. Again, this is not
+unique to Perl.
If you're concerned about people profiting from your code, then the
bottom line is that nothing but a restrictive license will give you