Retrologic News and Updates

• RetroCapture Lite and Pro released (v1.0.2) (Fri, 9 Mar 2007)
  RetroCapture is a CAPTCHA generator, written in 100% Java. RetroCapture Pro can be integrated with your web-application in several ways: batch image generation; server-mode generation; or direct Java library integration. RetroCapture has no dependence on the Java AWT, making it suitable for use in 'headless' server-side environments.
• RetroGuard Update (v2.3.0 commercial and GPL) (Wed, 28 Feb 2007)
  Support added for Java SE 6, including the new code attribute StackMapTable. Unsupported versions of the class file format now gives a warning instead of stopping the obfuscation process. Trim bug-fix: methods could be incorrectly trimmed if accessed only through base class references. Readme.txt now includes 'Quick Start' documentation.
• RetroCapture update (v0.9.2) (Mon, 26 Jun 2006)
  Fixed bug relating to resource loading on certain systems. Various image quality and speed improvements.
• RetroCapture Lite CAPTCHA Generator released (v0.9.1) (Wed, 17 May 2006)
  RetroCapture Lite is a CAPTCHA generator, written in 100% Java and with absolutely no dependence on the Java AWT. This makes it suitable for use in 'headless' server-side environments.
• RetroGuard Update (v2.2.0 commercial and GPL) (Fri, 31 Mar 2006)
  '.option Repackage' safe repackaging of classes into top-level packages, reducing obfuscated size. '.option Trim' available in both GPL and commercial versions. '.option Generic' added, currently equivalent to '.attribute Signature'. RGdefault utility added, outputs internal default script. '.nowarn <class>' added to script format, suppression of reflection warnings from log. '.option MapClassString' bug-fix for certain inner classes. Error-handling improved when duplicate classfiles are detected in the input jar. Documentation updates.
• RetroGuard Update (v2.1.2 commercial / v2.0.5 GPL) (Thu, 25 Aug 2005)
  Fixed an interaction between negation commands (!class / !method / !field) and certain multiple inheritance graphs that caused a non-fatal failure to rename some methods and fields, when renaming should be possible. Added display of version number to RetroGuard usage message.
• RetroGuard Update (v2.1.1 commercial / v2.0.4 GPL) (Tue, 19 Jul 2005)
  Additional checks to prevent RetroGuard terminating with a warning on certain JDK1.4.2 classfiles.
• RetroGuard Update (v2.1.0) - Unused method, field, and class trimming (Wed, 15 Jun 2005)
  '.option Trim' added enabling unused methods, fields, and even whole classes to be trimmed by RetroGuard. This can lead to significant reduction in jar size, particularly in cases where only a few classes are being used from a larger library.
• RetroGuard Update (v2.0.3) - Minor Update, RGtrace (Wed, 1 Jun 2005)
  'RGtrace' tool added, helping to interpret obfuscated stack traces. '.option LineNumberDebug' added, allowing line number information to be preserved for stack traces without exposing unobfuscated class names within the 'SourceFile' attribute.
• RetroGuard Documentation - Script Examples Updated (Fri, 27 May 2005)
  RetroGuard scripting language examples have been extended to cover new features such as: class, method, and field access flags; use of the 'extends' clause; the 'and_class' modifier; use of the wildcards '*' and '**'.
• RetroGuard Update (v2.0.2) - Minor Update (Wed, 30 Mar 2005)
  Explicit array bounds checking added to Code attribute parser. Behavior of script entries '!class', '!method' and '!field' changed. These statements no longer force obfuscation of package level identifiers, which in v2.0.1 could lead to unexpected behavior such as the obfuscation of package level identifiers while classes in those packages were preserved from obfuscation.
• RetroGuard Update (v2.0.1) - Major Upgrade, Dual-Licensing (Fri, 4 Feb 2005)
  RetroGuard is now available in a dual-licensed format: GPL for non-commercial users, and an annual commercial license for commercial users. Feature upgrades include: Apache Ant tasks; automatic Class.forName()/.class handling; improved script wildcarding; full support for JDK-1.5/JDK-5 Generics, Enumerations, and Annotations; improved handling of serialization and RMI; many other script language improvements.
• RetroGuard Update (v1.1.16) - JDK-1.5/JDK-5 (Fri, 10 Dec 2004)
  RetroGuard now compiles under JDK1.5/JDK5. Updated classfile version checking to accept MAJOR_VERSION = 0x31 (49) as used in JDK1.5/JDK5 with default compilation option -source 1.5
• Thanks for the RetroGuard donations (Mon, 29 Nov 2004)
  Thank you to everyone who has taken the time to donate to the RetroGuard project. Your contributions help make the RetroGuard for Java obfuscator a high priority and enable further development of RetroGuard.
• RetroGuard Update (v1.1.15) - Deprecated attribute (Tue, 23 Nov 2004)
  Added 'Deprecated' to the list of classfile attributes which can be preserved during obfuscation. Use script file syntax: .attribute Deprecated
• Jargon File (v4.4.7) - mirror (Thu, 11 Nov 2004)
  A local mirror of The Jargon File has been added to the Retrologic site. Features specific to this mirror include a no-frames alphabetic index at the top of each page, a 'Random Entry' link, and an RSS feed of random Jargon File entries.
• RetroGuard Update (v1.1.14) - manifest file bugfix (Thu, 26 Feb 2004)
  Fixed long-standing bug in handling of manifest file continuation lines. Thanks to Grant Gould for reporting this.
• RetroGuard Update (v1.1.13) - JDK1.4 bugfix (Sat, 2 Nov 2002)
  Addition to major bugfix in v1.1.12 regarding JDK1.4-compiled code: implemented interfaces as well as the superclass are now traversed to resolve obfuscated method and field names. Also, System.exit(0) in RetroGuard (removed in v1.1.10) has been added back. For Ant integration (pre-JDK1.4 only), spawn a separate VM for RetroGuard.
• RetroGuard Update (v1.1.12) - JDK1.4 bugfix (Tue, 29 Oct 2002)
  Major fix from v1.1.11 regarding JDK1.4-compiled code: Changes to the JDK1.4 compiler from prior versions broke RetroGuard's ability to obfuscate any non-trivial inheritance structure in the code. The symptom was methods and fields defined in superclasses not being found at runtime in obfuscated code. The RetroGuard renaming mechanism has been updated to cope with these JDK1.4 compiler changes. The bug only affected code compiled with JDK1.4 which was only supported recently in RetroGuard v1.1.11, exposing the bug.
• RetroGuard Update (v1.1.11) - version update for JDK1.4 (Tue, 8 Oct 2002)
  Updated classfile version checking to accept MAJOR_VERSION = 0x30 (48) as used in JDK1.4 with compilation option "-source 1.4"
• RetroGuard Update (v1.1.10) - version update for JDK1.4 (Mon, 7 Oct 2002)
  Updated classfile version checking to accept MAJOR_VERSION = 0x2E (46) as used in JDK1.4. Classfile integrity checking now provides more detailed error messages. Removed error check that invalidly triggered on valid (but unusual) identifiers like "XX$$71". System.exit(0) is no longer called on normal termination, to ease integration with tools like Ant.