CN112347430A - IOS application reinforcement protection system - Google Patents

Abstract

Compared with the prior art, the IOS application reinforcement protection system can effectively solve the problems of anti-reverse compilation, anti-debugging and anti-tampering processing, has extremely high safety coefficient and cracking cost, and improves the cracking difficulty by several orders of magnitude.

Description

IOS application reinforcement protection system

Technical Field

The invention relates to the technical field of IOS application security, in particular to an IOS application reinforcement protection system.

Background

The IOS is a handheld device operating system developed by Apple inc, which was originally designed for use by the iPhone as published by the Macworld conference, earlier than 2007, 1, 9, and was subsequently introduced to Apple products such as iPod touch, iPad, and Apple TV. iOS is also Darwin based and thus also belongs to Unix-like commercial operating systems, as does apple's Mac OS X operating system. Originally, the system is named iPhone IOS, the world wide digital television (WWDC) announces the system as iOS until 6.7.2010, and the data of Canalys shows that iOS occupies 30% of the market share of the global smartphone system by 11.2011, and the market share of the U.S. is 43%.

With the continuous development of the mobile phone application market, the acceleration rate of malicious applications on the IOS platform exceeds that of the Android platform. IOS applications also face security issues such as reverse cracking, shoplifting cracking, second package signing, etc. In order to solve the related problems, the IOS virtual machine source code is protected, and related reinforcement products are released for the iOS platform.

At present, most IOS reinforcement processing methods adopt command scripts to carry out character string encryption, class name, method name and picture hash value change on current project codes, but the mode is only based on basic code confusion, and has no good precaution effect on code decompilation and tampering technologies, so that the problems of decompilation prevention, debugging prevention and tampering prevention are solved at present.

Disclosure of Invention

Aiming at the defects of the prior art, the invention provides an IOS application reinforcement protection system which aims to solve the problem that IOS application protection is not comprehensive, and can effectively solve the problems of anti-compilation, anti-debugging and anti-tampering processing.

In order to achieve the purpose, the invention adopts the following technical scheme:

an IOS application reinforcement protection system includes a code obfuscation module, a string encryption module, and a code virtualization module.

Preferably, the code obfuscation module divides, scrambles, hides and inserts flower instructions into the control flow of the original code, so that the code logic is complicated without influencing the original logic, and the App store shelf availability is improved.

Preferably, the character string encryption module encrypts a static constant character string defined in the code and decrypts the static constant character string at runtime.

Preferably, the code virtualization module is a DX-VM virtual machine instruction that compiles the original code into dynamic.

Preferably, the reinforcement protection method performs one-key encryption through an IOS installation package compiling tool.

Preferably, the language used by the ruggedized protection system includes one or more of C/C + +, BASIC, Prolog, Python, PHP, Ruby, and Lua.

Preferably, the tool used by the code obfuscation module is prosguard.

Preferably, the character string encryption module adopts the following program:

#include <stdio.h>

#include <string.h>

#define LODWORD(_qw) ((unsigned long)(_qw))

#define HIDWORD(_qw) ((unsigned long)(((_qw) >> 32) & 0xffffffff))

char *pkey = "www.oschina.net";

char *keymap = "abcdefghijklmnopqrstuvwxyz";

void encrypt(char *username, char *key)

{

int i;

unsigned __int64 v6;

unsigned __int64 tmp;

int nameLen = strlen(username);

for ( i = 0; i != nameLen; ++i )

{

tmp = (keymap[i] * username[i] ^ 0x28FC) & 0xFFFFFFF;

v6 = LODWORD(tmp);

tmp = (unsigned int)keymap[i] * (unsigned __int64)(unsigned int)username[i] >> 32;

v6 += HIDWORD(tmp);

key[i] = pkey[v6 % 0xF];

key[i + 1] = 0;

}

}

int main(int argc, char* argv[])

{

char *name = "luobotou";

char key[64] = {0};

encrypt(name, key);

printf("name:%s\nkey:%s \n", name, key);

getchar();

return 0;

}。

compared with the prior art, the invention has the beneficial effects that:

firstly, strong safety protection:

1. source codes do not need to be uploaded, and the problem of code leakage does not need to be worried about;

2. the SAAS platform and the privatization deployment scheme meet the safety requirements of different customers.

Secondly, flexible one-key reinforcement:

1. the operation is convenient and fast, the normal development and packaging processes are not influenced, the package is uploaded to the SAAS reinforcement platform, and reinforcement is completed by one key;

2. the protection configuration, such as the code confusion strength and the code confusion ratio, can be flexibly adjusted according to the needs.

And thirdly, perfect iOS environment compatibility:

1. improving the probability of putting the App store on shelf;

2. after consolidation, the IPA and static library of the tape Bitcode can be packed, supporting submission of Bitcode to App store.

Drawings

FIG. 1 is a schematic diagram of a code fragment of an IOS application reinforcement protection system according to the present invention;

FIG. 2 is a flow chart of code segment control for an IOS application reinforcement protection system according to the present invention;

FIG. 3 is a pseudo code diagram of a code segment of an IOS application reinforcement protection system according to the present invention;

FIG. 4 is a schematic diagram of code logic obfuscation of an IOS application reinforcement protection system according to the present invention;

FIG. 5 is a flowchart illustrating a post-decompilation protection control of an IOS application reinforcement protection system according to the present invention;

FIG. 6 is a schematic diagram of string encryption for an IOS application reinforcement protection system according to the present invention;

fig. 7 is a schematic diagram of code virtualization of an IOS application hardened protection system according to the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings of the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments.

An IOS application reinforcement protection system includes a code obfuscation module, a string encryption module, and a code virtualization module.

A code obfuscation module: the control flow of an original code is segmented, disordered and hidden, a floral instruction is inserted, the code logic is complicated without influencing the original logic, the App store shelf life is improved, a tool used by the code confusion module is ProGuard, after the code is subjected to logic confusion protection, the control flow graph of the function becomes very complicated, a large number of useless code blocks which cannot be executed are interspersed in the function, logic jumping among the useless code blocks is achieved, and the difficulty of reverse analysis is greatly improved.

A string encryption module: the method comprises the steps of encrypting static constant character strings defined in a code, decrypting in a running mode, preventing an attacker from performing static analysis through the character strings, guessing code logic, encrypting all the static constant character strings, decrypting in the running mode, preventing the attacker from performing static analysis through the character strings, and guessing the code logic. After the character strings in the code are encrypted, all the character strings are replaced by encrypted references, and the character strings in the plain text cannot be seen by any decompilation means.

A code virtualization module: the original code is compiled into a dynamic DX-VM virtual machine instruction, the instruction runs on a DX virtual machine and cannot be decompiled to return readable source code, after code virtualization protection is adopted, the decompilation of the function cannot see any content similar to the original code, and only the call to a subsystem of the virtual machine exists in a function body.

The reinforcement protection system performs one-key encryption through an IOS installation package compiling tool.

The language used by the reinforcement protection system comprises one or more of C/C + +, BASIC, Prolog, Python, PHP, Ruby and Lua.

The character string encryption module adopts the following programs:

#include <stdio.h>

#include <string.h>

#define LODWORD(_qw) ((unsigned long)(_qw))

#define HIDWORD(_qw) ((unsigned long)(((_qw) >> 32) & 0xffffffff))

char *pkey = "www.oschina.net";

char *keymap = "abcdefghijklmnopqrstuvwxyz";

void encrypt(char *username, char *key)

{

int i;

unsigned __int64 v6;

unsigned __int64 tmp;

int nameLen = strlen(username);

for ( i = 0; i != nameLen; ++i )

{

tmp = (keymap[i] * username[i] ^ 0x28FC) & 0xFFFFFFF;

v6 = LODWORD(tmp);

tmp = (unsigned int)keymap[i] * (unsigned __int64)(unsigned int)username[i] >> 32;

v6 += HIDWORD(tmp);

key[i] = pkey[v6 % 0xF];

key[i + 1] = 0;

}

}

int main(int argc, char* argv[])

{

char *name = "luobotou";

char key[64] = {0};

encrypt(name, key);

printf("name:%s\nkey:%s \n", name, key);

getchar();

return 0;

}。

the IOS reinforcement protection method comprises the following operation processes: the code of the figure 1 is compiled and analyzed, the analysis process is shown in figure 2, and then the code is inversely compiled into a pseudo code, as shown in figure 3, character strings used in the code logic and the source code are all clearly visible and basically consistent with the source code structure, the control flow of the original code is divided, disordered and hidden, or a flower instruction is inserted into a function to realize the confusion of the code, so that the code logic is complicated but the original code logic is not influenced, as shown in figure 4, after the logic confusion protection is carried out on the code, the control flow graph of the function becomes very complicated, a large number of useless code blocks which cannot be executed are inserted into the function, and the logic jumping among the useless code blocks is carried out, so that the difficulty of inverse analysis is greatly enhanced; if the decompilation prevention function is started, the control flow graph is completely hidden, only one code block is left, and the effective code cannot be decompiled, as shown in fig. 5, which is very effective for resisting a reverse analysis tool.

As shown in FIG. 6, all static constant strings are encrypted, C/C + +/OC/Swift strings are supported, decryption is performed during runtime, an attacker is prevented from performing static analysis through the strings, code logic is guessed, after the strings in the code are encrypted, all the strings are replaced by encrypted references, any decompilation means cannot see the strings in the clear, and the world! Hello, World! character strings can be easily decompiled but protected from view.

As shown in fig. 7, the original code is compiled into a dynamic DX-VM virtual machine instruction, and the dynamic DX-VM virtual machine instruction cannot be decompiled to return a readable source code, any tool cannot directly decompile the virtual machine instruction, after the code virtualization protection is adopted, the decompiling of the function cannot see any content similar to the original code, and only the call to the virtual machine subsystem is performed in the function body.

The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art should be considered to be within the technical scope of the present invention, and the technical solutions and the inventive concepts thereof according to the present invention should be equivalent or changed within the scope of the present invention.

Claims (8)

1. An IOS application reinforcement protection system, characterized in that: the reinforcement protection system comprises a code obfuscation module, a character string encryption module and a code virtualization module.

2. The IOS application hardened protection system of claim 1, wherein: the code confusion module divides, disorganizes and hides the control flow of the original code, inserts the flower instruction, complicates the code logic without influencing the original logic, and improves the App store shelf probability.

3. The IOS application hardened protection system of claim 1, wherein: the character string encryption module encrypts the static constant character string defined in the code and decrypts the character string during running.

4. The IOS application hardened protection system of claim 1, wherein: the code virtualization module compiles the original code into dynamic DX-VM virtual machine instructions.

5. The IOS application hardened protection system of any one of claims 2-4, wherein: the reinforcement protection method carries out one-key encryption through an IOS installation package compiling tool.

6. The IOS application hardened protection system of claim 5, wherein: the language used by the reinforcement protection system comprises one or more of C/C + +, BASIC, Prolog, Python, PHP, Ruby and Lua.

7. The IOS application hardened protection system of claim 4, wherein: the tool used by the code obfuscation module is prosguard.

8. The IOS application hardened protection system of claim 3, wherein: the character string encryption module adopts the following programs:

#include <stdio.h>

#include <string.h>

#define LODWORD(_qw) ((unsigned long)(_qw))

#define HIDWORD(_qw) ((unsigned long)(((_qw) >> 32) & 0xffffffff))

char *pkey = "www.oschina.net";

char *keymap = "abcdefghijklmnopqrstuvwxyz";

void encrypt(char *username, char *key)

{

int i;

unsigned __int64 v6;

unsigned __int64 tmp;

int nameLen = strlen(username);

for ( i = 0; i != nameLen; ++i )

{

tmp = (keymap[i] * username[i] ^ 0x28FC) & 0xFFFFFFF;

v6 = LODWORD(tmp);

tmp = (unsigned int)keymap[i] * (unsigned __int64)(unsigned int)username[i] >> 32;

v6 += HIDWORD(tmp);

key[i] = pkey[v6 % 0xF];

key[i + 1] = 0;

}

}

int main(int argc, char* argv[])

{

char *name = "luobotou";

char key[64] = {0};

encrypt(name, key);

printf("name:%s\nkey:%s \n", name, key);

getchar();

return 0;

}。

Images