Skip to content

THE PROCESS OF SIGNING AND VERIFYING DIGITAL SIGNATURES (Part 2)

After the signer hashes the content of the contract into a hash string, they use their private key to sign that hash, creating a digital signature cipher hash A.

The process of verifying the digital signature information (Verification) is as follows:

1. The recipient receives the contract document, including the main content and the digital signature “cipher hash A”. At this point, the recipient separates the contract document content and the digital signature for independent processing.

2. In the contract document content, the recipient performs a similar task to the signer. They use a hash algorithm program (MD5 or SHA), similar to the signer, to hash the word document. This results in a unique character string with a fixed length.

Let’s call this string H2, representing the hash string of the recipient, which has been hashed:
(software) -> hash + word file -> string H2.

3. The recipient uses the signer’s public key (signer public key) to decrypt the “cipher hash A” attached to the contract document, resulting in the string “string H”: cipher hash A + signer’s public key -> string H.

4. Compare the information between string H and string H2. If they match, it means the content is accurate, and there has been no alteration to the content. The accuracy of the person who created the document is verified, completing the digital signature information verification process.

—————————–

Source: Admin compilation