Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.help > #2845
| From | markspace <markspace@nospam.nospam> |
|---|---|
| Newsgroups | comp.lang.java.help |
| Subject | Re: Finally java class file encryption possible. |
| Date | 2013-10-30 12:06 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <l4rlbj$bco$1@dont-email.me> (permalink) |
| References | (3 earlier) <u1p5ka-tt6.ln1@s.simpson148.btinternet.com> <9611b714-c4c1-42e3-80dc-edd2f1939b36@googlegroups.com> <bmf7ka-is7.ln1@s.simpson148.btinternet.com> <db658622-4627-4f2e-9c17-2d76cb6400ca@googlegroups.com> <16pm8rba3p5hh$.wng8plh755vm$.dlg@40tude.net> |
On 10/30/2013 11:17 AM, Joerg Meier wrote: > On Wed, 30 Oct 2013 10:40:28 -0700 (PDT), Java Encryptor wrote: > >> So basically there is no way we can prevent our class from de-compiling. > > No, of course not - in the end, the computer still has to be able to decode > them to run them, and anything the computer does, a potential thief can do. > It's best to just obfuscate your code and then be done with it and accept > that some people will be looking at your code. Obfuscation can make stack traces and log output hard to read (they'll print the obfuscated class and method names). Better I think to: 1. Provide enough value that it's more work to steal code than it is to subscribe to your service/product. 2. Keep some of the code on a server where folks can't get at it, and make API calls over the network to return results. 3. Use the courts for egregious cases of theft.
Back to comp.lang.java.help | Previous | Next — Previous in thread | Next in thread | Find similar
Finally java class file encryption possible. Java Encryptor <java.encryptor@gmail.com> - 2013-10-25 02:16 -0700
Re: Finally java class file encryption possible. Roedy Green <see_website@mindprod.com.invalid> - 2013-10-25 04:08 -0700
Re: Finally java class file encryption possible. Jukka Lahtinen <jtfjdehf@hotmail.com.invalid> - 2013-10-25 16:21 +0300
Re: Finally java class file encryption possible. Java Encryptor <java.encryptor@gmail.com> - 2013-10-27 06:40 -0700
Re: Finally java class file encryption possible. Java Encryptor <java.encryptor@gmail.com> - 2013-10-27 06:37 -0700
Re: Finally java class file encryption possible. Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2013-10-27 10:25 -0700
Re: Finally java class file encryption possible. Java Encryptor <java.encryptor@gmail.com> - 2013-10-28 05:52 -0700
Re: Finally java class file encryption possible. Steven Simpson <ss@domain.invalid> - 2013-10-28 15:57 +0000
Re: Finally java class file encryption possible. Java Encryptor <java.encryptor@gmail.com> - 2013-10-29 11:30 -0700
Re: Finally java class file encryption possible. Steven Simpson <ss@domain.invalid> - 2013-10-29 22:22 +0000
Re: Finally java class file encryption possible. Java Encryptor <java.encryptor@gmail.com> - 2013-10-30 05:38 -0700
Re: Finally java class file encryption possible. Steven Simpson <ss@domain.invalid> - 2013-10-30 13:54 +0000
Re: Finally java class file encryption possible. Java Encryptor <java.encryptor@gmail.com> - 2013-10-30 10:40 -0700
Re: Finally java class file encryption possible. Joerg Meier <joergmmeier@arcor.de> - 2013-10-30 19:17 +0100
Re: Finally java class file encryption possible. markspace <markspace@nospam.nospam> - 2013-10-30 12:06 -0700
Re: Finally java class file encryption possible. Joerg Meier <joergmmeier@arcor.de> - 2013-10-30 21:27 +0100
Re: Finally java class file encryption possible. eduardo.coca.sola@gmail.com - 2014-02-12 03:21 -0800
csiph-web