Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #17817 > unrolled thread

FAQ Topic - How do I protect my javascript code? (2012-12-24)

Started by"FAQ server" <javascript@dotinternet.be>
First post2012-12-24 00:00 +0000
Last post2012-12-31 15:55 -0700
Articles 2 — 2 participants

Back to article view | Back to comp.lang.javascript


Contents

  FAQ Topic - How do I protect my javascript code? (2012-12-24) "FAQ server" <javascript@dotinternet.be> - 2012-12-24 00:00 +0000
    Re: FAQ Topic - How do I protect my javascript code? (2012-12-24) Mike - 2012-12-31 15:55 -0700

#17817 — FAQ Topic - How do I protect my javascript code? (2012-12-24)

From"FAQ server" <javascript@dotinternet.be>
Date2012-12-24 00:00 +0000
SubjectFAQ Topic - How do I protect my javascript code? (2012-12-24)
Message-ID<50d79b0a$0$289$14726298@news.sunsite.dk>
-----------------------------------------------------------------------
FAQ Topic - How do I protect my javascript code?
-----------------------------------------------------------------------

With clientside javascript you can't as your code is distributed
in source form and is easily readable. With JScript, there is the
Script Encoder (see MSDN), but this is nothing more than obfuscation.
Attempting to disable the context menu does nothing to
protect your script in a Web browser.

Your code is likely protected under copyright laws. See:
<URL: http://www.wipo.int/about-ip/en/copyright.html>
<URL: http://webdesign.about.com/od/copyright/Copyright_Issues_on_the_Web_Intellectual_Property.htm>


The complete comp.lang.javascript FAQ is at
http://jibbering.com/faq/

-- 

The sendings of these daily posts are proficiently hosted
by http://www.pair.com.

[toc] | [next] | [standalone]


#17898

FromMike
Date2012-12-31 15:55 -0700
Message-ID<2012123115551781453-@news.giganews.com>
In reply to#17817
Even with obfuscation, there are ways around this and you may even pay 
a performance penalty. Many modern JavaScript runtimes use a 
precompilation step to optimize code and I doubt they were designed for 
and sufficiently tested in this type of scenario. My suggestion is to 
move anything that you do not want available  in the client-side source 
to server-side processing. If your concern is infringement of your 
copyrights, use something other than HTML/JavaScript for your 
presentation layer.

On 2012-12-24 00:00:03 +0000, FAQ server said:

> -----------------------------------------------------------------------
> FAQ Topic - How do I protect my javascript code?
> -----------------------------------------------------------------------
> 
> With clientside javascript you can't as your code is distributed
> in source form and is easily readable. With JScript, there is the
> Script Encoder (see MSDN), but this is nothing more than obfuscation.
> Attempting to disable the context menu does nothing to
> protect your script in a Web browser.
> 
> Your code is likely protected under copyright laws. See:
> <URL: http://www.wipo.int/about-ip/en/copyright.html>
> <URL: 
> http://webdesign.about.com/od/copyright/Copyright_Issues_on_the_Web_Intellectual_Property.htm> 
> 
> 
> 
> The complete comp.lang.javascript FAQ is at
> http://jibbering.com/faq/

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.javascript


csiph-web