aspose file tools
The moose likes Java in General and the fly likes securing Java code from unauthorized disassembling Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


JavaRanch » Java Forums » Java » Java in General
Reply Bookmark "securing Java code from unauthorized disassembling" Watch "securing Java code from unauthorized disassembling" New topic
Author

securing Java code from unauthorized disassembling

ali honarmand
Ranch Hand

Joined: Oct 12, 2009
Posts: 32

hi everyone,
I have recently faced a new fact that every Java class could be disassembled into pure Java code using some Free software!!! Now here is the question how is that possible to secure the code in a manner that could be safe enough. I mean someone (say, a child) could not disassemble the code with hit of a button?


A. Honarmand
Lester Burnham
Rancher

Joined: Oct 14, 2008
Posts: 1337
Define "safe enough". Ultimately, client-side Java code can not only be disassembled, but decompiled. You can make it harder, but a determined attacker will prevail.
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 16487
    
    2

Somebody would have to build the infrastructure which supported that button which the child could press. But what's your problem with that? You don't want children seeing your source code? Why not?
Lance Miller
Greenhorn

Joined: Jun 23, 2008
Posts: 21
Obfuscated_code
java obfuscator
This will not "secure" the code. But it makes it so someone will have to work a little bit harder to reverse engineer your code. Ironically though, doing this may provide greater enticement to those capable of doing such. More so than if you did not obfuscate. They like the challenge... but not as much as they like to brag about successfully meeting the challenge. And guess how they brag about it...

In the end, the best way to "secure" your code is with a good EULA and a good team of lawyers ;)
ali honarmand
Ranch Hand

Joined: Oct 12, 2009
Posts: 32

Lance Miller wrote:Obfuscated_code
java obfuscator
This will not "secure" the code. But it makes it so someone will have to work a little bit harder to reverse engineer your code. Ironically though, doing this may provide greater enticement to those capable of doing such. More so than if you did not obfuscate. They like the challenge... but not as much as they like to brag about successfully meeting the challenge. And guess how they brag about it...

In the end, the best way to "secure" your code is with a good EULA and a good team of lawyers ;)

thanks for help.
It works well, and also makes it a bit more difficult to reveal the code.
ali honarmand
Ranch Hand

Joined: Oct 12, 2009
Posts: 32

Paul Clapham wrote:Somebody would have to build the infrastructure which supported that button which the child could press. But what's your problem with that? You don't want children seeing your source code? Why not?

I just wanted to know about it. and also sometimes it is desirable for some customers. you know, they want to round you. I'm a a fan of Open Source Community
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: securing Java code from unauthorized disassembling
 
Similar Threads
how to copy files form server to local path?
data transfer urgentttttttt
Using the equals method
How to generate HTML to display XML
Mac-specific applet-Javascript communication problem