CN109981592B

CN109981592B - Method and electronic equipment for generating key by combining multiple clients and multiple servers

Info

Publication number: CN109981592B
Application number: CN201910153545.9A
Authority: CN
Inventors: 颜泽; 谢翔; 傅志敬; 孙立林
Original assignee: Juzix Technology Shenzhen Co ltd
Current assignee: Juzix Technology Shenzhen Co ltd
Priority date: 2019-02-28
Filing date: 2019-02-28
Publication date: 2021-07-16
Anticipated expiration: 2039-02-28
Also published as: CN109981592A

Abstract

The application provides a method and electronic equipment for generating a key by combining multiple clients and multiple servers, which are applied to a key management system, wherein the key management system comprises: n customer ends and N key servers, wherein N is a positive integer greater than or equal to 2, the method comprises the following steps: the N clients and the N key servers respectively generate and store key components; the N clients and the N key servers establish a secure channel through bidirectional authentication; and the N clients and the N key servers obtain a target public key through the safety channel based on respective key components. By the mode, the problem that the existing key management system is low in safety and flexibility is solved, and the technical effect of effectively improving the safety and flexibility of the key management system is achieved.

Description

Method and electronic equipment for generating key by combining multiple clients and multiple servers

Technical Field

The application belongs to the technical field of information security, and particularly relates to a method for generating a key by combining multiple clients and multiple servers and electronic equipment.

Background

At present, for a key service system, a key server generally generates a key, and then distributes the generated key to a key user, which inevitably increases the burden of the key server, and because the key is generated by a single key server, all key generation rules are specified and maintained by the key server itself, and the flexibility is not high.

In view of the above problems in the existing key system, no effective solution has been proposed.

Disclosure of Invention

The application aims to provide a method for generating a key by combining multiple clients and multiple servers and electronic equipment, and the purpose of effectively improving the security and flexibility of key management can be achieved.

The application provides a method for generating a key by combining multiple clients and multiple servers and an electronic device, which are realized as follows:

a method for generating a key by combining multiple clients and multiple servers is applied to a key management system, and the key management system comprises: n customer ends and N key servers, wherein N is a positive integer greater than or equal to 2, the method comprises the following steps:

the N clients and the N key servers respectively generate and store key components;

the N clients and the N key servers establish a secure channel through bidirectional authentication;

and the N clients and the N key servers obtain a target public key through the safety channel based on respective key components.

In one embodiment, the obtaining, by the N clients and the N key servers, a target public key through the secure channel based on respective key components includes:

selecting two devices from the N key servers and the N clients as MPC calculators;

each client and each key server in the N clients and the N key servers except the MPC calculator divides the key component corresponding to the client and each key server in the N clients and the N key servers into a first sub-key and a second sub-key, transmits the first sub-key to first equipment in the MPC calculator through the secure channel, and transmits the second sub-key to second equipment in the MPC calculator;

and the first equipment and the second equipment initiate MPC calculation through the secure channel to obtain the target public key.

In one embodiment, after the N clients and the N key servers obtain the target public key through the secure channel based on their respective key components, the method further includes:

a first client initiates a signature request, wherein the signature request carries data to be signed, and the first client is one of the N clients;

each client and each key server in the N clients and the N key servers except the MPC calculator divides the key component generated by the client and each key server in the N clients and the N key servers into a first sub-key and a second sub-key, transmits the first sub-key to first equipment in the MPC calculator through the secure channel, and transmits the second sub-key to second equipment in the MPC calculator;

the first device and the second device initiate MPC calculation through the secure channel to sign the data to be signed, so as to obtain a signature file;

and sending the signature file to each client and each key server except the MPC calculation party in the N clients and the N key servers.

a first client initiates an operation request, wherein the first client is one of the N clients;

the first device and the second device initiate MPC calculation to obtain 2N operation components, and carry out signature on the 2N operation components to obtain 2N signature files;

issuing the 2N operation components and the 2N signature files to N clients and N key servers in a one-to-one correspondence manner;

and the N clients and the N key servers verify the correctness of the received signature file through the target public key, and store the received operation components under the condition of passing the verification.

In one embodiment, the operation request includes at least one of: backup requests, restore requests, and refresh requests.

and the N clients and the N key servers initiate MPC calculation through the secure channel to obtain the target public key.

a first client initiates a signature request, wherein the signature request carries data to be signed and the target public key, and the first client is one of the N clients;

and the N clients and the N key servers initiate MPC calculation through the secure channel to perform signature operation on the data to be signed to obtain a signature file, and verify the correctness of the signature file according to the target public key.

the N clients and the N key servers initiate MPC calculation to obtain 2N operation components, and the 2N operation components are signed to obtain 2N signature files;

An electronic device comprising a processor and a memory for storing processor-executable instructions, the instructions when executed by the processor implementing the steps of the method of:

A computer readable storage medium having stored thereon computer instructions which, when executed, implement the steps of a method comprising:

According to the method and the electronic device for generating the key by combining the multiple clients and the multiple servers, the multiple clients and the multiple servers respectively generate own key components locally, a secure channel is established between the clients and the servers, and then a target public key is obtained based on the secure channel, so that the generation and the management of the key are completed. By the mode, the problem that the existing key management system is low in safety and flexibility is solved, and the technical effect of effectively improving the safety and flexibility of the key management system is achieved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

FIG. 1 is an architecture diagram of a key system provided herein;

FIG. 2 is a flowchart of a method for jointly generating a key by multiple clients and multiple servers provided by the present application;

FIG. 3 is an interactive schematic of key generation of example 1 provided herein;

FIG. 4 is an interactive illustration of key usage of example 1 provided herein;

FIG. 5 is an interactive schematic of the key backup of example 1 provided herein;

FIG. 6 is an interactive schematic of key recovery of example 1 provided herein;

FIG. 7 is an interaction diagram of key refresh for example 1 provided herein;

FIG. 8 is an interactive schematic of key generation of example 2 provided herein;

FIG. 9 is an interactive illustration of key usage of example 2 provided herein;

FIG. 10 is an interactive schematic of the key backup of example 1 provided herein;

FIG. 11 is an interactive schematic of key recovery of example 2 provided herein;

FIG. 12 is an interaction diagram of key refresh for example 2 provided herein;

fig. 13 is a schematic structural diagram of an electronic device provided in the present application.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the present example, a plurality of clients and a plurality of servers respectively generate their own key components locally, a secure channel is established between the client and the server, and then a target public key is obtained based on the secure channel, so that generation and management of the key are completed, and the technical effect of effectively improving the security and flexibility of the key management system is achieved.

In this example, a method for generating a key by combining multiple clients and multiple servers is provided, and is applied to a key management system, as shown in fig. 1, the key management system may include: n clients and N key servers, wherein N is an integer greater than or equal to 2.

Fig. 2 is a flowchart of a method of an embodiment of a method for generating a key by combining multiple clients and multiple servers according to the present application. Although the present application provides method operational steps or apparatus configurations as illustrated in the following examples or figures, more or fewer operational steps or modular units may be included in the methods or apparatus based on conventional or non-inventive efforts. In the case of steps or structures which do not logically have the necessary cause and effect relationship, the execution sequence of the steps or the module structure of the apparatus is not limited to the execution sequence or the module structure described in the embodiments and shown in the drawings of the present application. When the described method or module structure is applied in an actual device or end product, the method or module structure according to the embodiments or shown in the drawings can be executed sequentially or executed in parallel (for example, in a parallel processor or multi-thread processing environment, or even in a distributed processing environment).

Specifically, as shown in fig. 2, a method for generating a key by combining multiple clients and multiple servers according to an embodiment of the present application may include the steps of:

step 201: the N clients and the N key servers respectively generate and store key components;

the client is a key user, including but not limited to an App, an application server, and the like, and what form the client exists specifically may be selected according to actual needs, which is not limited in the present application. The key server is a key service party and is used for providing key related services.

That is, the clients 1 to N and the key servers 1 to N each locally generate and store a key component.

Step 202: the N clients and the N key servers establish a secure channel through bidirectional authentication;

specifically, the client and the key server can complete bidirectional authentication through a KYC (Know your customer, identity confirmation program), and issue authentication materials to complete a registration process; wherein, the identity confirming program may include but is not limited to at least one of the following: short message, mailbox identifying code, account password, fingerprint, human face, certificate, etc.

Step 203: and the N clients and the N key servers obtain a target public key through the safety channel based on respective key components.

In implementation, the N clients and the N key servers obtain the target public key through the Secure channel based on the respective key components, which may be obtained through a Multi-Party MPC (Secure Multi-Party Computation), that is, all the key servers and the clients participate in MPC Computation, or may obtain the target public key through two-Party MPCs, that is, two MPC participants are selected from the key servers and the clients to participate in MPC Computation.

The use of key shares in these two MPC calculation modes is described below:

1) MPC in two parties:

the obtaining of the target public key by the N clients and the N key servers through the secure channel based on the respective key components may include the following steps:

s1: selecting two devices from N key servers and the N clients as MPC calculation parties;

s2: each client and each key server in the N clients and the N key servers except the MPC calculator divides the key component corresponding to the client and each key server in the N clients and the N key servers into a first sub-key and a second sub-key, transmits the first sub-key to first equipment in the MPC calculator through the secure channel, and transmits the second sub-key to second equipment in the MPC calculator;

s3: and the first equipment and the second equipment initiate MPC calculation through the secure channel to obtain the target public key.

For example: the key servers 1, 2 initiate MPC computations over a secure channel: the private key SK is calculated through the key components SK1, SK2, (SK 3-2 n) -1 and (SK 3-2 n) -2, the public key PK is calculated through the private key SK, and the PK is returned to the client and the key server after being stored. Because the whole process is a complete MPC calculation, the private key SK is not actually generated (either in the calculation process or in the use process), and the SK 1-2 n does not appear in the calculation interaction process (i.e. the SK 1-2 n is not transmitted in the network layer for calculation).

After the N clients and the N key servers obtain the target public key through the secure channel based on their respective key components, the signature may be performed using the key components according to the following steps:

s1: a first client initiates a signature request, wherein the signature request carries data to be signed, and the first client is one of the N clients;

s2: each client and each key server in the N clients and the N key servers except the MPC calculator divides the key component generated by the client and each key server in the N clients and the N key servers into a first sub-key and a second sub-key, transmits the first sub-key to first equipment in the MPC calculator through the secure channel, and transmits the second sub-key to second equipment in the MPC calculator;

s3: the first device and the second device initiate MPC calculation through the secure channel to sign the data to be signed, so as to obtain a signature file;

s4: and sending the signature file to each client and each key server except the MPC calculation party in the N clients and the N key servers.

After the target public key and the key component are obtained, sometimes the key component needs to be backed up, restored, refreshed, and the like, and specifically, the key component can be backed up, restored, and refreshed according to the following steps:

s1: a first client initiates an operation request, wherein the first client is one of the N clients;

s3: the first equipment and the second equipment initiate MPC calculation to obtain 2N operation components, and carry out signature on the 2N operation components to obtain 2N signature files;

s4: issuing the 2N operation components and the 2N signature files to N clients and N key servers in a one-to-one correspondence manner;

s5: and the N clients and the N key servers verify the correctness of the received signature file through the target public key, and store the received operation components under the condition of passing the verification.

That is, the operation request may include, but is not limited to, at least one of: backup requests, restore requests, and refresh requests.

2) Multi-party MPC:

the obtaining of the target public key by the N clients and the N key servers through the secure channel based on the respective key components may include: and the N clients and the N key servers initiate MPC calculation through the secure channel to obtain the target public key.

For example: the client and the key server establish a secure channel through authentication of the authentication material, and initiate MPC calculation: and calculating a private key SK through the key components SK 1-2 n, and calculating a public key PK through the private key SK. And returning the public key to the client and the key server for storage respectively. Because the whole process is a complete MPC calculation, the private key SK is not actually generated (either in the calculation process or in the use process), and the SK 1-2 n does not appear in the calculation interaction process (i.e. the SK 1-2 n is not transmitted in the network layer for calculation).

s1: a first client initiates a signature request, wherein the signature request carries data to be signed and the target public key, and the first client is one of the N clients;

s2: and the N clients and the N key servers initiate MPC calculation through the secure channel to perform signature operation on the data to be signed to obtain a signature file, and verify the correctness of the signature file according to the target public key.

s1: a first client initiates an operation request, wherein the first client is one of the N clients; the operation request may include, but is not limited to, at least one of: backup requests, restore requests, and refresh requests.

S2: the N clients and the N key servers initiate MPC calculation to obtain 2N operation components, and the 2N operation components are signed to obtain 2N signature files;

s3: issuing the 2N operation components and the 2N signature files to N clients and N key servers in a one-to-one correspondence manner;

s4: and the N clients and the N key servers verify the correctness of the received signature file through the target public key, and store the received operation components under the condition of passing the verification.

The above method is described below with reference to several specific examples, however, it should be noted that the specific examples are only for better illustrating the present application and should not be construed as limiting the present application.

In the embodiment, a key management method generated and stored by a plurality of servers based on two-party secure computation is provided, and is applied to key generation, use, storage, backup, recovery, refreshing and other operations of a key management system. Specifically, different clients and key servers independently generate key components, and finally, two-party MPCs are used to generate public keys, and the two-party MPCs use a plurality of clients and a plurality of key servers to calculate signatures.

Specifically, based on the scenario, key generation, usage, storage, backup, recovery, and refresh may be performed as follows:

1) generating

As shown in fig. 3, the following steps may be included:

s1: client 1 generates and saves component SKn + 1;

s2: the client and the key server complete bidirectional authentication through KYC, and issue authentication materials to complete a registration process, and the client 1 initiates a key generation request;

s3: the client 2-n and the key server 1-n respectively locally generate and store key components SK 2-2 n;

s4: the server randomly selects two clients or key servers as MPC calculation parties, and assumes that a key server 1 and a key server 2 are selected as MPC calculation parties;

s5: the client 1-n and the key server 1-n establish a secure channel through mutual authentication, the SK3 is split into SK3-1 and SK3-2, the SK3-1 is transmitted to the key server 1, and the SK3-2 is transmitted to the key server 2; by analogy, the SK2n is split into (SK2n) -1 and (SK2n) -2, and the (SK2n) -1 is transmitted to the key server 1 and the (SK2n) -2 is transmitted to the key server 2;

s6: the key servers 1, 2 initiate MPC computations over a secure channel: the private key SK is calculated through the key components SK1, SK2, (SK 3-2 n) -1 and (SK 3-2 n) -2, the public key PK is calculated through the private key SK, and the PK is returned to the client and the key server after being stored. Because the whole process is a complete MPC calculation, the private key SK is not actually generated (either in the calculation process or in the use process), and the SK 1-2 n does not appear in the calculation interaction process (i.e. the SK 1-2 n is not transmitted in the network layer for calculation).

2) Use of

As shown in fig. 4, the following steps may be included:

s1: the client 1 initiates a signature request and provides a public key PK as a unique identifier and data to be signed;

s2: the server randomly selects two clients or key servers as MPC calculation parties, and assumes that a key server 1 and a key server 2 are selected as MPC calculation parties;

s3: the client 1-n and the key server 1-n complete bidirectional authentication through KYC and establish a secure channel, then SK3 is split into SK3-1 and SK3-2, SK3-1 is transmitted to the key server 1, and SK3-2 is transmitted to the key server 2; by analogy, the SK2n is split into (SK2n) -1 and (SK2n) -2, and the (SK2n) -1 is transmitted to the key server 1 and the (SK2n) -2 is transmitted to the key server 2;

s4: the key servers 1, 2 initiate MPC computations over a secure channel: the private key SK is calculated through the key components SK1, SK2, (SK 3-2 n) -1, (SK 3-2 n) -2, and the data to be signed is signed through the private key SK. And returns the signature to the client and the key server. Because the whole process is a complete MPC calculation, the private key SK is not actually generated (either in the calculation process or in the use process), and the SK 1-2 n does not appear in the calculation interaction process (i.e. the SK 1-2 n is not transmitted in the network layer for calculation).

3) Storing

The key or key component may be stored in, but is not limited to, one of the following forms:

a database: storing the key or the key component through a database, wherein the key or the key component can be stored in an encrypted manner;

key file: the key or the key component is saved in a key file form through derivation, wherein the key or the key component can be saved in an encrypted mode;

HSM: the key or the key component is stored through the hardware security module, wherein the key or the key component can be stored in an encrypted manner;

mnemonic words: the key live key component is converted into a series of mnemonic words to be stored;

two-dimensional code: and generating a corresponding two-dimensional code through a key or a key component for storage, wherein the key or the key component can be stored in an encrypted manner.

4) Backup of

As shown in fig. 5, the following steps may be included:

s1: the client 1 initiates a backup request;

s3: the client 1-n and the key server 1-n complete bidirectional authentication and establish a secure channel through KYC, then SK3 is split into SK3-1 and SK3-2, SK3-1 is transmitted to the key server 1, and SK3-2 is transmitted to the key server 2; by analogy, the SK2n is split into (SK2n) -1 and (SK2n) -2, and the (SK2n) -1 is transmitted to the key server 1 and the (SK2n) -2 is transmitted to the key server 2;

s4: the key servers 1, 2 initiate MPC computations over a secure channel: the secret key SK is calculated through the key components SK1, SK2, (SK 3-2 n) -1, (SK 3-2 n) -2, secret sharing is conducted through the secret key SK to generate new backup components SK 1-2 n ', and the new SK 1-2 n' is signed. And respectively issuing the SK1 '-SK 2 n' and the signature thereof to the corresponding key server and the client. Because the whole process is complete MPC calculation, the private key SK is not really generated (whether in the calculation process or in the use process), and the SK 1-2 n does not appear in the calculation interaction process (namely, the SK 1-2 n is not transmitted in the network layer for calculation);

s5: after receiving the relevant information, the client and the key server verify the correctness of the received backup component through the received signature, and if the received backup component passes the verification, the client and the key server save the received backup component.

5) Recovery

As shown in fig. 6, the following steps may be included:

s1: the client 1 acquires backup components in a backup mode and initiates a recovery request;

s2: the server randomly selects two clients or servers as MPC calculation parties, and assumes that a key server 1 and a key server 2 are selected as MPC calculation parties;

s3: the client 1-n and the key server 1-n complete bidirectional authentication and establish a secure channel through KYC, then split the backup component SK3 ' into SK3 ' -1 and SK3 ' -2, and transmit SK3 ' -1 to the key server 1 and SK3 ' -2 to the key server 2; by analogy, the SK2n ' is split into (SK2n ') -1 and (SK2n ') -2, and (SK2n ') -1 and (SK2n ') -2 are transmitted to the key server 1 and the key server 2 respectively;

s4: the key servers 1, 2 initiate MPC computations over a secure channel: the private key SK is calculated through the backup components SK1 ', SK 2', (SK 3-2 n ') -1, (SK 3-2 n') -2, and secret sharing is performed through the private key SK to generate new SK 1-2 n. And sign the new SK 1-2 n. And respectively issuing the SK 1-SK 2n and the signatures thereof to the corresponding client and the key server. Because the whole process is complete MPC calculation, the private key SK is not really generated (in the calculation process or the use process), and the SK 1-2 n 'does not appear in the calculation interaction process (i.e. the SK 1-2 n' is not transmitted in the network layer for calculation);

s5: after the client and the key server receive the related information, the correctness of the received new key component is verified through the received signature. And if the verification is passed, updating and storing the received new key component.

6) Refreshing

As shown in fig. 7, the following steps may be included:

s1: the client 1 initiates a key refreshing request;

s3: the client 1-n and the key server 1-n complete bidirectional authentication and establish a secure channel through KYC, then SK3 is split into SK3-1 and SK3-2, SK3-1 is transmitted to the key server 1, and SK3-2 is transmitted to the key server 2; by analogy, the SK2n is split into (SK2n) -1 and (SK2n) -2, and (SK2n) -1 is transmitted to the key server 1 and (SK2 n') -2 is transmitted to the key server 2;

s4: the key servers 1, 2 initiate MPC computations over a secure channel: the private key SK is calculated through SK1, SK2, (SK 3-2 n) -1, (SK 3-2 n) -2, and secret sharing is carried out through the private key SK to generate new SK 1-2 n. And sign the new SK 1-2 n. And respectively issuing the SK 1-SK 2n and the signatures thereof to the corresponding client and the key server. Because the whole process is complete MPC calculation, the private key SK is not really generated (whether in the calculation process or in the use process), and the SK 1-2 n does not appear in the calculation interaction process (namely, the SK 1-2 n is not transmitted in the network layer for calculation);

s5: after the client and the key server receive the related information, the correctness of the received key component is verified through the received signature. And if the verification is passed, updating and storing the received key components.

Example 2

In the embodiment, a key management method generated and stored by a plurality of servers based on secure multi-party computation is provided, and is applied to key generation, use, storage, backup, recovery, refreshing and other operations of a key management system. Specifically, the multiple clients and the multiple key servers respectively generate private key components, public keys are obtained through the MPC, signatures are calculated through the MPC through the multiple clients and the multiple key servers, and the MPC is calculated through the private key components to refresh the components of the multiple clients and the multiple key servers.

1) generating

As shown in fig. 8, the following steps may be included:

s1: client 1 generates and saves component SKn + 1;

s3: after receiving the key generation request, the client and the key server respectively generate key components, for example: the key server 1 generates a key component SK1, and the key server 2 generates a key component SK 2; by analogy, key server n generates key share SKn. Client 2 generates key classification SKn + 2; by analogy, client n generates key component SK2 n;

s4: the client and the key server establish a secure channel through authentication of the authentication material, and initiate MPC calculation: and calculating a private key SK through the key components SK 1-2 n, and calculating a public key PK through the private key SK. And returning the public key to the client and the key server for storage respectively. Because the whole process is a complete MPC calculation, the private key SK is not actually generated (either in the calculation process or in the use process), and the SK 1-2 n does not appear in the calculation interaction process (i.e. the SK 1-2 n is not transmitted in the network layer for calculation).

2) Use of

As shown in fig. 9, the following steps may be included:

s2: bidirectional authentication is completed between the client and the key server through KYC, and a secure channel is established;

s3: the client and the key server initiate MPC calculation through a secure channel: and carrying out signature operation on the data to be signed, and verifying the correctness of the signature through the PK public key.

3) Storing

4) Backup of

As shown in fig. 10, the following steps may be included:

s1: the client 1 initiates a backup key request;

s2: establishing a secure channel between the client and the key server through KYC, and initiating MPC calculation: generating a private key SK, generating backup key components SK1 '-SK 2 n' by a secret sharing algorithm, signing SK1 '-SK 2 n' by using SK, and generating signatures S1 '-S2 n'. The signature and the backup key component are respectively issued to different key servers, for example: the SK1 'and the S1' are issued to the key server 1; the SK2 'and S2' are issued to the key server 2; and so on, sending SKn 'and Sn' to the key server n. The signature and the backup key component are respectively issued to different clients, for example: delivering SKn +1 'and Sn + 1' to the client 1; delivering SKn +2 'and Sn + 2' to the client 2; and so on, the SK2n ', S2 n' are issued to the client n. Because the whole process is a complete MPC calculation, the private key SK is not actually generated (either during calculation or use);

s3: and each client and the key server verify the validity of the received signature through the previously stored public key PK, and if the received signature is valid, the received backup key component is saved.

5) Recovery

As shown in fig. 11, the following steps may be included:

s1: the client 1 acquires a backup component through a backup mode and initiates a recovery request;

s2: the client and the key server complete bidirectional authentication through KYC and establish a secure channel, a backup key is obtained through a backup mode, and MPC calculation is performed to verify whether a backup component is correct: and calculating a private key SK, generating a public key PK through the SK, and if the PK is the same as the stored PK, passing the verification. If the verification is passed, SK 1-SK 2n is generated by secret sharing algorithm, SK 1-SK 2n is signed by using SK, and signatures S1-S2 n are generated. SK 1-SK 2n and signatures S1-S2 n are issued to different clients and key servers respectively, for example: issue SK1, S1 to the key server 1; issue SK2, S2 to the key server 2; by analogy, delivering SKn and Sn to the key server n, and delivering SKn +1 and Sn +1 to the client 1; SKn +2 and Sn +2 are issued to the client 2; and the same way, the SK2n and S2n are issued to the client n. Because the entire process is a complete MPC calculation, the private key SK is not actually generated (either during calculation or use).

S3: and each key server and each client verify the validity of the signature through the previously stored public key PK, and if the signature is valid, the key components are updated and stored.

6) Refreshing

As shown in fig. 12, the following steps may be included:

s1: the client 1 initiates a key refreshing request;

s2: bidirectional authentication is completed between the client and the key server through KYC, a safety channel is established, and MPC calculation is initiated: generating a private key SK, generating new working components SK 1-SK 2n through a secret sharing algorithm, signing SK 1-SK 2n through SK, and generating signatures S1-S2 n. The signatures are respectively issued to different key servers and clients, for example: issue SK1, S1 to the key server 1; issue SK2, S2 to the key server 2; by analogy, delivering SKn and Sn to the key server n, and delivering SKn +1 and Sn +1 to the client 1; SKn +2 and Sn +2 are issued to the client 2; and the same way, the SK2n and S2n are issued to the client n. Because the whole process is a complete MPC calculation, the private key SK is not actually generated (either during calculation or use);

s3: and each key server and each client verify the validity of the signature through the previously stored public key PK, and if the signature is valid, the key component is updated and stored, namely, a new work component is stored.

The method embodiments provided in the above embodiments of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking the example of the method running on the electronic device, fig. 13 is a hardware structure block diagram of the electronic device of the method for generating a key by combining multiple clients and multiple servers according to the embodiment of the present invention. As shown in fig. 13, the computer terminal 10 may include one or more (only one shown) processors 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions. It will be understood by those skilled in the art that the structure shown in fig. 13 is only an illustration and is not intended to limit the structure of the electronic device. For example, the computer terminal 10 may also include more or fewer components than shown in FIG. 13, or have a different configuration than shown in FIG. 13.

The memory 104 may be used to store software programs and modules of application software, such as program instructions/modules corresponding to the method for generating a key by combining multiple clients and multiple servers in the embodiment of the present invention, and the processor 102 executes various functional applications and data processing by executing the software programs and modules stored in the memory 104, that is, the method for generating a key by combining multiple clients and multiple servers that implements the application program described above. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission module 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission module 106 includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission module 106 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

An embodiment of the present application further provides a specific implementation manner of an electronic device, which is capable of implementing all steps in the method for generating a key by combining multiple clients and multiple servers in the foregoing embodiment, where the electronic device specifically includes the following contents: a processor (processor), a memory (memory), a communication Interface (Communications Interface), and a bus; the processor, the memory and the communication interface complete mutual communication through the bus; the processor is configured to invoke the computer program in the memory, and when executing the computer program, the processor implements all the steps in the method for jointly generating a key by multiple clients and multiple servers in the foregoing embodiment, for example, when executing the computer program, the processor implements the following steps:

step 1: the N clients and the N key servers respectively generate and store key components;

step 2: the N clients and the N key servers establish a secure channel through bidirectional authentication;

and step 3: and the N clients and the N key servers obtain a target public key through the safety channel based on respective key components.

As can be seen from the above description, in the method and the electronic device for generating a key by combining multiple clients and multiple servers in the embodiment of the present application, the multiple clients and the multiple servers respectively generate their own key components locally, a secure channel is established between the client and the server, and then a target public key is obtained based on the secure channel, thereby completing generation and management of the key. By the mode, the problem that the existing key management system is low in safety and flexibility is solved, and the technical effect of effectively improving the safety and flexibility of the key management system is achieved.

Embodiments of the present application further provide a computer-readable storage medium capable of implementing all steps of the method for generating a key by combining multiple clients and multiple servers in the foregoing embodiments, where the computer-readable storage medium stores thereon a computer program, and when the computer program is executed by a processor, the computer program implements all steps of the method for generating a key by combining multiple clients and multiple servers in the foregoing embodiments, for example, when the processor executes the computer program, the processor implements the following steps:

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the hardware + program class embodiment, since it is substantially similar to the method embodiment, the description is simple, and the relevant points can be referred to the partial description of the method embodiment.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

Although the present application provides method steps as described in an embodiment or flowchart, additional or fewer steps may be included based on conventional or non-inventive efforts. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or client product executes, it may execute sequentially or in parallel (e.g., in the context of parallel processors or multi-threaded processing) according to the embodiments or methods shown in the figures.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

Although embodiments of the present description provide method steps as described in embodiments or flowcharts, more or fewer steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in a process, method, article, or apparatus that comprises the recited elements is not excluded.

For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, in implementing the embodiments of the present description, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units, and the like. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may therefore be considered as a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.

The embodiments of this specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The described embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of an embodiment of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.

The above description is only an example of the embodiments of the present disclosure, and is not intended to limit the embodiments of the present disclosure. Various modifications and variations to the embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present specification should be included in the scope of the claims of the embodiments of the present specification.

Claims

1. A method for generating a key by combining multiple clients and multiple servers is applied to a key management system, and the key management system comprises: n customer ends and N key servers, wherein N is a positive integer greater than or equal to 2, the method comprises:

the N clients and the N key servers obtain target public keys through the secure channel based on respective key components;

wherein, the obtaining of the target public key by the N clients and the N key servers through the secure channel based on the respective key components includes:

selecting two devices from the N key servers and the N clients as a secure multi-party computing (MPC) calculator;

2. The method according to claim 1, wherein after the N clients and the N key servers obtain target public keys through the secure channel based on their respective key components, the method further comprises:

3. The method according to claim 1, wherein after the N clients and the N key servers obtain target public keys through the secure channel based on their respective key components, the method further comprises:

4. The method of claim 3, wherein the operation request comprises at least one of: backup requests, restore requests, and refresh requests.

5. The method of claim 1, wherein obtaining the target public key by the N clients and the N key servers through the secure channel based on the respective key components comprises:

6. The method of claim 5, wherein after the N clients and the N key servers obtain target public keys through the secure channel based on their respective key components, the method further comprises:

7. The method of claim 5, wherein after the N clients and the N key servers obtain target public keys through the secure channel based on their respective key components, the method further comprises:

8. The method of claim 7, wherein the operation request comprises at least one of: backup requests, restore requests, and refresh requests.

9. An electronic device comprising a processor and a memory for storing processor-executable instructions that when executed by the processor implement: the steps of the method of any one of claims 1 to 8.

10. A computer readable storage medium having stored thereon computer instructions which, when executed, implement the steps of the method of any one of claims 1 to 8.