Re: Protecting source code

On 25 Aug 2006, at 19:56, Tim Pushor wrote: [snip] I think it may also be useful to be able to prove in a court that you took steps to keep your secrets away from prying eyes, and that whoever belonged to those prying eyes deliberately took steps to uncover your secret - Regardless of the ac

Re: Protecting source code

What about products like CPANEL, how do they do it? There must be some standard usage already with Perl being as prevalent as it is. Currently we've separated our perl code out onto its own server and use proxies to get to and fro. It keeps a level of protection on our code. We just serve the o

Re: Protecting source code

On Aug 25, 2006, at 2:34 PM, David E. Wheeler wrote: I think that if obfuscating the source code (by compiling or encrypting or whatever) is a high priority for you, then Perl may not be the best choice of language for your software. And even for Java there are decompilers and for PHP the c

Re: Protecting source code

I think that if obfuscating the source code (by compiling or encrypting or whatever) is a high priority for you, then Perl may not be the best choice of language for your software. And even for Java there are decompilers and for PHP the code must be unencrypted to run. So maybe C is the best choic

Re: Protecting source code

Danny Brian wrote: It will always be true that a dedicated hacker will be able to decompile, dump opcodes, or otherwise reverse engineer the work of another, regardless of the language or file format. But the value of compiling a program is not so much its security, but its illusion of securit

Re: Protecting source code

I think that if mod_perl programs could be very well encrypted, this technology would be a little more used than it is now, but they can't, and if this is a disadvantage for some of us, we shouldn't say that the programmers shouldn't need such a thing. Teddy makes a good point. This discussio

Re: Protecting source code

On Aug 25, 2006, at 11:05, Octavian Rasnita wrote: Hi americans :-) Heh. Nailed me. ;-) So the programmer works for the source code, makes it open source, and then comes another programmer that gets it, delete the name of the author, make some changes, and then sell the program pretendin

Re: Protecting source code

Hi americans :-) Please try to understand that the situation is not everywhere like in USA regarding the respect for copyright, including the respect for open source licenses. I have seen the suggestion for protecting the code by a license for many times, but there are countries where those licen

Re: Protecting source code

AFAIK, I doubt it. I'm not a mod_perl power user but what you're asking seems to me like asking if perl can run binaries that are compiled out of C code generated with perlcc. There's always XS if you want to include C code.. or ofcourse, you can always just write a pure C Apache module instead of

Re: Protecting source code

On Aug 25, 2006, at 09:58, Jonathan Vanasco wrote: at that point, i realized two things: a- encrypting/obfuscating perl code just doesn't work when you need to decrypt it. it also doesn't work when there are decompilers and stuff out there. the best you can do is make something margina

Re: Protecting source code

On Aug 25, 2006, at 11:13 AM, Hendrik Van Belleghem wrote: 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 deve

Re: Protecting source code

Hi, 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-sou

Re: Protecting source code

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 no

Re: Protecting source code

On 25 Aug 2006, at 12:41, Ali ISIK wrote: How about stunnix, folks, does anyone have any experience with their product? Ahhh... Stunnix. You may find , and www.theregister.co.uk/2003/07/03/o

Re: Protecting source code

How about stunnix, folks, does anyone have any experience with their product? --Ali Isik On 8/23/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote: On Aug 23, 2006, at 8:01 AM, Miha Lampret wrote: > Hello all, > > I am writting web application for mod_perl which will be installed > on client's s

RE: Protecting source code

> Best way- fill it with copyright notices, use a restrictive license, > get them to sign a document. > > That's really the only way to protect perl code-- by legally > protecting it. > And then suing the ass off of your client if they break it. > > You can not 'protect' perl source the way you a

Re: Protecting source code

> 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

Re: Protecting source code

As the author of Filter::CBC, another source code encryption module, I can officially state that module encryption is not supported by my module either. You might want to look at Filter::Crypto but I have no experience with it. HTH On 8/23/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote: On Aug

Re: Protecting source code

On Aug 23, 2006, at 8:01 AM, 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