secureSWF v3.3 beta

Update : secureSWF v3.3 has been officially released.

We are very excited that v3.3 is almost ready. Today, we have finally been able to put together a build that we can share with you. v3.3 went through an intensive series of refactoring that enabled us to fix long standing issues as what @bunnyhero kindly reported and add new features that we’ve been excited about for a while.

While v3.3 is a minor release, it adds new features and enhancements that qualifies for a major release for most software vendors. The new version introduces the following:

Advanced Code Transformation Selection

Is all code created equal? We do not think so. Some parts of your code are definitely worth the overhead Control Flow Obfuscation adds and the file size increase Dynamic Code Wrapping does. But  you are probably happy leaving other parts of your code less protected for the sake of better performance or smaller file size. Now with this new feature, which opens up by clicking the “Advanced” button in Protection Options tab, you can override the code transformation settings for each function.

But the most useful thing about this is overriding the settings for code that breaks after obfuscation. For example, if you get an unbalanced stack verification error after obfuscating a file, you no longer have to turn off Control Flow Obfuscation for the entire code. You can now turn it off for the function that is causing the error which is usually at the top of the call stack trace.

Exclude 3rd-Party SWC Code

When using a third-party SWC file in your Flash project, there is a chance that it is already obfuscated. If so, the result SWF file will contain obfuscated code blocks that will prevent secureSWF from successfully parsing and analyzing your SWF file. To solve this issue, you can now add the SWC file that you have been using in secureSWF and it will skip the code blocks in your SWF files that came from it.

Enhanced Control Flow Obfuscation

We’ve enhanced our Control Flow Obfuscation algorithm making it more random and much harder to trace. You will no longer see stuff as if(false) or if(true) in your obfuscated code. Instead, we are using your own variables and parameters to evaluate our branching statements. Don’t worry, this change does not affect the performance and the file size increase is still negligible.

PDF Reports

secureSWF can now generate a nice and shiny PDF report that details all the changes it did to your code. Please note that the reports still need some polishing that we will definitely do before the official release.

Easier Classes Navigation

We’ve separated Classes from Frame Labels names in ActionScript 3 projects for good. You can now browse your code without the noise frame labels adds. All frame labels can still be found in nice table next to the classes.

Enhanced Performance

You will notice that it now take less time for secureSWF to process your code and, more importantly, will consume less memory. We still plan for even further enhancements in the next releases.

Enhanced CLI and Ant Script Integration

We want you to be able to do everything secureSWF can do using the command-line interface or an Ant script. And we are working to make that happen. This version includes many enhancements and additions to the CLI and Ant task. Please note that we haven’t updated the documentation yet. Contact our support team for a draft documentation of the CLI and Ant task new features.

Download secureSWF v3.3 beta

secureSWF Demo Version

secureSWF Professional Version (Requires Registration Information)

secureSWF Standard Version (Requires Registration Information)

secureSWF Personal Version (Requires Registration Information)

This entry was posted in secureSWF Updates and tagged , , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>