Morn-n' --

You might want to consider a couple of things --

   1) "Obfuscation" in an interpreted language can't really be done.
You can make it harder for the User to read you code, but you can't do
anything that makes in hard (or impossible) for the User to *run* the
code.  Source code distribution and all that.

   2) If you obfuscate, the User is quite likely to wonder what you
are hiding -- what back-door or malware are you *really* trying to
hide?  Personally, if I am handed a package that is "protected", I lob
it back at the Bosses: "If they don't have anything to hide, then why
did they go to such lengths to hide something....?"  On a couple of
occasions this has lead the offending software getting dropped from
consideration.  We make it a contract deal-breaking clause that we
will receive the "clear" source as well as the Documentation set,
particularly for Software under wither the GPL or the Artistic
License.

   3) Consider where you as a Perl Developer would be if the Perl
run-time were 'obfuscated' (I know, oxymoron, but.); the beauty of
Open Source tools is that you *can* look under the covers and learn
*how* the Magic is done.

 Build a good tool, charge reasonably and fairly, and people will not
think twice about the cost (how many copies of WinZip have I installed
(at $14.99 a pop) in my lifetime?).  Besides, you make your money on
the Consulting/Customized features in the product.


B

On Fri, Aug 20, 2010 at 12:46 PM, Tobias Eichner
<tobiaseichne...@yahoo.de> wrote:
>> Why do you need any obfuscator?  If you want to protect your code from
>> web access, put it in a module in a directory that cannot be access from
>> the web and put a stub that calls the module at the site.
>
> It's not as easy as this, since people receive the source code files.
>
> I know that obfuscation is nothing that can prevent a pro from reading the
> scripts, but it's my aim to prevent the average user to read the code.
>
> Guess that Acme::Bleach module is also required at the target system ? Haven't
> closely looked at it, but will do so shortly. Thanks for the hint.
>
>
>
> --
> To unsubscribe, e-mail: beginners-unsubscr...@perl.org
> For additional commands, e-mail: beginners-h...@perl.org
> http://learn.perl.org/
>
>
>



-- 

Bob Goolsby
bob.gool...@gmail.com

--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/


Reply via email to