Protect Your Java™ Applications

6. JarCryp™ versus obfuscators

Below the JarCryp™ bytecode encryption is compared with common obfuscating.

Feature	Obfuscator	JarCryp™
Code protection	Only packages, classes and method names are replaced. The bytecode and in particular constants are still observable and changeable. Sometimes, at least parts of the source code can be restored by decompilation.	The whole source code is encrypted
Protection of ressources	No protection for images, text-files, configuration data, and so on	All resource files are fully encrypted
Logging, Debugging, Error Handlig	Meaningful logging or debugging is problematic. Error reports are possibly meaningless, since stack traces cannot be evaluated in the common way.	No restrictions in comparison to unencrypted applications.
Compatibility	Problems due to the substantial code changes, sometimes walking the tightrope on bytecode conformity, are likely. Possibly not all Java VM versions are supported.	The byte code is executed unchanged. Thus compatibility with all Java versions is ensured.
File Size	JAR files are typically of significant smaller size	File sizes are reduced by an average of 10% only
Platform Independency	Mostly 100% pure Java	Native library necessary. However thanks to ANSI C++ programming this library is available for major operating systems. The use of JNI (Java Native Interface) enables us to port the library for the use in different environments.

Get to know the JInstaller™ Secure Edition which incorporates the JarCryp™ Technology.