WO2020024993A1 - Method and system for generating public-private key pair - Google Patents

Abstract

The present invention provides a method and system for generating a public-private key pair. The method comprises: generating a first password, and generating a first private key and a first public key according to the first password; sending signature information to a server for the server to verify the identity, and receiving first encrypted information returned by the server after the verification is passed; encrypting first user information by means of a second public key to generate second encrypted information, and sending the second encrypted information to the server for the server to decrypt by means of a second private key, performing hash on the decrypted result to obtain a second hash value, obtaining a first hash value recorded on a block chain, verifying whether the first hash value and the second hash value are the same; decrypting second password encrypted information by means of the first private key to obtain a second password, and generating a third private key and a third public key according to the second password. According to the present invention, a server terminal sends the second password to a user terminal, and the public and private key pair is generated according to the second password, thereby ensuring the security and privacy of the public and private key pair.

Description

Method and system for generating public and private key pairs Technical field

The present application relates to the field of information technology, and in particular, to a method and a system for generating a private key.

Background technique

The public-private key generation in the prior art generally generates a private key through a random number, and then generates the public key through a hash operation. For user transactions, the role of the private key is very important. However, in reality, private keys often appear Lost or obtained by others, this is very detrimental to the security of the user's account. A public and private key pair generation method that can securely generate and ensure that the private key cannot be easily obtained by others is needed.

Summary of the invention

In view of the above defects or deficiencies in the prior art, it is desirable to provide a secure method and system for generating public and private key pairs.

In a first aspect, the present invention provides a public-private key pair generation method, including:

Generating a first password, and generating a first private key and a first public key according to the first password;

Send the signature information to the server for the server to verify the identity, and receive the first encrypted information returned by the server after the verification is passed; wherein the signature information is generated by the signature of the first private key, and the first encrypted information is sent to the first user by the first public key The information is encrypted and generated, and the first user information includes contact information;

The first encrypted information is decrypted by the first private key to obtain the first user information, and the first user information is encrypted by the second public key to generate the second encrypted information; wherein the second public key is held by the server The public key corresponding to the second private key of

Send the second encrypted information to the server for the server to decrypt by the second private key, and hash the decryption result of the second encrypted information to obtain the second hash value, and obtain the first record recorded on the blockchain. A hash value to verify whether the first hash value and the second hash value are the same: yes, the second password encryption information is issued through the contact information in the decryption result; wherein the first hash value is the first user information A hash value, and the second password encryption information is generated by encrypting the second password with the first public key;

After receiving the second password encryption information, the second password encryption information is decrypted by the first private key to obtain a second password, and a third private key and a third public key are generated based on the second password.

Further, receiving the second password encryption information includes: receiving a verification code through a contact method stipulated in the contact information, sending the verification code for the server to send the second password encryption information after passing the verification, and receiving the second password encryption information.

Further, receiving the second password encryption information includes: directly receiving the second password encryption information through a contact manner stipulated in the contact information.

Further, generating the third private key and the third public key according to the second password includes: performing a specified first operation on the first private key and the second password, and performing a hash operation on the operation result to generate the third private key and the third public key. Three public keys.

Further, generating the third private key and the third public key according to the second password includes: hashing the second password to generate the third private key and the third public key.

Further, the first encrypted information returned by the receiving server after the verification passes includes: receiving unregistered information sent by the server, sending the registration information to the server for the server to associate the registration information with the first public key after the verification is passed, and, Hash the public key, registration information, and random number to obtain a third hash value, and store the third hash value on the blockchain, where the registration information includes contact information and identity information;

Receiving the first encrypted information returned by the server.

Further, the signature information includes a hash value of the latest block header on the blockchain.

Further, the first hash value is signed with the first private key held, and the signature is sent to the blockchain.

In a second aspect, the present invention provides a public-private key pair generation system, including:

A first password generating unit configured to generate a first password, and generate a first private key and a first public key according to the first password;

The first encrypted information receiving unit is configured to send the signature information to the server for the server to verify the identity, and receive the first encrypted information returned by the server after the verification is passed; wherein the signature information is generated by the signature of the first private key, and the first encryption The information is generated by encrypting the first user information by using the first public key, and the first user information includes contact information;

The second encrypted information generating unit is configured to decrypt the first encrypted information by using the first private key to obtain the first user information, and encrypt the first user information by using the second public key to generate the second encrypted information; , The second public key is the public key corresponding to the second private key held by the server;

The information sending unit is configured to send the second encrypted information to the server for the server to decrypt through the second private key, and hash the decryption result of the second encrypted information to obtain a second hash value, and obtain a record The first hash value on the blockchain verifies whether the first hash value and the second hash value are the same: Yes, the second password encryption information is issued through the contact information in the decryption result; wherein the first hash value The value is a hash value of the first user information, and the second password encryption information is generated by encrypting the second password with the first public key;

The public-private key pair generation unit is configured to receive the second password encryption information, decrypt the second password encryption information by using the first private key, obtain a second password, and generate a third private key and a third public key according to the second password.

Further, the public-private key pair generation unit includes: a second password receiving subunit configured to receive a verification code through a contact method agreed in the contact information, and send a verification code for the server to send the second password encryption information after passing the verification, and receive the second password Encrypted information.

Further, the public-private key pair generating unit includes: a password receiving subunit configured to directly receive the second password encrypted information through a contact method agreed in the contact information.

Further, the public-private key pair generation unit includes a first public-private key generation subunit configured to perform a specified first operation on the first private key and a second password, and perform a hash operation on the operation result to generate a third private key. And the third public key.

Further, the public-private key pair generation unit includes a second public-private key generation subunit configured to perform a hash operation on the second password to generate a third private key and a third public key.

The beneficial effects of the present invention:

The present invention sends a second password to the client after the server-to-user identity verification is passed, thereby generating a public-private key pair based on the second password. This ensures that the public-private key pair cannot obtain the second key without the first password. The password generates a public-private key pair based on the obtained second password, thereby ensuring the security and privacy of the public-private key pair.

BRIEF DESCRIPTION OF THE DRAWINGS

Other features, objects, and advantages of the present application will become more apparent by reading the detailed description of the non-limiting embodiments with reference to the following drawings:

FIG. 1 is a flowchart of a public-private key pair generation method according to an embodiment of the present invention.

FIG. 2 is a scene diagram of a preferred implementation provided by an embodiment of the present invention.

FIG. 3 is a scene diagram of another preferred embodiment of the present invention.

FIG. 4 is a flowchart of step S15 of a preferred embodiment of the method shown in FIG. 1.

FIG. 5 is a flowchart of step S15 of another preferred embodiment of the method shown in FIG. 1.

FIG. 6 is a flowchart of another preferred embodiment of the present invention.

FIG. 7 is a schematic structural diagram of a public-private key pair generation system provided by the present invention.

detailed description

The following describes the present application in detail with reference to the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the related invention, rather than limiting the invention. It should also be noted that, for convenience of description, only the parts related to the invention are shown in the drawings.

It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. The application will be described in detail below with reference to the drawings and embodiments.

FIG. 1 is a flowchart of a public-private key pair generation method according to an embodiment of the present invention.

As shown in FIG. 1, in this embodiment, the present invention provides a public-private key pair generation method, including:

S11. Generate a first password, and generate a first private key Ska and a first public key Pka according to the first password;

S12. Send the signature information to the server for the server to verify the identity, and receive the first encrypted information m returned by the server after the verification is passed; wherein the signature information is generated by the signature of the first private key Ska, and the first encrypted information m is passed through the first public The key Pka is generated by encrypting the first user information, and the first user information includes contact information;

S13. Decrypt the first encrypted information m by the first private key Ska to obtain the first user information, and encrypt the first user information by the second public key to generate the second encrypted information n. Among them, the second public key The public key corresponding to the second private key held by the server;

S14. Send the second encrypted information n to the server for the server to decrypt through the second private key, and hash the decrypted result of the second encrypted information n to obtain a second hash value, and obtain the record in the block. The first hash value on the chain verifies whether the first hash value and the second hash value are the same: Yes, the second password encryption information is issued through the contact information in the decryption result; wherein the first hash value is the first A hash value of user information, and the second password encryption information is generated by encrypting the second password Kb with the first public key Pka;

After receiving the second password encryption information, the second password encryption information is decrypted by the first private key Ska to obtain a second password, and a third private key and a third public key are generated according to the second password.

Specifically, in step S11, the user locally generates a first password Ka, and generates a first private key Ska and a first public key Pka from the first password Ka. The first password Ka may have a limited number of digits, and may also be a number, a letter, a symbol, or any combination of the three.

In step S12, the client obtains the latest block header hash value on the blockchain, signs it with the first private key Ska, and sends it to the server. After the server obtains the signature information, it uses the client's first public key Pka to perform the signature information. Verification. After the verification is passed, the server sends the first encrypted information m of the contact information encrypted by the first public key Pka to the client. Previously, when the user registered, the contact information was hashed to obtain a first hash value x, and The hash value is stored on the blockchain. At the same time, the registered identity information can be hashed to obtain a hash value. The first two private keys Ska signatures are sent to the blockchain to ensure that Immutable data.

The signature information sent by the user here includes the hash value of the latest block header on the blockchain, which can ensure that the signature information is up to date. In addition, the content of the signature information can also be other contents, as long as the server can verify the signature as the user himself That is, the above manner is a preferable choice.

In step S13, after receiving the first encrypted information m sent by the server, the user terminal decrypts it with the first private key Ska to obtain the first user information, and encrypts the first user information with the second public key of the server to generate Second encrypted information n.

In step S14, the user sends the second encrypted information n to the server, and the server decrypts the second encrypted information n with the second private key, and hashes the decrypted contact information to obtain the second hash value and the existence area. The first hash value x of the blockchain is compared. If the two hashes are the same, it proves that the second encrypted information n received by the server is correct.

In step S15, after the server verifies that the second encrypted information n is correct, the server sends a second password Kb encrypted by the first public key Pka to the client. After receiving the second password encrypted information, the user uses the first password held by the user. The private key Ska is decrypted to obtain a second password Kb, and a third private key and a third public key are generated according to Kb.

FIG. 2 is a scene diagram of a preferred implementation manner provided by an embodiment of the present invention, as shown in FIG. 2:

After the client generates the first private key Ska and the first public key Pka according to the first password Ka, it sends signature information to the server. The signature information is generated by the first private key Ska signing the hash value of the latest block header of the blockchain. This ensures that the signature is up-to-date. After receiving the signature information sent by the user, the server uses the user's first public key Pka to pass the verification, and then sends to the user the first encrypted information m stored on the server by the user, and the user uses the first public key Pka to the mobile phone The encrypted number is generated. After receiving the encrypted mobile phone number, the user decrypts it with the first private key Ska to obtain the mobile phone number, and then encrypts the mobile phone number with the second public key of the server, sends it to the server, and the server uses its second private key. The decrypted mobile phone number is obtained, and the mobile phone number is hashed to obtain a second hash value y. The first hash value x of the mobile phone number hash that is stored on the blockchain by the user is obtained, and It ’s worth comparing with y. If the comparison is the same, then send a verification code to the user. The user returns the verification code to the server. After the server passes the verification, it sends the user the second password Kb encrypted information encrypted by the first public key Pka. The user uses the first private key Ska to decrypt the encrypted information to obtain a second password Kb, and generates a third private key and a third public key through the second password.

Here, the mobile phone number described is only a specific manifestation of contact information, and may also be other schemes such as a mailbox that can implement receiving a user verification code, and is not limited by this embodiment.

FIG. 3 is a scene diagram of another preferred embodiment of the method of the present invention. As shown in Figure 3,

After the client generates the first private key Ska and the first public key Pka according to the first password Ka, it sends signature information to the server. The signature information is generated by the first private key Ska signing the hash value of the latest block header of the blockchain. This ensures that the signature is up-to-date. After receiving the signature information sent by the user, the server uses the user's first public key Pka to pass the verification, and sends to the user the first encrypted information m stored on the server by the user. The encrypted information is used by the user to use the first public key Pka to the mobile phone. The encrypted number is generated. After receiving the encrypted mobile phone number, the user decrypts it with the first private key Ska to obtain the mobile phone number, and then encrypts the mobile phone number with the second public key of the server, sends it to the server, and the server uses its second private key. The decrypted mobile phone number is obtained, and the mobile phone number is hashed to obtain a second hash value y. The first hash value x of the mobile phone number hash that is stored on the blockchain by the user is obtained, and It ’s worth comparing with y. If the comparison is the same, it will verify that the information sent is correct, and directly send the user the second password Kb encrypted information encrypted by the first public key Pka, and the user decrypts with the first private key Ska to obtain the second password Kb. And generate a third private key and a third public key through the second password.

Here, the mobile phone number described is only a specific expression form of contact information, and may also be another scheme such as a mailbox that can implement receiving a user verification code, and is not limited by this embodiment.

FIG. 4 is a flowchart of step S15 of another preferred embodiment of the method shown in FIG. 1. As shown in FIG. 4, step S15 includes:

S151. Receive the second password encryption information, and decrypt the second password encryption information by using the first private key Ska to obtain a second password.

S152. Perform a specified first operation on the first private key Ska and the second password, and perform a hash operation on the operation result to generate a third private key and a third public key.

Specifically, after the user receives the second encrypted information n (the foregoing process is consistent with any of the methods in FIGS. 1-3, and is not repeated here), the user obtains the second password Kb after decrypting it using the first private key Ska held, Then, the first private key Ska and the second password Kb are serially connected, and then a hash operation is performed on the serialized result, and finally a third private key and a third public key are obtained.

The specified first operation described in step S152 here may refer to the serial connection of the first private key Ska and the second password Kb, or the serial connection of Kb first and Ska, or other arithmetic algorithms. Limitations of this embodiment.

FIG. 5 is a flowchart of another preferred embodiment of the present invention. As shown in FIG. 5, step S15 includes:

S151. Receive the second password encryption information, and decrypt the second password encryption information by using the first private key Ska to obtain a second password Kb.

S152 ': Hash the second password Kb to generate a third private key and a third public key.

Specifically, after the user receives the second encrypted information n (the foregoing process is consistent with any of the methods in FIGS. 1-3, and is not repeated here), the user obtains the second password Kb after decrypting it using the first private key Ska held, Then directly hash the second password Kb, and finally obtain a third private key and a third public key.

FIG. 6 is a flowchart of another preferred embodiment of the present invention. As shown in FIG. 6, in a preferred embodiment, in step S12, after the user sends the signature information to the server, the server further includes:

S121. After the server passes the verification, it is determined whether the user is registered with the third hash value of the first public key Pka. If it is not registered, it receives the unregistered information sent by the server and sends the registration information to the server for server verification. The registration information is associated with the first public key Pka, and the first public key Pka, the registration information, and a random number are hashed to obtain a fourth hash value, and the fourth hash value is stored in the blockchain, where The registration information includes the contact information and identity information of the user;

S122. Receive the first encrypted information m returned by the server.

Specifically, after the user sends the signature information to the server, the server verifies the signature information. After the verification is passed, the server checks whether the third hash value of the first public key Pka is registered. If it is not registered, it sends unregistered information to the user. The user After receiving the unregistered information, provide the server with identity information (such as identity information, fingerprint information, voiceprint information, face information, GPS location, login IP and other characteristic information) and contact information (such as phone number, email, and other contact information) ) Register, the server associates the user's first public key Pka with the registration information, and hashes the first public key Pka, the registration information, and a random number to obtain a fourth hash value, and saves the hash value to On the blockchain.

In addition, further preferably, the server may also sign the fourth hash value with a second private key, and send the signature to the blockchain.

After the user is registered, the server sends the first encrypted information m to the user. For other steps, refer to any one of the methods in FIG. 1 to FIG. 5, and details are not described herein again.

FIG. 7 is a schematic structural diagram of a public-private key pair generation system provided by the present invention. As shown in FIG. 7, in a preferred embodiment, a public-private key pair generation system 7 includes:

A first password generating unit 701 configured to generate a first password, and generate a first private key Ska and a first public key Pka according to the first password;

The first encrypted information receiving unit 702 is configured to send the signature information to the server for the server to verify the identity, and receive the first encrypted information returned by the server after the verification is passed; wherein the signature information is generated by the signature of the first private key Ska, the first An encrypted information m is generated by encrypting the first user information by using the first public key Pka, and the first user information includes contact information;

The second encrypted information n generating unit 703 is configured to decrypt the first encrypted information m by using the first private key Ska to obtain the first user information, and encrypt the first user information by using the second public key to generate a second Encrypted information n; wherein the second public key is the public key corresponding to the second private key held by the server;

The information sending unit 704 is configured to send the second encrypted information n to the server for the server to decrypt using the second private key, and hash the decrypted result of the second encrypted information n to obtain a second hash value y. And, the first hash value x recorded on the blockchain is obtained, and it is verified whether the first hash value x and the second hash value y are the same: Yes, the second password encryption information is issued through the contact information in the decryption result Wherein, the first hash value x is a hash value of the first user information, and the second password encryption information is generated by encrypting the second password by the first public key Pka;

The public-private key pair generation unit 705 is configured to receive the second password encryption information, decrypt the second password encryption information by using the first private key Ska, obtain a second password, and generate a third private key and a third public key according to the second password. key.

Further preferably, the public-private key pair generation unit 705 includes: a second password receiving subunit 7051 configured to receive a verification code through a contact method stipulated in the contact information, and send the verification code for the server to send the second password encrypted information after passing the verification, Receive the second password encryption message.

Further preferably, the public-private key pair generating unit 705 includes: a password receiving subunit 7052 configured to directly receive the second password encrypted information through a contact manner agreed in the contact information.

Further preferably, the public-private key pair generation unit 705 includes: a first public-private key generation subunit 7053 configured to perform a specified first operation on the first private key Ska and a second password, and perform a hash operation on the operation result to Generate a third private key and a third public key.

Further preferably, the public-private key pair generation unit 705 includes: a second public-private key generation sub-unit 7054 configured to perform a hash operation on the second password to generate a third private key and a third public key.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code, which contains one or more functions to implement a specified logical function Executable instructions. It should also be noted that in some alternative implementations, the functions noted in the blocks may also occur in a different order than those marked in the drawings. For example, two blocks represented one after the other may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified function or operation , Or it can be implemented by a combination of dedicated hardware and computer instructions.

The units or modules described in the embodiments of the present application may be implemented by software, or by hardware. The described units or modules may also be provided in the processor. For example, each unit may be a software program provided in a computer or a mobile smart device, or may be a separately configured hardware device. Among them, the names of these units or modules do not in any way constitute a limitation on the units or modules themselves.

The above description is only a preferred embodiment of the present application and an explanation of the applied technical principles. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to the technical solution of the specific combination of the above technical features, but should also cover the above technical features or Other technical solutions formed by arbitrarily combining their equivalent features. For example, a technical solution formed by replacing the above features with technical features disclosed in the present application (but not limited to) with similar functions.

[Correction 16.10.2019 under Rule 91]
[deleted]

Claims (13)

A method for generating a public-private key pair, comprising: Generating a first password, and generating a first private key and a first public key according to the first password; Sending the signature information to the server for the server to verify the identity, and receiving the first encrypted information returned by the server after the verification is passed; wherein the signature information is generated by the signature of the first private key, and the first encryption The information is generated by encrypting the first user information by using the first public key, and the first user information includes contact information; Decrypting the first encrypted information by using the first private key to obtain first user information, and encrypting the first user information by using a second public key to generate second encrypted information; Two public keys are public keys corresponding to the second private key held by the server; Sending the second encrypted information to the server for the server to decrypt through the second private key, and hashing the decrypted result of the second encrypted information to obtain a second hash value, and To obtain a first hash value recorded on the blockchain and verify whether the first hash value and the second hash value are the same: Yes, then issue a second password through the contact information in the decryption result Encrypted information; wherein the first hash value is a hash value of the first user information, and the second password encryption information is generated by encrypting the second password by using the first public key; Receive the second password encryption information, decrypt the second password encryption information by using the first private key, obtain the second password, and generate a third private key and a third public key based on the second password . The method according to claim 1, wherein the receiving the second password encryption information comprises: Receive the verification code through the contact method agreed in the contact information, send the verification code for the server to send the second password encryption information after verification, and receive the second password encryption information. The method according to claim 1, wherein the receiving the second password encryption information comprises: And receiving the second password encryption information directly through a contact manner stipulated in the contact information. The method according to claim 2 or 3, wherein generating the third private key and the third public key according to the second password comprises: Perform a predetermined first operation on the first private key and the second password, and perform a hash operation on the operation results to generate a third private key and a third public key. The method according to claim 2 or 3, wherein generating the third private key and the third public key according to the second password comprises: The second password is hashed to generate a third private key and a third public key. The method according to any one of claims 1-3, wherein the receiving the first encrypted information returned by the server after passing the authentication comprises: After the server passes the verification, it is determined whether the user is registered with the third hash value of the first public key. If it is not registered, it receives unregistered information sent by the server, and sends registration information to the server for the server. Server verification, associating the registration information with the first public key after passing the verification, and hashing the first public key, the registration information, and a random number to obtain a fourth hash value, and A fourth hash value is stored on the blockchain, wherein the registration information includes the contact information and identity information of the user; Receiving the first encrypted information returned by the server. The method according to claim 6, wherein the signature information includes a hash value of a latest block header on a blockchain. The method according to claim 7, wherein: The first hash value is signed with the first private key held, and the signature is sent to the blockchain. A public-private key pair generation system includes: A first password generating unit configured to generate a first password, and generate a first private key and a first public key according to the first password; A first encrypted information receiving unit configured to send signature information to a server for the server to verify the identity, and receive the first encrypted information returned by the server after the verification is passed; wherein the signature information is sent by the first A private key signature is generated, the first encrypted information is generated by encrypting the first user information by using the first public key, and the first user information includes contact information; A second encrypted information generating unit is configured to decrypt the first encrypted information by using the first private key to obtain first user information, and encrypt the first user information by using a second public key to generate Second encryption information; wherein the second public key is a public key corresponding to a second private key held by the server; An information sending unit configured to send the second encrypted information to the server for the server to decrypt by using the second private key, and hash the decryption result of the second encrypted information to obtain The second hash value, and acquiring the first hash value recorded on the blockchain, and verifying whether the first hash value and the second hash value are the same: if yes, then passing through the decryption result Contact information of the second password encryption information; wherein the first hash value is a hash value of the first user information, and the second password encryption information is used to encrypt the second password by using the first public key generate; A public-private key pair generation unit configured to receive the second password encryption information, decrypt the second password encryption information by using the first private key, obtain the second password, and generate the second password based on the second password Third private key and third public key. The system according to claim 9, wherein the public-private key pair generation unit comprises: The second password receiving subunit is configured to receive a verification code through a contact manner agreed in the contact information, send the verification code for the server to send the second password encryption information after the verification is passed, and receive the second password encryption information. The system according to claim 9, wherein the public-private key pair generation unit comprises: A password receiving subunit configured to directly receive the second password encrypted information through a contact manner agreed in the contact information The system according to claim 10 or 11, wherein the public-private key pair generation unit comprises: The first public and private key generation subunit is configured to perform a specified first operation on the first private key and the second password, and perform a hash operation on the operation result to generate a third private key and a third public key. The system according to claim 10 or 11, wherein the public-private key pair generation unit comprises: The second public and private key generation subunit is configured to hash the second password to generate a third private key and a third public key.

Images