What's new in Stringer Java Obfuscator 1.6.7 Build 20140317
Mar 25, 2014
- Added support for Java 8 bytecode
- Added ability to use ProGuard’s map files, in order to use original class names to be set in Stringer’s filters
- Added ability to force version of bytecode
- Multiple String protection functions per package
- Enhanced Resource encryption function
- Improved Hide API mechanism, while using Integrity Protection
New in Stringer Java Obfuscator 1.5.1 (Oct 3, 2013)
- Our Developer Team is proud to announce the release of Stringer Java Obfuscator 1.5.1.
- This version was developed in close cooperation with our clients.
- The Integrity Protection function adapted to protect client-side Java applications from on-fly malicious modification (by malware).
- Added support for applications which are designed to work in OSGI containers.
- The Resource encryption function was improved for using in gaming applications.
- And, of course, we have added support for ADT 22 in Stringer Eclipse Plugin for Android developers.
New in Stringer Java Obfuscator 1.3.0 (Oct 3, 2013)
- Changes:
- The Resource Encryption function now supports JavaFX applications
- Improved internal protection scheme against popular decompilers
- Compatibility of applications protected by Stringer with Microsoft Security Essentials
New in Stringer Java Obfuscator 1.2.0 (Oct 3, 2013)
- Added new function Resource File Encryption
- Optimized protection algorithm
- Added support for Android SDK Tools Rev. 21
- Added support for Eclipse Juno
New in Stringer Java Obfuscator 1.1.2 (Oct 3, 2013)
- Changes:
- Added new functions: Protection from modification, Size optimization
- Improved mechanism of encryption/decryption
- Added fully functional GUI
- Added application for MacOS X
- Compatibility with Zelix KlassMaster™
- Windows 8 support
- Added Export Wizard in Eclipse for Android applications
- Optimized performance for Java 7 compiled applications (If using Protection from modification)
New in Stringer Java Obfuscator 1.1 (Oct 3, 2013)
- As you can see we have renamed Stringer Java Obfuscation Toolkit into Stringer Java Obfuscator, and we would like to tell you why and also announce the new version of our obfuscator.
- Besides the set of optimizations and fixes, we have new feature in Stringer Java Obfuscator 1.1 - protection from modification and integrity control for your Java programs. It means that if malicious user will change something in your classes the program (modified, illegal) not work at all. And this is our main reason to rename. Now Stringer Java Obfuscator not only encrypts your Strings, but offers you a great features to protect your Java applications entirely.
- Classical methods of protection an applications from modification are: digital signature, or convertation of an application into a native code. We, in the new version of our obfuscator, offer you revolutionary approach, which allows automatic integrity control on your Java applications. The main feature here that we control the byte-code inside JVM, so it's virtually impossible to modify the byte-code.
- A size of a processed application by Stringer Java Obfuscator in comparison with digital signature method is much less. Besides of protection from modification, Stringer Java Obfuscator allows you to optimize the size and startup time of your applications.
New in Stringer Java Obfuscator 1.0.6 (Oct 3, 2013)
- Stringer Java Obfuscator 1.0.6 (Trinidad):
- Java 7 support
- Stringer now fixes incorrect stack map frames in a byte-code produced by ProGuard 4.7
- A new annotation @insecure: disables protection of specified String constants within a class
- Several bugs fixed, related to the initialization of static variables, if protected class and class with Stringer methods contains references to each other.
New in Stringer Java Obfuscator 1.0.5 (Oct 3, 2013)
- We added ability of protection strings in interfaces and enums
- Stringer Annotations library added in Eclipse plugin
- More detailed verbose output