CN110765424B - Android application reinforcement method and computer equipment - Google Patents

Abstract

The invention provides an android application reinforcement method, which comprises the steps of obtaining an APK to be reinforced, and obtaining a dex file from the APK; encrypting the dex file, and writing a decryption strategy and a memory adaptation scheme into the so file; recompiling to obtain a reinforced APK; the invention also provides computer equipment which is configured with a set of security policy, thereby effectively avoiding the apk from being decompiled, tampered and secondarily utilized.

Description

Android application reinforcement method and computer equipment

Technical Field

The invention relates to an android application reinforcement method and computer equipment.

Background

At present, the market share of android in global mobile market exceeds 6, that is, more than half of mobile phone users in the world use mobile devices mounted in an android system, and for this reason, global app application has been well developed in recent years, and the safety problem brought with the growth also urges a large number of solutions about application safety, wherein the most attractive solution is a strengthening solution of apk.

The conventional strengthening scheme of the apk is not landing loading, namely memory loading, but the common scheme is a scheme provided based on a certain android system version, for example, in the android4.4 version, dalvik is used for optimizing a dex file, so that the memory loading mode is necessarily direct loading of the dex file, but in the version after 4.4, the android system is used for optimizing the dex file by using an art virtual machine, the previous scheme cannot be effective, and in addition, even in the version after 4.4, the memory loading mode of the dex file is not consistent, and moreover, a hacker can easily obtain code logic of the file to crack the file due to the single memory loading mode.

Disadvantage 1: the conventional reinforcing scheme is single and cannot be adapted to android systems of various versions, and nowadays, the apk reinforcing scheme is also adapted along with the day.

And (2) disadvantage: the method is characterized in that the method is reinforced to be not loaded to the ground, but the method also has the great disadvantage that in dynamic debugging, a complete dex file is easy to obtain in a memory, so even though the scheme of memory loading can effectively prevent static analysis, for dynamic debugging, if the scheme of memory loading is single, the method is easy to be utilized by people, and attack means such as memory dump are used.

Disclosure of Invention

The technical problem to be solved by the invention is to provide an android application reinforcement method and computer equipment, a set of security policies are configured, and the apk is effectively prevented from being decompiled, tampered and secondarily utilized.

One of the present invention is realized by: an android application reinforcement method comprises the following steps:

step 1, obtaining an APK to be reinforced, and obtaining a dex file from the APK;

step 2, encrypting the dex file, and writing a decryption strategy and a memory adaptation scheme into the so file;

and 3, recompiling to obtain the reinforced APK.

Further, the step 1 is further specifically: and obtaining the APK to be reinforced, and then performing decompiling to obtain a dex file.

Further, the step 2 is further specifically: and compressing and encrypting the dex file, and writing a decryption strategy and a memory adaptation scheme into the so file.

Further, the memory adaptation scheme is as follows:

if the application system is android4.4, loading a dex file by using dalvik so as to obtain a dex instance;

if the application systems are android5.0 to android6.0, calling an openmemory method of libart. so as to load a dex file, thereby obtaining a dex instance;

if the application systems are from android 7.0 to android7.1.2, replacing the virtual dex in the load in the memory by using a hook scheme so as to obtain a dex instance;

and if the application systems are android8.0 to android9.0, loading the dex in the memory by using a class loader loaded by a new mechanism memory of the android to obtain a dex instance.

The second invention is realized by the following steps: a computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein: the processor implements the following steps when executing the program:

step 1, obtaining an APK to be reinforced, and obtaining a dex file from the APK;

step 2, encrypting the dex file, and writing a decryption strategy and a memory adaptation scheme into the so file;

and 3, recompiling to obtain the reinforced APK.

Further, the step 1 is further specifically: and obtaining the APK to be reinforced, and then performing decompiling to obtain a dex file.

Further, the step 2 is further specifically: and compressing and encrypting the dex file, and writing a decryption strategy and a memory adaptation scheme into the so file.

Further, the memory adaptation scheme is as follows:

if the application system is android4.4, loading a dex file by using dalvik so as to obtain a dex instance;

if the application systems are android5.0 to android6.0, calling an openmemory method of libart. so as to load a dex file, thereby obtaining a dex instance;

if the application systems are from android 7.0 to android7.1.2, replacing the virtual dex in the load in the memory by using a hook scheme so as to obtain a dex instance;

and if the application systems are android8.0 to android9.0, loading the dex in the memory by using a class loader loaded by a new mechanism memory of the android to obtain a dex instance.

The invention has the following advantages: the method can reinforce and protect the android application, and can be adapted to systems from android4.4 to android 9.0; the reinforced Android application is safer and not utilized by others, and a set of security strategy is configured, so that the apk is effectively prevented from being decompiled, tampered and secondarily utilized.

Drawings

The invention will be further described with reference to the following examples with reference to the accompanying drawings.

FIG. 1 is a flowchart of an android application reinforcement method of the present invention.

FIG. 2 is a flow chart of apk reinforcement in an embodiment of the present invention.

Fig. 3 is a flowchart of a memory load adaptation scheme in an embodiment of the present invention.

Detailed Description

As shown in fig. 1, the android application reinforcement method of the present invention includes:

step 1, obtaining an APK to be reinforced, and then performing decompiling to obtain a dex file;

step 2, compressing and encrypting the dex file, and writing a decryption strategy and a memory adaptation scheme into the so file, wherein the memory adaptation scheme is as follows:

if the application system is android4.4, loading a dex file by using dalvik so as to obtain a dex instance;

if the application systems are android5.0 to android6.0, calling an openmemory method of libart. so as to load a dex file, thereby obtaining a dex instance;

if the application systems are from android 7.0 to android7.1.2, replacing the virtual dex in the load in the memory by using a hook scheme so as to obtain a dex instance;

if the application systems are android8.0 to android9.0, loading dex in the memory by using a class loader loaded by a new mechanism memory of the android to obtain a dex instance;

and 3, recompiling to obtain the reinforced APK.

The computer equipment comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, and is characterized in that: the processor implements the following steps when executing the program:

step 1, obtaining an APK to be reinforced, and then performing decompiling to obtain a dex file;

step 2, compressing and encrypting the dex file, and writing a decryption strategy and a memory adaptation scheme into the so file, wherein the memory adaptation scheme is as follows:

if the application system is android4.4, loading a dex file by using dalvik so as to obtain a dex instance;

if the application systems are android5.0 to android6.0, calling an openmemory method of libart. so as to load a dex file, thereby obtaining a dex instance;

if the application systems are from android 7.0 to android7.1.2, replacing the virtual dex in the load in the memory by using a hook scheme so as to obtain a dex instance;

if the application systems are android8.0 to android9.0, loading dex in the memory by using a class loader loaded by a new mechanism memory of the android to obtain a dex instance;

and 3, recompiling to obtain the reinforced APK.

One specific embodiment of the present invention:

the invention provides a reinforcing scheme adaptive to each android platform, and a set of security policies are configured, so that the apk is effectively prevented from being decompiled, tampered and secondarily utilized.

The invention provides an APK reinforcing scheme, as shown in FIG. 2, the process is as follows:

1. and obtaining the APK to be reinforced.

2. And decompiling the APK to be reinforced to obtain a code file needing to be protected, namely a dex file.

3. And integrally compressing and encrypting the dex file, and writing an encryption and decryption strategy and a memory adaptation scheme into the so file.

4. After integration, the consolidated APK is recompiled.

Wherein, for the memory loading, the adaptation of each android version needs to be processed correspondingly, as shown in fig. 3,

1. and (4) directly loading the dex file by using dalvik at android4.4 so as to obtain a dex instance.

2. And calling an openmemory method of libart. so at android 5.0-6.0 to load a dex file, thereby obtaining a dex instance.

3. 7.0 to android7.1.2, because the version change, the previous openmemory method of libart.so is not applicable, the hook scheme, read, open, fork, fstat, etc. function of hook libart.so will be used to replace the dummy dex in the load in the memory, and actually load the source dex, thereby obtaining the dex instance.

4. And in android8.0 to 9.0, a class loader loaded by a new mechanism memory of the android is used for loading dex in the memory to obtain a dex instance.

Keywords and key terms:

decompiling: the apk decompiling relies on a third-party tool, apktool, to unpack and separate the original apk into important files such as res (resource folder), resources, arsc (binary resource file), classes, dex (source code resource file), lib (attachment component), android manifest.

Class loader: the Android class loader has the meaning that a dex file is optimized to be capable of running in Android equipment.

Memory loading: the memory loading in the invention has the practical meaning that a class loader is applied to call a dex instance in the memory, thereby achieving the function of loading without falling to the ground.

Although specific embodiments of the invention have been described above, it will be understood by those skilled in the art that the specific embodiments described are illustrative only and are not limiting upon the scope of the invention, and that equivalent modifications and variations can be made by those skilled in the art without departing from the spirit of the invention, which is to be limited only by the appended claims.

Claims (4)

1. An android application reinforcement method is characterized by comprising the following steps: the method comprises the following steps:

step 1, obtaining an APK to be reinforced, and obtaining a dex file from the APK;

step 2, compressing and encrypting the dex file, and writing a decryption strategy and a memory adaptation scheme into the so file; the memory adaptation scheme is as follows:

if the application system is android4.4, loading a dex file by using dalvik so as to obtain a dex instance;

if the application systems are android5.0 to android6.0, calling an openmemory method of libart. so as to load a dex file, thereby obtaining a dex instance;

if the application systems are from android 7.0 to android7.1.2, replacing the virtual dex in the load in the memory by using a hook scheme so as to obtain a dex instance;

if the application systems are android8.0 to android9.0, loading dex in the memory by using a class loader loaded by a new mechanism memory of the android to obtain a dex instance;

and 3, recompiling to obtain the reinforced APK.

2. The android application reinforcement method of claim 1, wherein the android application reinforcement method comprises the following steps: the step 1 is further specifically as follows: and obtaining the APK to be reinforced, and then performing decompiling to obtain a dex file.

3. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein: the processor implements the following steps when executing the program:

step 1, obtaining an APK to be reinforced, and obtaining a dex file from the APK;

step 2, compressing and encrypting the dex file, and writing a decryption strategy and a memory adaptation scheme into the so file; the memory adaptation scheme is as follows:

if the application system is android4.4, loading a dex file by using dalvik so as to obtain a dex instance;

if the application systems are android5.0 to android6.0, calling an openmemory method of libart. so as to load a dex file, thereby obtaining a dex instance;

if the application systems are from android 7.0 to android7.1.2, replacing the virtual dex in the load in the memory by using a hook scheme so as to obtain a dex instance;

if the application systems are android8.0 to android9.0, loading dex in the memory by using a class loader loaded by a new mechanism memory of the android to obtain a dex instance;

and 3, recompiling to obtain the reinforced APK.

4. A computer device according to claim 3, wherein: the step 1 is further specifically as follows: and obtaining the APK to be reinforced, and then performing decompiling to obtain a dex file.

Images