Android Application Obfuscation

 2.3sdk has two new features:
1.When I first installed 2.3, I checked the SDK directory and found that a folder "proguard" was added under <sdk_path> \ tools, as shown in, I was wondering if Google had finally taken proguard into consideration. Theoretically, obfuscation of Java is acceptable, but the key lies in how to compile the proguard obfuscation script.

2. After sdk2.3 is used, a file "proguard. cfg" will be added to the new project compared with the previous one ". The proguard script is required for obfuscation.
For example:

The Code is as follows:

1. -Optimizationpasses 5
2. -Dontusemixedcaseclassnames
3. -Dontskipnonpubliclibraryclasses
4. -Dontpreverify
5. -Verbose
6. -Optimizations! Code/simplification/arithmetic ,! Field /*,! Class/merging /*
8. -Keep public class * extends Android. App. Activity
9. -Keep public class * extends Android. App. Application
10. -Keep public class * extends Android. App. Service
11. -Keep public class * extends Android. content. broadcastreceiver
12. -Keep public class * extends Android. content. contentprovider
13. -Keep public class com. Android. Vending. Licensing. ilicensingservice
15. -Keepclasseswithmembernames class *{
16. Native <Methods>;
17. }
19. -Keepclasseswithmembernames class *{
20. Public <init> (Android. content. Context, Android. util. attributeset );
21. }
23. -Keepclasseswithmembernames class *{
24. Public <init> (Android. content. Context, Android. util. attributeset, INT );
25. }
27. -Keepclassmembers Enum *{
28. Public static ** [] values ();
29. Public static ** valueof (Java. Lang. String );
30. }
32. -Keep class * implements Android. OS. parcelable {
33. Public static final Android. OS. parcelable $ creator *;
34. }

As you can see from the script, obfuscation retains the basic components inherited from activity, service, application, broadcastreceiver, contentprovider, and so on.

All native variable names and class names are retained. All classes Use constructors with fixed parameter formats, such as enumeration. (For more information, see examples and comments in <proguard_path> \ examples .)

Well, it's almost done. Let's take a look at how to generate a obfuscated APK. Please note that the new features of the SDK are available in the document, so the document is very important.

View the sdk2.3 document and go to "<androidsdk_path>/docs/GUIDE/developing/tools/proguard.html".Enabling proguard"Is described as follows:

1. To enable proguard so that it runs as part of an ant or eclipse build, set the proguard. config property in the <project_root>/default. properties file. the path can be an absolute path or a path relative to the project's root.

Okay, so do it.

Add the following phrase "proguard. Config = proguard. cfg" to "Default. properties" of the project, for example:

In this way, the ADT obfuscation operation has been set. The next step is the normal packaging and signature ..
It is the notepad that comes with the SDK demo: