TW202236131A - Digital signature private key verification method to ensure that the correlation between the private key and the issued document cannot be maliciously tampered with - Google Patents

Abstract

The present invention discloses a digital signature private key verification method. After receiving a verification data including a public key, a private key, a signature data, and a public and private key generation data, the server terminal uses a first hash algorithm to generate a hash value according to the public key and the signature data, and verifies the signature data according to the hash value. When the signature data is verified successfully, the server terminal transmits the hash value, the public key, the private key, and the public and private key generation data to the blockchain system. The blockchain system generates a target block corresponding to the blockchain system and including the hash value, the public key, the private key, and the public and private key generation data, and adds the target block to the blockchain corresponding to the blockchain system. Finally, the server terminal verifies the private key according to the public key of the target block and the public and private key generation data.

Description

Digital signature private key verification method

The invention relates to a verification method, in particular to a digital signature private key verification method.

A digital signature is a method that functions similarly to an ordinary signature written on paper, but uses techniques in the field of public key encryption to authenticate digital messages.

In use, there will be a private key that only the person knows, and a public key that is public. The private key is used when signing, and the public key is used when verifying the signature. Because anyone can sign the money claiming that he is the sender himself, the sender's public key must be registered with someone trusted by the recipient (the identity authentication authority). After registration, the authentication authority sends a digital certificate to the sender. After signing the file, the sender sends the digital certificate together with the file and the signature to the recipient, and the recipient asks the identity authentication agency whether it is really a file signed with the sender's private key.

However, if the identity authentication agency is hacked and the information of the identity authentication agency is maliciously tampered with, its fairness cannot be guaranteed.

Therefore, the object of the present invention is to provide a digital signature private key verification method that can ensure that the association between the private key and the issued file cannot be maliciously tampered with.

Therefore, the digital signature private key verification method of the present invention is implemented by a server end, a user end, and a block chain system, and the server end is connected to the use end and the block chain system through a communication network. The signature private key verification method includes a step (A), a step (B), a step (C), a step (D), a step (E), a step (F), and a step (G).

In the step (A), after receiving a verification data from the client, the verification data includes a public key, a private key, a signature data, and a parameter required to generate the public key and the private key According to the public key and the signature data, the server uses a first hash algorithm to generate a hash value, and verifies the signature data according to the hash value.

In the step (B), when the verification of the signed data is successful, the server sends the hash value, the public key of the verification data, the private key, and the data generated by the public and private keys to the blockchain system.

In the step (C), the blockchain system generates data based on the hash value and the public key, the private key, and the public-private key of the verification data, and generates a pair of corresponding blockchain systems including the hash value And the public key, the private key of the verification data, and the target block of the data generated by the public and private key.

In the step (D), the block chain system adds the target block to a block chain corresponding to the block chain system to generate a transaction identification code related to the target block, and the transaction The identification code is sent to the server.

In the step (E), the server generates and sends a data request including the transaction identification code to the blockchain system.

In the step (F), the block chain system transmits the hash value of the target block and the public key, the private key, and the public-private key generation of the verification data according to the transaction identification code requested by the data. data to the server.

In the step (G), the server verifies the private key of the verification data according to the public key of the verification data of the target block and the public-private key generation data.

The effect of the present invention is: verify the signed data according to the hash value by the server to verify the correlation between the signed data and the private key, and after successful verification, send the hash value and the public key of the verified data key, the private key, and the public-private key-generated data to the blockchain system, and verify the public key, the private key, and the public-private key-generated data of the verification data of the blockchain system again to ensure transmission The information on the way to the blockchain system has not been tampered with. When the verification is successful, it means that the association between the private key and the signed data has not been tampered with, and based on the characteristics of the blockchain, the private key The association with the signed data cannot be maliciously tampered with.

Before the present invention is described in detail, it should be noted that in the following description, similar elements are denoted by the same numerals.

Referring to FIG. 1 , a server 11 , a user 12 , and a blockchain system 13 for implementing an embodiment of the digital signature private key verification method of the present invention are illustrated.

The server 11 is connected to the user 12 and the blockchain system 13 via a communication network 100 , and the server 11 is, for example, a personal computer, a notebook computer, a server computer, or a cloud server. The user terminal 12 stores a signature data, the signature data includes a signatory image related to a signatory, a signature video related to the signing process of the signatory, a signature image related to the signature of the signatory, and One of at least one of the signature handwriting tracks related to the signature of the signatory, the user terminal 12 is, for example, a personal computer, a notebook computer, a tablet computer, or a smart phone, and the communication network 100 is, for example, the Internet Road (Internet), but not limited to this.

Referring to Figures 1 and 2, the following will illustrate the server end 11, the user end 12, and the details of the operation of each element of the block chain system 13 by this embodiment of the digital signature private key verification method of the present invention, and include the following step.

In step 21, the user terminal 12 obtains the public key, the private key, and a public-private key generation data with parameters required for generating the public key and the private key according to a predetermined value and a plurality of random key (Key) values . It is worth noting that, in this embodiment, the predetermined value is one of a facial feature value, a one-time password (One Time Password, OTP), and a file hash value related to a file, but not This is the limit.

Referring to FIG. 3 , step 21 includes sub-steps 211 to 213 , and the sub-steps included in step 21 are described below.

In step 211 , the client 12 obtains a plurality of digest values respectively corresponding to the random key values by using a second hash algorithm according to the predetermined value and the random key values. It should be noted that, in this embodiment, the second hash algorithm is, for example, a hash-based message authentication code (Hash-based Message Authentication Code, HMAC) algorithm, but it is not limited thereto.

In step 212, the user terminal 12 concatenates the digest values to obtain a concatenated value. It should be noted that, in this embodiment, the length of the concatenated value is, for example, 128 bits, and in other implementation manners, it may also be 256 bits, which is not limited thereto.

In step 213, the user 12 obtains the public key, the private key, and the public-private key generation data according to the concatenated value.

，其中

，

，若該串接值與該乘積值

互質，則該串接值為該私鑰 d，若該串接值與該乘積值

不互質時，則慢慢增加該串接值直到該串接值與該乘積值

互質(例如每次該串接值增加1，直到該串接值與該乘積值

互質)，以將與該乘積值

互質的值作為該私鑰 d，且該公鑰 e以下式獲得： d× e≡1 (mod ( p-1)( q-1))， 其中， d為該私鑰， e為該公鑰，該公鑰 e與該乘積值

互質，且該公鑰 e小於該乘積值

，該公私鑰產生資料包括該第一質數 p、該第二質數 q，及該乘積值

。 In detail, the user terminal 12 obtains a product value according to a first prime number p and a second prime number q different from the first prime number

,in

,

, if the concatenated value and the product value

mutual prime, then the concatenation value is the private key d , if the concatenation value and the product value

When not mutually prime, slowly increase the concatenation value until the concatenation value and the product value

Mutually prime (for example, each time the concatenation value increases by 1, until the concatenation value and the product value

coprime), so that the product value with the

The mutually prime value is used as the private key d , and the public key e is obtained by the following formula: d × e ≡1 (mod ( p -1)( q -1)), where d is the private key, e is the public key key, the public key e and the product value

Mutually prime, and the public key e is less than the product value

, the public-private key generation data includes the first prime number p , the second prime number q , and the product value

.

In step 22, the client 12 uses a first hash algorithm to generate a verification code according to the signature data. It should be noted that, in this embodiment, the first hash algorithm is, for example, a secure hash algorithm (Secure Hash Algorithm, SHA), but it is not limited thereto.

In step 23, the client 12 uses the private key to encrypt the signature data, the verification code, and a short certificate related to the validity period of the public key and the private key to generate an encrypted , the verification code and the signature information of the short certificate.

In step 24, the client 12 generates and transmits a verification data to the server 11 according to the public key, the private key, the data generated by the public and private keys, and the signature data, the verification data includes the public key, the The private key, the signing data, and the public and private key generation data.

In step 25, the server 11 uses the first hash algorithm to generate a hash value according to the public key and the signature data.

In step 26, the server 11 verifies the signature data according to the hash value. When the verification of the signature data fails, the process proceeds to step 27 ; and when the verification of the signature data succeeds, the process proceeds to step 28 .

With reference to FIG. 4 , step 26 includes sub-steps 261 to 263 , and the sub-steps included in step 26 are described below.

In step 261, the server 11 uses the public key to decrypt the signature data to obtain the verification code and the signature data.

In step 262, the server 11 uses the first hash algorithm to generate the hash value according to the signature data.

In step 263, the server 11 judges whether the hash value is equal to the verification code to verify the signed data. When it is judged that the hash value is not equal to the verification code, it means that the verification fails, and the process proceeds to step 27; when it is judged that the hash value is equal to the verification code, it means that the verification is successful, and the process proceeds to step 28.

In step 27 , the server 11 generates and sends an error message to the user 12 .

In step 28 , the server 11 sends the public key, the private key, and the public-private key generation data of the hash value and the verification data to the blockchain system 13 .

In step 29, the block chain system 13 generates data based on the hash value and the public key, the private key, and the public-private key of the verification data, and generates a pair of block chain systems 13 including the hash value and The public key, the private key of the verification data, and the target block of data generated by the public and private keys.

In step 30, the block chain system 13 adds the target block to a block chain corresponding to the block chain system 13 to generate a transaction identification code related to the target block and a record of the target block Add the time stamp (time stamp) of the block chain time to the block, and transmit the transaction identification code and the time stamp to the server 11. It is worth noting that in this embodiment, the time stamp can indicate that the signed data has been notarized at the time of the time stamp, and the short certificate will expire in a short time to ensure that the signed data can only be used around the time stamp , so that the private key is only used for the signing data. In other implementations, the blockchain system 13 can only generate and transmit the transaction identification code to the server 11, but it is not limited thereto.

In step 31 , the server 11 generates and sends a data request including the transaction identification code to the blockchain system 13 .

In step 32, the block chain system 13 transmits the hash value of the target block and the public key, the private key, and the public-private key generation data of the verification data according to the transaction identification code requested by the data to The server end 11.

In step 33, the server 11 generates data according to the public key and the public-private key of the verification data of the target block, and verifies the private key of the verification data to verify whether the private key of the verification data is obtained from The predetermined value and the random key values in step 21 are generated. When the verification of the private key of the verification material fails, the process proceeds to step 27; and when the verification of the private key of the verification material succeeds, the process ends.

Referring to FIG. 5 , step 33 includes sub-steps 331 to 332 , and the sub-steps included in step 25 are described below.

In step 331, the server 11 generates a verification private key according to the public-private key generation data and the public key.

Specifically, the server 11 calculates the verification private key d ′ according to the first prime number p and the second prime number q of the public-private key generation data and the public key e .

In step 332, the server 11 determines whether the verification private key is equal to the private key to verify the private key. When it is judged that the verification private key is not equal to the private key, it means that the private key of the verification data is not generated by the predetermined value and the random key values in step 21, the verification fails, and the process proceeds to step 26; When the verification private key is equal to the private key, it means that the private key of the verification data is generated by the predetermined value and the random key values in step 21, the verification is successful, and the process ends.

To sum up, in the digital signature private key verification method of the present invention, the server 11 verifies the signature data according to the hash value, so as to verify the correlation between the signature data and the private key, and after successful verification, transmit The public key, the private key, and the public-private key generation data of the hash value and the verification data are sent to the blockchain system 13, and the blockchain system 13 generates the public key, including the hash value and the verification data, The private key, and the public-private key generate the target block of data, and add the target block to the block chain corresponding to the block chain system 13, the server 11 obtains from the block chain system 13 and Verify the hash value of the target block and the public key of the verification data, the private key, and the data generated by the public and private keys to ensure that the data transmitted to the blockchain system 13 has not been tampered with. When the verification is successful, it means that the association between the private key and the signed data has not been tampered with, and based on the characteristics of the blockchain, the association between the private key and the signed data cannot be maliciously tampered with, so this can indeed be achieved. purpose of the invention.

But the above-mentioned ones are only embodiments of the present invention, and should not limit the scope of the present invention. All simple equivalent changes and modifications made according to the patent scope of the present invention and the content of the patent specification are still within the scope of the present invention. Within the scope covered by the patent of the present invention.

11: Server side 12: Use end 13: Blockchain system 100: Communication network 21~33: Steps 211~213: Steps 261~263: Steps 331~332: Steps

Other features and effects of the present invention will be clearly presented in the implementation manner with reference to the drawings, wherein: Fig. 1 is a block diagram illustrating a connection relationship between a server end, a user end, and a block chain system for implementing an embodiment of the digital signature private key verification method of the present invention; Fig. 2 is a flowchart illustrating this embodiment of the digital signature private key verification method of the present invention; Fig. 3 is a flow chart, assists in explaining the sub-steps that step 21 of Fig. 2 comprises; FIG. 4 is a flow chart to assist in explaining the sub-steps included in step 25 of FIG. 2; and FIG. 5 is a flowchart to assist in explaining the sub-steps included in step 32 of FIG. 2 .

21~33: Steps

Claims (10)

A digital signature private key verification method is implemented by a server, a user, and a block chain system, the server is connected to the user and the block chain system through a communication network, and the digital signature is private The key authentication method consists of the following steps: (A) After the server receives a verification data from the client, the verification data includes a public key, a private key, a signature data, and a The public and private key generation data of the parameters, using a first hash algorithm to generate a hash value based on the public key and the signing data, and verifying the signing data according to the hash value; (B) Through the server, when the verification of the signature data is successful, transmit the hash value and the public key of the verification data, the private key, and the data generated by the public and private keys to the blockchain system; (C) Generate data based on the public key, the private key, and the public-private key of the hash value and the verification data through the blockchain system, generate a pair of blockchain systems including the hash value and the Verify the public key of the data, the private key, and the target block of the data generated by the public and private key; (D) Add the target block to a block chain corresponding to the block chain system through the block chain system to generate a transaction identification code related to the target block, and use the transaction identification code sent to the server; (E) generating and sending a data request including the transaction identification code to the blockchain system through the server; (F) Send the hash value of the target block and the public key, the private key, and the public-private key generation data of the verification data to the server; and (G) Verifying the private key of the verification data by the server side according to the public key of the verification data of the target block and the public-private key generation data. The digital signature private key verification method as described in claim item 1 also includes the following steps before step (A): (H) Obtain the public key, the private key, and the public-private key generation data according to a predetermined value and a plurality of random key values through the client; (1) using the first hash algorithm to generate a verification code according to a signature data by the user; (J) using the private key to encrypt the signature data and the verification code by the client to generate the signature data with the signature data and the verification code; and (K) Using the client to generate and transmit the verification data including the verification code and the signature data to the server according to the public key, the private key, the public-private key-generated data, and the signature data. The digital signature private key verification method as described in claim 2, wherein, step (H) includes the following sub-steps: (H-1) Obtain a plurality of digest values respectively corresponding to the random key values by using a second hash algorithm according to the predetermined value and the random key values by the user end; (H-2) concatenating the digest values by the client to obtain a concatenated value; and (H-3) Obtain the public key, the private key, and the public-private key generation data according to the concatenated value through the client. The digital signature private key verification method as described in claim 3, wherein, in step (A), the first hash algorithm is a secure hash algorithm, and in step (H-1), the second hash algorithm The method is a hash operation message authentication code algorithm. The digital signature private key verification method as described in claim 3, wherein, in step (K) and step (A), the signing data also has a file, and in step (H-1), the predetermined value is One of a facial feature value, a one-time password, and a file hash value related to the file. The digital signature private key verification method as described in Claim 3, wherein, in step (H-3), the user obtains a prime number p based on a first prime number p and a second prime number q different from the first prime number product value

,in

,

, if the concatenated value and the product value

When not mutually prime, increase the concatenated value until the concatenated value and the product value

are mutually prime, and the public key e is obtained by the following formula: d × e ≡1 (mod ( p -1)( q -1)), where d is the private key, e is the public key, and the public key e and The product value

Mutually prime, and the public key e is less than the product value

, the public-private key generation data includes the first prime number p , the second prime number q , and the product value

. The digital signature private key verification method as described in claim 2, wherein, in step (1), the signature data includes a signatory image related to a signatory, a signature related to the signing process of the signatory At least one of a video, a signature image related to the signatory's signature, and a signature handwriting trace related to the signatory's signature. The digital signature private key verification method as described in claim 2, wherein, in step (J), the user also encrypts a short certificate related to the validity period of the public key and the private key, and the signature data Also having the short certificate, in step (D), the block chain system also generates a time stamp recording the time when the target block was added to the block chain, and also transmits the time stamp to the server. The digital signature private key verification method as described in claim 1, wherein, step (A) includes the following sub-steps: (A-1) Use the public key to decrypt the signature data to obtain the verification code and the signature data; (A-2) using the first hash algorithm to generate the hash value based on the signature data; and (A-3) Judging whether the hash value is equal to the verification code, so as to verify the signed data. The digital signature private key verification method as described in claim 1, wherein, step (G) includes the following sub-steps: (G-1) Generate data according to the public and private keys and generate a verification private key from the public key through the server; and (G-2) Using the server to determine whether the verification private key is equal to the private key to verify the private key.

Images