Just because you're using Apache (Apache License), mod_perl (Apache
License) and Perl (GPL/Artistic), it doesn't mean anything you develop
has to use any of those licenses. It is perfectly legal to license
your perl applications under any license you choose. It's also
perfectly ok to open-source an application written in a proprietary
language. Last I checked, programming language of choice has nothing
to do with the EULA (unless ofcourse the code was generated by a tool
that has a EULA which states that generated code cannot be
redistributed etc.. but that's just far-fetched). Protecting your
source the hard way by encrypting/obfuscating/compiling is still not
foolproof. There is no 100% safe way to do this. I'd stick to the EULA
and cross your fingers.

Then again, I'm not an attorney.

The reason for me not to use any of these encryption or obfuscation
tools (even though I wrote one), is purely for logical reasons. Source
readability is part of the perl featureset for me. If you don't want
people to read it, don't develop in a language that has it as one of
it's primary advantages.

my 2 cents


On 8/25/06, Saltbreez wrote:
> This conversation disturbs me at a level more fundamental than source
> code or business requirements.
> You write that you [are] "writting web application for mod_perl which
> will be installed on client's server". That is to say that you are
> using a product licensed as either GNU or Artistic. I am not an
> attorney, but my understanding of the intent of these licenses is to
> prevent people from doing just what you describe.
> If you want to protect your work, develop in a proprietary language.
> If you want to use the fruits of decades of open source enthusiasts
> work, then open your source.
> Christian Werner Sr.
> On 8/23/06, Miha Lampret wrote:
> > Hello all,
> >
> > I am writting web application for mod_perl which will be installed on
> > client's server. Application is almost finished and now I am wondering
> > which is the best way to protect source code.
> >
> > Already checked Module::Crypt but cound't get it to work. It doesn't
> > create any output file. I came a cross with schroud+ perl obfuscator
> > which looks ok, but I would like protect strings too. By strings I meen
> > text that is hardcoded in source and it is printed to web application
> > user. Do you have any experiences with other obfuscators or converters
> > to XS code?
> >
> > Any information is welcome.
> >
> > Thank you,
> > Miha
> >

> --
> Do you know how high... The Salt Breez
> the Robin flies, Also Know As ...
> Or why the Mint leaf... Christian Werner Sr
> smells so sweet? saltbreez@gmail.com
> The Salt Breez

Hendrik Van Belleghem
Spine - The backbone for your website - http://spine.sf.net