full-disclosure - Re: Java class obfuscation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3EF27908.9000302@ameritech.net>
From: dbailey27 at ameritech.net (northern snowfall)
Subject: Re: Java class obfuscation

>
>
>The aim of obfuscation is to make it hard(er) for decompilers
>to work, not make it unreadable.
>
>The trouble in attempting to get from the output of "gcc -O2" back
>to C code (in comparison to "gcc -g") is the aim.
>
Yeh, I understand that quite well. The point was that all a
decompiler has to do is play pseudo-JVM and you've got byte
code that can be translated to java.

Translating asm back into C isn't that hard. People forget
that you don't have to make the C look exactly like it did
before the compile, all you have to do is make it do what
the assembly tells you it's supposed to do.

Code isn't hard. People make it hard.

Don

http://www.7f.no-ip.com/~north_

>