If you want to protect your final SWFs, you'll need to obfuscate the SWF rather than obfuscating the source code. While changing variable / function / etc names in the source code before compilation will provide some protection, it makes the process much more complex and misses out on several additional levels of possible obfuscation available by processing the compiled SWF.
There are numerous SWF obfuscators available; here's a topic that covers that (note all of the linked topics on the right-hand side). My personal favorite is secureSWF.
There is no need to obfuscate your code since it is compiled and that will take care of it. Now if you are referring to a de-compiler then don't because it will correct all your obfuscation.
发布评论
评论（3）
如果您想保护最终的 SWF，则需要对 SWF 进行混淆，而不是对源代码进行混淆。虽然在编译之前更改源代码中的变量/函数/等名称将提供一些保护，但它会使过程变得更加复杂，并且会错过通过处理编译的 SWF 可能产生的几个额外级别的混淆。
有许多可用的 SWF 混淆器； 这里一个涵盖该内容的主题（请注意右侧的所有链接主题）。我个人最喜欢的是 secureSWF。
If you want to protect your final SWFs, you'll need to obfuscate the SWF rather than obfuscating the source code. While changing variable / function / etc names in the source code before compilation will provide some protection, it makes the process much more complex and misses out on several additional levels of possible obfuscation available by processing the compiled SWF.
There are numerous SWF obfuscators available; here's a topic that covers that (note all of the linked topics on the right-hand side). My personal favorite is secureSWF.
我使用 Flash Secure Optimizer 便宜又安全
I use Flash Secure Optimizer cheap and secure
无需混淆您的代码，因为它已编译并且会处理它。现在，如果您指的是反编译器，那么就不要这样做，因为它会纠正您所有的混淆。
There is no need to obfuscate your code since it is compiled and that will take care of it. Now if you are referring to a de-compiler then don't because it will correct all your obfuscation.