secureSWF FAQ

What is the difference between the Professional, Standard, and Personal-Lite editions of secureSWF?


What's the upgrade policy from previous versions to secureSWF v4


Can I get an evaluation copy?


What is code obfuscation?


Why use code obfuscation?


My Flash app is no longer running after using secureSWF. What should I do?


Does secureSWF change the source code of my application?


How does secureSWF protect SWF files?


What is Statement-level Randomization?


What is Control Flow obfuscation?


What is Dynamic Code Wrapping?


What is Literal Strings Encryption?


Why would I use obfuscation to hide security vulnerabilities? Wouldn't it be better to ensure that I have no vulnerabilities?


What happens when I try to use a decompiler on an application run through secureSWF?


What versions of Flash does secureSWF support?


Can I use regular expressions to exclude or include certain identifiers?


How do I integrate secureSWF into my automated build process?


What about tools that convert SWF files into executable form such as .EXE files?


Is Flash Remoting a problem for secureSWF?


My application uses Flash components. Can I still use secureSWF?


How can secureSWF break decompilers without affecting the Flash player?


What does renaming to "unprintable and illegal characters" mean?