KR102449500B1 - Apparatus for executing application using configuration management to avoid exeption error and method thereof - Google Patents

Abstract

Disclosed are an apparatus and method for providing stable execution of an application by avoiding execution with configuration-managed original dex when an exception error occurs during execution of obfuscated dex by configuration management of obfuscated dex and non-obfuscated original dex . An apparatus for executing an application includes: a multi-dex unit in which a method obfuscated by execution of the application is executed; an original dex unit in which the shape is managed corresponding to the obfuscated method and the non-obfuscated original method is executed; an exception detection unit for detecting the occurrence of an exception error in a method executed in the multidex unit; and a configuration management unit that receives the exception error information detected by the exception detection unit and calls execution of the original method corresponding to the method of the multidex unit in which the exception error occurs in order to avoid the detected exception error.

Description

Apparatus for executing application using configuration management to avoid exeption error and method thereof

The present invention is a technology of configuration management, and more specifically, by adding an original dex to which obfuscation is not applied to a multidex to which obfuscation is applied in an application, configuration management is performed, and when the multidex is executed When an exception error occurs, an apparatus and method for avoiding the exception error by executing the added original dex.

Android has a limit of 65536 (4K) total methods that an app can have or reference. This is the maximum number that one Dalvik Executable (dex) file can reference and call. To put it simply, in the dex file, which is an Android executable, the total number of methods (eg, unit execution code) that is the execution unit of the dex file is 4K, which means that the execution size is limited.

Here, when the android support library or several open source libraries are added to the application and built, even if the method programmed by the programmer is 4K or less, the method of the added library is added, so it may exceed 4K. When an application exceeding 4K is built, an error message as shown in FIG. 1 may occur. The error message 100 of FIG. 1 is an exception error message 100 of an overflow in which the number of methods exceeds 4K.

In order to solve the above exception error message, Google proposes three methods.

1. Reduce the number of methods by using a lightweight library or refactoring well.

2. Use the Proguard feature to get rid of unused code

3. Use the multidex function

The functions of the app are getting more complex and advanced compared to when DEX was designed. Therefore, the problem is avoided by using the multi-dex function of 3 times. Multidex supports multiple dex files, allowing more than 65535 methods to be referenced. When the code 200 of the multidex is added to the gradle file as shown in FIG. 2, methods over 4K are allowed.

In Android 5.0 or higher, in which ART (Android Runtime, Multidex is provided as the default runtime for devices running Android 5.0 API level 21 or higher) is reflected, Multidex can be used as shown in FIG. 2 . However, if it is an earlier version, for example, if minSdkVersion is less than 21, you must use the multidex support library provided by Google.

An application generated based on the Multidex is subjected to obfuscation to prevent reverse engineering, and an exception error may occur during execution of the application to which the obfuscation is applied. For example, exception errors such as Class Not Found Exception, ArrayIndexOutOfBoundsException, and NullPointException are generated.

The obfuscation is a method that makes reverse engineering inconvenient by forcibly changing method names and symbols to reduce readability. The reason for implementing obfuscation is to enhance security. Applications requiring security, such as financial apps and wallets, apply basic security elements, so processing such as obfuscation and forgery prevention is applied to the application.

In particular, when an obfuscated application is executed in Android 5.0 or lower version, the above exception error occurs and abnormal termination occurs. The causes are various, but mainly open source made in version 5.0 or lower (API level 21 or lower) is often caused. As such, libraries created under API level 21 or lower sometimes handle exceptions in obfuscation to maintain execution compatibility, but it is desirable to maintain obfuscation for security enhancement.

For reference, versions below Android 5.0 occupy 28.5% of the total Android version. It is a level of market share that cannot be ignored from the perspective of the service provider that provides the application. A technology that ensures compatibility of function execution while providing security-enhanced apps to 28.5% of users is required.

Korean Patent Registration 10-1139871 (2012.05.02)

The present invention is to solve the above problem, and provides an application in which an obfuscated multi-dex and non-obfuscated original dex are configuration-managed in an Android OS environment, and an exception generated in the multi-dex when the application is executed in a low-spec OS An object of the present invention is to provide an apparatus and method for executing a corresponding original dex by avoiding errors.

According to one aspect, an apparatus for executing an application based on shape management includes: a multi-dex unit in which a method obfuscated by execution of the application is executed; an original dex unit in which the shape is managed in correspondence with the method and the original method that is not obfuscated is executed; an exception detection unit detecting occurrence of an exception error in the method executed in the multi-dex unit; and a configuration management unit that receives the exception error information detected by the exception detection unit and calls execution of the original method corresponding to the method of the multidex unit in which the exception error occurred in order to avoid the detected exception error.

After the multidex function is defined, the application is created as a multidex file in which each dex included in the multidex is allocated to an array structure, and the original method is appended to the array.

The exception detection unit, after storing the exception error information generated by obfuscation, receives the exception error information from the multidex unit to detect the occurrence of an exception error, and the received exception error information is stored in the exception error information If match, the matched exception error information is output to the configuration management unit.

The shape management unit manages the shape by storing mapping information between the method of the multi-dex unit and the original method of the original dex unit.

The configuration management unit receives, from the exception detection unit, exception error information including an execution address of a method in which an exception error occurs, inquires the method information from the multidex unit with the execution address, and corresponds to the inquired method information The original method information is searched using the mapping information, and the searched original method information is transmitted to the original dex unit to call execution of the original method.

When the exception error information received from the exception detection unit is new information, the shape management unit transmits the exception error information to the server in order to collect the exception error.

The server further includes a runtime inheritance unit that receives the exception error information, updates a method for resolving the received exception error information to request runtime inheritance, and receives and updates the inherited method from the server.

According to another aspect, there is provided a method of executing an application based on shape management, the method comprising: executing an obfuscated method of multidex by the execution of the application; detecting exception error information generated during execution of the method; managing the execution of the original method corresponding to the method in which the exception error occurred in order to avoid the detected exception error; and executing the non-obfuscated original method by replacing the execution of the method in which the exception error occurred.

According to one aspect of the present invention, when an exception error due to obfuscation occurs during the execution of an application by configuration management of the non-obfuscated original dex, the original dex is replaced with the configuration-managed original dex without interruption of the execution of the program due to the exception error. This provides stable execution of the program.

The following drawings attached to the present specification illustrate preferred embodiments of the present invention, and together with the detailed description of the present invention serve to further understand the technical spirit of the present invention, the present invention is a matter described in such drawings should not be construed as being limited to
1 is an exemplary diagram of a conventional exception error message generated when the number of methods exceeds 4K.
2 is an exemplary diagram of code defining a conventional multidex in which more than 4K methods are allowed.
3 is a schematic illustration of an application execution apparatus according to the first embodiment of the present invention.
FIG. 4 is a schematic flowchart of signal processing of the application execution apparatus of FIG. 3 .
5 is a schematic illustration of an application execution apparatus according to a second embodiment of the present invention.
6 is a schematic flowchart of signal processing of the application execution apparatus of FIG. 5 .

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Prior to this, the terms or words used in the present specification and claims should not be construed as being limited to their ordinary or dictionary meanings, and the inventor should properly understand the concept of the term in order to best describe his invention. Based on the principle that it can be defined, it should be interpreted as meaning and concept consistent with the technical idea of the present invention. Accordingly, the configuration shown in the embodiments and drawings described in the present specification is only one of the most preferred embodiments of the present invention and does not represent all of the technical spirit of the present invention, so at the time of the present application, various It should be understood that there may be equivalents and variations.

3 is a schematic illustration of an application execution apparatus 300 according to the first embodiment of the present invention.

The application execution device 300 includes a multi-dex unit 301 , an original dex unit 303 , an exception detection unit 305 , and a shape management unit 307 . Assuming that the application execution device 300 is a computing terminal (smart terminal) composed of a recording medium, a memory, and a processor, each of the components 301 to 307 is stored in the recording medium in the form of an application, and loaded into the memory by execution and processed by the processor. For example, an Android-based smart phone executes an application composed of each of the components 301 to 307 as the application execution device 300 .

For reference, the field structure of the dex file corresponding to the application has header, array, class data, and link data. The file header is kept in the header field. In the array field, indexes for each type of index included in the multidex are stored. In the class data field, a method corresponding to the class data of the stored index is stored as an executable code (command). Link data pointing to each dex file in the link data field is stored. Then, since the array index of the array field corresponds to the index of each dex, an array field, a class data field, and a link data field exist for each dex. For example, assuming a multi-dex consisting of 3 dexes, header + array[0~2] + class data_0/link data_0 + class data_1/link data_1 + class data_2/link data It can be expressed in the structure of _2.

The multi-dex unit 301 stores the obfuscated method for each dex included in the multi-dex, and the obfuscated method is executed by the execution of the application. In the obfuscated method executed in the multidex unit 301, since the method name and symbol are obfuscated, the execution address of the method fails to be referenced, and an obfuscation error may occur. If a corresponding exception error message is output from the application due to the occurrence of an obfuscation error, the application is stopped by an execution error during execution (eg ANR: Application Not Responding).

The original dex unit 303 is appended as the last dex of the multidex, and stores methods that are not obfuscated.

The exception detection unit 305 detects the occurrence of an exception error by receiving the exception error information generated during execution in the multidex unit 301 . The received exception error information is the execution address of the method in which the exception error occurred. The exception detection unit 305 inquires the obfuscation error information using the received exception error information as a key, and when the inquiry is successful, determines that it can be solved through avoidance execution of executing the original dex. For example, if the received exception error information matches any one of Class Not Found Exception, ArrayIndexOutOfBoundsException, and NullPointException, the inquiry is successful. As the inquiry is successful, the exception detection unit 305 outputs exception error information to the configuration management unit 307 .

The shape management unit 307 stores the name of the obfuscated method and the name of the original method to be mapped. Due to obfuscation, since the method name of the multi-dex unit 301 may not be deciphered, it is required to store information by mapping it with the method name of the corresponding original dex unit 303 .

When the configuration management unit 307 receives the exception error information from the exception detection unit 305 and receives the avoidance request by the configuration management, the method name of the multidex unit 301 corresponding to the received exception error information is checked. The shape management unit 307 inquires the corresponding original method name from the mapping information using the checked method name as a key. Then, the shape management unit 307 may bypass the application by calling the inquired original method instead of the method of the multidex unit 301 in which an exception error occurs.

4 is a schematic flowchart of signal processing of the application execution device 300 of FIG. 3 .

The application execution device 300 executes the application, and the obfuscated method stored in the multidex unit 301 is executed by the execution (S401). When an exception error occurs during execution of the obfuscated method, the multidex unit 301 outputs the execution address of the obfuscated method in which the exception error occurs to the exception detection unit 305 (S403).

The exception detection unit 305 detects the occurrence of an exception error by receiving the exception error information from the multidex unit 301 (S411). The exception detection unit 305 inquires the previously stored exception error information using the received exception error information as a key. An evasion request is made (S413).

The shape management unit 307 receives the request for avoiding execution by receiving the exception error information from the exception detecting unit 305 ( S421 ). The shape management unit 307 outputs the received exception error information to the multidex unit 301 to request the method name in which the exception error occurred, and the multidex unit 301 in which the exception error occurs by receiving the requested method name. ) to check the method name (S423). The shape management unit 307 inquires the method name of the original dex unit 303 corresponding to the checked method name from the mapping information, and then transmits the inquired original method name to the original dex unit 303 to call the bypass execution. (S425).

Then, the original dex called by the original dex unit 303 is executed (S431). This is to dynamically avoid the exception error that stops the execution of the application due to an obfuscation error through configuration management so that the execution is maintained.

5 is a schematic illustration of an application execution apparatus 500 according to a second embodiment of the present invention.

The application execution device 500 according to the second embodiment of the present invention transmits a new error to the configuration management server 590, and inherits the updated method from the configuration management server 500 at runtime to solve the new error, and is an exception. Resolves the interruption of the execution of the application due to an error.

Here, the application execution apparatus 500 has a difference between the shape management unit 507 and the runtime inheritance unit 509 in the configuration of the application execution apparatus 300 according to the first embodiment of FIG. 3 .

The configuration management unit 507 determines whether the generated exception error is newly generated, and if it is the newly generated exception error, uploads the newly generated exception error information to the configuration management server 590 . The configuration management server 590 collects exception errors from the configuration management unit 507 and registers updated class information to resolve the collected exception errors. When update information of a class is registered, the configuration management server 590 requests runtime inheritance from the application execution device 500 . In runtime inheritance, an application is updated by receiving an updated version while the application is running.

The runtime inheritance unit 509 receives and updates class information updated by the runtime inheritance request of the configuration management server 590 .

6 is a schematic flowchart of signal processing of the application execution device 500 of FIG. 5 .

The shape management unit 507 receives the exception error information from the exception detection unit 305 and receives a circular request (S601). The configuration management unit 507 determines whether the received exception error information is newly generated information, and if it is the newly generated information, uploads the newly generated exception error information to the configuration management server 590 ( S603 ).

The configuration management server 590 collects newly generated exception error information from the configuration management unit 507 (S611). The configuration management server 590 registers update information of a class that resolves the collected exception error information, and requests runtime inheritance of the updated class to the application execution device 500 ( S613 ).

The runtime inheritance unit 509 receives the update information requested for runtime inheritance from the configuration management server 507, and updates it with the received information (S621). After the application execution device 500 completes the update process, when the new exception error received in step S601 occurs, execution continues without interruption of the application by the updated class information.

Although the present invention has been described with reference to limited embodiments and drawings, the present invention is not limited thereto, and the technical idea of the present invention and claims to be described below by those skilled in the art to which the present invention pertains Of course, various modifications and variations are possible within the equivalent range of the range.

300: application execution device 301: multi-dex unit
303: original dex unit 305: exception detection unit
307: configuration management unit

Claims (14)

In a device for executing an application based on configuration management,
a multi-dex unit in which the obfuscated method is executed by the execution of the application;
an original dex unit in which the shape is managed in correspondence with the method and the original method that is not obfuscated is executed;
an exception detection unit detecting occurrence of an exception error in the method executed in the multi-dex unit; and
In order to receive the exception error information detected by the exception detection unit, and to avoid the detected exception error, the method corresponding to the method of the multidex unit in which the exception error occurred by using the mapping information between the obfuscated method and the original method The configuration management unit that calls the execution of the original method
A device comprising a. The method of claim 1,
After the multidex function is defined, the application is created as a multidex file in which each dex included in the multidex is allocated to an array structure, and the original method is appended to the array device to do. The method of claim 1,
The exception detection unit,
After storing the exception error information caused by obfuscation,
Receive exception error information from the multidex unit to detect the occurrence of an exception error, and output the matched exception error information to the configuration management unit when the received exception error information matches the stored exception error information device to do. The method of claim 1,
The shape management unit,
Apparatus, characterized in that by storing mapping information between the method of the multi-dex unit and the original method of the original dex unit, shape management. 5. The method of claim 4,
The shape management unit,
Receive exception error information including the execution address of the method in which the exception error occurred from the exception detection unit,
Method information is inquired from the multi-dex unit with the execution address, original method information corresponding to the inquired method information is retrieved using the mapping information, and the inquired original method information is transmitted to the original dex unit to the original method Device characterized in that invoking the execution of. The method of claim 1,
The shape management unit,
When the exception error information received from the exception detection unit is new information, the apparatus for transmitting the exception error information to the server to collect the exception error. 7. The method of claim 6,
The server receives the exception error information, and updates a method for resolving the received exception error information to request runtime inheritance,
The apparatus of claim 1, further comprising a runtime inheritance unit for receiving and updating the method for which inheritance is requested from the server. In the execution method of a device that executes an application based on configuration management,
executing the obfuscated method of the multidex by the execution of the application;
an exception error occurs during execution of the obfuscated method, and detecting the generated exception error information;
In order to avoid the detected exception error, by using the mapping information between the obfuscated method and the non-obfuscated original method, the execution of the original method corresponding to the obfuscated method in which the exception error occurred is called to manage the configuration to do; and
executing the original method by replacing the execution of the method in which the exception error occurred
How to include. 9. The method of claim 8,
After the multidex function is defined, the application is created as a multidex file in which each dex included in the multidex is allocated to an array structure, and the original method is appended to the array How to. 9. The method of claim 8,
The detecting step is
After storing the exception error information caused by obfuscation,
receiving the generated exception error information, detecting the occurrence of an exception error, and requesting execution of avoidance of the matched exception error when the received exception error information matches the stored exception error information . 9. The method of claim 8,
Before the step of managing the shape,
The method further comprising the step of storing mapping information between the obfuscated method and the non-obfuscated original method 12. The method of claim 11,
The shape management step is,
Receive exception error information including the execution address of the method in which the exception error occurred, inquire the obfuscated method information with the execution address, and use the mapping information for original method information corresponding to the inquired method information and invoking the execution by transmitting the inquired original method information. 9. The method of claim 8,
The shape management step is,
When the detected exception error information is new information, the method further comprising the step of transmitting the exception error information to a server to collect the exception error. 14. The method of claim 13,
The server receives the exception error information, and updates a method for resolving the received exception error information to request runtime inheritance,
The shape management step is,
Method characterized in that it further comprises the step of updating the method for which runtime inheritance is requested, received from the server.

Images