Java混淆 - ProGuard / yGuard / other？ [英] Java obfuscation - ProGuard/yGuard/other?

问题描述

这与最近的这些问题类似：

This is along similar lines as these recent questions:

用于减小尺寸的最佳Java混淆应用程序
创建不可反向工作的Java程序

然而，最终会推荐yGuard和其他ProGuard，但两者都没有提及。我想知道我们是否可以对每一个进行比较，并听取围墙双方的人们经历。在ProGuard网站上查看这个对比图表，它明显倾向于ProGuard。但是每个人的实际经验呢？哪一个会产生较小的输出？哪一个更难反编译？每个人都支持哪些Java版本？

However, one ends up recommending yGuard and the other ProGuard but neither mention both. I wonder if we could get a comparison of each one and hear peoples experiences from both sides of the fence. Looking at this comparison chart on the ProGuard website its clearly angled towards ProGuard. But what about real-world experience of each - which one produces smaller output? which one is harder to decompile from? what Java versions are supported by each?

我个人对J2ME的观点特别感兴趣，但请不要将讨论局限于此。

Personally I'm particularly interested from a J2ME point of view but please don't limit the discussion to that.

推荐答案

Proguard是一款更好的产品;特别是如果你花时间去完成J2ME的设置。

Proguard is a better product; especially if you take the time to go through the settings for J2ME.

特别是对于J2ME，有一个更好的（商业）产品叫做 mBooster

Specifically for J2ME there is a far better (commercial) product called mBooster

我的应用程序在通过Proguard后，我的尺寸已经提高了大约25％。这主要是为了对Jar文件中更好的Zip压缩以及对类合并和预验证的全面支持。

I've been getting around 25% improvement in size on my application after its been through Proguard. This is mainly to do with the better Zip compression on the Jar file and comprehensive support for class merging and preverification.

这篇关于Java混淆 - ProGuard / yGuard / other？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！