We made a submission script, how can we sell and protect it?

[justsexxx]

Hi,

A friend made a submission script for us. It's almost ready. It's really good. So good that he wants to sell it to more webmaster :)

But how can we protect it? I mean, when you sell a zip copy to someone, he can put it on a website and everyone is gonna use it free. How can we best protect the script against using it on more then 1 domain?

All suggestion are welcome,

Andre

[Jon]

depending on the language...

Php then you would have to create a call that has it call back to your server or create a code in it to actually make it only run on that domain...But without protecting the code they can simply remove the line and rewrite it a bit..I recomend using zend.com's php encryption shit...but its costly :(

CGI then you are screwed...the code can be rewritten easily...You would have to convert to C+ I think...Either that or you can add 5000000 call backs in the script

Jon

[CM]

I got the same prolem.

But i have seen some lame attemt to just rename all variables to some weird numbers and then put in a "secret" code in it to check that the cose is runing from the adress that the user is alowed to run it from.

But this way it is easy to just figure what all the variables to and and rename them to something simpler. And then find that part of the script that to the adress check.


But this is the best way i know. ;)
Please if anyone know a beter one plz post here... :(

[dj-ohki]

<delurk>
ah the wonders of keeping your code private.

zend encoder is pretty good from what ive read, though its $2400. *ouch*

perl/CGI you're screwed.

only decient bet is to distro compiled code, which you're only gonna be able to do with compiled code (C, C++, java, though id stray away from java, thats just me though).

and remember, if you do use a authencation host system, that can ALWAYS be cracked, so you gotta make it hard enough to discourage most people from trying to break it. (one time key hashes seems to work pretty well)

</delurk>