| 2:42 pm on Nov 19, 2005 (gmt 0)|
Alternatively you can render your code very difficult to edit by changing variable names and removing all line breaks.
NB you can't actually stop the script from being saved onto the user's hard disk though or it wouldn't run.
| 9:29 am on Nov 20, 2005 (gmt 0)|
If it is clientside I can get a hold of it PERIOD.
Now I have seen some sort of encryption method used. I understood that though I did not understand how to read or convert it. Yet the browser still executed the script.
| 1:40 am on Nov 23, 2005 (gmt 0)|
1) write in a condition that looks at the URL
var domainname = location.href;
2) obfuscate the heck out of the code until it's so unreadable that no one would ever bother stealing it.
People are tired of arguments why it's impossible to "protect" client-side code. And I'm tired of explaining it. Still, sometimes you get birdbrained suits who a) don't understand and b) won't liten, and to appease them try the methods above.
Use the word "algorithm" a lot. they like that.
| 1:46 am on Nov 23, 2005 (gmt 0)|
the best JS "encryption" usually involves turning the entire script into one long string, and mangling it with some kind of simple cipher.
The executable script uses a build-in decoder, then runs the result through exec()
| 4:10 am on Nov 23, 2005 (gmt 0)|