CN114553426B - Signature verification method, key management platform, security terminal and electronic equipment - Google Patents

Abstract

The application provides a signature verification method, a key management platform, a security terminal and electronic equipment, the method comprising: sending a first data writing instruction to the security terminal through a blockchain client; The security terminal responds to the first random number generated by the first data write instruction; sends a second data write instruction to the security terminal through the block chain client, and the second data write instruction Including a second random number, a first signature and ciphertext data, the first signature is a signature generated according to the first random number, and the ciphertext data is data obtained by encrypting target data; The block chain client obtains the second signature generated by the security terminal, and verifies the second signature. Two signatures generated by random numbers. This application can improve data security.

Description

Signature verification method, key management platform, secure terminal and electronic equipment

technical field

The present application relates to the technical field of blockchain, and more specifically, relates to a signature verification method, a key management platform, a security terminal and electronic equipment.

Background technique

In the blockchain system, each blockchain node realizes data transmission through an address identification similar to an email address. At the same time, the sender needs to sign the data information sent every time the data is transmitted. After receiving the data information, the receiver needs to Signature verification is carried out to prove the credibility of data information and prevent the flooding of false data services. However, data such as public and private keys are stored on blockchain nodes, and the data security is low.

Contents of the invention

Embodiments of the present application provide a signature verification method, a key management platform, a security terminal, and electronic equipment, so as to solve the problem of low data security.

In the first aspect, the embodiment of the present application provides a signature verification method applied to a key management platform, including:

Send the first data write instruction to the security terminal through the blockchain client;

Obtaining the first random number generated by the security terminal in response to the first data write instruction through the blockchain client;

Send a second data write instruction to the security terminal through the block chain client, the second data write instruction includes a second random number, a first signature and ciphertext data, and the first signature is based on The signature generated by the first random number, the ciphertext data is data obtained by encrypting the target data;

Obtain the second signature generated by the security terminal through the block chain client, and verify the second signature, the second signature is when the security terminal passes the verification of the first signature A signature generated according to the second random number.

In the second aspect, the embodiment of the present application also provides a signature verification method applied to a secure terminal, including:

Receive the first data write instruction sent by the key management platform through the blockchain client;

generating a first random number in response to the first data write instruction, and sending the first random number to the key management platform through the blockchain client;

Receive the second data writing instruction sent by the key management platform through the block chain client, the second data writing instruction includes the second random number, the first signature and ciphertext data, the first The signature is a signature generated by the key management platform according to the first random number, and the ciphertext data is data obtained by encrypting target data by the key management platform;

Verifying the first signature, and writing the ciphertext data when verifying that the first signature is passed, and generating a second signature according to the second random number;

Send the second signature to the key management platform through the block chain client.

In the third aspect, the embodiment of the present application also provides a key management platform, including:

The first sending module is used to send the first data writing instruction to the security terminal through the block chain client;

A first obtaining module, configured to obtain, through the blockchain client, a first random number generated by the security terminal in response to the first data write instruction;

The second sending module is configured to send a second data writing instruction to the security terminal through the block chain client, the second data writing instruction includes a second random number, a first signature and ciphertext data, The first signature is a signature generated according to the first random number, and the ciphertext data is data obtained by encrypting target data;

The second obtaining module is used to obtain the second signature generated by the security terminal through the block chain client, and verify the second signature, and the second signature is that the security terminal is verifying the A signature generated according to the second random number when the first signature is passed.

In the fourth aspect, the embodiment of the present application further provides a security terminal, including:

The first sending module is used to receive the first data writing instruction sent by the key management platform through the block chain client;

A generating module, configured to generate a first random number in response to the first data write instruction, and send the first random number to the key management platform through the blockchain client;

A receiving module, configured to receive a second data write instruction sent by the key management platform through the block chain client, the second data write instruction includes a second random number, a first signature and ciphertext data , the first signature is a signature generated by the key management platform according to the first random number, and the ciphertext data is data obtained by encrypting target data by the key management platform;

A verification module, configured to verify the first signature, write the ciphertext data in the case of passing the verification of the first signature, and generate a second signature according to the second random number;

The second sending module is configured to send the second signature to the key management platform through the block chain client.

In the fifth aspect, the embodiment of the present application also provides an electronic device, including a processor, a memory, and a program or instruction stored in the memory and running on the processor, and the program or instruction is executed by the processor When executed, the steps in the signature verification method disclosed in the first aspect of the embodiment of the present application are realized, or, when the program or instruction is executed by the processor, the signature verification method disclosed in the second aspect of the embodiment of the present application is realized in the steps.

In this way, in this embodiment, the key management platform sends a second data write instruction to the security terminal through the blockchain client, and the second data write instruction includes the second random number, the first signature and ciphertext data, the first signature is a signature generated according to the first random number, the ciphertext data is data obtained by encrypting target data, and the ciphertext data can be stored in the safe In the terminal, the target data is invisible to all nodes of the block chain, thereby achieving the technical effect of improving the security of the target data.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the accompanying drawings that need to be used in the description of the embodiments or prior art. Obviously, the accompanying drawings in the following description are only some of the present application. Embodiments, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without paying creative labor.

FIG. 1 is a schematic flow diagram of a signature verification method provided in an embodiment of the present application;

Fig. 2 is a schematic flowchart of another signature verification method provided by the embodiment of the present application;

FIG. 3 is a schematic structural diagram of a key distribution system provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a security terminal provided by an embodiment of the present application;

Fig. 5 is a schematic structural diagram of a security module provided by an embodiment of the present application;

Fig. 6 is a schematic flowchart of another signature verification method provided by the embodiment of the present application;

Fig. 7 is a schematic flowchart of another signature verification method provided by the embodiment of the present application;

FIG. 8 is a schematic structural diagram of a key management platform provided by an embodiment of the present application;

FIG. 9 is a schematic structural diagram of another key management platform provided by the embodiment of the present application;

FIG. 10 is a schematic structural diagram of another key management platform provided by the embodiment of the present application;

FIG. 11 is a schematic structural diagram of a security terminal provided by an embodiment of the present application;

Fig. 12 is a schematic structural diagram of another security terminal provided by an embodiment of the present application;

FIG. 13 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of this application.

Please refer to Figure 1, Figure 1 is a schematic flow diagram of a signature verification method provided in the embodiment of this application, which is applied to the key management platform, as shown in Figure 1, including the following steps:

Step 101. Send the first data writing instruction to the security terminal through the blockchain client.

Among them, the above-mentioned blockchain client and the above-mentioned security terminal may have a corresponding relationship, for example: the above-mentioned security terminal can be used as a trusted carrier of the blockchain user node, and the sensitive data such as the corresponding key of the above-mentioned blockchain client can be stored In the corresponding security terminal, but not visible to other blockchain nodes.

Wherein, the above-mentioned first data writing instruction may be an instruction that triggers the above-mentioned security terminal to send a random number, for example: during the signature verification process, the above-mentioned key management platform may generate a first signature through the first random number generated by the above-mentioned security terminal, The security terminal can verify the legitimacy of the identity of the key management platform through the first signature.

Step 102. Obtain the first random number generated by the security terminal in response to the first data write instruction through the blockchain client.

Wherein, the first random number may be generated by a security module in the security terminal, identity information (such as a private key) of the security terminal may be stored in the security module, and the security module may provide a signature capability.

Step 103: Send a second data write instruction to the security terminal through the blockchain client, the second data write instruction includes a second random number, a first signature and ciphertext data, and the first The signature is a signature generated according to the first random number, and the ciphertext data is data obtained by encrypting target data.

Wherein, the above-mentioned target data may be sensitive data that needs to be stored by the above-mentioned security terminal, for example: sensitive data such as identity key of the security module, service key, and unique identifier of the data consumer. In addition, the target data may be based on the security terminal distributing corresponding target data, so that the target data may form a mapping relationship with the security terminal.

Among them, the above-mentioned encryption can be completed in the encryption machine, for example: the above-mentioned key management platform is connected with the encryption machine, and all actions such as distribution and generation of keys can be completed in the encryption machine, so that the plaintext data will not be exposed to the outside world.

Step 104, obtain the second signature generated by the security terminal through the block chain client, and verify the second signature, the second signature is that the security terminal passes the verification of the first signature In the case of the signature generated according to the second random number.

Wherein, the above-mentioned second signature can be used to verify the legitimacy of the identity of the above-mentioned security terminal. When the above-mentioned security terminal verifies that the identity of the above-mentioned key management platform is legal through the above-mentioned first signature, the above-mentioned second signature is generated and transmitted to the above-mentioned key management platform. platform, so that the above-mentioned key management platform and the above-mentioned security terminal can conduct two-way authentication.

In addition, when the second signature verification is passed, that is, a secure channel is established between the key management platform and the security terminal, the key management platform may repeat the above steps to realize the distribution of all data.

In this embodiment, the key management platform sends a second data writing instruction to the security terminal through the blockchain client, and the second data writing instruction includes a second random number, a first signature and Ciphertext data, the first signature is a signature generated according to the first random number, the ciphertext data is data obtained by encrypting target data, and the ciphertext data can be stored in the security terminal , the target data is invisible to all nodes in the blockchain, thereby achieving the technical effect of improving the security of the target data.

In addition, the security terminal generates the second signature according to the second random number when the first signature is verified, and obtains the security terminal's verification of the first signature through the blockchain client. When the signature is passed, the second signature is generated according to the second random number, and the second signature is verified, and the legal identity of both parties can be verified each other to complete the data delivery, thereby improving the security of data transmission and confidentiality.

Optionally, before sending the second data writing instruction to the security terminal through the blockchain client, the method further includes:

Obtaining a function list supported by the security terminal through the blockchain client, and judging whether the security terminal supports key negotiation according to the function list;

If the secure terminal does not support key negotiation, encrypt the target data with a preset key to obtain the ciphertext data;

If the security terminal supports key negotiation, negotiate with the security terminal to obtain a session key, and use the session key to encrypt the target data to obtain the ciphertext data.

Wherein, the aforementioned preset key may be a management key preset in the aforementioned security terminal, for example: when the identity authentication key and the corresponding service key in the aforementioned security terminal are loaded, the aforementioned encryption key is completed through the preset key. The establishment of a secure channel between the key management platform and the above-mentioned secure terminal can reduce resource overhead and improve efficiency.

Wherein, the above-mentioned judging whether the security terminal supports key negotiation can be judged by whether there is a negotiation key in the security terminal, for example: the private key of the negotiation key can be preset in the security terminal during the production process of the security terminal In the security module, if the security terminal has the negotiation key, it can negotiate with the key management platform to obtain the session key.

In this embodiment, it is judged according to the function list whether the security terminal supports key negotiation, and the target data is encrypted using the preset key or session key, and if the security terminal does not support key negotiation In some cases, using the preset key to establish a secure channel between the key management platform and the secure terminal can reduce resource overhead, improve efficiency and user experience; in the case that the secure terminal supports key negotiation, and The security terminal negotiates to obtain a session key, and uses the session key to encrypt the target data to obtain the ciphertext data, which can ensure data integrity and confidentiality.

Optionally, the negotiating with the secure terminal to obtain the session key includes:

Send a key agreement instruction to the security terminal through the block chain client, the key agreement instruction includes a third random number, a session key factor ciphertext, and a third signature, and the session key factor ciphertext The data obtained by encrypting the generated session key factor;

Receive the fourth signature sent by the security terminal in response to the key agreement instruction through the blockchain client, where the fourth signature is decrypted by the security terminal after verifying that the third signature passes The session key factor ciphertext generates a session key, and generates a signature based on the session key and the third random number;

Verifying the fourth signature, and obtaining the session key based on the session key factor when the fourth signature is verified to pass.

Wherein, the above-mentioned session key factor encryption can be encrypted by a preset key. For example, if the above-mentioned secure terminal supports key negotiation, the above-mentioned secure terminal stores the private key of the negotiated key, and the above-mentioned key management platform corresponds to The public key of the negotiation key is stored, and the generated session key factor may be encrypted using the public key of the negotiation key to obtain the ciphertext of the session key factor.

Wherein, the fact that the fourth signature verification is passed can be understood as that the key management platform and the security terminal have finished negotiating, and both the key management platform and the security terminal can obtain the same session key according to the session key factor.

In this embodiment, by using the negotiated session key to encrypt the target data and calculate the signature, the integrity and confidentiality of the data can be guaranteed, thereby realizing the corresponding security of the target data from the key management platform to the blockchain client Terminal security delivery.

Optionally, before sending the second data writing instruction to the corresponding security terminal through the blockchain client, the method further includes:

Acquire the security terminal identifier, and generate the target data according to the security terminal identifier.

Among them, the above-mentioned target data can be obtained through a decentralized generation method, for example: use the method of secure terminal identification, version number and filling bytes to disperse the target data to form a block chain client to map a set of target data, each block chain The target data of the consumer node is not visible to other nodes.

In this embodiment, using the security terminal identifier to generate the target data can form a mapping relationship between a block chain user node corresponding to a group of target data, and different users have different encryption and decryption keys. It can decrypt the ciphertext data on the chain of different blockchain user nodes to improve data security and confidentiality.

Please refer to Figure 2, Figure 2 is a schematic flow diagram of another signature verification method provided by the embodiment of this application, which is applied to a security terminal, as shown in Figure 2, including the following steps:

Step 201: Receive the first data writing instruction sent by the key management platform through the blockchain client.

Step 202: Generate a first random number in response to the first data write instruction, and send the first random number to the key management platform through the blockchain client.

Step 203: Receive the second data writing instruction sent by the key management platform through the blockchain client, the second data writing instruction includes the second random number, the first signature and ciphertext data, so The first signature is a signature generated by the key management platform according to the first random number, and the ciphertext data is data obtained by encrypting target data by the key management platform.

Wherein, the above-mentioned key management platform can be connected with the encryption machine, the above-mentioned encryption can be completed in the encryption machine, and all operations such as distribution and generation of keys can be completed in the encryption machine.

Step 204: Verify the first signature, and if the first signature is verified, write the ciphertext data, and generate a second signature according to the second random number.

Wherein, the above verification of the first signature may be used to verify the legality of the identity of the key management platform, and the second signature may be used by the key management platform to verify the legality of the identity of the security terminal.

Wherein, the above-mentioned writing may be storing the above-mentioned ciphertext data in the security module of the above-mentioned security terminal. The module can also store the identity information (such as private key) of the above-mentioned blockchain client or the above-mentioned security terminal, and provide digital signature capabilities, hardware algorithm implementation capabilities for encryption and decryption, etc.

Step 205, sending the second signature to the key management platform through the blockchain client.

In this embodiment, by verifying the first signature, if the verification of the first signature is passed, the ciphertext data is written, and the second The signature is sent to the key management platform, which can store the encrypted ciphertext data of the target data, so that the target data is invisible to all nodes in the blockchain, thereby achieving the technical effect of improving the security of the target data.

In addition, the security terminal verifies the legitimacy of the identity of the key management platform through the first signature, and the key management platform verifies the legitimacy of the identity of the security terminal through the second signature. The two-way authentication between the key management platform and the security terminal can improve the security of data transmission and prevent the existence of a malicious party.

In addition, through the security terminal to store the identity information of the blockchain client and realize the hardware algorithm of digital signature and encryption and decryption, it can prevent Channel attacks and physical attacks such as SPA (Simple power analysis) or DPA (Differential Power Analysis) can achieve higher storage security and higher algorithm execution efficiency.

Optionally, before receiving the second data write instruction sent by the key management platform through the blockchain client, the method further includes:

sending a supported function list to the key management platform through the blockchain client, so that the key management platform can determine whether to support key negotiation according to the function list;

In the case of supporting key negotiation, negotiate with the key management platform to obtain the session key.

Wherein, the above-mentioned function list may include whether the above-mentioned security terminal supports the key agreement function, for example: when the above-mentioned security terminal is loaded with an identity authentication key and a corresponding service key, the above-mentioned security terminal cannot support the above-mentioned key agreement function.

In this embodiment, when key negotiation is supported, a session key is obtained through negotiation with the key management platform, and the target data is encrypted using the session key obtained through negotiation, which can ensure the security of the target data. Integrity and confidentiality, completing the safe delivery of target data from the key management platform to the security terminal.

Optionally, the negotiation with the key management platform to obtain the session key includes:

The key agreement instruction sent by the key management platform is received by the block chain client, the key agreement instruction includes a third random number, a session key factor ciphertext and a third signature, and the session key The factor ciphertext is the data obtained by encrypting the generated session key factor by the key management platform;

Verifying the third signature in response to the key agreement instruction, if the verification of the third signature is passed, decrypting the ciphertext of the session key factor to generate a session key, and according to the session key and the The third random number generates the fourth signature;

Sending the fourth signature to the key management platform through the block chain client.

In this embodiment, by using the negotiated session key to encrypt the target data and calculate the signature, the integrity and confidentiality of the data can be guaranteed, thereby realizing the corresponding security of the target data from the key management platform to the blockchain client Terminal security delivery.

As a specific embodiment, please refer to Figure 3. Figure 3 shows a key distribution system that can be applied to the signature verification method in the embodiment of this application. As shown in Figure 3, the system 300 includes a blockchain system 301 , key management platform 302 , cipher machine 303 , security terminal system 304 and identity authentication system 305 .

Among them, the blockchain system 301 includes a blockchain client SDK (Software Development Kit, software development kit) and HTTP REST (Representation State Transfer, presentation layer state conversion) interface, and the security terminal system 304 includes multiple security terminals.

As shown in Figure 4, the security terminal is equipped with hardware such as a baseband communication computer minimum system 401, a touch screen 402, a security module 403, an information collection module 404, a communication module 405, and a power supply module 406, and runs a graphical interface operating system and embedded software. equipment. Security terminals can obtain items and materials with unique identification codes or exchange information between security terminals through contact or non-contact methods (camera code scanning, induction, wired connection or wireless communication, etc.). The security terminal can generate property rights transfer registration information and directly apply for chaining to the blockchain system. The security terminal is a registration device that both the party that transfers the property rights and the party that transfers the property rights should have. The minimum baseband communication computer system 401 is mainly composed of a baseband chip, a radio frequency chip, a clock, a non-volatile memory, and a volatile memory. Interface and IO (Input/Output, input/output), etc. The touch screen 402 can be a capacitive or resistive touch screen, which provides graphic display capability on the one hand and touch control capability on the other hand. The information collection module 404 may include information collection devices such as cameras, NFC (Near Field Communication, near field communication) or infrared scanning. The communication module 405 can provide Bluetooth (Bluetooth), WIFI (Wireless Fidelity, wireless fidelity) and other short-distance communication capabilities. The power module 406 may be composed of a battery, a charging circuit, an interface and the like. The security terminal is equipped with a security module inside, and the security unit of the security module stores the identity information (such as a private key) of the security terminal and provides a signature capability, and the security module can be called externally through the interface to digitalize the input data using the private key stored in the security module. signature, but the outside cannot directly obtain private key information through the interface; the SIM (Subscriber Identity Module, Subscriber Identity Module) unit of the security module 403 provides cellular network communication capabilities.

Wherein, as shown in FIG. 5 , the security module 403 may be a minimum security computing unit including a security storage medium 4031, an MCU (Microcontroller Unit, micro control unit) 4032, a control circuit logic 4033, a communication module 4034, and a display module 4035. The medium 4031 is based on the safety design of anti-channel attack, laser attack, physical destruction, etc., and the safe storage medium 4031 can be FLASH (flash memory), ROM (Read-Only Memory, read-only memory), EEPROM (Electrically Erasable Programmable ROM) , Chargeable Erasable Programmable Read-Only Memory), OTP (One Time Programmable, One Time Programmable) and other non-volatile storage devices, which can safely store sensitive data and effectively prevent leakage. MCU4032 and control circuit logic 4033 cooperate to complete the operation of the on-chip embedded operating system, and provide external security services such as signature and encryption and decryption. The communication module 4034 is mainly used to complete the docking with the account authority management system, provide a hardware interaction interface, and provide power for the security module at the same time, mainly in the form of a USB (Universal Serial Bus, Universal Serial Bus) interface. The display module 4035 may be an LCD (Liquid Crystal Display, liquid crystal display), and the LCD is used for prompting the current status of the security module, mainly including power-on, normal, abnormal and so on.

The key management platform 302 cooperates with the cipher machine 303 to form a complete key management system, which is a server application composed of background, database and other technologies, and is mainly used to complete security module identification collection, key distribution, key distribution and data management and other functions. When the security module needs to load or update the key, the blockchain user client SDK will send a key loading or updating application, and the key management platform 302 will pass the two-way authentication. After the authentication is passed, it will respond to the application to complete the loading and downloading of the key. hair.

The identity authentication system 305 includes an identity authentication platform and a supporting security module. The identity authentication platform is a server application composed of Web front-end, Web back-end, database and other technologies. On the one hand, the identity authentication system 305 provides account rights management capabilities (for example, the administrator or operator stores the public key and ID of the authorized security terminal in the blockchain, and the administrator or operator stores the public key and ID of the authorized security module Store certificates in the block chain, etc.); users of the identity authentication system 305, including administrators, business roles (such as enterprises and organizations of related businesses in the alliance), etc., all need to use the security module to log in to the identity authentication system. This is because the user's private key and ID are stored in the security module, and the user uses the identity authentication system to execute the request using the private key signature; when the block chain system receives the request, it will use the block The corresponding public key and ID stored in the block chain are verified for signature; the request block chain that passes the verification will only be accepted.

Among them, the key management platform 302 is used to generate a 1024-bit RSA public-private key pair as the authorized public-private key pair of the data consumer, and at the same time generate the data consumer’s unique identifier DCID, and store it in the database for unified management; through the blockchain client The online security channel established between the SDK and the key management platform 302 writes the data consumer's unique identifier DCID, symmetric key, private key and authorization validity period into the security module of the security terminal; the data consumer's unique identifier DCID and public key Key storage certificate and blockchain; the client SDK of blockchain users is used in conjunction with the security module to check the validity period of the authorization. If it expires, the security module will become invalid. Signature verification methods can include the following procedures:

When the security module is started for the first time, the blockchain user client SDK inquires whether the security module has a business key or an identity authentication key, obtains the query information, and informs the key management center of the query information;

The key management center obtains the unique identifier and function list of the security module, and the function list includes whether the security module supports functions such as key negotiation;

According to whether there is a key, submit a key loading or key update application to the key management platform;

The security module receives the key update application;

The security module generates a random number SARand as a response and returns to the key management platform;

The key management platform selects a reasonable method according to the function list supported by the security module to encrypt the key to form ciphertext data, and at the same time the key management platform generates a random number SPRand, uses SARand to generate a signature, and converts the ciphertext data, SPRand After cascading with the signature data, send the data to update the security module key;

After the blockchain client SDK receives the delivered data, it forwards it to the security module, and the security module verifies the signature result of the key management platform to confirm the identity of the key management platform, and writes the current key data after the verification is passed. At the same time, use SPRand to generate a signature and upload it;

After the key management platform receives the signature data, it verifies whether the security module is legal, and then repeats the above steps to complete the distribution and writing of all keys.

Wherein, the random number SARand represents the above-mentioned first random number, the random number SPRand represents the above-mentioned second random number, the signature generated by using SARand represents the above-mentioned first signature, and the signature generated by using SPRand represents the above-mentioned second signature.

Among them, the above-mentioned blockchain users may include operators, financial service providers, regulators and other parties who need to view the data on the chain that meets the corresponding public key authority. The sensitive data of the participants need to be stored in the security module, and the participants need to store The sensitive data requirements are as follows:

Table 1

Among them, the structure of the key is stored in the form of "key header + key body". The key header mainly defines key-related attributes, and the key body refers to the key value. The specific definition is as follows:

Table 2

key type key ID key version key attempts key length key value

If the number of key errors exceeds the number of attempts, the security module will be locked, and the operator needs to perform an unlocking operation, otherwise the security module function cannot be used normally.

In this service, the management of symmetric keys (except the data encryption root key) adopts the root key -> sub-key decentralized management, that is, the server manages the root key, while the sub-key on the security module is managed by The root key is obtained through certain parameter operations. The decentralization level and related requirements of keys are as follows:

The management key must be preset when the security module is produced. The management key types include ISD key (the security module is the Java platform) and the master control key (the security module is the Native platform). The two-level structure is used, as follows:

Secondary structure: manage root key -> subkey;

Decentralized parameters: DCID+version number;

The distribution of keys at all levels is shown in the table below:

table 3

root key key management system subkey security module

The subkey needs to be preset during the production process of the security module, and other keys can be authorized and updated online and offline.

The lock key adopts a two-level structure, which is described as follows:

Secondary structure: lock root key -> subkey;

Decentralized parameters: SEID+version number;

The distribution of keys at all levels is shown in the table below:

Table 4

root key key management system subkey security module

The unlock key adopts a two-level structure, which is described as follows:

Secondary structure: unlock root key -> subkey;

Decentralized parameters: SEID+version number;

The distribution of keys at all levels is shown in the table below:

table 5

root key key management system subkey security module

The data encryption root key adopts a one-level management structure, which is described as follows:

One-level structure: the root key corresponding to the data encryption key in the security chip is directly written into the security module. When decrypting data, the root key is first dispersed to obtain the decryption sub-key through the data "SEID+version number" on the chain, and then Then decrypt the ciphertext data on the chain;

The distribution of keys at all levels is shown in the table below:

Table 6

root key key management system root key security module

The signature key is a 1024bit RSA public-private key pair generated by the key management system;

The distribution of keys is shown in the table below:

Table 7

private key security module public key key management system

The negotiation key is a 1024bit RSA public-private key pair generated by the key management system;

The distribution of keys is shown in the table below:

Table 8

private key security module public key key management system

The negotiated key is preset in the security module during the production process of the security module.

Among them, the subkey distribution method of the symmetric key may include the following process:

The dispersal parameter of the key is 16 bytes (if it is less than 16 bytes, first add 0x80, if it is less than 16 bytes, then add 0x00 to 16 bytes);

For a 128Bit key, use the ECB (Electronic Codebook) algorithm corresponding to the key to encrypt the dispersed parameters using the root key to obtain a subkey; for a 256Bit key, combine the above 16-byte dispersed parameters with The value after the parameter is reversed is connected to form a 32-byte distributed parameter, and the root key is used to encrypt the distributed parameter with the ECB algorithm corresponding to the key to obtain a subkey. For example: if the encryption key (root key) in the mobile authorization key group is AES-128Bit key KeyRoot, the SEID of a security chip is 11223344556677889900, and the key version number is 01, then the subkey KeySub of the security chip is pressed Obtained as follows:

Fill SEID to 16 bytes: 11223344556677889900018000000000;

Calculate the subkey SubKey=

AES-28-EncECB(KeyRoot)[11223344556677889900018000000000].

Among them, the key agreement algorithm based on asymmetric key may include the following process:

In the case that the two parties in the session use an asymmetric key for one-way negotiation, the session key can be obtained by using the session key calculation method based on the asymmetric key.

The 128Bit session key is calculated as follows:

SessionKeyEnc＝LEFT16[HASH256[session key factor||‘ENC&MAC’||secure platform random number]];

SessionKeyMac＝RIGHT16[HASH256[session key factor||'ENC&MAC'||security platform random number]];

The 256Bit session key is calculated as follows:

SessionKeyEnc=HASH256[session key factor||‘ENC’||secure platform random number] SessionKeyMac=HASH256[session key factor||‘MAC’||secure platform random number];

Among them, the length of the session key factor is 16 bytes, which is generated by the security platform and encrypted with the public key of the security module and transmitted to the security module; HASH256 can represent a 256-bit digest algorithm, and SHA256 can be selected according to the actual situation; LEFT16/RIGHT16 can represent parameters The left 16 bytes and right 16 bytes.

As shown in Figure 6, the signature verification method may specifically include the following processes:

The key management platform application sends the first data write command to the blockchain client SDK;

The blockchain client SDK sends the first data write command to the security module OS;

The security module OS returns a response to the blockchain client SDK, wherein the response includes the random number SARand;

The blockchain client SDK returns a response to the key management platform application;

The key management platform application sends a data write request message to the key management platform, and the data write message request includes a random number SARand;

The key management platform generates a second data write instruction, and the second data write instruction includes DATA (data) ciphertext, random number SPRand and signature SPMAC;

The key management platform sends a second data write instruction to the key management platform application;

The key management platform application sends the second data write command to the blockchain client SDK;

The blockchain client SDK sends a second data write command to the security module OS;

The security module OS verifies the identity of the key management platform and performs data writing operations;

The security module OS returns the result to the blockchain client SDK, and the returned result includes the signature SAMAC;

The blockchain client SDK returns the result to the key management platform application;

The key management platform application returns the result to the key management platform;

The key management platform verifies the OS identity of the security module, and the data writing is completed.

Among them, the random number SARand represents the above-mentioned first random number, the random number SPRand represents the above-mentioned second random number, the signature SPMAC represents the above-mentioned first signature, the signature SAMAC represents the above-mentioned second signature, and the DATA ciphertext represents the above-mentioned ciphertext data, as shown in Figure 7 As shown, in the case that the above-mentioned security terminal supports key negotiation, the direct key negotiation process between the above-mentioned key management platform and the above-mentioned security terminal is as follows:

The key management platform generates the random number SPRand and the session key factor, encrypts the session key factor with the public key of the security module to obtain the ciphertext of the session key factor, and calculates the key management platform signature SPMAC;

The key management platform sends a session key message to the key management platform application, and the session key message includes a random number SPRand, a session key factor ciphertext, and a signature SPMAC;

The key management platform application calls the blockchain client SDK, and sends a key agreement instruction to the blockchain client SDK. The key agreement instruction includes random number SPRand, session key factor ciphertext, and signature SPMAC;

The blockchain client SDK sends key negotiation instructions to the security module OS;

The security module OS verifies the signature SPMAC, decrypts the ciphertext of the session key factor and generates a session key, and calculates the signature SAMAC by using the session key and the random number SPRand;

The security module interface sends a response to the blockchain client SDK, and the response includes the signature SAMAC;

The blockchain client SDK sends a response to the key management platform application;

The key management platform application sends a response to the key management platform;

The key management platform verifies the signature SAMAC and generates a session key.

Wherein, the random number SPRand represents the above-mentioned third random number, the public key of the security module is the public key preset in the security module for negotiating keys, the signature SPMAC represents the above-mentioned third signature, and the signature SAMAC represents the above-mentioned fourth signature.

Wherein, the session key generated by the above-mentioned key management platform can be directly obtained according to the above-mentioned session key factor, and the above-mentioned session key is generated when the above-mentioned key management platform verifies that the signature SAMAC passes.

In this embodiment, the unified management and distribution of keys is carried out through the key management platform, and a mapping relationship is formed with user IDs (or security module IDs) through the generation of asymmetric key pairs and the dispersion of symmetric keys, which can improve data security. Security, and the distribution and generation of keys are all completed in the cipher machine connected with the key management platform, which can avoid the exposure of plaintext data. At the same time, a security channel is established through the key management platform and the hardware security module corresponding to the blockchain user node, and the key distribution is performed by updating the key through the security channel ciphertext to ensure data security.

In addition, the identity information of blockchain users or security terminals is stored through the security module. Based on the current mainstream role division of the blockchain, the roles of operators of the identity authentication system, such as administrators, authorized organizations, and regulatory organizations, are clearly proposed. The identity information (such as private key) of the storage block chain user or security terminal is provided and signature capability is provided, which provides hardware security guarantee for the block chain application and can expand the application scenarios of the block chain.

Please refer to FIG. 8. FIG. 8 is a schematic structural diagram of a key management platform provided by an embodiment of the present application. As shown in FIG. 8, the key management platform 800 includes:

The first sending module 801 is used to send the first data writing instruction to the security terminal through the block chain client;

A first obtaining module 802, configured to obtain, through the blockchain client, a first random number generated by the security terminal in response to the first data write instruction;

The second sending module 803 is configured to send a second data writing instruction to the security terminal through the block chain client, the second data writing instruction includes a second random number, a first signature and ciphertext data , the first signature is a signature generated according to the first random number, and the ciphertext data is data obtained by encrypting target data;

The second obtaining module 804 is used to obtain the second signature generated by the security terminal through the block chain client, and verify the second signature, and the second signature is the verification of the security terminal. A signature generated according to the second random number when the first signature is passed.

Optionally, as shown in Figure 9, the key management platform 800 may also include:

The third acquiring module 805 is configured to acquire a function list supported by the security terminal through the blockchain client, and determine whether the security terminal supports key negotiation according to the function list;

The first encryption module 806 is configured to use a preset key to encrypt the target data to obtain the ciphertext data when the security terminal does not support key negotiation;

The second encryption module 807 is configured to negotiate with the security terminal to obtain a session key when the security terminal supports key negotiation, and use the session key to encrypt the target data to obtain the encryption key. text data.

Optionally, the second encryption module 807 negotiates with the security terminal to obtain a session key, including:

Send a key agreement instruction to the security terminal through the block chain client, the key agreement instruction includes a third random number, a session key factor ciphertext, and a third signature, and the session key factor ciphertext The data obtained by encrypting the generated session key factor;

Receive the fourth signature sent by the security terminal in response to the key agreement instruction through the blockchain client, where the fourth signature is decrypted by the security terminal after verifying that the third signature passes The session key factor ciphertext generates a session key, and generates a signature based on the session key and the third random number;

Verifying the fourth signature, and obtaining the session key based on the session key factor when the fourth signature is verified to pass.

Optionally, as shown in Figure 10, the key management platform 800 may also include:

The fourth acquiring module 808 is configured to acquire the security terminal identifier, and generate the target data according to the security terminal identifier.

The key management platform 800 can implement various processes implemented by the key management platform in the method embodiment in FIG. 1 , and details are not repeated here to avoid repetition. The key management platform 800 can achieve the technical effect of improving data security.

Please refer to FIG. 11. FIG. 11 is a schematic structural diagram of a security terminal provided by an embodiment of the present application. As shown in FIG. 11, the security terminal 1100 includes:

The first sending module 1101 is used to receive the first data writing instruction sent by the key management platform through the blockchain client;

A generating module 1102, configured to generate a first random number in response to the first data write instruction, and send the first random number to the key management platform through the blockchain client;

The receiving module 1103 is configured to receive the second data writing instruction sent by the key management platform through the blockchain client, the second data writing instruction includes a second random number, a first signature and a ciphertext data, the first signature is a signature generated by the key management platform according to the first random number, and the ciphertext data is data obtained by encrypting target data by the key management platform;

A verification module 1104, configured to verify the first signature, and write the ciphertext data when the first signature is verified to pass, and generate a second signature according to the second random number;

The second sending module 1105 is configured to send the second signature to the key management platform through the blockchain client.

Optionally, as shown in Figure 12, the security terminal 1100 may also include:

The third sending module 1106 is configured to send a supported function list to the key management platform through the blockchain client, so that the key management platform can determine whether to support key negotiation according to the function list;

The negotiation module 1107 is configured to negotiate with the key management platform to obtain a session key when key negotiation is supported.

Optionally, the negotiating with the key management platform in the negotiation module 1107 to obtain the session key includes:

The key agreement instruction sent by the key management platform is received by the block chain client, the key agreement instruction includes a third random number, a session key factor ciphertext and a third signature, and the session key The factor ciphertext is the data obtained by encrypting the generated session key factor by the key management platform;

Verifying the third signature in response to the key agreement instruction, if the verification of the third signature is passed, decrypting the ciphertext of the session key factor to generate a session key, and according to the session key and the The third random number generates the fourth signature;

Sending the fourth signature to the key management platform through the block chain client.

The security terminal 1100 can implement various processes implemented by the security terminal in the method embodiment in FIG. 2 , and details are not repeated here to avoid repetition. The security terminal 1100 can achieve the technical effect of improving data security.

Please refer to FIG. 13 , the embodiment of the present application also provides an electronic device, the electronic device 1300 includes a processor 1301, a memory 1302, a program or instruction stored in the memory 1302 and operable on the processor 1301, the program or instruction When executed by the processor 1301, each process of the foregoing signature verification method embodiment can be realized, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.

It should be noted that, in this document, the term "comprising", "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions are performed, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or the part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) execute the method of each embodiment of the present application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Under the inspiration of this application, without departing from the purpose of this application and the scope of protection of the claims, many forms can also be made, all of which belong to the protection of this application.

Claims (10)

1. A signature verification method, characterized in that it is applied to a key management platform, comprising: Send the first data write instruction to the security terminal through the blockchain client; Obtaining the first random number generated by the security terminal in response to the first data write instruction through the blockchain client; Send a second data write instruction to the security terminal through the block chain client, the second data write instruction includes a second random number, a first signature and ciphertext data, and the first signature is based on The signature generated by the first random number, the ciphertext data is data obtained by encrypting the target data; Obtain the second signature generated by the security terminal through the block chain client, and verify the second signature, the second signature is when the security terminal passes the verification of the first signature A signature generated according to the second random number. 2. The method according to claim 1, wherein, before sending the second data writing instruction to the security terminal through the blockchain client, the method further comprises: Obtaining a function list supported by the security terminal through the blockchain client, and judging whether the security terminal supports key negotiation according to the function list; If the secure terminal does not support key negotiation, encrypt the target data with a preset key to obtain the ciphertext data; If the security terminal supports key negotiation, negotiate with the security terminal to obtain a session key, and use the session key to encrypt the target data to obtain the ciphertext data. 3. The method according to claim 2, wherein said negotiating with said security terminal to obtain a session key comprises: Send a key agreement instruction to the security terminal through the block chain client, the key agreement instruction includes a third random number, a session key factor ciphertext, and a third signature, and the session key factor ciphertext The data obtained by encrypting the generated session key factor; Receive the fourth signature sent by the security terminal in response to the key agreement instruction through the blockchain client, where the fourth signature is decrypted by the security terminal after verifying that the third signature passes The session key factor ciphertext generates a session key, and generates a signature based on the session key and the third random number; Verifying the fourth signature, and obtaining the session key based on the session key factor when the fourth signature is verified to pass. 4. The method according to claim 1, wherein, before sending the second data writing instruction to the corresponding security terminal through the block chain client, the method further comprises: Acquire the security terminal identifier, and generate the target data according to the security terminal identifier. 5. A signature verification method, characterized in that it is applied to a security terminal, comprising: Receive the first data write instruction sent by the key management platform through the blockchain client; generating a first random number in response to the first data write instruction, and sending the first random number to the key management platform through the blockchain client; Receive the second data writing instruction sent by the key management platform through the block chain client, the second data writing instruction includes the second random number, the first signature and ciphertext data, the first The signature is a signature generated by the key management platform according to the first random number, and the ciphertext data is data obtained by encrypting target data by the key management platform; Verifying the first signature, and writing the ciphertext data when verifying that the first signature is passed, and generating a second signature according to the second random number; Send the second signature to the key management platform through the block chain client. 6. The method according to claim 5, wherein before receiving the second data write instruction sent by the key management platform through the blockchain client, the method further comprises: sending a supported function list to the key management platform through the blockchain client, so that the key management platform can determine whether to support key negotiation according to the function list; In the case of supporting key negotiation, negotiate with the key management platform to obtain the session key. 7. The method according to claim 6, wherein said negotiating with said key management platform to obtain a session key comprises: The key agreement instruction sent by the key management platform is received by the block chain client, the key agreement instruction includes a third random number, a session key factor ciphertext and a third signature, and the session key The factor ciphertext is the data obtained by encrypting the generated session key factor by the key management platform; Verifying the third signature in response to the key agreement instruction, if the verification of the third signature is passed, decrypting the ciphertext of the session key factor to generate a session key, and according to the session key and the The third random number generates the fourth signature; Sending the fourth signature to the key management platform through the block chain client. 8. A key management platform, characterized in that it comprises: The first sending module is used to send the first data writing instruction to the security terminal through the block chain client; A first obtaining module, configured to obtain, through the blockchain client, a first random number generated by the security terminal in response to the first data write instruction; The second sending module is configured to send a second data writing instruction to the security terminal through the block chain client, the second data writing instruction includes a second random number, a first signature and ciphertext data, The first signature is a signature generated according to the first random number, and the ciphertext data is data obtained by encrypting target data; The second obtaining module is used to obtain the second signature generated by the security terminal through the block chain client, and verify the second signature, and the second signature is that the security terminal is verifying the A signature generated according to the second random number when the first signature is passed. 9. A security terminal, characterized in that it comprises: The first sending module is used to receive the first data writing instruction sent by the key management platform through the block chain client; A generating module, configured to generate a first random number in response to the first data write instruction, and send the first random number to the key management platform through the blockchain client; A receiving module, configured to receive a second data write instruction sent by the key management platform through the block chain client, the second data write instruction includes a second random number, a first signature and ciphertext data , the first signature is a signature generated by the key management platform according to the first random number, and the ciphertext data is data obtained by encrypting target data by the key management platform; A verification module, configured to verify the first signature, write the ciphertext data in the case of passing the verification of the first signature, and generate a second signature according to the second random number; The second sending module is configured to send the second signature to the key management platform through the block chain client. 10. An electronic device, characterized in that it includes a processor, a memory, and a program or instruction stored on the memory and run on the processor, when the program or instruction is executed by the processor, the following The steps in the signature verification method according to any one of claims 1 to 4, or, when the program or instruction is executed by the processor, the signature verification method according to any one of claims 5 to 7 is realized in the steps.