WO2018165951A1 - Method and device for signature authentication during android apk startup - Google Patents

Abstract

Disclosed are a method and device for signature authentication during Android APK startup, the method comprising: obtaining a signature SGN file converted from an original APK installation file, and loading an OAT signature file of an installed APK; determining whether the OAT signature file is consistent with the signature SGN file; if yes, loading the APK, and if no, prohibiting APK startup. The OAT signature file is authenticated during APK startup, in order to determine whether the APK can be used.

Description

 Method and device for signing authentication when Android APK starts

 [0001] The present invention relates to the field of Android APK security authentication, and in particular, to a method and device for launching a signature authentication of an Android APK.

 Background technique

 [0002] The original Android system will check the signature when the APK is installed. The signature is different. If there is no signature or the signature is not passed, it cannot be installed or overwritten.

[0003] Google added a new ART (Android Run Time) to android4.4 to replace the previous Dalvik

, ART uses the OAT format file (OAT format file), installs the installer in the APK application, optimizes the APK installation package to the local machine code through the executable code de oat, that is, the installed file and the original file have very The big difference, we need to know the installed local machine code file by some means, after signing the local machine code file, can start the authentication of the local machine code file after starting the apk.

 [0004] The original APK is only installed after verifying the signature file in the META-INF directory inside the original APK file, but it will not be verified after startup. Android will no longer verify the APK when the APK is launched, which may result in the possibility of tampering with the successfully installed APK, which is a security risk.

[0005] Therefore, it is necessary to design an Android APK startup signature authentication method, start the APK that has been successfully installed, authenticate the signature, and ensure that the APK is not arbitrarily falsified. Once the APK is tampered with, A PK starts. You can find out that the user has been tampered with, has been tampering, can't run, and reduces security risks.

 technical problem

 [0006] The object of the present invention is to provide a method and device for launching an Android APK to initiate signature verification, and to perform signature verification when the APK is launched, to avoid using an APK that has been maliciously tampered with after installation.

 Problem solution

 Technical solution

[0007] In order to achieve the above object, the present invention adopts the following technical solutions: An Android APK launches 吋 signature authentication Method, the method includes:

 [0008] acquiring a signature SGN file converted from the original APK installation file, and loading the OAT signature file converted by the executable code of the installed APK;

[0009] determining whether the OAT signature file is consistent with the signature SGN file;

[0010] If yes, the APK is loaded, otherwise, the APK is disabled.

 [0011] Further, the method for converting the original APK installation file into a signature SGN file includes,

[0012] converting the original APK installation file into an OAT format file;

 [0013] The oatdata and oatexec segments in the OAT format file are calculated by the HASH256+RSA2048 algorithm to obtain a signature SGN file.

 [0014] Further, after calculating the oatdat a and oatexec segments in the 0AT format file by using the HASH256+RSA2048 algorithm, after obtaining the signature SGN file step, the method further includes

[0015] placing the signature SGN file into the original APK package file directory META-INF;

[0016] Repacking the APK file and installing the new APK file into the Android system.

[0017] Further, the step of loading and loading the executable code converted by the installed APK into the 0AT signature file includes,

 [0018] loading the 0AT signature file into the memory of the Android ART virtual machine.

 [0019] Further, the step of determining whether the 0AT signature file is consistent with the signature SGN file includes

[0020] determining whether the signature SGN file under the META-INF corresponding to the APK has been tampered with,

[0021] If yes, the activation of the APK is prohibited, otherwise the H ASH 256 values of the Oatdata and oatexec segments of the OAT signature file are calculated;

 [0022] determining whether the HASH256 value of the 0AT signature file is consistent with the HASH256 value saved in the signature SGN file under META-INF,

[0023] If they are consistent, the signature verification is successful, and the APK is loaded.

[0024] If they are inconsistent, it is forbidden to start the APK.

[0025]

 [0026] The present invention also provides an apparatus for launching 吋 signature authentication of an Android APK, including:

[0027] a signature file obtaining unit, configured to acquire a signature SGN file converted from an original APK installation file And loading the OAT signature file converted from the executable code of the installed APK;

[0028] The change determining unit is configured to determine whether the OAT signature file is consistent with the signature SGN file, and if so, load the APK, otherwise, prohibiting the launch of the APK.

[0029] Further, a conversion unit is further included, configured to convert the original APK installation file into an OAT format file.

And, calculating the oatdata and oatexec segments in the OAT format file by using the HASH256+RSA2048 algorithm to obtain a signature SGN file.

[0030] Further, a recovery unit and a packaging unit are further included.

 [0031] the restoring unit is configured to put the signature SGN file into the original APK package file directory META-INF;

 [0032] the packaging unit is configured to repackage the APK file, and install a new APK file into the Android system.

 [0033] Further, the signature file obtaining unit includes a loading module, and the loading module is configured to load the 0AT signature file into a memory of the Android ART virtual machine.

[0034] Further, the change determination unit includes a file tampering determination module and a numerical value determination module;

[0035] the file tampering determination module is configured to determine whether the signature SGN file under the META-INF corresponding to the APK has been tampered with, and if the tampering has been performed, the APK fails to be started, otherwise, the Oatdata of the 0AT signature file is calculated. The HASH256 value of the oatexec segment;

[0036] The value judging module is configured to determine whether the HASH256 value of the 0AT signature file is consistent with the HASH256 value stored in the signature SGN file under META-INF, and if the signature is consistent, the signature verification succeeds.

, load the APK, or, if not, disable the launch of the APK.

 Advantageous effects of the invention

 Beneficial effect

[0037] The beneficial effects of the present invention compared with the prior art are: The method and device for launching the 吋 signature authentication of the Android APK of the present invention, by acquiring the 0AT signature file and the signature SGN file, starting 吋, performing signature verification on the 0AT signature file Therefore, according to whether the 0AT signature file is changed, the behavior of the APK is restricted, and the APK that has been successfully installed is activated, the signature is authenticated, and the APK is not arbitrarily falsified. Once the APK is tampered with, the APK can be started. And found that the user has been tampered with and the slogan has not been run, reducing the security risks. Brief description of the drawing

 DRAWINGS

 1 is a block diagram of a method for triggering signature authentication of an Android APK according to an embodiment of the present invention; [0039] FIG. 2 is a block diagram showing a specific process for determining whether an OAT signature file is changed according to an embodiment of the present invention; 3 is a structural block diagram of an OAT format file according to an embodiment of the present invention;

[0041] FIG. 4 is a structural block diagram of an apparatus for initiating 吋 signature authentication of an Android APK according to an embodiment of the present invention; [0042] FIG. 5 is a structural block diagram of a change judging unit according to an embodiment of the present invention.

[0043]

The implementation, functional features, and advantages of the present invention will be further described with reference to the accompanying drawings.

 BEST MODE FOR CARRYING OUT THE INVENTION

 BEST MODE FOR CARRYING OUT THE INVENTION

 The specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

 [0046] It should be noted that all directional indications (such as up, down, left, right, front, back, ...) in the embodiments of the present invention are only used to explain in a certain posture. The relative positional relationship between the various components, the motion situation, and the like, if the specific posture changes, the directional indication also changes accordingly.

 In addition, the descriptions of "first", "second" and the like in the present invention are for the purpose of description only, and are not to be understood as indicating or implying their relative importance or implicitly indicating the number of indicated technical features. . Thus, features defining "first" and "second" may include at least one of the features, either explicitly or implicitly. In addition, the technical solutions between the various embodiments may be combined with each other, but must be based on the realization of those skilled in the art, and when the combination of the technical solutions is contradictory or impossible to implement, it should be considered that the combination of the technical solutions does not exist. It is also within the scope of protection required by the present invention.

[0048] The singular forms "a", "an", "the" It will be further understood that the phrase "comprising", used in the <RTI ID=0.0></RTI><RTIgt;</RTI><RTIgt;</RTI><RTIgt;</RTI> is intended to mean the presence of the features, integers, steps, operations, components and/or components, but does not exclude the presence or addition of one or more other features, Integers, steps, operations, components, components, and/or their groups. The phrase "and/or" used herein includes all or any of the elements and all combinations of one or more of the associated listed. [0049] Those skilled in the art will appreciate that all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the invention belongs, unless otherwise defined. It should also be understood that terms such as those defined in a general dictionary should be understood to have meaning consistent with the meaning in the context of the prior art, and will not be idealized or excessive unless specifically defined as here. The formal meaning is explained.

 [0050]

 [0051] Referring to FIG. 1 to FIG. 3, the method for launching the signature authentication of the Android APK provided by the embodiment, the method includes:

 [0052] Sl, converting the original APK installation file into an OAT format file.

 [0053] S2: Calculate the oatdata and oatexec segments in the OAT format file by using a HASH256+RSA2048 algorithm to obtain a signature SGN file.

[0054] S3. Put the signed SGN file into the original APK package file directory META-INF.

[0055] S4. Repackage the APK file and install the new APK file into the Android system.

[0056] S5. After the APK is launched, the signature SGN file converted from the original APK installation file is obtained, and the OAT signature file converted by the executable code of the installed APK is loaded.

[0057] S6. Determine whether the OAT signature file is consistent with the signature SGN file. If not, S7 prohibits starting the APK; if yes, S8, loading the APK.

[0058] For the SI step described above, the original APK format is mainly converted into the installed 0AT format file by using a homemade computer tool.

 [0059] For the S2 step, the signature SGN file is obtained, specifically, the signature SGN of the oatdata and oatexec segments in the OAT format file is calculated by the HASH256+RSA2048 algorithm as the signature SGN file.

[0060] As shown in FIG. 3, Google's original signature scheme will sign all the files and put the signature in the META-INF directory. After the Android APK is successfully installed, the executable code will be converted into a 0AT signature file, 0AT signature file. It is in 0AT format. Since the 0AT format file is essentially an ELF file, it has the structure of a general ELF file in the outermost layer. For example, it has a standard ELF file header and describes the file contents through Sections. A private ELF file, the 0AT format file contains two special segments, oatdata and oatexec. The former contains the contents of the dex file used to generate the local machine instructions. The latter contains the generated local machine instructions. The relationship between them is passed. Oat header stored in front of the oatdata segment Said. In addition, in the dynamic section of the OAT format file, three symbols oatdata, oatexec, and oatl astword are exported, and their values are used to define the start and end positions of the oatdata segment and the oatexec segment, where [oatdat a, oatexec-l] describes It is the starting and ending position of the oatdata segment, and [oatexec, oatlastword+3] describes the starting and ending position of oat exec.

 [0061] Therefore, the local machine command after the APK is installed according to the OAT format file can be used to convert the APK installation file into an OAT format file on the computer using the self-made computer tool, using the private key pair.

 OAT performs HASH256+RSA2048 signature, obtains the signed SGN file, puts the signed SGN file into the META-INF directory, and then repackages the APK, so that the OAT file signature can be authenticated at startup.

 [0062] For the above step S5, the APK starts, and the step of loading the OAT signature file is specifically loading the OAT signature file into the memory of the Android ART virtual machine.

[0063] Further, step S6 specifically includes the following steps:

 [0064] S61. Determine whether the signature SGN file under the META-INF corresponding to the APK has been tampered with, and if it has been tampered with, S7, prohibiting the activation of the APK;

[0065] Alternatively, if not tampering, S62, calculate the Oatdata of the OAT signature file and the HASH256 value of the oatexec segment, and proceeds to step S63;

 [0066] S63. Determine whether the HASH256 value of the OAT signature file is consistent with the HASH256 value stored in the signature SGN file under the META-INF. If they are consistent, the S8, the signature verification succeeds, the APK is loaded, or, if not, the S7 , prohibit the launch of the APK.

[0067] The above Android APK launches the method of signature authentication, by acquiring the signature SGN file, the APK of the Android system is started, and the signature SGN file is signature-authenticated, thereby limiting the behavior of the APK according to whether the signature SGN file is changed. To enable the successful installation of the APK, verify the signature, and ensure that the APK is not arbitrarily tampered with. Once the APK has been tampered with, the APK can be found after the APK is launched, and the user has been tampered with and cannot be run. , reduce security risks.

 [0068]

 As shown in FIG. 4 and FIG. 5, the device for initiating 吋 signature authentication of the Android APK provided in this embodiment includes a conversion unit 1, a signature file acquisition unit 2, a loading module 5, and a change determination unit 6.

[0070] a conversion unit 1, the conversion unit is configured to convert an original APK installation file into a 0AT format file, And calculating the oatdata and oatexec segments in the OAT format file by using the HASH256+RSA2048 algorithm

, get the signed SGN file.

 [0071] The signature file obtaining unit 2 is configured to acquire a signature SGN file converted from the original APK installation file, and load an OAT signature file converted by the executable code of the installed APK.

 [0072] The signature file obtaining unit 2 includes a loading module 5 for loading the OAT signature file into the memory of the Android ART virtual machine.

 [0073] The change determining unit 6 is configured to determine whether the OAT signature file is consistent with the signature SGN file, and if so, load the APK, otherwise, prohibiting the activation of the APK.

 [0074] The conversion unit 1 described above converts the original APK format into a file of the installed OAT format file by using a homemade computer tool in the conversion file.

 [0075] The signature file obtaining unit 2 obtains the signature SGN file, specifically, the Oatdata and oatexec segments in the OAT format file are calculated by the HASH256+RSA2048 algorithm as the signature SGN file.

 [0076] Since Google's original signature scheme will sign all the files and put the signature in the META-INF directory, after the Android APK is successfully installed, the executable code will be converted into an OAT signature file, and the OAT signature file is an OAT format file. One, since the 0AT format file is essentially an ELF file, it has the structure of a general ELF file at the outermost layer, for example, it has a standard ELF file header and describes the file content by Section, as a private Android. An ELF file, the 0AT format file contains two special sections oatdata and oatexec, the former contains the contents of the dex file used to generate the local machine instructions, and the latter contains the generated local machine instructions, the relationship between them is stored in Oat header description in front of the oatdata section. In addition, in the dynamic section of the 0AT format file, three symbols oatdata, oatexec, and o atlastword are exported, and their values are used to define the start and end positions of the oatdata segment and the oatexec segment, where [oat data, oatexec-l] describes It is the starting and ending position of the oatdata segment, and [oatexec, oatlastword+3] describes the starting and ending position of oatexec.

 [0077] Therefore, the local machine command after the APK is installed according to the 0AT format file (only the home computer tool is used to convert the APK installation package into the 0AT format file on the computer, using the private key pair

0AT performs HASH256+RSA2048 signature, obtains the signature SGN file, puts the signature SGN file into the META-INF directory, and then repackages the APK, so that the OAT file signature can be authenticated at startup. [0078] The loading module 5 described above specifically loads the OAT signature file into the memory of the Android ART virtual machine.

[0079] In addition, the device for launching the signature authentication of the Android APK further includes a restoration unit 3 and a packaging unit 4.

[0080] The restoration unit 3 is configured to put the signature SGN file into the original APK package file directory META-INF.

 [0081] The packaging unit 4 is configured to repackage the APK file and install the new APK file into the Android system.

Further, the change judging unit 6 includes a file tampering judging module 61 and a numerical value judging module 62.

[0083] The file tampering determination module 61 is configured to determine whether the signature SGN file under the META-INF corresponding to the APK has been tampered with, and if the tampering has been performed, the APK fails to be started. Otherwise, the 0 atdata of the OAT signature file is calculated. The HASH256 value of the oatexec segment.

[0084] The value judging module 62 is configured to determine whether the HASH256 value of the OAT signature file and the HASH256 value stored in the signature SGN file under the META-INF are consistent. If the signature is consistent, the signature verification succeeds, the APK is loaded, or If it is inconsistent, it is forbidden to start the APK.

[0085] The device for initiating the signature authentication of the Android APK is configured to acquire the signature SG N file and the OAT signature file by the signature file acquiring unit 2, and the change determination unit 6 performs signature verification on the signature SGN file and the OAT signature file, thereby According to whether the OAT signature file is consistent with the signature SGN file, the behavior of the APK is restricted, and the successfully installed APK is activated, the signature is authenticated, and the A PK is not arbitrarily falsified. Once the APK is tampered with, the APK is started. You can find out that the user has been tampered with, has been tampering, can't run, and reduces security risks.

 [0086]

 The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the invention, and the equivalent structure or equivalent process transformations made by the description of the present invention and the drawings are used directly or indirectly. Other related technical fields are equally included in the scope of patent protection of the present invention.

Claims

 Claim A method for launching a signature authentication of an Android APK, the method comprising: acquiring a signature SGN file converted from an original APK installation file, and loading the OAT of the executable code converted by the installed APK Signature file Determining whether the OAT signature file is consistent with the signature SGN file; If so, load the APK, otherwise, it is forbidden to launch the APK. The method for triggering the signature authentication of the Android APK according to claim 1, wherein the method for converting the original APK installation file into a signature SGN file comprises: converting the original APK installation file into an OAT format file; The oatdata and oat exec segments in the OAT format file are calculated by the HASH256+RSA2048 algorithm to obtain a signature SGN file. The method for triggering the signature authentication of the Android APK according to claim 2, wherein the calculating the oatdata and oatexec segments in the OAT format file by the HASH256+RSA2048 algorithm to obtain the signature SGN file, further includes Put the signed SGN file into the original APK package file directory META-INF; repackage the APK file and install the new APK file into the Android system. The method for triggering the signature authentication of the Android APK according to claim 1, wherein the step of loading and loading the executable code converted from the installed APK into the 0AT signature file comprises: The 0AT signature file is loaded into the memory of the Android ART virtual machine. The method for launching the signature authentication of the Android APK according to claim 2, wherein the step of loading and loading the executable code converted by the installed APK into the 0AT signature file comprises: The 0AT signature file is loaded into the memory of the Android ART virtual machine. The method for triggering authentication of an Android APK according to claim 3, wherein the step of loading and loading the OAT signature file converted by the executable code of the installed APK comprises: The OAT signature file is loaded into the memory of the Android ART virtual machine. The method for determining the signature of an Android APK in accordance with claim 3, wherein the step of determining whether the OAT signature file is consistent with a signature SGN file comprises: determining, according to the META-INF corresponding to the APK Whether the signature SGN file has been tampered with, if yes, prohibiting the activation of the APK, otherwise calculating the HASH256 value of the Oatdata and oate xec segments of the OAT signature file; Determining whether the HASH256 value of the 0AT signature file is consistent with the HASH256 value saved in the signature SGN file under META-INF, If they are consistent, the signature verification is successful, and the APK is loaded. If they are inconsistent An Android APK launching signature authentication device, comprising: a signature file obtaining unit, configured to acquire a signature converted from an original APK installation file An SGN file, and loading the executable code converted by the installed APK into a 0AT signature file; The change judging unit is configured to judge whether the 0AT signature file is consistent with the signature SGN file, and if so, load the APK, otherwise, prohibiting the launch of the APK. The apparatus for triggering authentication of an Android APK according to claim 8, further comprising a converting unit, configured to convert the original APK installation file into a 0AT format file, and calculate the 0AT by using a HASH256+RSA2048 algorithm. The oatdata and oatexec sections in the format file get the signed SGN file. The device for initiating 吋 signature authentication of an Android APK according to claim 9, further comprising a restoring unit and a packing unit, The restoring unit is configured to put the signed SGN file into the original APK package file directory META-INF; The packaging unit is configured to repackage the APK file and install the new APK file into the Android system. The apparatus for initiating the signature authentication of the Android APK according to claim 8, wherein the signature file acquisition unit includes a loading module, and the loading module is configured to load the 0AT signature file into the Android ART virtual machine. Within the memory. [Claim 12] The device for triggering authentication of the Android APK according to claim 8, wherein the change determination unit includes a file tampering determination module and a numerical determination module; and the file tampering determination module is configured to determine Whether the signature SGN file under the META-INF corresponding to the APK has been tampered with, if the tampering has been made, the APK fails to be started, otherwise, the HASH256 value of the Oatdata and oatexec segments of the OAT signature file is calculated;  The value judging module is configured to determine whether the HASH256 value of the OAT signature file and the HASH256 value stored in the signature SGN file in the ME TA-INF are consistent. If the signature is consistent, the signature verification succeeds, the APK is loaded, or If not consistent, it is forbidden to start APK