Mutual signing and mutual checking method and system for electronic signature

Abstract

The invention discloses a mutual signing and mutual checking method and system for electronic signatures, and belongs to the technical field of electronic signatures, and the method comprises the steps: an enterprise uploads a blank contract template covered with an electronic signature, a client terminal carries out the uniform segmentation of the electronic signature, carries out the transformation and modification of the electronic signature based on a unique identification code, and enables the electronic signature to serve as an enterprise checking voucher. A paper signature image and an enterprise inspection voucher are uploaded to a service terminal, an enterprise user shoots the paper signature, the service terminal verifies both parties of the enterprise user and establishes an encrypted signing channel, and when the enterprise user signs a contract, client terminals of both parties send own unique identification codes to the opposite parties, so that the enterprise user can check the signed contract. The verification is carried out based on the unique identification code of the other enterprise, the electronic contract covered with the electronic signature is sent to the client terminal of the other enterprise, and the electronic signature on the electronic contract is verified, so that a third party can be prevented from signing an uneven contract by using a false electronic signature, and the confidentiality of the electronic signature and the electronic contract of the enterprise is improved.

Description

Technical Field

[0001] This application belongs to the field of electronic signature technology, specifically, it relates to a method and system for mutual signing and verification of electronic signatures. Background Technology

[0002] Electronic contracts, also known as e-commerce contracts, are agreements reached between two or more parties in electronic form through electronic information networks to establish, modify, or terminate property-related civil rights and obligations. This changes the traditional practice of using paper as the original evidence. Electronic signature systems are a high-tech technology that has emerged with the development of information technology. They mainly solve the problem of signing and sealing electronic documents, and are used to identify the signatory of electronic documents, ensure the integrity of documents, and ensure the authenticity, reliability, and non-repudiation of documents.

[0003] Existing electronic signature systems typically encrypt the electronic contracts and signatures of both parties during transmission to mitigate security risks. However, if one party's electronic signature is leaked to a malicious individual before signing, allowing them to use the leaked signature to sign and seal electronic contracts with other companies in the name of their own company, the existing system will determine the initiator's compliance and make the contract valid, potentially leading to disputes or adverse consequences for both companies. Furthermore, if one party uses a fake electronic signature for profit, it will also negatively impact the other party. Moreover, if each registered company uploads its electronic signature and contract to a server for verification, an attack on the server to steal these documents could result in even more severe economic losses. Summary of the Invention

[0004] To address the aforementioned problems and technical deficiencies, this application adopts the following technical solution: a method for mutual signing and verification of electronic signatures, comprising the following steps:

[0005] Enterprises upload blank contract templates with electronic signatures to the client terminal. The client terminal evenly divides the electronic signatures on the blank contract templates, transforms and modifies each divided electronic signature based on a unique identifier, and uses it as the enterprise's verification certificate. The paper signature image and all enterprise verification certificates are then uploaded to the service terminal.

[0006] Before signing a contract, enterprise users take a picture of the paper seal. The service terminal verifies both parties based on the image of the paper seal. After verification, an encrypted signing channel is established between the client terminals of both parties.

[0007] Enterprise users will download the corresponding client on their mobile phones or log in via a webpage. They will scan and photograph the paper signature using their mobile phones. The service terminal will compare and verify the scanned content with the uploaded paper signature image. Once the verification is successful, the service terminal will establish an encrypted signing channel and return a channel login code to the enterprise user. Both enterprise users will enter the channel login code to join the encrypted signing channel.

[0008] When enterprise users sign a contract, both parties' client terminals send their own unique identification codes to each other. Based on the other party's unique identification codes, the electronic contract with the electronic seal is sent to the other enterprise's client terminal. At the same time, the electronic seal on the electronic contract is verified based on the other enterprise's verification certificate. After the verification is successful, both parties sign the electronic contract.

[0009] Preferably, the unique identifier is generated by the client terminal after the enterprise user downloads the client terminal and performs authentication, registration and binding;

[0010] The unique identifier is generated by encoding the IP address, enterprise account ID, hardware machine code, account registration time, and client terminal unique code according to pre-defined encoding rules.

[0011] Furthermore, the pre-defined encoding rules within the client terminal are obtained through a predefined strong hash function and concatenation obfuscation rules;

[0012] During installation and registration, the client terminal obtains its current public IP address and generates a fixed-length IP address code according to predefined rules.

[0013] When a user registers a corporate account, the service terminal uses a globally unique and unchangeable corporate account ID number assigned to the corporate account.

[0014] Collect the CPU's unique serial number to generate the CPU code, collect the motherboard's serial number or UUID to generate the motherboard code, and combine the CPU code and the motherboard code to generate the hardware machine code.

[0015] The precise timestamp of when a user completes the registration and binding of their enterprise account is used as the account registration time.

[0016] Furthermore, when a user successfully downloads and installs the client terminal software package for the first time, the service terminal uses a secure random number generator to generate a strong random number as a unique code for the client terminal and stores it in the service terminal, while simultaneously sending it to the client terminal's local encrypted database.

[0017] The unique identifier of the client terminal is stored in a local encrypted database, and the original parameters are encrypted and modified during transmission.

[0018] The service terminal stores a unique identifier and the latest verification certificate associated with it.

[0019] Preferably, the verification based on the other party's unique identifier includes:

[0020] Collect some information from the other party's client terminal, including IP address encoding, enterprise account ID number, and hardware machine code;

[0021] Based on pre-defined encoding rules, some information is independently encoded. The encoded identifier is then matched one by one with the unique identifier. If a match fails, the encrypted signing channel is closed.

[0022] Preferably, the verification of the electronic signature on the electronic contract based on the verification certificate includes:

[0023] The client terminal retrieves and downloads the other party's inspection certificate from the service terminal;

[0024] The electronic signature on the electronic contract is modified based on the unique identifier of the other party's client terminal.

[0025] The modified electronic signature will be matched and similarity calculated with all inspection certificates one by one.

[0026] The calculation result is compared with a preset verification threshold. If the result is lower than the preset verification threshold, the verification fails.

[0027] Furthermore, the client terminal has a built-in encoder converter that converts the unique identifier into a multi-dimensional vector;

[0028] By using multidimensional vectors to modify the electronic signature on a blank contract template or electronic contract in multiple dimensions, a transformed and modified verification signature can be obtained.

[0029] The process of making multi-dimensional modifications to an electronic signature is as follows:

[0030] Load and extract the electronic signature image that needs to be modified from the blank contract template, and evenly segment the electronic signature image;

[0031] The parser reads the currently valid unique identifier and uses a preset deterministic pseudo-random function algorithm to convert the unique identifier into a high-dimensional feature vector with a fixed dimension.

[0032] Feature extraction is performed on the segmented electronic signature image to obtain an initial signature vector that can characterize the visual structural characteristics of the signature;

[0033] The high-dimensional feature vector is modulated into spatial domain parameters applied to the signature image. The spatial domain parameters are input into a specific dimension of a specific transformation matrix, and the perturbation vector is output. The perturbation vector is used to perform nonlinear offset, scaling and permutation on the initial signature vector to obtain the transformed signature vector.

[0034] The merged and transformed signature vector is reconstructed into a new signature image, which is then used as the verification signature.

[0035] A system for mutual signing and verification of electronic signatures includes:

[0036] The registration and binding module is used to authenticate, register, and bind enterprise users, and generate unique identification codes;

[0037] The voucher generation module is used to transform and modify the electronic signature on the blank contract template based on the unique identifier code, and use it as the company's verification voucher.

[0038] Service terminals are used to acquire and store the company's inspection certificates;

[0039] The contract verification module is used to verify the content format of electronic contracts based on a blank contract template from another company.

[0040] The contract verification module is used to send an electronic contract bearing an electronic signature to another company, and at the same time verify the electronic signature on the electronic contract based on the other company's inspection certificate.

[0041] An electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the content of the electronic signature mutual verification method as described above.

[0042] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the content of the electronic signature mutual signing and verification method as described above.

[0043] Compared to existing technologies, the beneficial effects of this application are as follows:

[0044] This application generates a unique identifier code that is bound to enterprise users and client terminals. The electronic signature is modified using the unique identifier code and uploaded to the service terminal. When the two enterprises sign a contract, the electronic signature is modified using the other party's current electronic signature and the unique identifier code. The similarity between the modified content on the server and the current modified content is then calculated. When a third party steals the enterprise account and electronic signature, the unique identifier code of the third party's client terminal cannot obtain the same verification signature as the service terminal, thus preventing the enterprise from signing illegal contracts with third parties and causing economic losses.

[0045] At the same time, when one of the contracting companies uses a fake electronic signature, even if the unique identifier is genuine, it will not be able to obtain the same verification signature as the service terminal. This prevents companies from signing unequal contracts and incurring economic losses when the other party has malicious intent and uses a fake electronic signature.

[0046] Moreover, this application only requires uploading a blank contract template with the stamped and modified signature. What is sent to the other party is the electronic signature stamped on the electronic contract. The company does not need to provide an initial independent electronic signature and specific electronic contract content to the server. Even if the server terminal is attacked directly, there will be no leakage of the company's electronic signature or electronic contract, thus improving the confidentiality of the company's electronic signature and electronic contract. Attached Figure Description

[0047] In the attached diagram:

[0048] Figure 1 This is a schematic diagram of the method steps in an embodiment of this application;

[0049] Figure 2 This is a schematic diagram of the system structure according to an embodiment of this application;

[0050] Figure 3 This is a schematic diagram of the device structure according to an embodiment of this application. Detailed Implementation

[0051] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are some embodiments of this application, but not all embodiments. Generally, the components of the embodiments of this application described and shown in the accompanying drawings can be arranged and designed in various different configurations.

[0052] Example 1

[0053] like Figure 1 As shown, a method for mutual signing and verification of electronic signatures includes the following steps:

[0054] Enterprises upload blank contract templates with electronic signatures to the client terminal. The client terminal evenly divides the electronic signatures on the blank contract templates, transforms and modifies each divided electronic signature based on a unique identifier, and uses it as the enterprise's verification certificate. The paper signature image and all enterprise verification certificates are then uploaded to the service terminal.

[0055] The unique identifier is generated by the client terminal after the enterprise user downloads the client terminal and completes authentication, registration, and binding.

[0056] The unique identifier is generated by encoding the IP address, enterprise account ID, hardware machine code, account registration time, and client terminal unique code based on pre-defined encoding rules.

[0057] The pre-defined encoding rules within the client terminal are obtained through a predefined strong hash function and concatenation obfuscation rules;

[0058] During installation and registration, the client terminal obtains its current public IP address and generates a fixed-length IP address code according to predefined rules.

[0059] When a user registers a corporate account, the service terminal uses a globally unique and unchangeable corporate account ID number assigned to the corporate account.

[0060] Collect the CPU's unique serial number. If there is no unique serial number or it is disabled for privacy reasons, use a combination hash of CPU model + stepping + number of cores + frequency to generate the CPU code.

[0061] Collect the motherboard serial number or UUID. If not, generate the motherboard code using a combination hash of motherboard model, manufacturer, and BIOS version.

[0062] The CPU code and motherboard code are combined to generate hardware machine code.

[0063] The precise timestamp used by a user to complete the registration and binding of their enterprise account is used as the account registration time, with the timestamp accurate to the millisecond level.

[0064] When a user successfully downloads and installs the client terminal software package for the first time, the server terminal uses a secure random number generator to generate a strong random number as a unique code for the client terminal and stores it in the server terminal. At the same time, it sends the code to the client terminal's local encrypted database.

[0065] The unique identifier of the client terminal is stored in a local encrypted database, and the original parameters are encrypted and modified during transmission.

[0066] The service terminal stores a unique identifier and the latest verification certificate associated with it.

[0067] The unique identifier for a client terminal is a unique identifier generated and sent to the client terminal by the service terminal each time the client terminal is downloaded and installed.

[0068] If a company's computer is accidentally installed with a new client terminal, the service terminal will re-verify the company's users (by phone, SMS, and facial recognition) and generate a new unique identifier for the client terminal.

[0069] Similarly, when a company replaces its computers, changes its computer hardware, or changes its IP address, the service terminal will also re-authenticate the company user.

[0070] At the same time, the electronic signature on the blank contract template is changed and modified and uploaded to the service terminal, which uses it as a new verification certificate for the enterprise.

[0071] The re-verification process includes:

[0072] When the client terminal detects a change or receives a reset command, it initiates a re-verification request to the service terminal using the enterprise account ID number.

[0073] After receiving the re-authentication request, the service terminal triggers multi-factor authentication:

[0074] The first factor: SMS verification code or voice verification code based on the reserved mobile phone number;

[0075] The second factor: The terminal camera captures dynamic faces, performs liveness detection, and compares them with pre-registered biometric features.

[0076] The third factor: verification link based on the reserved email address, or confirmation via manual phone call back;

[0077] After successful verification, the service terminal generates a new unique code for the client terminal, and the client terminal collects the current IP address code and hardware machine code to generate a new unique identifier.

[0078] The service terminal marks the old unique identifier as invalid and notifies the enterprise customer terminal that subsequent operations must use the new unique identifier.

[0079] Before signing a contract, enterprise users take a picture of the paper seal. The service terminal verifies both parties based on the image of the paper seal. After verification, an encrypted signing channel is established between the client terminals of both parties.

[0080] When enterprise users sign a contract, both parties' client terminals send their own unique identification codes to each other. Based on the other party's unique identification codes, the electronic contract with the electronic seal is sent to the other enterprise's client terminal. At the same time, the electronic seal on the electronic contract is verified based on the other enterprise's verification certificate. After the verification is successful, both parties sign the electronic contract.

[0081] Verification based on the other party's unique identifier includes:

[0082] Collect some information from the other party's client terminal, including IP address encoding, enterprise account ID number, and hardware machine code;

[0083] Based on pre-defined encoding rules, some information is independently encoded. The encoded identifier is matched one by one with the unique identifier. If the match fails, the encrypted signing channel is closed. The unique identifier has an expiration time.

[0084] Ensure that the unique identifier sent by the other party's client terminal matches the other party's information, and prevent the other party from using a false unique identifier.

[0085] Verification of electronic signatures on electronic contracts based on inspection certificates includes:

[0086] The client terminal retrieves and downloads the other party's inspection certificate from the service terminal;

[0087] The electronic signature on the electronic contract is modified based on the unique identifier of the other party's client terminal.

[0088] The modified electronic signature will be matched and similarity calculated with all inspection certificates one by one.

[0089] The calculation result is compared with a preset verification threshold. If the result is lower than the preset verification threshold, the verification fails.

[0090] If the verification fails, the electronic contract signing process will be terminated, and the signing process will be deemed invalid.

[0091] If the verification is successful, the contract is deemed valid.

[0092] The client terminal has a built-in encoder-converter that converts the unique identifier into a multi-dimensional vector.

[0093] By using multidimensional vectors to modify the electronic signature on a blank contract template or electronic contract in multiple dimensions, a transformed and modified verification signature can be obtained.

[0094] Multidimensional modifications are irreversible; reversing the modification of a verification signature will not yield the original electronic signature.

[0095] The encoding converter includes: a parser that securely reads unique identifiers from local storage, and an engine that implements specific irreversible mathematical transformations and vector conversions.

[0096] The process of making multi-dimensional modifications to an electronic signature is as follows:

[0097] Load and extract the electronic signature image that needs to be modified from the blank contract template, and evenly segment the electronic signature image;

[0098] The parser reads the currently valid unique identifier and uses a preset deterministic pseudo-random function algorithm to convert the unique identifier into a high-dimensional feature vector with a fixed dimension (the same unique identifier input yields the same vector, but the high-dimensional feature vector is highly discretized).

[0099] Feature extraction is performed on the segmented electronic signature image to obtain an initial signature vector that can characterize the visual structural characteristics of the signature;

[0100] The high-dimensional feature vector is modulated into spatial domain parameters applied to the signature image. The spatial domain parameters are input into a specific dimension of a specific transformation matrix, and the perturbation vector is output. The perturbation vector is used to perform nonlinear offset, scaling and permutation on the initial signature vector to obtain the transformed signature vector.

[0101] The merged and transformed signature vector is reconstructed into a new signature image, which is then used as the verification signature.

[0102] Example 2

[0103] Company A and Company B upload blank contract templates with electronic signatures to their own client terminals. The client terminals modify the electronic signatures on the blank contract templates based on unique identifiers and upload them to the service terminal. The service terminal uses them as inspection vouchers for Company A and Company B.

[0104] If Company A's account and electronic signature A are leaked, and a third party C wants to use Company A's account and electronic signature A to sign a contract with Company B and profit from it;

[0105] C sends the electronic contract bearing A's electronic signature to B's client terminal;

[0106] Company B obtains the unique identifier C of customer terminal C, and then modifies the electronic signature A based on the unique identifier C to obtain the verification certificate AC. The similarity calculation is performed between AC and the verification certificate A in the server. If the similarity fails, the electronic contract signing process is terminated and the signing process is deemed invalid.

[0107] Example 3

[0108] Company A and Company B upload blank contract templates with electronic signatures. The client terminal modifies the electronic signatures on the blank contract templates based on the unique identifier and uploads them to the service terminal. The service terminal uses them as the inspection certificate for Company A and the inspection certificate for Company B.

[0109] If Company A wants to use a fake electronic signature X to sign a contract with Company B and profit from it;

[0110] Company A sends an electronic contract bearing a fake electronic signature X to Company B's client terminal.

[0111] Company B obtains the unique identifier A from customer A's terminal, then modifies the fake electronic signature X based on the unique identifier A to obtain the verification certificate AX. The similarity calculation is performed between AX and the verification certificate A in the server, and the verification fails. The electronic contract signing process is then terminated, and the signing process is deemed invalid.

[0112] Example 4

[0113] like Figure 2 As shown, an electronic signature mutual signing and verification system includes:

[0114] The registration and binding module is used to authenticate, register, and bind enterprise users, and generate unique identification codes;

[0115] The unique identifier is generated by the client terminal after the enterprise user downloads the client terminal and completes authentication, registration, and binding.

[0116] The unique identifier is generated by encoding the IP address, enterprise account ID, hardware machine code, account registration time, and client terminal unique code based on pre-defined encoding rules.

[0117] The voucher generation module is used to transform and modify the electronic signature on the blank contract template based on the unique identifier code, and use it as the company's verification voucher.

[0118] Service terminals are used to acquire and store the company's inspection certificates;

[0119] The contract verification module is used to verify the content format of electronic contracts based on a blank contract template from another company.

[0120] The signature verification module is used to send an electronic contract bearing an electronic signature to another company, and at the same time verify the electronic signature on the electronic contract based on the other company's inspection certificate.

[0121] When enterprise users sign a contract, both parties will establish an encrypted signing channel. Both parties will send their own unique identification code to each other for verification.

[0122] Verification based on the other party's unique identifier includes:

[0123] Collect some information from the other party's client terminal, including IP address encoding, enterprise account ID number, and hardware machine code;

[0124] Based on pre-defined encoding rules, some information is independently encoded. The encoded identifier is then matched one by one with the unique identifier. If a match fails, the encrypted signing channel is closed.

[0125] Verification of electronic signatures on electronic contracts includes:

[0126] The system retrieves and downloads the inspection certificate from the other party's company from the service terminal. Based on the other party's unique identifier, it transforms and modifies the electronic signature on the electronic contract. It then calculates the similarity between the electronic signature and the blank contract template page with the verification signature on the inspection certificate. The calculation result is compared with a preset verification threshold. If the result is lower than the preset verification threshold, the verification fails.

[0127] Example 5

[0128] like Figure 3 As shown, from a hardware perspective, this application provides an embodiment of an electronic device containing all or part of an electronic signature mutual verification method. The electronic device includes a service processor and a distributed memory. The service processor is connected to the memory. The distributed memory stores a service self-management program configured to store machine-readable instructions. The service processor executes the service self-management program. When the instructions are executed by the processor, they implement the electronic signature mutual verification method as described above.

[0129] Example 6

[0130] Embodiments of this application also provide a computer-readable storage medium capable of implementing a mutual signing and verification method for electronic signatures with a server or client as the execution subject in the above embodiments. The computer-readable storage medium stores a computer program that, when executed by a processor, implements all the contents of the mutual signing and verification method for electronic signatures with a server or client as the execution subject in the above embodiments.

[0131] The embodiments described above are merely preferred embodiments of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications, improvements, and substitutions without departing from the concept of this application, and these all fall within the protection scope of this application.

Claims

1. A method for mutual signing and verification of electronic signatures, characterized in that, Includes the following steps: Enterprises upload blank contract templates with electronic signatures to the client terminal. The client terminal evenly divides the electronic signatures on the blank contract templates, transforms and modifies each divided electronic signature based on a unique identifier, and uses it as the enterprise's verification certificate. The paper signature image and all enterprise verification certificates are then uploaded to the service terminal. Before signing a contract, enterprise users take a picture of the paper seal. The service terminal verifies both parties based on the image of the paper seal. After verification, an encrypted signing channel is established between the client terminals of both parties. When enterprise users sign a contract, both parties' client terminals send their own unique identification codes to each other. Based on the other party's unique identification codes, the electronic contract with the electronic seal is sent to the other enterprise's client terminal. At the same time, the electronic seal on the electronic contract is verified based on the other enterprise's verification certificate. After the verification is successful, both parties sign the electronic contract.

2. The method for mutual signing and verification of electronic signatures according to claim 1, characterized in that, The unique identifier is generated by the client terminal after the enterprise user downloads the client terminal and performs authentication, registration and binding. The unique identifier is generated by encoding the IP address, enterprise account ID, hardware machine code, account registration time, and client terminal unique code according to pre-defined encoding rules.

3. The method for mutual signing and verification of electronic signatures according to claim 2, characterized in that, The pre-defined encoding rules in the client terminal are obtained by using a predefined strong hash function and concatenation obfuscation rules. During installation and registration, the client terminal obtains its current public IP address and generates a fixed-length IP address code according to predefined rules. When a user registers a corporate account, the service terminal uses a globally unique and unchangeable corporate account ID number assigned to the corporate account. Collect the CPU's unique serial number to generate the CPU code, collect the motherboard's serial number or UUID to generate the motherboard code, and combine the CPU code and the motherboard code to generate the hardware machine code. The precise timestamp of when a user completes the registration and binding of their enterprise account is used as the account registration time.

4. The method for mutual signing and verification of electronic signatures according to claim 3, characterized in that, When a user successfully downloads and installs the client terminal software package for the first time, the service terminal uses a secure random number generator to generate a strong random number as a unique code for the client terminal and stores it in the service terminal, while simultaneously sending it to the client terminal's local encrypted database. The unique identifier of the client terminal is stored in a local encrypted database, and the original parameters are encrypted and modified during transmission. The service terminal stores a unique identifier and the latest verification certificate associated with it.

5. The method for mutual signing and verification of electronic signatures according to claim 1, characterized in that, The verification based on the other party's unique identifier includes: Collect some information from the other party's client terminal, including IP address encoding, enterprise account ID number, and hardware machine code; Based on pre-defined encoding rules, some information is independently encoded. The encoded identifier is then matched one by one with the unique identifier. If a match fails, the encrypted signing channel is closed.

6. The method for mutual signing and verification of electronic signatures according to claim 1, characterized in that, The verification of electronic signatures on electronic contracts based on inspection certificates includes: The client terminal retrieves and downloads the other party's inspection certificate from the service terminal; The electronic signature on the electronic contract is modified based on the unique identifier of the other party's client terminal. The modified electronic signature will be matched and similarity calculated with all inspection certificates one by one. The calculation result is compared with a preset verification threshold. If the result is lower than the preset verification threshold, the verification fails.

7. The method for mutual signing and verification of electronic signatures according to claim 1, characterized in that, The client terminal has a built-in encoder converter that converts the unique identifier into a multi-dimensional vector. By using multidimensional vectors to modify the electronic signature on a blank contract template or electronic contract in multiple dimensions, a transformed and modified verification signature can be obtained. The process of making multi-dimensional modifications to an electronic signature is as follows: Load and extract the electronic signature image that needs to be modified from the blank contract template, and evenly segment the electronic signature image; The parser reads the currently valid unique identifier and uses a preset deterministic pseudo-random function algorithm to convert the unique identifier into a high-dimensional feature vector with a fixed dimension. Feature extraction is performed on the segmented electronic signature image to obtain an initial signature vector that can characterize the visual structural characteristics of the signature; The high-dimensional feature vector is modulated into spatial domain parameters applied to the signature image. The spatial domain parameters are input into a specific dimension of a specific transformation matrix, and the perturbation vector is output. The perturbation vector is used to perform nonlinear offset, scaling and permutation on the initial signature vector to obtain the transformed signature vector. The merged and transformed signature vector is reconstructed into a new signature image, which is then used as the verification signature.

8. A system for mutual signing and verification of electronic signatures, characterized in that, include: The registration and binding module is used to authenticate, register, and bind enterprise users, and generate unique identification codes; The voucher generation module is used to transform and modify the electronic signature on the blank contract template based on the unique identifier code, and use it as the company's verification voucher. Service terminals are used to acquire and store the company's inspection certificates; The contract verification module is used to verify the content format of electronic contracts based on a blank contract template from another company. The signature verification module is used to send an electronic contract bearing an electronic signature to another company, and at the same time verify the electronic signature on the electronic contract based on the other company's inspection certificate.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the content of the mutual signing and verification method of electronic signature as described in claim 1.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the content of the mutual signing and verification method of electronic signature as described in claim 1.

Images