July 13th, 2011· Integration with Powerflasher FDT
· FDTWouldn’t it be great to run secureSWF inside the most advanced Flash development platform? You will find a 5th download option when you download secureSWF v3.5; an FDT plugin! Copy the file into FDT plugins folder and a new secureSWF button will appear in FDT toolbar. That’s all what it takes to start running secureSWF within FDT.
· Kindisoft and Powerflasher are also announcing today a new partnership to empower you to make the best out of the Flash platform. secureSWF v3.5 is just a beginning of a much closer integration along the way. We’ll be working closely with the FDT team to bring you the ability to declare obfuscation settings within your code, debug obfuscated files, export a complete auto build script with a click of a button, and much more.
· Remove Debugging Information
· Keeping debugging information in released Flash applications can be useful for error reporting because source code line numbers and files names where an exception has been thrown can be found in the call stack. Unfortunately, this information is also available to attackers trying to reverse-engineer your code and it also costs a lot of file size.
· New options in secureSWF v3.5 will enable you to remove all debug information that you will no longer need outside a debugger, but will keep the source code line numbers. Error messages will show the obfuscated call stack trace (which you can de-obfuscate using the mapping table) with the line numbers.
· Local Variables Renaming for ActionScript 3
· Variables declared within the function scope in ActionScript 3 are usually compiled as registers without their specified names. But when they are not, for a number of reasons, the identifiers names are passed along the compiled code giving decompilers the ability to regenerate a very closer version on the original source code. With secureSWF v3.5, you can enable the ability to rename local variables in the few cases were they are still in the compiled code.
· Control Over Randomization
· Randomization is one of the most important protection mechanism for secureSWF. Proper randomization what makes it impossible to create another tool to reverse secureSWF protection. The downside is that a completely different SWF file will be generated every time you run secureSWF, which might not be favorable for testing or verification.
· To solve the dilemma, we added a new checkbox in the “Protection Options” tab labeled “Randomize Results” checked by default. When unchecked, secureSWF will generate exactly the same protected SWF file. This will guarantee a consistent output for the identical files and identical configurations.
· Detailed File Save Options
· Official support for Adobe Flash CS5
· Flash CS5With secureSWF v3.5 we officially support Adobe Flash CS5. You can now switch to CS5 with confidence that you can still rely on us to protect your work.
May 27th, 2010Integration with Powerflasher FDT:
· Wouldn’t it be great to run secureSWF inside the most advanced Flash development platform? You will find a 5th download option when you download secureSWF v3.5; an FDT plugin! Copy the file into FDT plugins folder and a new secureSWF button will appear in FDT toolbar. That’s all what it takes to start running secureSWF within FDT.
· Kindisoft and Powerflasher are also announcing today a new partnership to empower you to make the best out of the Flash platform. secureSWF v3.5 is just a beginning of a much closer integration along the way. We’ll be working closely with the FDT team to bring you the ability to declare obfuscation settings within your code, debug obfuscated files, export a complete auto build script with a click of a button, and much more.
Remove Debugging Information:
· Keeping debugging information in released Flash applications can be useful for error reporting because source code line numbers and files names where an exception has been thrown can be found in the call stack. Unfortunately, this information is also available to attackers trying to reverse-engineer your code and it also costs a lot of file size.
· New options in secureSWF v3.5 will enable you to remove all debug information that you will no longer need outside a debugger, but will keep the source code line numbers. Error messages will show the obfuscated call stack trace (which you can de-obfuscate using the mapping table) with the line numbers.
Local Variables Renaming for ActionScript 3:
· Variables declared within the function scope in ActionScript 3 are usually compiled as registers without their specified names. But when they are not, for a number of reasons, the identifiers names are passed along the compiled code giving decompilers the ability to regenerate a very closer version on the original source code. With secureSWF v3.5, you can enable the ability to rename local variables in the few cases were they are still in the compiled code.
Control Over Randomization:
· Randomization is one of the most important protection mechanism for secureSWF. Proper randomization what makes it impossible to create another tool to reverse secureSWF protection. The downside is that a completely different SWF file will be generated every time you run secureSWF, which might not be favorable for testing or verification.
· To solve the dilemma, we added a new checkbox in the “Protection Options” tab labeled “Randomize Results” checked by default. When unchecked, secureSWF will generate exactly the same protected SWF file. This will guarantee a consistent output for the identical files and identical configurations.
Detailed File Save Options:
· Ok. We get it. You want to specify a new name for each file and you want that saved in the project configuration file. secureSWF v3.5 will save the selected output option and adds a new save option that enables you to specify the new name for each file if you want to.
· Official support for Adobe Flash CS5
· With secureSWF v3.5 we officially support Adobe Flash CS5. You can now switch to CS5 with confidence that you can still rely on us to protect your work.
October 27th, 2009· Super Compression
· Complete AIR and SWC Files Support
· Uber-Detailed Configuration Rules
June 6th, 2009· Advanced Code Transformation Selection.
· Exclude 3rd-Party SWC Code.
· Enhanced control flow obfuscation.
· PDF Reports.
· Easier Classes navigation.
· Enhanced CLI and Ant Scripr integration.
· Enhaced performance: better memory usage.
March 4th, 2009· Includes several bug fixes and introduces three new features.
· Control Over Aggressive Renaming - Aggressive Renaming turns identifiers names into a mix of symbols, whitespaces, and numbers that are illegal for ActionScript. While this is completely safe for the Flash Player, it causes trouble when parsing and writing XML. You can now turn aggressive renaming off for better compatibility with XML data-binding. When turned off, the new identifiers names will still be illegal for ActionScript, but fine with XML.
· Using ActionScript Keywords for New Identifiers Names - You will find another new checkbox in the Identifiers Renaming tab. When "Use ActionScript Keywords" is checked, Identifiers Renaming will use ActionScript reserved words, such as switch, case, if, while, do... etc, for 38 of the new identifiers names whither they are packages, classes, functions or variables. It will randomly select the identifiers that will be renamed into ActionScript keywords.
· Local Execution Prevention - We thought you might find it useful to prevent users from running your Flash application locally while it can still run on every other domain. The new checkbox under Encrypted Domain Locking will do just that if you don't want to lock your SWF file to your domain while still don't want users to run it on their local machine.
· Bug Fixes - We've done many general enhancements and fixed almost every issue that was reported to us through the Error Reporting tool. Most significant fixes are: A better layout for the Protection Options tab, we've fixed the issue with activating secureSWF on some localized versions of Windows, smart renaming now works for ActionScript 3 frame labels, and we now properly fill up the identifiers tables for ActionScript 2.
Find us on Google+
