🚀 go-pugleaf

"Michael Kutscher" <Michael-Kutscher@pc-coach.de> schrieb im Newsbeitrag
news:97qk90$lhm$01$1@news.t-online.com...
> Hi!
>
> In JB 3.0 is under project-settings-compiler settings the option "seal
code"
> (translation from german, might have another name in the english version).
>
> ...But... I don't know, if it's any good or if there are "unsealing" tools
> since aeons...

I think this should mean "obfuscating" (?). Note that the JB included
obfuscation task is really weak!

There are some two or three really good commercial obfuscators available as
third party products. Personally I choosed Zelix KlassMaster (see: http://
www.zelix.com) as my obfuscator of choice, since it offers the best
obfuscation quality I've seen so far and related to other such commercial
products it's really cheap (compare it's individual developer pricing for
example with the pricing of 4th pass sourceguard or other products).


> Another way needs lots of work: Scramble the code yourself: Just as in
good
> old basic-times: When your programm works _absolutely_stable_, make some
> spaghetti-code out of it. Put useless additional functions into it, break
> functions in two, put funktions together in one that have nothing to do
with
> each other. And of cause don't write "a++" ... instead "a=b+c/4" with c
set
> to 4 anywhere else and a set to a another place.
>
> It's just write, when You self have a real horror of ever correcting an
> error in it... :-)

IMO, nobody would do it in Java this way anymore, since an obfuscator can do
this boring task much better for you. - With an obfuscator you don't touch
your sources at all for any obfuscation, instead you compile your projects
the normal way, build an jar and then let the obfuscator read in your ready
compiled classes or jar file. The obfuscator then processes/works on your
projects bytecode instead of the sources and builds new obfuscated classes
(or a directly jar which contain your obfuscated classes) for you!

> The one, who decompiles it, will get a bit more horror: he hasn't any
> speaking variable-names :-)
>
> But: Nothing of this will stop a real enthusiast who wants to clone your
> ideas... it will just dicouradge him and increase his working hours.

Well, if your projects contain a fair amount of (say some more...) classes
and you use a good 2nd generation obfuscating tool it's *realy* hard (I will
*not* say impossible) for someone to decipher your sources from the final
obfuscated bytecode stuff.

Valentino