WO2015161682A1 - Multi-party authorized apk signing method and system - Google Patents

Abstract

Provided are a multi-party authorized APK signing method and system, comprising: signature servers of different terminal device manufacturers use respective work private keys to sign the signed data comprising an original APK file to generate signature data of different terminal device manufacturers, and place a manufacturer work public key certificate into the signature data of the terminal device manufacturers or pre-install in a terminal device; an receipt institution signature server forms the signature data of different terminal device manufacturers into a signed APK file in a DER format in a time sequence of signatures, the signed APK file comprising the original APK file and a signature file header, and the signature file header comprising data for identifying a signed file and identifying the number of the signature data of the terminal device manufacturers, and the specific positions of the signature data in the signed APK file; the terminal device acquires the signed APK file, and, after determining that the signed APK file contains the corresponding terminal device manufacturer signature data, positions and authenticates the terminal device manufacturer signature data, and allows installation and operation after the authentication succeeds.

Description

Multi-party authorized APK signature method and system

Technical field

The invention relates to APK The field of signature authentication, especially involving a multi-party authorization APK Signature method and system.

Background technique

Bank card( BANK Card As a payment tool is becoming more and more popular, the usual bank card payment system includes a point-of-sale terminal ( Point Of Sale , POS ), POS Receipt system POSP ),password keyboard( PIN PAD ) and hardware encryption machine ( Hardware and Security Module , HSM ). among them POS The terminal can accept the bank card information, has the communication function, and accepts the instructions of the teller to complete the financial transaction information and the related information exchange device; POS Billing system POS Centralized management of terminals, including parameter download, key download, accept, process or forward POS Terminal transaction request, and POS The terminal returns the transaction result information, which is a centralized management and transaction processing system; POS The program above is downloaded and updated by the acquirer. due to Android The versatility of the system, the acquiring agency began to purchase Android systematic POS Terminal Equipment. Android System installation package is called APK , Android Package abbreviation of.

But because POS There are many terminal equipment manufacturers, each manufacturer is improving POS The security of the terminal device will be needed after downloading. POS Install and run the program for signature verification, only the legally signed program is allowed to install or run. And because the vendor implementation mechanism is different, it can be downloaded and installed to different vendors. Android system POS Terminal APK The signed file format is inconsistent, resulting in the acquisition of different manufacturers by the acquirer. Android system POS Terminal equipment, need to maintain different signature tools at the same time Android System and the same APK Maintain different versions of signed APK Documents, bringing cumbersome maintenance work and great maintenance costs to the acquiring institution, it is necessary to propose a kind of APK Signature scheme, reduce the pair of acquiring institutions APK The maintenance cost of the signature.

Summary of the invention

The object of the present invention is to provide a convenient acquiring institution to uniformly manage different manufacturers. Android The signature of the system terminal device, a multi-party authorization to reduce maintenance costs APK Signature method and system.

In order to achieve the above object, one technical solution adopted by the present invention is:

Multi-party authorized APK Signature methods, including:

: Different terminal equipment manufacturers CA Each server generates a vendor root public-private key pair, and generates a vendor root public key certificate from the vendor root public key; each terminal device vendor signature server generates a vendor work public-private key pair, and distributes the work public key to the respective vendor. CA Server, vendor CA The server uses the vendor root private key to generate a vendor work public key certificate for the vendor work public key signature;

: Different terminal device vendor signature servers use their respective vendor work private key pairs including the original APK The signed data signature of the file generates signature data of different terminal device vendors, and the respective manufacturer work public key certificates are put into the respective manufacturer signature data or pre-installed in the terminal device according to different terminal device vendors' verification mechanisms; different terminals Device vendors pre-install their respective vendor root public key certificates in their respective terminal devices;

The acquirer signature server uses different vendor signature data generated by different terminal device vendor signature servers in the order of signature time. DER Format composition signed APK File; wherein the signed APK File includes original APK a file and a signature file header, the signature file header includes a base file and an extension file, where the basic file is used to identify that the file has been signed, and the extension file is used to identify the number of vendor signature data of different terminal devices and The vendor signature data of each terminal device is signed APK The specific location in the file;

: the terminal device obtains the signed signature from the acquirer signature server APK File, judge signed APK Whether there is vendor signature data generated by the terminal device manufacturer corresponding to the terminal device in the file, and after determining that there is corresponding vendor signature data, the terminal device passes the signed signature. APK The file header of the file locates the vendor signature data;

After obtaining the vendor root public key certificate, the terminal device uses the vendor root public key certificate to verify the legality of the vendor working public key certificate in the vendor signature data. After verifying the legality, the terminal device extracts the working public key verification signature data in the vendor working public key certificate. Allow installation or operation after verification.

Another technical solution provided by the present invention is:

Multi-party authorized APK a signature system, comprising: a terminal device manufacturer server, an acquirer server, and a terminal device server;

The terminal device manufacturer server includes a first generation module, a second generation module, and a first signature module;

The first generation module is used by different terminal equipment vendors CA Each server generates a vendor root public-private key pair, generates a vendor root public key certificate from the vendor root public key, and generates a vendor work public key certificate by using the vendor root private key to sign the vendor work public key;

The second generation module is configured to generate a vendor public-private key pair for each terminal device vendor signature server, and distribute the work public key to the respective vendor. CA server;

The first signature module is used by different terminal device vendor signature servers to use respective vendor work private key pairs including original APK The signed data signature of the file generates signature data of different terminal device vendors, and the respective manufacturer work public key certificates are put into the respective manufacturer signature data or pre-installed in the terminal device according to different terminal device vendors' verification mechanisms; different terminals Device vendors pre-install their respective vendor root public key certificates in their respective terminal devices;

The acquirer server includes a second signature module;

The second signature module is used by the acquiring institution signature server to adopt different vendor signature data generated by different terminal device manufacturer signature servers according to the sequence of signature times. DER Format composition signed APK File; wherein the signed APK File includes original APK a file and a signature file header, the signature file header includes a base file and an extension file, where the basic file is used to identify that the file has been signed, and the extension file is used to identify the number of vendor signature data of different terminal devices and The vendor signature data of each terminal device is signed APK The specific location in the file;

The terminal device server includes a first determining module, a positioning module, a first verification module, and a second verification module;

The first determining module is configured to acquire, by the terminal device, the signed signature from the acquiring institution signature server APK File, judge signed APK Whether there is vendor signature data generated by the terminal device manufacturer corresponding to the terminal device in the file;

The positioning module is configured to: after the terminal device determines that there is corresponding vendor signature data, pass the signed APK The file header of the file locates the vendor signature data;

The first verification module is configured to verify, by the terminal device, the legality of the vendor working public key certificate in the vendor signature data by using the vendor root public key certificate;

The second verification module is configured to: after the terminal device successfully verifies the legality of the working public key certificate of the manufacturer, the terminal device extracts the working public key verification signature data in the vendor working public key certificate, and allows the installation or operation after the verification is passed.

The beneficial effects of the present invention are: a multi-party authorized APK Signature method and system, including by signature server pairs of different terminal devices APK The signed data of the file is respectively signed and operated to generate the respective signature data, and then adopted by the acquiring institution in order. DER Format composition signed APK File, signed APK The file includes the number of the terminal device and the signature data of each terminal device manufacturer that have been subjected to the signature operation and is signed. APK The header of the file where the file is used for different terminal devices to get signed APK After the file is extracted, the corresponding signature data of the terminal device needs to be verified for legality, and the verification can be performed after the verification. APK Install or run.

Through the invention, the terminal device is required to download APK In the process, only need to identify the signed one that has been signed by its own terminal device. APK File, and after locating the signature data of its own terminal device, use its own verification mechanism to verify the legality. After the verification is passed, it can be allowed. APK Install or run. The invention guarantees the signature APK After the transmission process, the integrity and legality can realize that the terminal equipment of different manufacturers only need to maintain their own signature verification mechanism, which greatly reduces the maintenance cost of the customer.

DRAWINGS

Figure 1 Multi-authorized for the present invention APK Flow diagram of the signature method;

Figure 2 Multi-authorized for the present invention APK Steps in the signature method 5 Specific process block diagram;

Figure 3 Multi-authorized for the present invention APK a block diagram of the signature system;

Figure 4 Multi-authorized for the present invention APK a block diagram of the composition of the acquirer server in the signature system;

Figure 5 Multi-authorized for the present invention APK a block diagram of the first verification module in the signature system;

Figure 6 Multi-authorized for the present invention APK A block diagram of the composition of the second verification module in the signature system.

The main components of the symbol description:

Terminal equipment manufacturer server  1 ; Acquirer server  2 ; Terminal device server  3

First generation module  010 ; Second generation module  011 ; First signature module  012 ;

Second signature module  020 ; First judgment module  030 ; Positioning module  031 ;

First verification module  032 ; Second verification module  033 ; Third signature module 021 ;

Write module  022 ; Second judgment module  023 ; Second judgment unit  0321 ;

Third judgment unit  0322 ; First arithmetic unit 0331 ; Third judgment unit 0332 .

detailed description

The terminal equipments of different manufacturers generate signature data of the signatures of the signed data, and then send the vendor signature data to the signing server of the acquiring institution, and the signature server of the acquiring institution adopts DER Format composition signed APK File, vendor's terminal device installed or running signed APK When the file is obtained, the manufacturer obtains the signature data of the vendor corresponding to the terminal device for verification, and the installation or operation is performed after the verification is passed. APK Document, the invention is convenient to expand DER The format code stores the signature data of different vendors, and the terminal device only needs to obtain and check the data of the manufacturer's signature corresponding to the manufacturer, and implement the verification mechanism for different vendors. Android The terminal device only needs to maintain a set of signature implementation mechanism, and the cost of the different signing mechanism of different terminal equipment manufacturers needs to be maintained at the same time.

The detailed description of the technical contents, structural features, and the objects and effects of the present invention will be described in detail below with reference to the accompanying drawings.

Please refer to the picture 1 Multi-authorized for the present invention APK A block diagram of the signature method.

Multi-party authorized APK Signature methods, including:

: Different terminal equipment manufacturers CA Each server generates a vendor root public-private key pair, and generates a vendor root public key certificate from the vendor root public key; each terminal device vendor signature server generates a vendor work public-private key pair, and distributes the work public key to the respective vendor. CA Server, vendor CA The server uses the vendor root private key to generate a vendor work public key certificate for the vendor work public key signature;

: Different terminal device vendor signature servers use their respective vendor work private key pairs including the original APK The signed data signature of the file generates signature data of different terminal device vendors, and the respective manufacturer work public key certificates are put into the respective manufacturer signature data or pre-installed in the terminal device according to different terminal device vendors' verification mechanisms; different terminals Device vendors pre-install their respective vendor root public key certificates in their respective terminal devices;

The acquirer signature server uses different vendor signature data generated by different terminal device vendor signature servers in the order of signature time. DER Format composition signed APK File; wherein the signed APK File includes original APK a file and a signature file header, the signature file header includes a base file and an extension file, where the basic file is used to identify that the file has been signed, and the extension file is used to identify the number of vendor signature data of different terminal devices and The vendor signature data of each terminal device is signed APK The specific location in the file;

: the terminal device obtains the signed signature from the acquirer signature server APK File, judge signed APK Whether there is vendor signature data generated by the terminal device manufacturer corresponding to the terminal device in the file, and after determining that there is corresponding vendor signature data, the terminal device passes the signed signature. APK The file header of the file locates the vendor signature data;

After obtaining the vendor root public key certificate, the terminal device uses the vendor root public key certificate to verify the legality of the vendor working public key certificate in the vendor signature data. After verifying the legality, the terminal device extracts the working public key verification signature data in the vendor working public key certificate. Allow installation or operation after verification.

This program adopts DER The format encodes the signature data of the terminal devices of different manufacturers after the respective signature operations, and sorts according to the time sequence of the signatures, and adopts DER The format is easy to be encoded, and it can well accommodate the manufacturer's signature data of different terminal equipment manufacturers, and they are independent. The signature file header described in this scenario identifies the signed APK The type of the file and the length of the offset and offset of the data after being signed by different vendors are used to determine whether there is signature data that has been signed by the own terminal device after downloading to the terminal device of different vendors; the signature file header is also used. Positioning signature data is signed APK File signed APK The specific location in the file facilitates the terminal devices of different manufacturers to obtain their respective signature data for their respective verifications. In the process of signing the respective terminal devices of different manufacturers, different vendors will put their respective manufacturer's work public key certificates into their respective generated manufacturer's signature data or pre-installed in the terminal device according to their own needs. When the terminal device performs the verification, the manufacturer's work public key pre-installed in the manufacturer's terminal device does not need to verify the legality and is directly used for the verification, and the manufacturer's work public key certificate stored in the terminal device manufacturer's signature data needs to be used. The manufacturer's root public key certificate is used to verify its legality. After verification, the subsequent verification steps can be continued. Otherwise, the signature data is invalid.

This solution realizes that the terminal device is downloading APK When you file, you only need to recognize the signed APK The file has the signature data signed by the own terminal device, locates and obtains the corresponding signature data, and uses its own verification mechanism to verify the legality. After verification, it can run. APK The method of installation or operation, through this program can not only quickly verify the signature APK After the transmission is complete and legal, the customer who purchases the terminal equipment of different manufacturers can no longer need to maintain the different signature verification mechanisms of the terminal equipment of different manufacturers at the same time, which greatly reduces the maintenance cost of the customer.

Embodiment 1:

Based on the above solution, the embodiment further includes steps S1 Previously included the following steps:

The acquirer signature server will be original APK File tail padding 0x00 Four bytes are filled to ensure original APK End of file 0x00 After the end as the signed data;

step S3 Also includes:

: The identity, version and original of the signed data will be signed by the acquirer's signature server. APK The length of the file and the check value are written into the base file;

step S4 Said in the judgment APK Whether there is a terminal device manufacturer signature data corresponding to the terminal device in the file is specifically:

According to signed APK The identifier and version of the different signed data in the basic file of the signature file header in the file determine whether there is signature data belonging to the own terminal device.

In this implementation manner, the terminal devices of different vendors are respectively implemented for verification and acquisition. APK At the same time, the specific implementation steps are also included in the steps. S1 The previous signatory server of the acquirer will be original APK File for four bytes, insufficient 0x00 Fill and fill in at the end 4 One 0x00 To ensure that the original file is APK At the end of 0x00 For subsequent coding. In the steps S2 Also includes the identity, version, and original of the signed data that the acquirer signature server will be signed. APK The length of the file and the check value are written into the base file for the step S3 When downloading to a different terminal device, the terminal device determines whether the signature operation of the own terminal device is performed by using the identifier, version, and check value of the signed data in the base file.

Embodiment 2:

Based on the above solution, the embodiment further includes steps S1 The different terminal device vendor signature servers use their respective vendor work private key pairs to include the original APK The signed data signature of the file generates different terminal device vendor signature data" specifically includes:

Different terminal equipment vendor signature servers will include the original APK The signed data of the file is calculated by hashing to get the hash value. HASH 1 ; will hash HASH 1 Signed according to a certain signature filling method to get signed APK File; will be signed APK The file uses the working private key of the terminal device manufacturer's signature server to perform a signature operation to generate signature data of different terminal device vendors.

This embodiment implements the verification of each terminal device of different manufacturers. APK At the same time, it also includes specific different terminal device manufacturers' signature servers with their respective working private key pairs including the original APK The specific process of signing the signed data of the file to generate signature data of different terminal device vendors, and obtaining a hash value by performing hash calculation on the signed data HASH 1 And hash value HASH 1 according to PKCS#1-V1.5 The signature filling method is filled to obtain the signed file, and the signed file is signed by the private key to generate the terminal device manufacturer signature data, and is added to adopt DER Mode coded signed APK In the file, modify the signed at the same time APK The file header of the file adds the offset and length of the currently added vendor terminal device vendor signature data to the corresponding extension field of the file header. According to this method, the signature data signed by different vendor terminal devices is followed. DER The coding format is exhausted, which facilitates the expansion of data and facilitates the acquisition of corresponding signature data of terminal devices of different manufacturers during the verification.

Please refer to the picture 2 , a multi-party authorization for the invention APK Steps in the signature method 5 The specific process block diagram.

Embodiment 3:

Based on the above solution, the embodiment is further included in the step S5 Specifically include:

: Determine whether the vendor work public key certificate is pre-installed in the terminal device, and if so, obtain the vendor work public key certificate, and enter the step S53 If not, pass the signed APK The file header of the file is located and obtains the vendor signature data corresponding to the device terminal;

: Obtain the vendor work public key certificate in the vendor signature data; the terminal device uses the pre-installed vendor root public key certificate to verify the legality of the vendor work public key certificate in the vendor signature data, and enter the step after the verification is passed. S53 ;

: The terminal device extracts the work public key verification signature data in the vendor work public key certificate and calculates a hash to obtain a hash value. HASH 2 ; judging the hash value HASH 1 And hash value HASH 2 Is it consistent, if it is, then it is signed APK File legal, allowed APK Installation; if not, then judged signed APK File is not legal, not allowed APK installation.

The embodiment specifically includes the step of obtaining a legal work public key after determining the signature file after the signature operation of the own terminal device. Specifically, determining whether the device terminal has a pre-installed legal work public key, if any, Obtaining the legal work public key directly into the location to obtain the signature data step to decrypt the signature data; if not, extracting the terminal device work public key certificate from the obtained signature data, and using the vendor root public key certificate pre-installed in the terminal device Verify the validity of the working device public key certificate of the terminal device. After the verification is passed, the signature data is decrypted by using the public key in the working public key certificate. The hash value is obtained by performing a hash on the acquired signature data again. HASH 2 , comparing the hash value of the signature data before it is transmitted HASH 1 Determine the legality and integrity of the signature data to ensure that the signature file has not been tampered with during transmission.

Please refer to the picture 3 Multi-authorized for the present invention APK A block diagram of the composition of the signature system.

Another technical solution adopted by the present invention is:

Multi-party authorized APK Signature system, including terminal equipment vendor servers 1 Acquirer server 2 And terminal device server 3 ;

Terminal device manufacturer server 1 Including the first generation module 010 Second generation module 011 And first signature module 012 ;

The first generation module 010 For different terminal equipment manufacturers CA Each server generates a vendor root public-private key pair, generates a vendor root public key certificate from the vendor root public key, and generates a vendor work public key certificate by using the vendor root private key to sign the vendor work public key;

The second generation module 011 Used by different terminal device manufacturers to generate a vendor's work public-private key pair and distribute the work public key to their respective vendors. CA server;

The first signature module 012 Used by different terminal device vendors to sign servers using their respective vendor work private key pairs including original APK The signed data signature of the file generates signature data of different terminal device vendors, and the respective manufacturer work public key certificates are put into the respective manufacturer signature data or pre-installed in the terminal device according to different terminal device vendors' verification mechanisms; different terminals Device vendors pre-install their respective vendor root public key certificates in their respective terminal devices;

The acquirer server 2 Including the second signature module 020 ;

The second signature module 020 Used by the acquiring institution signature server to adopt different vendor signature data generated by different terminal device manufacturer signature servers according to the order of signature time. DER Format composition signed APK File; wherein the signed APK File includes original APK a file and a signature file header, the signature file header includes a base file and an extension file, where the basic file is used to identify that the file has been signed, and the extension file is used to identify the number of vendor signature data of different terminal devices and The vendor signature data of each terminal device is signed APK The specific location in the file;

Terminal device server 3 Including the first judgment module 030 Positioning module 031 First verification module 032 And second verification module 033 ;

The first determining module 030 For the terminal device to obtain the signed from the acquirer signature server APK File, judge signed APK Whether there is vendor signature data generated by the terminal device manufacturer corresponding to the terminal device in the file;

Positioning module 031 , after the terminal device determines that there is corresponding vendor signature data, and passes the signed APK The file header of the file locates the vendor signature data;

The first verification module 032 For the terminal device to verify the legality of the vendor working public key certificate in the vendor signature data by using the vendor root public key certificate;

The second verification module 033 After the terminal device successfully verifies the legality of the working public key certificate of the manufacturer, the terminal device extracts the working public key verification signature data in the manufacturer's working public key certificate, and allows the installation or operation after the verification is passed.

Please refer to the picture 4 , a multi-party authorization for the invention APK Acquirer server in the signature system 2 The composition of the block diagram.

Embodiment 4:

On the basis of the foregoing solution, the acquiring institution of the embodiment further includes a third signature module. 021 Write module 022 And second judgment module 023 ;

The third signature module 021 , used for the acquirer signature server will be original APK File tail padding 0x00 Four bytes are filled to ensure original APK End of file 0x00 After the end as the signed data;

The write module 022 , for the identity, version, and original of the signed data that the acquiring institution signature server will be signed APK The length of the file and the check value are written into the base file;

The second determining module 023 For the acquiring institution signature server to determine whether there are different terminal device manufacturers that need to perform the signing operation, if yes, different terminal device manufacturers call their respective manufacturer signature servers to perform the signing operation, and modify the signature file header; if not, then End.

The modifying the signature file header in the embodiment includes modifying the length of the file body in the basic file in the file header, and adding the signature data content after the new terminal device manufacturer signature operation in the extended file.

Embodiment 5:

The first signature module in the embodiment is based on the foregoing solution. 012 Including a signature unit;

The signature unit for different terminal device vendor signature servers will include the original APK The signed data of the file is calculated by hashing to get the hash value. HASH 1 ; will hash HASH 1 Signed according to a certain signature filling method to get signed APK File; will be signed APK The file uses the working private key of the terminal device manufacturer's signature server to perform a signature operation to generate signature data of different terminal device vendors.

Please refer to the picture 5- Figure 6 , respectively, a multi-party authorization for the present invention APK The first verification module in the signature system 032 Block diagram of the composition and a multi-party authorization of the present invention APK Second verification module in the signature system 033 The composition of the block diagram.

Embodiment 6:

Based on the foregoing solution, the first verification module in this implementation manner 032 Including the second judging unit 0321 And a third verification unit; the second verification module 033 First arithmetic unit 0331 And third judgment unit 03320322 ;

The second determining unit 0321 For judging whether the vendor work public key certificate is pre-installed in the terminal device, and if so, obtaining the vendor work public key certificate; if not, passing the signed APK The file header of the file is located and obtains the vendor signature data corresponding to the device terminal;

The third verification unit is configured to acquire, by the terminal device, a vendor work public key certificate in the vendor signature data; the terminal device uses the pre-installed vendor root public key certificate to verify the legality of the vendor work public key certificate in the vendor signature data;

The first arithmetic unit 0331 For the terminal device to extract the work public key verification signature data in the vendor work public key certificate and calculate the hash to obtain a hash value. HASH 2 ;

The third determining unit 03320322 For the terminal device to determine the hash value HASH 1 And hash value HASH 2 Is it consistent, if it is, then it is signed APK File legal, allowed APK Installation; if not, then judged signed APK File is not legal, not allowed APK installation.

The invention provides a multi-party authorized APK Signature method and its system, which are easy to expand DER Encoding the manufacturer's signature data generated by different terminal equipment manufacturers after their respective signature operations, and different terminal equipments are required for downloading. APK In the process, only the signature file signed by the own terminal device is identified, and after verifying the signature data of the terminal device, the verification validity is verified by using the verification mechanism of the terminal device, and the verification can be allowed after the verification is passed. APK Install or run. The invention ensures the signature APK After the integrity of the transmission, the signature data of the superimposed signature of the terminal equipment of multiple manufacturers is eliminated at the same time. Further, the maintenance cost of the customer is greatly reduced, and the customer only needs to maintain the terminal equipment of the manufacturer. Its own signature verification mechanism.

The above is only the embodiment of the present invention, and is not intended to limit the scope of the invention, and the equivalent structure or equivalent process transformation of the present invention and the contents of the drawings may be directly or indirectly applied to other related technologies. The fields are all included in the scope of patent protection of the present invention.

Claims (8)

1. A multi-party authorized APK signature method, which is characterized in that:

   S1: Each terminal device manufacturer CA server generates a vendor root public-private key pair, and generates a vendor root public key certificate by using a vendor root public key; each terminal device vendor signature server generates a vendor work public-private key pair, and distributes the work public key to each The vendor CA server, the vendor CA server generates the vendor work public key certificate by using the vendor root private key to sign the vendor work public key;

   S2: Different terminal device manufacturer signature servers use different vendor work private keys to generate signed data signatures of the original APK file to generate different terminal device vendor signature data, and according to different terminal device manufacturers' verification mechanism, the respective manufacturer work public key certificates are used. Put into the generated manufacturer's signature data or pre-installed in the terminal device; different terminal device manufacturers pre-install their respective vendor root public key certificates in their respective terminal devices;

   S3: The acquiring institution signature server uses different DER format data generated by different terminal device manufacturer signature servers in the order of signature time to form a signed APK file; wherein the signed APK file includes the original APK file and the signature file. The header file includes a basic file and an extended file, where the basic file is used to identify that the file has been signed. The extended file is used to identify the number of vendor signature data of different terminal devices and different terminal devices. The specific location of the vendor signature data in the signed APK file;

   S4: The terminal device obtains the signed APK file from the acquiring institution signature server, and determines whether there is a vendor signature data generated by the terminal device manufacturer corresponding to the terminal device in the signed APK file, and determines that there is a corresponding vendor signature data. Afterwards, the terminal device locates the vendor signature data by using a file header of the signed APK file;

   S5: After obtaining the vendor root public key certificate, the terminal device uses the vendor root public key certificate to verify the legality of the vendor working public key certificate in the vendor signature data, and after verifying the legality, the terminal device extracts the working public key verification signature data in the vendor working public key certificate. After the verification is passed, it is allowed to install or run.
2. The multi-party authorized APK signature method according to claim 1, wherein before step S1, the method further comprises:

   The acquirer signature server fills the original APK file with 0x00 four bytes to ensure that the original APK file ends with 0x00 and is used as the signed data.

   Step S3 further includes:

   S31: The acquiring institution signature server writes the identifier of the signed data, the version, and the length and check value of the original APK file into the basic file;

   In the step S4, “determining whether there is a terminal device manufacturer signature data corresponding to the terminal device in the signed APK file” is specifically:

   It is determined whether there is signature data belonging to the own terminal device according to the identifier and version of the different signed data in the basic file of the signature file header in the signed APK file.
3. The multi-party authorized APK signature method according to claim 1, wherein in step S2, the "different terminal device manufacturer signature servers generate signature data signatures including the original APK file using respective vendor work private keys. The signature data of different terminal equipment manufacturers specifically includes:

   The signature server of different terminal equipment manufacturers will calculate the hash of the signed data of the original APK file to obtain the hash value HASH 1; the hash value HASH 1 is filled according to a certain signature filling method to obtain the signed APK file; the APK file will be signed. The signature operation of the terminal device manufacturer's signature server is used to generate different terminal device vendor signature data.
4. The multi-party authorized APK signature method according to claim 3, wherein the step S5 specifically includes:

   S51: determining whether the vendor work public key certificate is pre-installed in the terminal device, and if yes, obtaining the vendor work public key certificate, and proceeding to step S53; if not, passing the signed APK The file header of the file is located and obtains the vendor signature data corresponding to the device terminal;

   S52: Obtain a vendor work public key certificate in the vendor signature data; the terminal device uses the pre-installed vendor root public key certificate to verify the legality of the vendor work public key certificate in the vendor signature data, and after the verification passes, proceeds to step S53;

   S53: The terminal device extracts the work public key verification signature data in the vendor work public key certificate and calculates a hash to obtain a hash value HASH 2; determines whether the hash value HASH 1 and the hash value HASH 2 are consistent, and if yes, determines that the Signature APK file is legal, allowing APK to be installed; if not, it is determined that the signed APK file is illegal and APK is not allowed to install.
5. A multi-party authorized APK signature system, which comprises a terminal device manufacturer server, an acquirer server and a terminal device server;

   The terminal device manufacturer server includes a first generation module, a second generation module, and a first signature module;

   The first generation module is configured to generate a vendor root public-private key pair by each terminal device manufacturer CA server, generate a vendor root public key certificate from the vendor root public key, and generate a vendor work public signature by using the vendor root private key to the vendor work public key. Key certificate

   The second generation module is configured to generate a vendor public-private key pair for each terminal device vendor signature server, and distribute the work public key to a respective vendor CA server;

   The first signature module is used by different terminal device manufacturer signature servers to generate signature data of different terminal device vendors by using the respective vendor work private keys to generate signed data signatures of the original APK file, according to the verification mechanism of different terminal device vendors. The respective manufacturer's work public key certificates are placed in the respective manufacturer's signature data or pre-installed in the terminal device; different terminal device manufacturers pre-install their respective vendor root public key certificates in their respective terminal devices;

   The acquirer server includes a second signature module;

   The second signature module is configured to use the DER format to form a signed APK file by using the DER format of different vendor signature data generated by different terminal device manufacturer signature servers according to the signature time sequence; wherein the signed APK file is The original APK file and the signature file header are included, and the signature file header includes a basic file and an extended file, where the basic file is used to identify that the file has been signed. The extended file is used to identify the vendor signature data of different terminal devices. The number and the specific location of the vendor signature data of each terminal device in the signed APK file;

   The terminal device server includes a first determining module, a positioning module, a first verification module, and a second verification module;

   The first determining module is configured to obtain, by the terminal device, the signed APK file from the acquiring institution signature server, and determine whether the signed APK file has vendor signature data generated by the terminal device manufacturer corresponding to the terminal device;

   The positioning module is configured to: after the terminal device determines that there is corresponding vendor signature data, locate the vendor signature data by using a file header of the signed APK file;

   The first verification module is configured to verify, by the terminal device, the legality of the vendor working public key certificate in the vendor signature data by using the vendor root public key certificate;

   The second verification module is configured to: after the terminal device successfully verifies the legality of the working public key certificate of the manufacturer, the terminal device extracts the working public key verification signature data in the vendor working public key certificate, and allows the installation or operation after the verification is passed.
6. The multi-party authorized APK signature system according to claim 5, wherein the acquiring institution further comprises a third signature module, a writing module and a second determining module;

   The third signature module is used by the acquiring institution signature server to fill the original APK file tail with 0x00 four bytes, to ensure that the original APK file tail ends with 0x00 as the signed data;

   The writing module is used by the acquiring institution signature server to write the identifier of the signed data, the version and the length of the original APK file and the check value into the basic file;

   The second determining module is configured to determine, by the acquiring institution, the signing server, whether different terminal device manufacturers need to perform a signing operation, and if so, different terminal device manufacturers call their respective vendor signature servers to perform a signing operation, and modify the signature file. Head; if not, it ends.
7. The multi-party authorized APK signature system according to claim 5, wherein the first signature module comprises a signature unit;

   The signature unit is used by different terminal device manufacturers to calculate a hash of the signed data of the original APK file to obtain a hash value HASH 1; and the hash value HASH 1 is filled according to a certain signature filling method to obtain a signed APK. File; the signed APK file is signed by the working device private key of the terminal device manufacturer's signature server to generate different terminal device vendor signature data.
8. The multi-party authorized APK signature system according to claim 5, wherein the first verification module comprises a second determination unit and a third verification unit; the second verification module comprises a first operation unit and a Three judgment unit;

   The second determining unit is configured to determine whether the vendor work public key certificate is pre-installed in the terminal device, and if yes, obtain the vendor work public key certificate; if not, locate and obtain the device terminal by using the file header of the signed APK file Corresponding vendor signature data;

   The third verification unit is configured to acquire, by the terminal device, a vendor work public key certificate in the vendor signature data; the terminal device uses the pre-installed vendor root public key certificate to verify the legality of the vendor work public key certificate in the vendor signature data;

   The first operation unit is configured to: the terminal device extracts the work public key verification signature data in the vendor work public key certificate and calculates a hash to obtain a hash value HASH 2;

   The third determining unit is configured to determine, by the terminal device, whether the hash value HASH 1 and the hash value HASH 2 are consistent. If yes, determine that the signed APK file is legal, and allow the APK to be installed and run; if not, determine the signed APK The file is not legal and does not allow the APK to be installed or run.