What's new in secureSWF 4.6 Build 3883
Sep 9, 2014
- Support for AIR 15:
- We now support all AIR versions. Including AIR 15 beta.
- Manual Activation:
- If you need to activate secureSWF on an offline, or behind a firewall, machine, you can now use the manual activation process.
- Using your registration information, and the Verification Key, you can activate secureSWF without the need to connect to the activation server. Of course, this will only work on the machine which you have used to generate the Machine ID. The manual activation process can be done via the GUI or the CLI.
- Enhanced Protection Against Decompilers:
- As we frequently do, the new build also updates the protection mechanisms we use to prevent decompilers from generating anything useful or running at all. We recommend that you re-run your apps through the new version and publish an update.
- Better String Encryption Performance:
- We’ve enhanced the performance of the string decryption routine, which runs every time your code accesses an encrypted string. This means your app will now perform a bit faster if you are using string encryption. The enhancement applies to both RC4 and AES algorithms.
- 5. Bug Fixes:
- We’ve fixed an issue with String Encryption advanced selection dialog in the GUI. We’ve also fixed almost all reported crashes. Please keep sending crash reports. We rely on them to make secureSWF more stable and reliable.
New in secureSWF 4.5 Build 3859 (Jun 24, 2014)
- Eliminated the need for Flex or AIR SDKs. secureSWF can now sign AIR and APK files all by itself.
- Internal certificate for signing AIR and APK files when none is provided.
- Generate AIRI from AIR files and vice versa.
- Ability to protect native desktop AIR apps.
- Protection options have been enhanced to crash all the latest decompilers.
- Packages, classes, and non-private members are excluded from renaming in SWC files by default.
- Export to Ant now generates separate rules for protection options and renaming options.
- Fixed inconsistent results when protecting with GUI and then exporting to Ant.
- Windows 8.1 support.
- Fixed retention of save each file as in Windows.
- Fixed relative path issues on Mac.
- Rules list in the configuration options tab got redesigned.
- Added search for literal strings.
- GUI now saves maximized state.
- Fixed finding main SWF file in AIR and APK apps containing spaces in their names.
- Export to Ant utility now saves the latest used location.
- Fixed “Unable to parse the engine output” issue.
- Added ability to activate secureSWF from Ant.
- Fixed applying renaming values in configuration rules.
- Fixed all reported crashes which we were able to regenerate.
New in secureSWF 4.0 Build 3820 (May 28, 2013)
- Fast and lightweight engine; reworked identifier renaming; improved code protection; code optimization; fast RC4 and extra-secure AES encryption; hassle-free domain locking; encrypted loader protects all SWF assets; SWF file optimization, and a whole lot more!
New in secureSWF 3.6 Build 6034 (Nov 1, 2011)
- New features and enhancements:
- In-code secureSWF configurations
- Flash CS5.5 & Flash Builder 4.5 fully supported
- Protect AIR for Android APK files
New in secureSWF 3.4 Build 3935 (Oct 28, 2009)
- Super Compression:
- You’ve asked and we have delivered! secureSWF can now reduce your SWF file size. In our labs, we’ve seen Flash SWF file sizes drop by 30%. This new feature can reduce the file size up to 10% by itself!
- Unlike other obfuscators that just bloat the size of your SWF files, secureSWF can actually reduce your file size when using identifiers renaming, size optimization, and this new amazing feature.
- Complete AIR and SWC Files Support:
- secureSWF is proud to be the only protection and obfuscation product on the market fully supporting AIR and SWC files. What does that mean? It means you can directly protect your whole AIR application from within secureSWF. Say goodbye to the manual process of protecting each embedded SWF file and then fumbling to properly package the AIR application. secureSWF will automatically handle packaging and protecting your AIR application. It also means you can now use all secureSWF’s features for SWC and AIR files too!
- Uber-Detailed Configuration Rules:
- Previous versions of secureSWF enabled you to specify how your code will be obfuscated down to a single function or identifier. This is powerful, but we’ve heard from users that pinpointing individual functions and identifiers is very time consuming. Because of this, we’ve added the Rules tab. Now, you can just tell secureSWF exactly what to do with all the code in an entire package, or a single class. Just write in the pattern and check the options you want to override.
New in secureSWF 3.1 Build 2841 (Dec 18, 2008)
- We are happy and proud to be able to provide you with Flash CS4 support!
- Not only that, this version of secureSWF has gone through many internal changes that enhances existing features and fixes issues that were reported to us. Please keep sending us your valuable feedback.
- Adobe's Flash CS4 Support
- One major change is that we now officially support Flash CS4 and Flash player 10. And yes, this is all through a free of charge minor version update!
- secureSWF v3.1 supports Flash CS4 new features such as Vector. data type, dynamic sound API, and new BitmapData methods. You can now start publishing your 3D animations with confidence.
- Full UTF-8 Encoding Support
- Another major improvement is full UTF-8 support. If you have faced problems with non-English text after protecting your files with previous versions of secureSWF, then with this new version, it will all be an issue from the past.
- General Enhancements
- We have done many internal improvements that fixes all the known issue, enhances secureSWF's ActionScript protection and optimization, and ensures better general performance and memory usage.