in reply to using source filter with mod_perl scripts

Simple and easy : dont' do it, forget about it, it doesn't work and it doesn't offer any protection.
Even if your application is unreadable, it won't prevent anyone from copying it and use it, even if you rewrite it in C. Nobody cares about your code anyway, as long as they have the application and can use it (how many people do you know who bought their copy of Photoshop with good money?).
If you're looking for the definite solution against piracy, I have bad news for you : there isn't any. So don't try harder to find a good answer to a bad question.
PS: A super search about "hiding code" or "hiding source" will provide you with many similar discussions.
  • Comment on Re: using source filter with mod_perl scripts

Replies are listed 'Best First'.
Re^2: using source filter with mod_perl scripts
by avo (Pilgrim) on Jun 06, 2006 at 15:23 UTC
    It actualy doesn't finish there. The installer is taking a fingerprint of the current system hardware and generating an installation key which must be accompanied with a unlock / activation key provided by the support people. This key works for this hardware / installation id only. The key is stored inside the encrypted source code - which is done by the same encrypted source code... It's working 100% without problem. I've done some tests... it is practicaly very difficult for someone to copy the code - "just like that". Glad that I heard your reply makes me feel good.
      Well, kudos for the challenge, but all this encryption stuff was probably quite a lot of work, and I don't think it will bring your company any additional customer... So it's probably actually a net loss from a business point-of-view :)
        Well, at the end of the day we will deal with other companies, and not personals... which will probably be the difference... We'll see. At present I have 30 restaurants using the system... and because of the value behind I am sure somebody will try to copy it.
        Well... time will show... :)