许多 RSL 中的 AS3 混淆
我正在开发一个非常大的闪存项目，该项目在运行时库之间广泛共享代码。 我正在评估是否要混淆我们的代码，以及使用哪个混淆器，但我很难找到一个符合要求的混淆器。
- 许多 RSL、许多源代码树和项目。 -我们使用一些动态属性，因此我希望对重命名哪些符号有很好的控制。 -可集成到构建系统中
我查看了 Amayeta，但我不相信它具有我需要的细粒度控制。 我查看了 irrfuscator，但它似乎非常不成熟，并且似乎不能很好地扩展到大型项目。
还有其他建议吗？ 我知道混淆或加密并不能提供完整的保护，我只是想让人们更难骚扰我们。
另一方面，如果不存在可接受的混淆器，我会认为我们不需要这样做。
I'm working on a very large flash project that shares code extensively across runtime libraries. I'm evaluating whether to obfuscate our code, and which obfuscator to use, and I'm having trouble finding one that fits the bill.
-Many RSLs, many source trees and projects.
-We use some dynamic properties, so I'd like to have a good deal of control over which symbols are renamed.
-Integrable into a build system
I looked at Amayeta, but I'm not convinced it has the fine-grained control I need.
I looked at irrfuscator, but it seems very immature, and doesn't seem to scale well to large projects.
Any other recommendations? I'm aware that obfuscation or encryption won't provide complete protection, I'm just looking to make it harder for folk to mess with us.
On the other hand, if no acceptable obfuscator exists, I'll just argue that we don't need to do it.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
看来，由于您要使用大量共享库，因此您不必混淆变量、方法甚至某些字符串，因为其他 swf 需要能够访问它们。 这使得它的用处大大减少，并且反编译器更容易产生可读的结果。
删除空格可能也起不了多大作用，因为反编译器也都是从头开始格式化代码。
缩小它会稍微缩小编译后的大小，并且加密字符串可能会有所帮助，但前提是它们不会妨碍 SWF (RSL) 互操作性。
我要问的底线问题是，那些不顾一切地去反编译代码的人，是否也会不顾一切地“破坏”本质上由组合函数和短变量名称组成的东西？
It seems that since you're going with lots of shared libraries, that you'll have to not obfuscate the vars, methods or even some strings--since the other swfs will need to be able to access them. Which makes it a lot less useful, and a bit easier for a decompiler to produce readable results.
Stripping the whitespace might probably won't do much either, since the decompilers all format the code from scratch too.
Minifying it would shrink the compiled size a little bit, and encrypting the strings might be helpful, but only if they don't get in the way of SWF (RSL) interoperability.
The bottom line question I'd ask is that are the people who are desperate enough to bother decompiling the code, aren't also going to be desperate enough to "defuscate" the what will essentially be combined functions and short var names?