[Javascript] Encrypting JavaScript

Tim Makins spindrift at oceanfree.net
Thu May 15 12:52:37 CDT 2003


Thanks for all the comments on encryption. In my case, I'm doing a lot of
quite complicated real-time geometrical calculations to do with maps, based
on current cursor position and displaying a number of results on the status
bar, so I don't want anyone else to use it on their maps. Of course any
knowledgeable programmer can duplicate the code, as has been mentioned, but
there's so much going on it would take them a while, and I don't
particularly want to make it any easier.

By the way, I see that the following:

 self.status = "blah_de_blah_de_blah";

doesn't work with Mozilla. What does ?

Tim in Ireland.


----- Original Message -----
From: "Cutter (JavaScript List)" <javascript at theblades-family.com>
To: "[JavaScript List]" <javascript at LaTech.edu>
Sent: 15 May 2003 16:40
Subject: Re: [Javascript] Encrypting JavaScript


> If one uses ColdFusion for a server-side scripting language then you can
> encrypt the entire .cfm document (which I also use for external .js docs
> by naming them .cfm and calling them from the script tag.) The truly
> wanting will still find a way to decrypt, but it's worth a try.
>
> Steve Blades
> Seacrets
>
> Andrew Gibson wrote:
>
> >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.
> >>
> >>
> >>
> >
> >
> >
> >_______________________________________________
> >Javascript mailing list
> >Javascript at LaTech.edu
> >https://lists.LaTech.edu/mailman/listinfo/javascript
> >
> >
>
>
> _______________________________________________
> Javascript mailing list
> Javascript at LaTech.edu
> https://lists.LaTech.edu/mailman/listinfo/javascript
>



More information about the Javascript mailing list