42
Originally posted by Jeroen Wenting:
You want your code to be invisible to the owners of the machine on which it is deployed???
Short answer: don't deploy your code to their machine.
If you're so paranoid you don't even trust your customers to the point that you want to hide your classnames from them, I suggest you find some other customers or better yet a different line of business (say, selling blunt knifes or rifles with the firing chamber welded shut).
Or if you want to remain in the software business, start up an ASP (application service provider) and host the software yourself, renting out serverspace and bandwidth rather than having the customers running their own servers.
42
Originally posted by Jeroen Wenting:
I'm quite practical...
ANY file you send to a customer can potentially be used to figure out your deepest secrets.
If those secrets are so important that you want noone to know them, the only thing you can do is not send any files to anyone.
That means remote hosting of services in an environment controlled directly by you where only the data generated by your application ever reaches the customer in the form of text, html, or whatever format they can use.
If your level of paranoia extends to not wanting to take advise you don't like, that's your problem not mine.
42
Vadivel Pm wrote:What you said that only correct. I did major research on it. All the classes which are directly used by jsp. So jsp is executed by the server during the runtime. During the obfuscation we cannot change the class name,package name and field names which are resides in jsp.
As per my knowledge we can make .jar file as obfuscator but those the jar files will not work in the jsp. I am sure in this.
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |