简体   繁体   English

Android AESObfuscator与Proguard

[英]android AESObfuscator vs proguard

When setting up Android LVL I see that it uses AESObfuscator. 设置Android LVL时,我看到它使用AESObfuscator。 Do you then use Proguard? 然后,您是否使用Proguard? Are they used together or one or the other? 它们一起使用还是彼此使用?

Have a look at http://developer.android.com/guide/publishing/licensing.html , which provides some background on both license response obfuscation (through AESObfuscator) and code obfuscation (using Proguard). 看看http://developer.android.com/guide/publishing/licensing.html ,它提供了有关许可证响应混淆(通过AESObfuscator)和代码混淆(使用Proguard)的一些背景知识。

To sum things up: You will want to use both as they both address different obfuscation domains (data vs. code). 总结一下:您将要同时使用这两种方法,因为它们都处理不同的混淆域(数据与代码)。

AESObfuscator is an implementation of Obfuscator from Android LVL, it is used by LVL to protect sensitive licensing data stored on local device (by simply obfuscate data before storing it). AESObfuscator是Android LVL的Obfuscator的实现,LVL使用它来保护存储在本地设备上的敏感许可数据(通过在存储之前简单地对数据进行混淆)。 This is happened at runtime. 这是在运行时发生的。

Obfuscation step in Proguard is mainly used to obfuscate your source code to increase difficulties of decompilation from pirate. Proguard中的混淆步骤主要用于混淆您的源代码,以增加从海盗进行反编译的难度。 This is happened at project build time, (before compile your source dode) 这是在项目构建时发生的(在编译源代码之前)

We usually use both together. 我们通常将两者一起使用。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM