WO2020177429A1

WO2020177429A1 - Method and apparatus for embedding codes in application, and electronic device

Info

Publication number: WO2020177429A1
Application number: PCT/CN2019/123871
Authority: WO
Inventors: 汪德嘉; 邵根波; 钱潇龄; 孟啸龙
Original assignee: 江苏通付盾信息安全技术有限公司
Priority date: 2019-03-07
Filing date: 2019-12-09
Publication date: 2020-09-10
Also published as: ZA202100858B; CN109933350A; CN109933350B

Abstract

Disclosed are a method and apparatus for embedding codes in an application, and an electronic device. The method comprises: integrating an SDK into an application, and according to a pre-set loading sequence, embedding loading information of the SDK in a dynamic library information list of an executable file of the application; according to file information of the SDK, modifying offset information and length information of dynamic library loading information included in the executable file; modifying loading serial number information, of an original dynamic library, included in the executable file, and offset address information, in the executable file, of a code corresponding to the original dynamic library, and modifying serial number information of position information, of the original dynamic library, in a code segment; and generating an updated application file according to the modified executable file. The method can embed, without a source code, the SDK for any application according to a specified loading sequence, such that when the application to which the SDK is added runs, SDK codes can be dynamically called according to the specified loading sequence, and the compatibility thereof is higher.

Description

Method, device and electronic equipment for embedding code in application

Technical field

The present invention relates to the technical field of code integration, in particular to a method, device and electronic equipment for embedding codes in applications.

Background technique

SDK (Software Development Kit, software development kit) usually refers to a collection of development tools used by software engineers to build application software for a specific software package, software framework, hardware platform, or operating system. When developing an application, a technician can connect the SDK to the application and directly use the functions provided by the SDK. Therefore, embedding the SDK in the application helps to enrich the functions of the application and meet the various needs of users.

The prior art (CN 107463359A) discloses a convenient method for embedding code in the iOS ipa package. Specifically: (1) Adding the hook script of the SDK: Add the hook script to the project code in the iOS project source code. The packaging tool generates the ipa (iPhone Application) release package; (2) Implant code: decompress the ipa package, compile the code that needs to be imported into a dynamic library, and add it to the Framework directory; (3) Resign and repackage it into New ipa; (4) Dynamic call, when the new ipa package is running, it dynamically connects with the dynamic library through the hook script to call the function of the embedded code. This method can reduce the workload of SDK access.

However, in the process of implementing the present invention, the inventor found that the prior art lacks a way to embed the SDK according to the specified loading sequence, so that the application embedded with the SDK can dynamically call the SDK code according to the specified loading sequence at runtime. Program.

Summary of the invention

In view of the above problems, the present invention is proposed to provide a method, device and electronic device for embedding codes in applications that overcome the above problems or at least partially solve the above problems.

According to one aspect of the present invention, there is provided a method for embedding code in an application, including:

Integrate the SDK into the application, and embed the SDK loading information in the dynamic library information list of the executable file of the application according to the preset loading sequence;

According to the SDK file information, modify the offset information and length information of the dynamic library loading information contained in the executable file;

Modify the loading sequence number information of the original dynamic library contained in the executable file and the offset address information of the code corresponding to the original dynamic library in the executable file, and modify the sequence number information of the location information of the original dynamic library in the code segment;

Generate an update application file based on the modified executable file.

Optionally, the file information of the SDK specifically includes at least one of the following: dynamic library name information, file storage path information, file size information, and structure information; the dynamic library loading information specifically includes at least one of the following: redirection information, static Binding information.

Optionally, modifying the sequence number information of the location information of the original dynamic library in the code segment specifically includes:

Calculate symbol pointer information according to the paragraph number information and offset information of the dynamic library, and determine the starting position information of the original dynamic library and call code position information according to the symbol pointer information;

Modify the starting position information of the original dynamic library and the serial number information of the calling code position information.

Optionally, the loading information of the SDK specifically includes at least one of the following: file path information and name information.

Optionally, the method further includes:

Perform re-signature authentication processing on the updated application file.

Optionally, if the method is applied to IOS applications, before the method is executed, it further includes:

Decompress the program application file of the IOS application and extract the executable file of the IOS application;

The method further includes: performing re-signature authentication processing on the updated application file.

According to another aspect of the present invention, there is provided a device for embedding code in an application, including:

The integration module is suitable for integrating the SDK into the application, and embeds the loading information of the SDK in the dynamic library information list of the executable file of the application according to the preset loading sequence;

The first modification module is adapted to modify the offset information and length information of the dynamic library loading information contained in the executable file according to the file information of the SDK;

The second modification module is suitable for modifying the loading sequence number information of the original dynamic library contained in the executable file and the offset address information of the code corresponding to the original dynamic library in the executable file, as well as the position of the original dynamic library in the code segment The serial number of the information is modified;

The application file generating module is suitable for generating an updated application file according to the modified executable file.

Optionally, the second modification module is further adapted to:

Optionally, wherein, the device further includes:

The extraction module is suitable for decompressing program application files of IOS applications and extracting executable files of IOS applications;

The re-signature module is suitable for performing re-signature authentication processing on the updated application file.

According to another aspect of the present invention, there is provided an electronic device, including: a processor, a memory, a communication interface, and a communication bus. The processor, the memory, and the communication interface complete mutual communication through the communication bus. Communication

The memory is used to store at least one executable instruction, and the executable instruction causes the processor to perform the operation corresponding to the method of embedding code in the application.

According to another aspect of the present invention, a computer storage medium is provided, the storage medium stores at least one executable instruction, and the executable instruction causes a processor to perform operations corresponding to the above method of embedding code in an application. .

The method, device and electronic device for embedding code in an application according to the present invention include: integrating the SDK into the application, and embedding the loading information of the SDK in the dynamic library information list of the executable file of the application according to a preset loading sequence ; According to the file information of the SDK, modify the offset information and length information of the dynamic library loading information contained in the executable file; modify the loading sequence number information of the original dynamic library contained in the executable file and the code corresponding to the original dynamic library. The offset address information in the executable file is modified, and the serial number information of the original dynamic library location information in the code segment is modified; the updated application file is generated according to the modified executable file. This method can separate the source code and embed the SDK according to the specified loading sequence for any application, so that the newly added SDK can dynamically call the SDK code according to the specified loading sequence at runtime, which has higher compatibility.

The above description is only an overview of the technical solution of the present invention. In order to understand the technical means of the present invention more clearly, it can be implemented in accordance with the content of the description, and in order to make the above and other objectives, features and advantages of the present invention more obvious and understandable. In the following, specific embodiments of the present invention are specifically cited.

Description of the drawings

By reading the detailed description of the preferred embodiments below, various other advantages and benefits will become clear to those of ordinary skill in the art. The drawings are only used for the purpose of illustrating the preferred embodiments, and are not considered as a limitation to the present invention. Also, throughout the drawings, the same reference symbols are used to denote the same components. In the attached picture:

Fig. 1 shows a schematic flowchart of a method for embedding code in an application according to an embodiment of the present invention;

FIG. 2 shows a schematic flowchart of a method for embedding code in an application according to another embodiment of the present invention;

Figure 3 shows a schematic structural diagram of an apparatus for embedding codes in an application according to another embodiment of the present invention;

Fig. 4 shows a schematic structural diagram of an electronic device according to an embodiment of the present invention.

detailed description

Hereinafter, exemplary embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

Fig. 1 shows a schematic flow chart of a method for embedding code in an application according to an embodiment of the present invention. As shown in Fig. 1, the method includes:

In step S101, the SDK is integrated into the application, and the loading information of the SDK is embedded in the dynamic library information list of the executable file of the application according to the preset loading sequence.

Integrate the SDK into the application, find the dynamic library information list in the loading command of the application executable file, and insert the SDK loading information in the dynamic library information list according to the preset loading sequence, such as the file path and name of the SDK, etc. . Among them, the preset loading sequence is the running sequence of the embedded code. For example, the embedded code can be run first or in other specified sequences. Those skilled in the art can set the preset loading sequence according to actual needs.

Step S102: Modify the offset information and length information of the dynamic library loading information contained in the executable file according to the file information of the SDK.

First, read the dynamic library loading information in the executable file, such as redirection information, static binding information, etc.; then, according to the embedded SDK file information, such as the dynamic library name, file storage path, file size information, and structure Information, etc., modify the offset and length of the dynamic library loading information.

Step S103: Modify the loading sequence number information of the original dynamic library contained in the executable file and the offset address information of the code corresponding to the original dynamic library in the executable file, and modify the sequence number information of the location information of the original dynamic library in the code segment to modify.

Due to the newly added SDK, it is necessary to modify the dynamic library binding information in the executable file, specifically modify the loading sequence number information of the original dynamic library and the offset address information of the code corresponding to the original dynamic library in the file. At the same time, it is also necessary to modify the serial number of the original dynamic library location information in the code segment.

Step S104: Generate an update application file according to the modified executable file.

Use the modified executable file to replace the original executable file, and repackage the modified executable file to generate an updated application file. In the subsequent process, when starting the update application, according to the modified dynamic library information list, the newly added SDK will implant the code according to the aforementioned preset loading sequence.

According to the embedding code in the application provided by this embodiment, the SDK is first integrated into the application, and the loading information of the SDK is embedded in the dynamic library information list of the executable file of the application according to the preset loading sequence; then, according to the SDK file Information, modify the offset information and length information of the dynamic library loading information contained in the executable file; secondly, modify the loading sequence number information of the original dynamic library contained in the executable file and the code corresponding to the original dynamic library in the executable file Modify the offset address information of the code segment, and modify the serial number information of the original dynamic library location information in the code segment; finally, generate an updated application file based on the modified executable file. This method can separate the source code and embed the SDK according to the specified loading sequence for any application, so that the newly added SDK can dynamically call the SDK code according to the specified loading sequence during runtime, which has higher compatibility.

Fig. 2 shows a schematic flow chart of a method for embedding code in an application according to another embodiment of the present invention. In this embodiment, an IOS application is taken as an example for description. As shown in Fig. 2, the method includes:

Step S201: Decompress the program application file of the IOS application, extract the executable file of the IOS application, and integrate the SDK into the application.

Decompress the ipa installation package of the IOS application, extract the Mach-o file (executable file), and integrate the SDK into the application.

Step S202: Embed the SDK loading information in the dynamic library information list of the executable file of the application according to the preset loading sequence.

It is important to point out that after the existing technology inserts the SDK into the system library, due to the priority loading of the system library and the added third-party library of the application itself, some functions of the newly added SDK may not be loaded normally and cause a crash. . Therefore, the prior art lacks a technical solution that can preferentially load the newly added SDK. The method provided in this embodiment enables the newly added SDK to be loaded in an arbitrary loading sequence. When the preset loading sequence is specifically the first loading sequence (that is, the first loading), the above-mentioned system library and the application itself can be solved. Errors and crashes caused by priority loading of the added third-party libraries.

Specifically, the list of dynamic library information is searched in the load command of the executable file, and the SDK loading information is inserted in the list of dynamic library information according to the preset loading sequence, where the SDK loading information includes at least one of the following: File path information, name information.

Step S203: Modify the offset information and length information of the dynamic library loading information contained in the executable file according to the file information of the SDK.

Read the dynamic library loading information in the executable file, and then modify the offset information and length information of the dynamic loading information according to the SDK file information, where the dynamic library loading information specifically includes at least one of the following: redirection information , Static binding information. The file information of the SDK specifically includes at least one of the following: dynamic library name information, file storage path information, file size information, and structure information.

Take the addition of PayegisSharkIV.framework as an example, where the offset length added in the load command can be calculated as 96 through the file path "@executable_path/Frameworks/PayegisSharkIV.framework/PayegisSharkIV", which is calculated by traversing the redirection information and the static binding information table The OPCODE and IMMEDIATE values can be increased to 0 for the redirection information table, 6 for the static binding information table, and 16 for the added length after adding 0 bits.

Step S204: Modify the loading sequence number information of the original dynamic library contained in the executable file and the offset address information of the code corresponding to the original dynamic library in the executable file.

Traverse the dynamic library binding information in the executable file. Due to the newly added SDK, it is necessary to modify the loading sequence number of the original dynamic library and the offset address of the code corresponding to the original dynamic library in the executable file.

Take the default loading sequence as the first loading sequence as an example. Simply put, there are 10 original dynamic libraries, with serial numbers 1, 2, 3...10. Add the SDK corresponding dynamic library before all the original dynamic libraries, then The serial number of the newly added dynamic library is 1, and the serial number of the original dynamic library is sequentially modified to 2, 3, 4...11. At the same time, the offset address of the code corresponding to the original dynamic library in the executable file needs to be modified.

Step S205: Calculate symbol pointer information according to the paragraph number information and offset information of the dynamic library, determine the starting position information and calling code position information of the original dynamic library according to the symbol pointer information; check the starting position information and calling code of the original dynamic library The serial number information of the location information is modified.

According to the symbol pointer information calculated from the paragraph number information and offset information of the dynamic library, the starting position information of the original dynamic library and the calling code position information under the code segment can be obtained, and then the starting position information and the calling code of the original dynamic library can be obtained. The serial number of the location information is modified.

Step S206: Generate an updated application file according to the modified executable file, and perform re-signature authentication processing on the updated application file.

The modified executable file is replaced with the original executable file, and the modified executable file is repackaged to generate an updated application file, and the resignature tool is used for resignature authentication. In the subsequent process, when the update application is started, the added SDK will adjust the embedded code according to the preset loading order according to the list of modified dynamic library information.

It can be seen that the method of this embodiment can be summarized into the following processing stages: (1) Decompression and extraction stage. (2) Executable file modification processing stage, specifically modifying the loading information and binding information of the executable file. (3) In the repackaging stage, the modified executable file is used to replace the original executable file to generate a new application file, and the new application file is resigned to form a new ipa package.

It can be seen that the method according to this embodiment can break away from the source code, and embed the SDK in a specified loading sequence for any application, such as security components (signature verification, secondary packaging detection, jailbreak detection, anti-injection, etc.), dynamic rent monitoring , Debugging module, etc., so that the SDK code can be called according to the specified loading sequence when the application is running, and the application scenarios are wide. When referring to the preset loading sequence as the first loading sequence, it can also solve the problem that after the existing SDK is inserted into the system library, because other library information is loaded first, the newly added SDK has errors or even crashes, and the compatibility is better. .

Fig. 3 shows a schematic structural diagram of a device for embedding code in an application according to another embodiment of the present invention. As shown in Fig. 3, the device includes: an integration module, a first modification module, a second modification module, and application file generation Module.

Wherein, the integration module 31 is suitable for integrating the SDK into the application, and embeds the loading information of the SDK in the dynamic library information list of the executable file of the application according to a preset loading sequence;

The first modification module 32 is adapted to modify the offset information and length information of the dynamic library loading information contained in the executable file according to the file information of the SDK;

The second modification module 33 is adapted to modify the loading sequence number information of the original dynamic library contained in the executable file and the offset address information of the code corresponding to the original dynamic library in the executable file, and modify the original dynamic library in the code segment. Modify the serial number information of the location information;

The application file generating module 34 is adapted to generate an updated application file according to the modified executable file.

In an optional manner, the file information of the SDK specifically includes at least one of the following: dynamic library name information, file storage path information, file size information, and structure information; the dynamic library loading information specifically includes at least one of the following: Redirection information, static binding information.

In an optional manner, the second modification module 32 is further adapted to:

In an optional manner, the loading information of the SDK specifically includes at least one of the following: file path information and name information.

In an optional manner, the above device for embedding code in an application further includes:

For the specific structure and working principle of each of the above modules, please refer to the description of the corresponding steps in the method embodiment, which will not be repeated here.

The embodiment of the present application provides a non-volatile computer storage medium, the computer storage medium stores at least one executable instruction, and the computer executable instruction can execute the method of embedding code in the application in any of the foregoing method embodiments .

FIG. 4 shows a schematic structural diagram of an electronic device according to an embodiment of the present invention, and the specific embodiment of the present invention does not limit the specific implementation of the electronic device.

As shown in FIG. 4, the electronic device may include: a processor (processor) 402, a communication interface (Communications Interface) 404, a memory (memory) 406, and a communication bus 408.

among them:

The processor 402, the communication interface 404, and the memory 406 communicate with each other through the communication bus 408.

The communication interface 404 is used to communicate with network elements of other devices, such as clients or other servers.

The processor 402 is configured to execute the program 410, and specifically can execute relevant steps in the above-mentioned method for embedding code in an application.

Specifically, the program 410 may include program code, and the program code includes computer operation instructions.

The processor 402 may be a central processing unit CPU, or an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present invention. The one or more processors included in the electronic device may be the same type of processor, such as one or more CPUs, or different types of processors, such as one or more CPUs and one or more ASICs.

The memory 406 is used to store the program 410. The memory 406 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

The program 410 may be specifically used to make the processor 402 execute the method of embedding code in an application in any of the foregoing method embodiments. For the specific implementation of each step in the program 410, reference may be made to the corresponding description in the corresponding steps and units in the above-mentioned method of embedding code in the application, which is not repeated here.

The algorithms and displays provided here are not inherently related to any particular computer, virtual system or other equipment. Various general-purpose systems can also be used with the teaching based on this. From the above description, the structure required to construct this type of system is obvious. In addition, the present invention is not directed to any specific programming language. It should be understood that various programming languages can be used to implement the content of the present invention described herein, and the above description of a specific language is to disclose the best embodiment of the present invention.

In the instructions provided here, a lot of specific details are explained. However, it can be understood that the embodiments of the present invention can be practiced without these specific details. In some instances, well-known methods, structures and technologies are not shown in detail, so as not to obscure the understanding of this specification.

Similarly, it should be understood that in order to simplify the present disclosure and help understand one or more of the various inventive aspects, in the above description of the exemplary embodiments of the present invention, the various features of the present invention are sometimes grouped together into a single embodiment, Figure, or its description. However, the disclosed method should not be interpreted as reflecting the intention that the claimed invention requires more features than those explicitly stated in each claim. More precisely, as reflected in the following claims, the inventive aspect lies in less than all the features of a single embodiment disclosed previously. Therefore, the claims following the specific embodiment are thus explicitly incorporated into the specific embodiment, wherein each claim itself serves as a separate embodiment of the present invention.

Those skilled in the art can understand that it is possible to adaptively change the modules in the device in the embodiment and set them in one or more devices different from the embodiment. The modules or units or components in the embodiments can be combined into one module or unit or component, and in addition, they can be divided into multiple sub-modules or sub-units or sub-components. Except that at least some of such features and/or processes or units are mutually exclusive, any combination can be used to compare all features disclosed in this specification (including the accompanying claims, abstract and drawings) and any method or methods disclosed in this manner or All the processes or units of the equipment are combined. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.

In addition, those skilled in the art can understand that although some embodiments described herein include certain features included in other embodiments but not other features, the combination of features of different embodiments means that they are within the scope of the present invention. Within and form different embodiments. For example, in the following claims, any one of the claimed embodiments can be used in any combination.

The various component embodiments of the present invention may be implemented by hardware, or by software modules running on one or more processors, or by their combination. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in the electronic device according to the embodiments of the present invention. The present invention can also be implemented as a device or device program (for example, a computer program and a computer program product) for executing part or all of the methods described herein. Such a program for realizing the present invention may be stored on a computer-readable medium, or may have the form of one or more signals. Such signals can be downloaded from Internet websites, or provided on carrier signals, or provided in any other form.

It should be noted that the above-mentioned embodiments illustrate the present invention rather than limit the present invention, and those skilled in the art can design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be constructed as a limitation to the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of multiple such elements. The invention can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. do not indicate any order. These words can be interpreted as names.

Claims

A method of embedding code in an application, including:

Integrating the SDK into the application, and embedding the loading information of the SDK in the dynamic library information list of the executable file of the application according to a preset loading sequence;

Modify the offset information and length information of the dynamic library loading information contained in the executable file according to the file information of the SDK;

Modify the loading sequence number information of the original dynamic library contained in the executable file and the offset address information of the code corresponding to the original dynamic library in the executable file, and modify the original dynamic library information in the code segment Modify the serial number information of the location information;

Generate an update application file based on the modified executable file.
The method according to claim 1, wherein the file information of the SDK specifically includes at least one of the following: dynamic library name information, file storage path information, file size information, and structure information; the dynamic library loading information specifically includes At least one of the following: redirection information, static binding information.
The method according to claim 1, wherein said modifying the sequence number information of the location information of the original dynamic library in the code segment specifically comprises:

Calculate symbol pointer information according to the paragraph number information and offset information of the dynamic library, and determine the starting position information of the original dynamic library and the calling code position information according to the symbol pointer information;

Modify the starting position information of the original dynamic library and the sequence number information of the calling code position information.
The method according to claim 1, wherein the loading information of the SDK specifically includes at least one of the following: file path information and name information.
The method according to any one of claims 1 to 4, wherein the method is applied to an IOS application, before the method is executed, further comprising:

The program application file of the IOS application is decompressed, and the executable file of the IOS application is extracted; the method further includes: performing re-signature authentication processing on the updated application file.
A device for embedding code in an application, including:

The integration module is adapted to integrate the SDK into the application, and embed the SDK loading information in the dynamic library information list of the executable file of the application according to a preset loading sequence;

The first modification module is adapted to modify the offset information and length information of the dynamic library loading information contained in the executable file according to the file information of the SDK;

The second modification module is adapted to modify the loading sequence number information of the original dynamic library contained in the executable file and the offset address information of the code corresponding to the original dynamic library in the executable file, and modify the code segment Modify the serial number information of the location information of the original dynamic library;

The application file generating module is suitable for generating an updated application file according to the modified executable file.
The device according to claim 6, wherein the file information of the SDK specifically includes at least one of the following: dynamic library name information, file storage path information, file size information, and structure information; the dynamic library loading information specifically includes At least one of the following: redirection information, static binding information.
The device according to claim 6, wherein the second modification module is further adapted to:

Calculate symbol pointer information according to the paragraph number information and offset information of the dynamic library, and determine the starting position information of the original dynamic library and the calling code position information according to the symbol pointer information;

Modify the starting position information of the original dynamic library and the sequence number information of the calling code position information.
The device according to claim 6, wherein the loading information of the SDK specifically includes at least one of the following: file path information and name information.
The device according to any one of claims 6-9, wherein the device further comprises:

The extraction module is adapted to decompress the program application file of the IOS application and extract the executable file of the IOS application;

The re-signature module is adapted to perform re-signature authentication processing on the updated application file.
An electronic device, comprising: a processor, a memory, a communication interface, and a communication bus. The processor, the memory, and the communication interface communicate with each other through the communication bus;

The memory is used to store at least one executable instruction, and the executable instruction causes the processor to perform an operation corresponding to the method for embedding code in an application according to any one of claims 1-5.
A computer storage medium, wherein at least one executable instruction is stored in the storage medium, and the executable instruction causes a processor to execute the method for embedding code in an application according to any one of claims 1-5. operating.