4 Replies - 3146 Views - Last Post: 07 January 2005 - 03:21 AM Rate Topic: -----

#1 born2c0de  Icon User is offline

  • printf("I'm a %XR",195936478);
  • member icon

Reputation: 180
  • View blog
  • Posts: 4,667
  • Joined: 26-November 04

Protecting Java Source Code

Post icon  Posted 05 January 2005 - 09:31 AM

Java Decompilers are available on the web. The decompiling accuracy of these Applications is very accurate. It even decompiles J2ME code as well as J2EE code.

Is there any way to prevent Java code from being decompiled?
I've heard of Packers that are usually used to reduce executable size and to protect source code from being disassembled. But Packers only exist for EXE Files right? Or do they work for .class files as well?
Is This A Good Question/Topic? 0
  • +

Replies To: Protecting Java Source Code

#2 Amadeus  Icon User is offline

  • g+ + -o drink whiskey.cpp
  • member icon

Reputation: 248
  • View blog
  • Posts: 13,507
  • Joined: 12-July 02

Re: Protecting Java Source Code

Posted 05 January 2005 - 10:00 AM

Check out this forum. It suggests some Java Obfuscators.
Was This Post Helpful? 0
  • +
  • -

#3 Amadeus  Icon User is offline

  • g+ + -o drink whiskey.cpp
  • member icon

Reputation: 248
  • View blog
  • Posts: 13,507
  • Joined: 12-July 02

Re: Protecting Java Source Code

Posted 05 January 2005 - 10:05 AM

This one is also good.
Was This Post Helpful? 0
  • +
  • -

#4 stdunbar  Icon User is offline

  • New D.I.C Head

Reputation: 1
  • View blog
  • Posts: 9
  • Joined: 17-December 04

Re: Protecting Java Source Code

Posted 05 January 2005 - 01:06 PM

Realize that while there are obfuscators you can still jad the code and get a pretty good idea what is going on. Additionally, you can end up hurting yourself as your stacktraces can be hard to read. For example, for a Siebel integration I'm doing the wingnuts at Siebel must have used an obfuscator:

at com.siebel.om.conmgr.e.a(Unknown Source)
at com.siebel.om.conmgr.e.a(Unknown Source)
at com.siebel.om.conmgr.d.d(Unknown Source)
at com.siebel.om.om.b.a(Unknown Source)
at com.siebel.data.SiebelDataBean.login(SiebelDataBean.java)



So what is the problem? In this case, what the heck was the point of obfuscating the code as you've got to have Siebel for it to work anyway.

That may not be your case but be warned that you may have issues like this. If a customer sends you a stacktrace even you might not know where the problem happened!

This post has been edited by stdunbar: 05 January 2005 - 01:07 PM

Was This Post Helpful? 0
  • +
  • -

#5 born2c0de  Icon User is offline

  • printf("I'm a %XR",195936478);
  • member icon

Reputation: 180
  • View blog
  • Posts: 4,667
  • Joined: 26-November 04

Re: Protecting Java Source Code

Posted 07 January 2005 - 03:21 AM

hmm...i never thought of that....interesting...
Was This Post Helpful? 0
  • +
  • -

Page 1 of 1