WO2019080110A1

WO2019080110A1 - Apk signature authentication method and system

Info

Publication number: WO2019080110A1
Application number: PCT/CN2017/108082
Authority: WO
Inventors: 陈菲菲; 孟陆强; 彭波涛; 江中杰
Original assignee: 福建联迪商用设备有限公司
Priority date: 2017-10-27
Filing date: 2017-10-27
Publication date: 2019-05-02
Also published as: CN107980132A

Abstract

An APK signature authentication method and system. The method comprises: S1, signing an original APK file to generate signature information; S2, adding a self-defined ID-value field to an APK signature block, inserting the signature information into the self-defined ID-value field, and generating a signed APK file; S3, a terminal acquiring the signed APK file, extracting the signature information, and restoring the original APK file; and S4, the terminal verifying the legitimacy of the signature information and the original APK file, and after verification is passed, the terminal installing the original APK file. The method does not affect an original signature authentication mechanism of an operating system of a terminal, and can be applied to systems with Android 7.0 or higher. The system has good compatibility and wide applicability. An order receiving mechanism can be downloaded to a payment terminal manufacturer device and other Android devices as long as one signed APK file is generated, thereby reducing the maintenance cost of the order receiving mechanism.

Description

APK signature authentication method and system

[0001] The present invention relates to the field of signature authentication, and in particular, to a method and system for authenticating an APK signature.

Background technique

[0002] Android is a Linux-based source operating system issued by Google, and the installer on it is in the APK (Android Package) format. The APK file format is actually a zip compressed file format, which is mainly divided into three parts, namely compressed file content source data, compressed directory source data and directory end identifier structure.

[0003] In the field of financial payment, generally, an acquirer purchases a smart terminal device of a payment terminal manufacturer, and installs an acquirer's own program on the payment terminal, and the installation program is an APK format. The acquirer maintains the signed APK for the purchaser's payment terminal device and may also need to install the APK into other Androi d devices.

[0004] The applicant of the present invention has previously filed an invention patent application with the application number 201510780639.0, and discloses an APK signature authentication method and system thereof, and adds signature information to the META-INF directory of the APK source file. program can be run before And _rO id7.0 system is normal, but from the beginning And _rO id7.0 system Jian, the introduction of a new application signature scheme APK signature scheme v2, APK V2 format that is native signature. The native signature of the APK V2 format will sign the entire APK data, and the APK that was originally signed in the V2 format is not allowed to be inserted into the META-INF directory. Therefore, the above scheme does not apply to systems with A nd _rO id 7.0 or higher, and it is necessary to improve them to overcome the above problems.

technical problem

[0005] The technical problem to be solved by the present invention is: Providing a method and system for authenticating an APK signature, which is compatible with the native signature mechanism of the V2 format of the terminal operating system, improves the compatibility of the APK signature authentication, and can adapt to different versions of the Android system.

Problem solution

Technical solution

[0006] In order to solve the above technical problem, a technical solution adopted by the present invention is: [0007] A method for authenticating an APK signature, comprising the steps of:

[0008] Sl, signing the original APK file to generate signature information;

[0009] S2, adding a custom ID-value field in the APK signature block, inserting the signature information into the customized ID-value field, and generating a signed APK file;

[0010] S3. The terminal acquires the signed APK file, extracts the signature information, and restores the original APK file.

[0011] S4. The terminal verifies the legality of the signature information and the original APK file. After the verification is passed, the terminal installs the original APK file.

[0012] In order to solve the above technical problem, another technical solution adopted by the present invention is:

[0013] An APK signature authentication system, including an acquirer and a terminal, the acquirer including a first memory

a first processor and a first computer program stored on the first memory and operable on the first processor, the terminal comprising a second memory, a second processor, and being stored in the second memory and operable a second computer program running on the second processor,

[0014] the first processor executes the first computer program to implement the following steps:

[0015] Sl, signing the original APK file to generate signature information;

[0016] S2, adding a custom ID-value field in the APK signature block, inserting the signature information into the customized ID-value field, and generating a signed APK file;

[0017] the second processor executes the second computer program to implement the following steps:

[0018] S3. Obtain the signed APK file, extract the signature information, and restore the original APK file.

[0019] S4. Verify the legality of the signature information and the original APK file, and after the verification is passed, install the original APK file.

Advantageous effects of the invention

Beneficial effect

[0020] The beneficial effects of the present invention are: adding a custom ID-value field in the APK signature block, and inserting the signature information signed by the original APK file into the customized ID-value field, without affecting the terminal. original inspection mechanisms to check the operating system, the system can be applied and _rO above id7.0, good compatibility, wide applicability, and as long as the acquirer generate a signed APK file, it can be downloaded to the payment terminal manufacturers On the device and other Android devices, reduce the maintenance costs of the acquirer.

Brief description of the drawing

DRAWINGS

1 is a flowchart of a method for authenticating an APK signature according to an embodiment of the present invention;

2 is a schematic structural diagram of a APK signature authentication system according to an embodiment of the present invention;

3 is a schematic diagram of a data format of signature information according to an embodiment of the present invention;

4 is a schematic diagram of a file format of an APK file after a native signature V2 and an organization signature according to an embodiment of the present invention;

[0025] Description of the label:

[0026] 1, the acquiring institution; 2, the first memory; 3, the first processor;

4, the terminal; 5, the second memory; 6, the second processor; 7, APK signature authentication system.

Detailed ways

[0027] The most critical idea of the present invention is: adding a custom ID-value field to the APK signature block, and inserting the signature information signed by the original APK file into the customized ID-value field without affecting The original check mechanism of the terminal operating system.

[0028] Please refer to FIG. 1, a method for authenticating an APK signature, including the steps:

[0029] Sl, signing the original APK file to generate signature information;

[0030] S2, adding a custom ID-value field to the APK signature block, inserting the signature information into the customized ID-value field, and generating a signed APK file;

[0031] S3. The terminal acquires the signed APK file, extracts the signature information, and restores the original APK file.

[0032] S4. The terminal verifies the legality of the signature information and the original APK file. After the verification is passed, the terminal installs the original APK file.

[0033] It can be seen from the above description that the beneficial effects of the present invention are: adding a custom ID-v alue field to the APK signature block, and inserting the signature information signed by the original APK file into the customized ID-value. APK file field, will not affect the original inspection mechanism signed terminal operating system, the system can be applied and _rO above id7.0, good compatibility, wide applicability, and as long as the acquirer generates a signed, we can lower It is loaded on payment terminal manufacturer equipment and other Android devices to reduce the maintenance cost of the acquirer.

[0034] Further, the step S2 specifically includes:

[0035] According to the APK signature block format, a custom ID-value field is added to the APK signature block, the signature information is inserted into the customized ID-value field, and the APK signature of the original APK file is modified accordingly. The block length and the directory end identification structure of the block generate the signed APK file.

[0036] According to the above description, according to the APK signature block format, a custom ID-valu e field is added to the APK signature block, the signature information is inserted into the customized ID-value field, and the original APK is modified accordingly. The block length of the APK signature block of the file and the end of directory identifier structure, the generated APK file is generated, and the signed APK file is compared with the original APK file, and the APK signature block only adds a custom ID-val ue field. V2 native format in line with the signed APK file format, does not affect the sign of the native Android experience, so for more than id7.0 equipment And _rO, can be properly installed.

[0037] Further, the block length and the directory end identifier structure of the APK signature block of the original APK file are modified to include:

[0038] The block length of the APK signature block is added to the size of the custom ID_value field, and the directory offset position in the directory end identifier structure plus the size of the custom ID_value field.

[0039] As can be seen from the above description, since the APK file format is not changed, but a custom ID-value conforming to the APK signature block format is added to the APK signature block, the custom ID-value is added. The signature information, so only the data length of the APK signature block is changed. Therefore, it is only necessary to adaptively modify the block length of the APK signature block and the directory offset position in the directory end identification structure, and the modification is small and the operation is convenient and fast.

[0040] Further, the sign information is extracted in the step S3, and the original APK file is restored to be specifically included.

[0041] copying the signature information from the ID-value field customized in the APK signature block according to the ID identifier;

[0042] deleting the customized ID-value field from the APK signature block, and modifying the APK file accordingly

The block length of the APK signature block and the end of directory identifier structure restore the original APK file.

[0043] According to the above description, the signature information is copied from the APK signature block according to the ID identifier, and is deleted from the APK signature block, and the block length and the directory end identifier structure of the APK signature block of the APK file are modified correspondingly, and restored. The original APK file, which can verify the original APK file and guarantee the original AP. [0044] Further, the block length and the directory end identifier structure of the APK signature block of the modified APK file specifically include:

[0045] The block length of the APK signature block is subtracted from the size of the custom ID-value field, and the directory end position in the directory identifier structure is subtracted from the size of the custom ID-value field.

[0046] As can be seen from the above description, since only the data size of the APK signature block is changed, after the signature information is deleted from the corresponding location, only the block length of the APK signature block and the directory offset in the directory end identifier structure need to be changed. The location is convenient and fast.

[0047] Further, the step S1 specifically includes:

[0048] generating an acquirer work public key certificate, and distributing the public key corresponding to the work mechanism public key certificate of the acquirer to different vendors;

[0049] using the original APK file and the acquirer signature description information as the signed data, and calculating a hash on the signed data to obtain a first hash value;

[0050] filling the first hash value to obtain the padded data;

[0051] acquiring a private key corresponding to the work mechanism public key certificate of the acquiring institution, and signing the filled data by using the private key to obtain the acquiring institution signature data;

[0052] generating signature information including the acquirer signature description information, the acquirer signature data, and the acquirer work public key certificate.

[0053] Further, the terminal verifying the legality of the signature information and the original APK file in the step S4 specifically includes:

[0054] the terminal verifies the legality of the work function public key certificate of the acquirer in the signature information by using the acquirer root public key certificate generated by the corresponding manufacturer according to the public key;

[0055] if the verification is passed, extracting the second public key from the acquiring institution working public key certificate, and decrypting the acquiring institution signature data by using the second public key to obtain a first hash value;

[0056] calculating a hash of the receipt structure signature description information and the original APK file to obtain a second hash value; [0057] determining whether the second hash value is consistent with the first hash value, If they are consistent, the verification is passed.

[0058] It can be seen from the above description that the object signed by the acquiring institution is the original APK file, and the acquiring institution public key certificate is uniformly generated by the acquiring institution, and the public key corresponding to the working institution public key certificate of the acquiring institution is distributed to Different vendors, different vendors' CA servers use the public key to generate the acquirer root public key certificate according to the respective certificate generation algorithm, and the terminal uses the acquirer root public key certificate to verify the acquirer work public key in the signature information. The validity of the certificate, after the verification is passed, the public key issued by the acquirer is used for each check, to ensure the integrity of the signed APK file in the data transmission process and the legitimacy of the APK, and the acquirer is also targeting the terminal equipment of different manufacturers. Simply maintaining a signed file and a set of signature implementation mechanisms greatly reduces the cost of maintaining the APK signature for the acquirer.

[0059] Further, the installing, by the terminal, the original APK file in the step S4 includes:

[0060] extracting native signature data from the APK signature block, and restoring the APK file that is not originally signed;

[0061] verifying the legality of the native signature data and the APK file that is not originally signed, after verification

Install the APK file that is not natively signed.

[0062] It can be seen from the above description that the APK signature authentication method of the present invention does not affect the native authentication mechanism of the terminal operating system, and the terminal can successfully perform the native authentication mechanism and install the APK file that is not originally signed, and the compatibility is good. .

Referring to FIG. 2, an APK signature authentication system 7 includes an acquirer 1 and a terminal 4. The acquirer 1 includes a first memory 2, a first processor 3, and is stored in the first memory 2. And a first computer program running on the first processor 3, the terminal 4 includes a second memory 5, a second processor 6, and is stored on the second memory 5 and operable on the second processor 6. a second computer program, characterized in that

[0064] The first processor 3 executes the first computer program to implement the following steps:

[0065] Sl, signing the original APK file to generate signature information;

[0066] S2, adding a custom ID-value field in the APK signature block, inserting the signature information into the customized ID-value field, and generating a signed APK file;

[0067] The second processor 6 executes the second computer program to implement the following steps:

[0068] S3. Obtain the signed APK file, extract the signature information, and restore the original APK file.

[0069] S4. Verify the legality of the signature information and the original APK file, and after the verification is passed, install the original APK file.

[0070] It can be seen from the above description that the beneficial effects of the present invention are: adding a custom ID-v alue field to the APK signature block, and inserting the signature information signed by the original APK file into the customized ID-value. area Will not affect the original inspection mechanism signed terminal operating system, the system can be applied And _rO above id7.0, good compatibility, wide applicability, and as long as the acquirer generate a signed APK file, it can be downloaded to pay On the terminal manufacturer equipment and other Android devices, the maintenance cost of the acquirer is reduced.

[0071] Further, the step S2 specifically includes:

[0072] According to the APK signature block format, a custom ID-value field is added to the APK signature block, the signature information is inserted into the customized ID-value field, and the APK signature of the original APK file is modified accordingly. The block length and the directory end identification structure of the block generate the signed APK file.

[0073] According to the above description, according to the APK signature block format, a custom ID-valu e field is added to the APK signature block, the signature information is inserted into the customized ID-value field, and the original APK is modified accordingly. The block length of the APK signature block of the file and the end of directory identifier structure, the generated APK file is generated, and the signed APK file is compared with the original APK file, and the APK signature block only adds a custom ID-val ue field. V2 native format in line with the signed APK file format, does not affect the sign of the native Android experience, so for more than id7.0 equipment And _rO, can be properly installed.

[0074] Further, the modifying the block length and the directory end identifier structure of the APK signature block of the original APK file specifically includes:

[0075] The block length of the APK signature block is added to the size of the custom ID-value field, and the directory offset position in the directory end identifier structure plus the size of the custom ID_value field.

[0076] As can be seen from the above description, since the APK file format is not changed, only a custom ID-value conforming to the APK signature block format is added to the APK signature block, and the custom ID-value is added. The signature information, so only the data length of the APK signature block is changed. Therefore, it is only necessary to adaptively modify the block length of the APK signature block and the directory offset position in the directory end identification structure, and the modification is small and the operation is convenient and fast.

[0077] Further, the sign information is extracted in the step S3, and the original APK file is restored to be specifically included.

[0078] copying the signature information from the ID-value field customized in the APK signature block according to the ID identifier;

[0079] deleting the customized ID-value field from the APK signature block, and modifying the APK file accordingly

[0080] According to the above description, the signature information is copied from the APK signature block according to the ID identifier, and is extracted from the APK. Delete the signature block, modify the block length of the APK signature block of the APK file and the end of the directory identifier structure, and restore the original APK file, which can not only verify the original APK file, but also ensure that the original AP K file can be successfully executed at the terminal. Check the installation.

[0081] Further, the block length and the directory end identifier structure of the APK signature block of the modified APK file specifically include:

[0082] The block length of the APK signature block is subtracted from the size of the custom ID_value field, and the directory offset position in the directory end identifier structure is subtracted from the size of the custom ID-value field.

[0083] As can be seen from the above description, since only the data size of the APK signature block is changed, after the signature information is deleted from the corresponding location, only the block length of the APK signature block and the directory offset in the directory end identifier structure need to be changed. The location is convenient and fast.

[0084] Further, the step S1 specifically includes:

[0085] generating an acquirer work public key certificate, and distributing the public key corresponding to the work mechanism public key certificate of the acquirer to different vendors;

[0086] using the original APK file and the acquirer signature description information as the signed data, and calculating a hash on the signed data to obtain a first hash value;

[0087] filling the first hash value to obtain the padded data;

Obtaining a private key corresponding to the work permit public key certificate of the hiring institution, and signing the filled data by using the private key to obtain the acquirer signature data;

[0089] generating signature information including the acquirer signature description information, the acquirer signature data, and the acquirer work public key certificate.

[0090] Further, verifying the legality of the signature information and the original APK file in the step S4 specifically includes:

[0091] verifying the legality of the acquiring institution working public key certificate in the signature information by using the acquiring institution root public key certificate generated by the corresponding manufacturer according to the public key;

[0092] if the verification is passed, extracting the second public key from the acquiring institution working public key certificate, and decrypting the acquiring institution signature data by using the second public key to obtain a first hash value;

[0093] calculating a hash of the receipt structure signature description information and the original APK file to obtain a second hash value; [0094] determining whether the second hash value is consistent with the first hash value, If they are consistent, the verification is passed. [0095] It can be seen from the above description that the object signed by the acquiring institution is the original APK file, and the acquiring institution public key certificate is uniformly generated by the acquiring institution, and the public key corresponding to the working institution public key certificate of the acquiring institution is distributed to Different vendors, different vendors' CA servers use the public key to generate the acquirer root public key certificate according to the respective certificate generation algorithm, and the terminal uses the acquirer root public key certificate to verify the acquirer work public key in the signature information. The validity of the certificate, after the verification is passed, the public key issued by the acquirer is used for each check, to ensure the integrity of the signed APK file in the data transmission process and the legitimacy of the APK, and the acquirer is also targeting the terminal equipment of different manufacturers. Simply maintaining a signed file and a set of signature implementation mechanisms greatly reduces the cost of maintaining the APK signature for the acquirer.

[0096] Further, the installing the original APK file in the step S4 includes:

[0097] extracting native signature data from the APK signature block, and restoring the APK file that is not originally signed;

[0098] verifying the legality of the native signature data and the APK file that is not originally signed, after verification

Install the APK file that is not natively signed.

[0099] It can be seen from the above description that the APK signature authentication system of the present invention does not affect the native authentication mechanism of the terminal operating system, and the terminal can smoothly perform the native authentication mechanism and install the APK file that is not originally signed, and the compatibility is good. .

Embodiment 1

[0101] Please refer to FIG. 1, a method for authenticating an APK signature, including the steps:

[0102] Sl, signing the original APK file, and generating signature information;

[0103] Specifically, the acquirer 1 invokes the encryption device to generate a first public private key pair and a second public private key pair, and the acquirer 1 performs a signature operation on the second public key by using the first private key to generate an acquirer work public key. The certificate Acquirer WCRT distributes the first public key corresponding to the acquirer work public key certificate AcquirerWCRT to a CA server of a different vendor;

[0104] The acquiring institution 1 uses the original APK file and the acquiring institution signature description information as the signed data Sourc eData, and calculates a hash for the signed data SourceData to obtain a first hash value HASH1;

[0105] The acquiring institution 1 fills the first hash value HASH1 according to the signature filling manner of PKCS#1_V1.5, and obtains the filled data PAD_dat _a;

[0106] The acquirer 1 acquires a second private key corresponding to the acquirer work public key certificate from the secure storage medium, and encrypts and signs the filled data by using the second private key to obtain an acquirer. Signature data Si Gnature;

[0107] The acquirer signature description information, the acquirer signature data Signature, the acquirer work public key certificate AcquirerWCRT, and the signature file header are spliced together to generate the signature information of the acquirer, and the data format of the signature information is as shown in FIG. The indication information of the acquiring institution is not fixed, and the signature data of the acquiring institution is described. The length of the signature data of the acquiring institution is 256 bytes, which is the result of signing the original APK file, and the public key certificate of the acquiring institution is uncertain. Long, is the agency work public key certificate used for signature. The signature file is not long, but does not exceed lk. It is used to identify the signature file type and the data offset and length of the signing data of the acquiring institution. Signature data;

[0108] S2, adding a custom ID-value field in the APK signature block, inserting the signature information into the customized ID-value field, and generating a signed APK file;

[0109] According to the APK signature block format, a custom ID-value field is added to the APK signature block, the signature information is inserted into the customized ID-value field, and the APK signature of the original APK file is modified accordingly. a block length and a directory end identifier structure of the block. Specifically, a block length of the APK signature block is added to a size of the custom ID-value field, and a directory offset position in the directory end identifier structure is added. Customize the size of the ID - value field to generate the signed APK file;

[0110] FIG. 4 is a diagram showing changes in the format of an APK file after the native signature of the APK file that is not originally signed and the signature of the acquirer;

[0111] As can be seen from FIG. 4, after the acquiring institution signs the APK file after the native signature V2, the structure of the native signature APK file is not changed, and the custom ID-value field in the APK signature block is inserted. Signature f π息;

[0112] S3. The terminal 4 acquires the signed APK file, extracts the signature information, and restores the original AP K file.

[0113] Specifically, the signature information is copied from the ID-value field customized in the APK signature block according to the ID identifier; the customized ID-value field is deleted from the APK signature block, and the APK file is modified accordingly. APK block length and directory end identifier structure, specifically, the block length of the APK signature block minus the size of the custom ID-value field, the directory offset position in the directory end identifier structure minus Define the ID—the size of the value field, and restore the original APK file;

[0114] wherein the ID identifier of the APK native signature is fixed to 0x7109871a, in order to avoid conflict, it may be defined The ID of the signature information is 0x71536966, and may be other values, as long as it does not conflict with the ID identifier of the native signature of the APK;

[0115] S4. The terminal verifies the legality of the signature information and the original APK file. After the verification is passed, the terminal installs the original APK file.

[0116] The validity of the verification of the signature information and the original APK file by the terminal 4 specifically includes:

[0117] The CA servers of different vendors generate the acquirer root public key certificate by using the first public key issued by the acquirer according to the respective certificate generation mechanism, and pre-install the acquirer root public key certificate in the respective vendors. In the terminal;

[0118] The terminal 4 verifies the legality of the acquirer work public key certificate AcquirerWCRT in the signature information by using the acquirer root public key certificate;

[0119] If the verification is passed, the terminal 4 extracts the second public key using the acquirer work public key certificate AcquirerWCRT.

Decrypting the acquiring institution signature data by using the second public key to obtain a first hash value HASH1;

[0120] The terminal 4 calculates a hash of the receipt structure signature description information and the original APK file to obtain a second hash value HASH2;

Determining whether the second hash value is consistent with the first hash value. If they are consistent, it is proved that the signed APK file obtained by the terminal 4 is legal and has not been tampered with, and the vendor device has signed the APK file. Passing the verification, allowing the terminal to install the original APK file;

[0122] Since the original APK file is an APK file after the original check, the terminal 4 needs to process the natively signed APK file in the process of installing the original APK file. The legality of the verification, that is, the original verification process of the terminal 4, specifically includes:

[0123] extracting native signature data from the APK signature block, and restoring the APK file that is not originally signed;

[0124] verifying the legality of the native signature data and the APK file that is not originally signed, and after the verification is passed, installing the APK file that is not originally signed.

Embodiment 2

[0126] Please refer to FIG. 2, an APK signature authentication system 7 includes an acquirer 1 and a terminal 4. The acquirer 1 includes a first memory 2, a first processor 3, and is stored in the first memory 2. And a first computer program running on the first processor 3, the terminal 4 includes a second memory 5, a second processor 6, and is stored on the second memory 5 and operable on the second processor 6. a second computer program, characterized in that [0127] The first processor 3 executes the first computer program to implement the following steps:

[0128] Sl, signing the original APK file, and generating signature information;

[0129] Specifically, the acquirer 1 invokes the encryption device to generate a first public private key pair and a second public private key pair, and the acquirer 1 performs a signature operation on the second public key by using the first private key to generate an acquirer work public key. Certificate Acquirer

The WCRT distributes the first public key corresponding to the acquirer work public key certificate AcquirerWCRT to a CA server of a different manufacturer;

[0130] The acquiring institution 1 uses the original APK file and the acquiring institution signature description information as the signed data Sourc eData, and calculates a hash for the signed data SourceData to obtain a first hash value HASH1;

[0131] The acquirer 1 fills the first hash value HASH1 according to the signature filling manner of PKCS#1_V1.5, and obtains the padded data PAD_dat _a;

[0132] The acquiring institution 1 acquires a second private key corresponding to the acquiring institution work public key certificate from the secure storage medium, and encrypts and signs the filled data by using the second private key to obtain an acquiring institution. Signature data Si gnature;

[0133] The acquirer signature description information, the acquirer signature data Signature, the acquirer work public key certificate AcquirerWCRT, and the signature file header are spliced together to generate the signature information of the acquirer, and the data format of the signature information is as shown in FIG. The indication information of the acquiring institution is not fixed, and the signature data of the acquiring institution is described. The length of the signature data of the acquiring institution is 256 bytes, which is the result of signing the original APK file, and the public key certificate of the acquiring institution is uncertain. Long, is the agency work public key certificate used for signature. The signature file is not long, but does not exceed lk. It is used to identify the signature file type and the data offset and length of the signing data of the acquiring institution. Signature data;

[0134] S2, adding a custom ID-value field to the APK signature block, inserting the signature information into the customized ID-value field, and generating the signed APK file;

[0135] According to the APK signature block format, a custom ID-value field is added to the APK signature block, the signature information is inserted into the customized ID-value field, and the APK signature of the original APK file is modified accordingly. a block length and a directory end identifier structure of the block. Specifically, a block length of the APK signature block is added to a size of the custom ID-value field, and a directory offset position in the directory end identifier structure is added. Customize the size of the ID - value field to generate the signed APK file;

[0136] FIG. 4 shows the native signature of the APK file that is not originally signed and the signature of the acquirer. After the change of the format of the APK file;

[0137] As can be seen from FIG. 4, after the acquirer 1 signs the APK file after the native signature V2, the structure of the native signature APK file is not changed, and the custom ID-value field in the APK signature block is used. Insert the signature f π;

[0138] The second processor 6 executes the second computer program to implement the following steps:

[0139] S3. Obtain the signed APK file, extract the signature information, and restore the original APK file.

[0140] Specifically, the signature information is copied from the ID-value field customized in the APK signature block according to the ID identifier; the customized ID-value field is deleted from the APK signature block, and the APK file is modified accordingly. APK block length and directory end identifier structure, specifically, the block length of the APK signature block minus the size of the custom ID-value field, the directory offset position in the directory end identifier structure minus Define the ID—the size of the value field, and restore the original APK file;

[0141] wherein the ID of the native signature of the APK is fixed to 0x7109871a. To avoid conflict, the ID of the signature information may be defined as 0x71536966, or other values, as long as the ID of the native signature of the APK does not conflict with the identifier of the native signature of the APK. Yes;

[0142] S4. Verify the legality of the signature information and the original APK file, and after the verification is passed, install the original APK file;

[0143] wherein verifying the legality of the signature information and the original APK file specifically includes:

[0144] The CA servers of different vendors generate the acquirer root public key certificate by using the first public key issued by the acquirer according to the respective certificate generation mechanism, and pre-install the acquirer root public key certificate in the respective vendors. In the terminal;

[0145] the terminal 4 verifies the legality of the acquirer work public key certificate AcquirerWCRT in the signature information by using the acquirer root public key certificate;

[0146] If the verification is passed, the terminal 4 extracts the second public key using the acquirer work public key certificate AcquirerWCRT.

[0147] The terminal 4 calculates a hash of the receipt structure signature description information and the original APK file to obtain a second hash H.

ASH2;

[0148] determining whether the second hash value is consistent with the first hash value, and if yes, proving that the terminal 4 obtains The signed APK file is legal and has not been tampered with. The vendor device passes the verification of the signed APK file, allowing the terminal 4 to install the original APK file.

[0149] Since the original APK file is an APK file after the original check, the terminal 4 needs to process the natively signed APK file in the process of installing the original APK file. The legality of the terminal is verified, that is, the original verification process of the terminal, which specifically includes:

[0150] extracting native signature data from the APK signature block, and restoring the APK file that is not originally signed;

[0151] verifying the legality of the native signature data and the APK file that is not originally signed, and after the verification is passed, installing the APK file that is not originally signed.

[0152] In summary, the present invention provides an APK signature authentication method and system, adding a custom ID-value field to an APK signature block, and inserting signature information of the original APK file into the self. ID-value field defined, without affecting the primary mechanism for inspection check terminal operating system, more systems id7.0, good compatibility, wide applicability, and to generate a long acquirer APK signed document can be applied and _rO , can download to payment terminal manufacturer equipment and other Android devices, reducing the maintenance cost of the acquirer

Claims

Claim

[Claim 1] A method for authenticating an APK signature, comprising the steps of:

51. Sign the original APK file to generate signature information;

52. Add a custom ID-value field to the APK signature block, insert the signature information into the customized ID-value field, and generate a signed APK file;

53. The terminal acquires the signed APK file, extracts the signature information, and restores the original APK file.

54. The terminal verifies the legality of the signature information and the original APK file, and after the verification is passed, the terminal installs the original APK file.

[Claim 2] The APK signature authentication method according to claim 1, wherein

The step S2 specifically includes:

Adding a custom ID-value field to the APK signature block according to the APK signature block format, inserting the signature information into the customized ID-value field, and modifying the APK signature block of the original AP K file accordingly. The block length and directory end identification structure, the generated AP K file is generated.

[Claim 3] The APK signature authentication method according to claim 2, wherein

The block length and the directory end identifier structure of the APK signature block of the original APK file are modified to include:

The block length of the APK signature block is added to the size of the custom ID_value field, and the directory offset position in the directory end identifier structure is added to the size of the custom ID-value field.

[Claim 4] The APK signature authentication method according to claim 1, wherein

The step of extracting the signature information in the step S3, the restoring the original APK file specifically includes: copying the signature information from the ID-value field customized in the APK signature block according to the ID identifier; and using the customized ID-value field The block is deleted from the APK signature block, and the block length and the directory end identifier structure of the APK signature block of the AP K file are modified correspondingly, and the original APK file is restored.

[Attachment 5] The APK signature authentication method according to claim 4, wherein The block length and the directory end identifier structure of the APK signature block of the modified APK file specifically include:

The block length of the APK signature block is subtracted from the size of the custom ID-value field, and the directory end identifier structure is offset from the directory size of the custom ID-value field.

[Claim 6] The APK signature authentication method according to claim 1, wherein

The step S1 specifically includes:

Generating an acquirer work public key certificate, and distributing the public key corresponding to the work order public key certificate of the acquirer to different vendors;

Combining the original APK file and the acquirer signature description information as the signed data, and calculating a hash on the signed data to obtain a first hash value;

Filling the first hash value to obtain the padded data;

Obtaining a private key corresponding to the working institution public key certificate of the acquiring institution, and signing the filled data by using the private key to obtain the acquiring institution signature data;

Signature information including the acquirer signature description information, the acquirer signature data, and the acquirer work public key certificate is generated.

[Attachment 7] The APK signature authentication method according to claim 6, wherein

The legality of the terminal verifying the signature information and the original APK file in the step S4 includes:

The terminal verifies the legality of the work function public key certificate of the acquirer in the signature information by using the acquirer root public key certificate generated by the corresponding manufacturer according to the public key; if the verification is passed, the work is performed from the acquirer The key certificate extracts the second public key, decrypts the acquirer signature data by using the second public key, and obtains a first hash value; and calculates a hash for the receipt structure signature description information and the original APK file, Obtaining a second hash value;

It is determined whether the second hash value is consistent with the first hash value, and if they are consistent, the verification is passed.

[Attachment 8] The APK signature authentication method according to claim 6, wherein The installing the original APK file by the terminal in the step S4 includes:

Extracting the native signature data from the APK signature block, restoring the APK file that is not originally signed; verifying the legality of the native signature data and the APK file not originally signed, after the verification is passed, installing the unsigned signature APK file.

[Claim 9] An APK signature authentication system, comprising an acquirer and a terminal, the acquirer comprising a first memory, a first processor, and being stored on the first memory and on the first processor a first computer program running, the terminal comprising a second memory, a second processor, and a second computer program stored on the second memory and operable on the second processor, wherein

The first processor executes the first computer program to implement the following steps:

51. Sign the original APK file to generate signature information;

52. Add a custom ID-value field to the APK signature block, insert the signature information into the customized ID-value field, and generate a signed APK file; the second processor executes the second The computer program implements the following steps:

53. Obtain the signed APK file, extract the signature information, and restore the original APK file;

54. Verify the legality of the signature information and the original APK file, and after the verification is passed, install the original APK file.

[Claim 10] The APK signature authentication system according to claim 9, wherein

The step S2 specifically includes:

[Claim 11] The APK signature authentication system according to claim 10, wherein

a block length of the APK signature block plus a size of the custom ID_value field, The directory offset location in the directory end identification structure plus the size of the custom ID-value field.

The APK signature authentication system according to claim 9, wherein

The step of extracting the signature information in the step S3, the restoring the original APK file specifically includes: copying the signature information from the ID-value field customized in the APK signature block according to the ID identifier; and using the customized ID-value field Remove from the APK signature block and modify the AP accordingly

The block length of the APK signature block of the K file and the end of directory identifier structure restore the original APK file.

The APK signature authentication system according to claim 12, characterized in that

The block length and the directory end identifier structure of the APK signature block of the modified APK file specifically include:

The APK signature authentication system according to claim 9, wherein

The step S1 specifically includes:

Filling the first hash value to obtain the padded data;

The APK signature authentication system according to claim 14, wherein

The verification of the legality of the signature information and the original APK file in the step S4 specifically includes: Verifying the legality of the work function public key certificate of the acquirer in the signature information by using the acquirer root public key certificate generated by the corresponding manufacturer according to the public key;

If the verification is passed, extracting the second public key from the acquiring institution working public key certificate, decrypting the acquiring institution signature data by using the second public key, and obtaining a first hash value; The single structure signature description information and the original APK file calculate a hash to obtain a second hash value;

[Claim 16] The APK signature authentication system according to claim 9, wherein

The installing the original APK file in the step S4 includes: