[Javascript] Encrypting JavaScript

[andyg at ihug.co.nz (Andrew Gibson)]

I'm sure there are good reasons for trying to encrypt or hide client side
code....or else, we are saying Jscript can never be used for a commercial
application  !?

But lets face it, any snippet of your client side code, can be easily
duplicated by any experienced code writer.....without even seeing the
source.....

Its the application in total that you would want to protect I would think,
and because this would normally be a combination of client and server side
script, a developer might be hard pressed to copy the entire application for
their own use.......I dont know if reverse engineering is the term, but by
the time they got it working for themselves, and were able to maintain it,
they would have been better off doing it from scratch!

Andrew Gibson


> Considering that:
> x = 1
>
> Becomes:
> var V1AQAPKRV="z'02'1F'023"; V1Avjgnglevj=""; V1Aqapkrv="";var V02amfg3;
> V02amfg3=V1AQAPKRV.length;for (i=0;i<V02amfg3;i++){
> V1Avjgnglevj+=String.fromCharCode(V1AQAPKRV.charCodeAt(i)^2) }
> V1Aqapkrv=unescape(V1Avjgnglevj);document.write(V1Aqapkrv);
>
>   It seems to me to just be an ugly mess.  I wouldn't call that
> "encrypted" because someone could interpret it the same way the
> javascript processor would - ie: it's not "secure"
>
>   It does make it more difficult for the causally curious to see what
> you're doing.  That's probably why it's called the javascript obfuscator
> rather than the javascript encryptor.
>