JP2006165881A - Signature data preparation system, signature data preparation terminal, signature verification terminal and certificate verification server - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To shorten a signature verification time for making it unnecessary to verify a certificate in signature verification. <P>SOLUTION: At the time of preparing a signature by using a signature preparation user certificate, a signature preparation user PC 10 transmits the signature preparation user certificate to a certificate verification server 20 in order to receive the verification of the signature preparation user certificate. The certificate verification server 20 verifies the received signature preparation user certificate, and returns server signature data 1 including the verification result to the signature preparation user PC 10. The signature preparation user PC 10 prepares terminal signature data 2 by using the server signature data 1 and a text to be signed as the object of signature, and transmits the terminal signature data 2 to a signature verification user PC 30. The signature verification user PC 30 receives the terminal signature data 2 from the signature preparation user PC 10, and verifies the signature included in the terminal signature data 2. The verification result of the signature preparation user certificate is included in the terminal signature data 2 so that it is not necessary for the signature verification user PC 30 to verify the signature preparation user certificate. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a signature data creation system that creates signature data including an electronic signature.

  Signature verification using the conventional PKI (Public Key Infrastructure) method is performed by combining signature value verification and certificate verification (combining signature value verification and certificate verification). General signature verification method).

  However, verification work can be time consuming and cumbersome, so there is a system that eliminates the need to re-execute verification processing that has been performed in the past by assigning and storing verification history such as verification results as a log. (For example, Patent Document 1).

  Patent Document 1 is a system that guarantees that signature verification has been performed in the past by signing a history of signature verification with respect to a certain signature document together with other necessary information, and saves the trouble of performing signature verification again. . However, Patent Document 1 does not mention anything about the means for shortening the signature creation verification process itself, and does not allow the processing time of the signature verification process itself to be shortened.

  The problem with certificate verification is that it generally takes time. This is because the certificate is verified by tracing the certificate back to the original trusted signing authority, such as the certificate of the authority that certifies the certificate, the certificate of the authority that certifies the certificate, etc. . Alternatively, it is performed simultaneously with verification with a CRL (Certificate Revocation List) which is a list of revoked certificates.

For this reason, in a signature verification system for a document with low importance, there is a case where the verification processing only performs signature value verification. However, there is a problem with the security aspect of electronic data because it is not possible to determine whether the certificate used for signature creation is a trusted certificate only by performing signature value verification without performing certificate verification. .
JP 2002-99843

  The present invention has been made to solve the above-described problems, and aims to shorten the time for signature verification.

The signature data creation system of the present invention includes:
A signature data creating terminal that creates an electronic signature using certificate data, creates signature data including the electronic signature, and transmits the created signature data; a certificate verification server that verifies the certificate data; In the signature data creation system with
The signature data creation terminal
Sending the certificate data to the certificate validation server;
The certificate validation server
Receiving the certificate data, verifying the received certificate data, and sending a verification result to the signature data creation terminal as a server-side verification result;
The signature data creation terminal
The server-side verification result is received, the signature data including the electronic signature and the received server-side verification result is generated, and the generated signature data is transmitted to a predetermined terminal.

  According to the present invention, the signature data creation terminal receives the verification of the certificate when creating the signature data, and includes the verification result in the signature data. For this reason, the terminal that has received the signature data can omit the certificate verification at the time of the signature verification work, and the time for the verification work can be shortened.

Embodiment 1 FIG.
The first embodiment will be described with reference to FIGS. FIG. 1 is a configuration diagram showing the entire simple certificate verification system 100 (an example of a signature data creation system). FIG. 2 is a diagram showing a configuration of the server signature data 1 created by the certificate verification server 20. FIG. 3 shows the configuration of the terminal signature data 2 created by the signature creation user PC 10 (an example of a signature data creation terminal). FIG. 4 is a diagram showing a simple notation when the data structure of the terminal signature data 2 of FIG. 3 is applied to an XML signature. FIG. 5 is a diagram illustrating the operation of the simple certificate verification system 100. FIG. 6 is a flowchart showing the operation of the simple certificate verification system 100. FIG. 7 is a sequence diagram of the simple certificate verification system 100.

  As shown in FIG. 1, the simple certificate verification system 100 includes a signature creation user PC 10, a certificate verification server 20, and a signature verification user PC 30 (an example of a signature verification terminal). The signature creation user PC 10, the certificate verification server 20, and the signature verification user PC 30 are connected to a network (not shown) and can communicate with each other. Each of the signature creation user PC 10 and the certificate verification server 20 creates signature data including an electronic signature created by itself. Hereinafter, the signature data created by the certificate verification server 20 is referred to as “server signature data 1”, and the signature data created by the signature creation user PC 10 is referred to as “terminal signature data 2”.

An outline of the simple certificate verification system 100 will be described.
(1) The signature creation user PC 10 certifies the signature creation user certificate in order to receive verification of the signature creation user certificate when creating a signature using the signature creation user certificate (an example of certificate data). To the certificate verification server 20.
(2) The certificate verification server 20 verifies the received signature creation user certificate, and obtains server signature data 1 (an example of server-side signature inclusion data) including the verification result (hereinafter referred to as server-side verification result), A reply is sent to the signature creation user PC 10. In the following, the “signature creation user certificate” received by the certificate validation server 20 from the signature creation user PC 10 and verified may be referred to as “verified certificate data”. A “signature creation user certificate” that has not been received and not verified by the certificate verification server 20 may be referred to as “unverified certificate data”.
(3) The signature creation user PC 10 creates terminal signature data 2 (an example of signature data) using the server signature data 1 and the text to be signed as signature targets, and transmits the signature data to the signature verification user PC 30.
(4) The signature verification user PC 30 receives the terminal signature data 2 from the signature creation user PC 10 and verifies the signature included in the terminal signature data 2.

  Next, the configuration of the signature creation user PC 10 will be described. The signature creation user PC 10 includes a signature creation side data transmission / reception unit 11 (an example of a signature creation side communication unit) that exchanges data with other devices, a user side signature creation unit that creates an electronic signature and creates terminal signature data 2 12 (an example of a signature creation unit), a signature creation user certificate storage unit 13 (certificate data storage unit) that stores a signature creation user certificate used to create an electronic signature, and a certificate verification server 20 A verification result storage unit 14 for storing the server signature data 1 including the verification result.

  Next, the configuration of the certificate verification server 20 will be described. The certificate verification server 20 includes a server-side data transmission / reception unit 21 that exchanges data with other devices, a certificate verification unit 22 that verifies a signature creation user certificate received from the signature creation user PC 10, creates an electronic signature, and A server-side signature creation unit 23 that creates server signature data 1 including a verification result, and a certificate verification server certificate storage unit 24 that stores a certificate verification server certificate that certifies itself are provided.

  Next, the configuration of the signature verification user PC 30 will be described. The signature verification user PC 30 includes a signature verification side data transmission / reception unit 31 that exchanges data with other devices, a signature verification unit 32 that verifies the signature of the terminal signature data 2 received from the signature creation user PC 10, and the acquired certificate verification. And a verification terminal storage unit 34 for storing a server certificate. In addition, the signature verification unit 32 includes a binary value comparison unit 33 that compares “unverified certificate data” and “verified certificate data” as binary values.

Next, a specific operation of the simple certificate verification system 100 will be described with reference to FIGS. First, the operation of the certificate verification server 20 will be described.
(1) The signature creation user PC 10 transmits a “signature creation user certificate” used for the signature by the user to the certificate verification server 20 by the signature creation side data transmission / reception unit 11 (S101).
(2) The certificate verification server 20 receives the “signature creation user certificate” by the server-side data transmission / reception unit 21.
(3) The certificate verification server 20 performs “certificate verification” on the “signature generation user certificate” received from the signature generation user PC 10 by the certificate verification unit 22 (S102). Hereinafter, the verification of the “signature creation user certificate” by the certificate verification unit 22 is referred to as “certificate verification”.
(4) Thereafter, the server-side signature creation unit 23 (a) “signature creation user certificate verification result” (server-side verification result) obtained by “certificate verification” by the certificate verification unit 22 (b) ) “Validated certificate data”, (c) “time information” indicating the time when “signature creation user certificate” was verified, and the like, and the signature value (server (Example of side signature) and “server signature data 1” are created (S103). Regarding signature targets, (a) “server-side verification result” and (b) “verified certificate data” are required signature targets. In addition, (c) “time information” and the like are optional, and an arbitrary value is used as a signature target element. Further, the server-side verification result may be an arbitrary value according to the rules for system construction. FIG. 2 shows an example of “server signature data 1” created by the server-side signature creation unit 23. As shown in FIG. 2, (a) “server-side verification result” and (b) “verified certificate data” are signed as signature targets. That is, “server signature data 1” includes (a) “server-side verification result” and (b) “verified certificate data” as signature targets, and includes a signature value from the certificate verification server 20.
(5) In general, the certificate used for signature is usually attached to the signature data. However, in the first embodiment, the “certificate verification server certificate” that is the certificate used for the signature by the certificate verification server 20 is not attached to the “server signature data 1”. The “certificate verification server certificate” is required for the verification, but in the first embodiment, the signature verification user PC 30 later acquires the “certificate verification server certificate” directly from the certificate verification server 20 ( It is assumed that it will be used for verification in S108 described later, and is not necessary.
(6) The certificate verification server 20 returns “server signature data 1” created by the server side signature creation unit 23 to the signature creation user PC 10 using the server side data transmission / reception unit 21 (S104).

Next, the operation of the signature creation user PC 10 that has returned “server signature data 1” from the certificate verification server 20 will be described.
(1) In the signature creation user PC 10, the signature creation side data transmission / reception unit 11 receives “server signature data 1” returned from the certificate verification server 20. The verification result storage unit 14 stores the received “server signature data 1”.
(2) The user-side signature creation unit 12 sets “server signature data 1” returned from the certificate verification server 20 and the document to be signed as “signature target element”, and “signature creation user certificate” (unverified) A signature value (an example of an electronic signature) is created using certificate data), and "terminal signature data 2" is created (S105).
(3) An example of “terminal signature data 2” created by the user-side signature creation unit 12 is shown in FIG. In the example of FIG. 3, the signature target by the user side signature creation unit 12 is the signature target body, “server signature data 1”, and “signature creation user certificate used for signature creation created by the user side signature creation unit 12. (Unverified certificate data). The terminal signature data 2 includes a signature value created by the user-side signature creation unit 12. FIG. 4 shows a data configuration when the configuration of FIG. 3 is applied to an XML signature. The description in FIG. 4 is a simplified version of the XML signature, and details are based on the XML signature standard of the standardization organization W3C (World Wide Web Consortium). There are three types of XML signature schemes, Enveloped, Detached, and Enveloping, and an example of using the Enveloping format is shown.
(4) The signature creation user PC 10 sends this “terminal signature data 2” to the signature verification user PC 30 via the signature creation data transmitter / receiver 11 (S106).

Next, the operation of the signature verification user PC 30 that receives “terminal signature data 2” from the signature creation user PC 10 will be described.
(1) In the signature verification user PC 30, the signature verification side data transmission / reception unit 31 receives “terminal signature data 2” sent from the signature creation user PC 10.
(2) The signature verification unit 32 first performs “signature value verification” in order to verify “terminal signature data 2” received from the signature creation user PC 10 (S107 to S110). By this “signature value verification”, it can be confirmed that the data is not falsified. In order to perform “signature value verification” of “terminal signature data 2” by the signature verification unit 32, a “signature creation user certificate” and a “certificate verification server certificate” are required. In the first embodiment, the signature verification user PC 30 verifies using “unverified certificate data” and “verified certificate data”. In the second embodiment, a case where only “verified certificate data” is used will be described.
(3) “Unverified certificate data” present in “terminal signature data 2” is used as “signature creation user certificate”.
(4) The “certificate verification server certificate” is acquired directly from the certificate verification server 20 by the signature verification user PC 30. In addition, it is not necessary to acquire each time, and may be acquired when it is not owned (S107) (S108).
(5) The signature verification unit 32 performs “signature value verification” using “unverified certificate data” and “certificate verification server certificate” (S109, S110).
(6) Next, in the case of Yes in S110, the signature verification unit 32 confirms whether the “unverified certificate data” is valid, so that “unverified certificate data” and “verified certificate data” Are compared with each other (S111, S112). The “certificate verification server certificate” is valid because it is obtained directly from the certificate verification server 20 by the signature verification user PC 30. The “unverified certificate data” is used by the signature creation user PC 10 for the signature, but it is unconfirmed by the certificate verification server 20 whether it is a valid certificate. Therefore, it is compared whether “unverified certificate data” is the same as “verified certificate data” present in the signature document of “terminal signature data 2” (S111, S112). This comparison is performed by the binary value comparison unit 33 comparing “unverified certificate data” and “verified certificate data” as binary values. As a result of comparison, it is understood that “verified certificate data” and “unverified certificate data” used for signature by the signature creation user PC 10 are different from each other if they are not identical. In this case, signature verification fails (S115).
(7) Further, the signature verification unit 32 checks the server-side verification result of “verified certificate data” present in “terminal signature data 2” (S113, S114), and “verified certificate data”. Confirm the validity of. If valid, the signature verification is successful (S116).

  As described above, in the first embodiment, the certificate verification server 20 performs the certificate verification work when the signature generation user PC 10 generates a signature. The signature creation user PC 10 includes the server-side verification result in the signature target. For this reason, certificate verification at the time of signature verification work of the signature verification user PC 30 can be omitted, and the time for verification work can be shortened. In particular, when a large amount of signature verification is performed in a system that accepts various data, it is effective because it is highly possible that the system performance is degraded due to the verification processing time.

  In addition, there are many cases where a single signed document is sent to a large number of destinations and verified. In this case, the load on the verification server is concentrated, and the server system performance is likely to deteriorate. Mitigation is important.

  In addition, the validity of the certificate at the time when the signature is verified can be confirmed by including time information indicating the time when the certificate is verified in the signature target created by the certificate verification server. Specifically, it is effective when a time lag occurs between the signature creation and the certificate verification, such as a workflow for handling a signed document or long-term storage of a signed document.

  In addition, since the verification work is performed by the certificate verification server 20 in advance of signing, it is possible to prevent a situation in which a certificate is accidentally revoked.

Embodiment 2. FIG.
The second embodiment will be described with reference to FIG. The second embodiment is an embodiment in which step S111 in FIG. 6 is omitted. In the first embodiment, the signature verification user PC 30 verifies the signature value by the signature creation user PC 10 using “unverified certificate data” included in “terminal signature data 2” in S109. On the other hand, in the second embodiment, the signature verification unit 32 of the signature verification user PC 30 directly uses the “verified certificate data” included in the “terminal signature data 2”, and uses the signature value by the signature creation user PC 10 as the signature value. Validate. Therefore, the step of comparing “unverified certificate data” and “verified certificate data” in step S111 of FIG. 6 is not necessary.

The operation of FIG. 8 will be briefly described. S201 to S208 are the same as S101 to S108 in FIG.
(1) In S209, the signature verification unit 32 of the signature verification user PC 30 verifies the signature value by the signature creation user PC 10 using “verified certificate data” included in “terminal signature data 2”.
(2) If the verification fails in S210, the process proceeds to S211 and the signature verification fails and ends. If the verification is successful, the process proceeds to S212.
(3) In S212, the signature verification unit 32 checks the server-side verification result included in “terminal signature data 2”. The following is the same as FIG.

  The signature data creation system described in the first embodiment and the second embodiment is configured so that the signature creation user PC 10, the certificate verification server 20, and the signature verification user PC 30 are connected to the network and can communicate with each other. At the time of creation, the signature creation user PC 10 sends a signature creation user certificate used for signature to the certificate verification server 20, and the certificate validation server 20 responds to the signature creation user certificate sent from the signature creation user PC 10. The server signature data 1 is created by performing verification, signing the certificate verification result, time, verified certificate, and the like as signature targets. The server signature data 1 is characterized in that the certificate verification server certificate of the certificate verification server 20 is not attached.

  In the signature data creation system described in the first and second embodiments, the signature creation user PC 10 receives the server signature data 1 created by the certificate verification server 20, and signs the text data to be signed as a signature target. And “signature document” is created.

  The signature data creation system described in the first embodiment and the second embodiment performs signature value verification of the certificate verification server 20 using the obtained “certificate of the certificate verification server” and creates a signature. The signature value verification of the user PC 10 is characterized by verifying using the “signature creation user certificate” (unverified certificate data) in the “signature document”.

  The signature data creation system described in the first embodiment and the second embodiment performs the signature to confirm that “signature creation user certificate” (unverified certificate data) is equal to “verified certificate data”. It is characterized in that “validated certificate data” which is data to be signed by the certificate verification server 20 in the document is compared with “unverified certificate data” in binary value.

  The signature data creation system described in the first embodiment and the second embodiment can specify the verification date and time by including “time information” in the server signature data of the certificate verification server 20. It is possible to guarantee the validity of “verified certificate data”.

  In the signature data creation system described in the first embodiment and the second embodiment, the certificate verification server 20 verifies the “signature creation user certificate” (verified certificate data) and the verification result (server). Side verification result) and the time (time information) at which the verification was performed are used as signature targets to create “server signature data 1”, and the signature creation user PC 10 sets “server signature data 1” as the signature target text. Creating “terminal signature data 2” signed using the “signature creation user certificate” (unverified certificate data) possessed by the user, and holding the data in the final signature document format .

1 is a configuration diagram illustrating an entire simple certificate verification system 100 according to Embodiment 1. FIG. 4 is a diagram showing a configuration of server signature data 1 created by a certificate verification server 20 in the first embodiment. FIG. 2 shows a configuration of terminal signature data 2 created by a signature creation user PC 10 in the first embodiment. FIG. 4 is a diagram showing a simple notation method when the data configuration of terminal signature data 2 of FIG. 3 is applied to an XML signature in the first embodiment. 6 is a diagram illustrating an operation of the simple certificate verification system 100 according to Embodiment 1. FIG. 4 is a flowchart illustrating an operation of the simple certificate verification system 100 according to the first embodiment. 3 is a sequence diagram of a simple certificate verification system 100 according to Embodiment 1. FIG. 10 is a flowchart illustrating an operation of the simple certificate verification system 100 according to the second embodiment.

Explanation of symbols

  1 server signature data, 2 terminal signature data, 2a XML signature, 10 signature creation user PC, 11 signature creation side data transmission / reception unit, 12 user side signature creation unit, 13 signature creation user certificate storage unit, 14 verification result storage unit, DESCRIPTION OF SYMBOLS 100 Simple certificate verification system, 20 Certificate verification server, 21 Server side data transmission / reception part, 22 Certificate verification part, 23 Server side signature preparation part, 24 Certificate verification server certificate memory | storage part, 30 Signature verification user PC, 31 Signature verification side data transmission / reception unit, 32 Signature verification unit, 33 Binary value comparison unit, 34 Verification terminal side storage unit.

Claims (14)

A signature data creating terminal that creates an electronic signature using certificate data, creates signature data including the electronic signature, and transmits the created signature data; a certificate verification server that verifies the certificate data; In the signature data creation system with
The signature data creation terminal
Sending the certificate data to the certificate validation server;
The certificate validation server
Receiving the certificate data, verifying the received certificate data, and sending a verification result to the signature data creation terminal as a server-side verification result;
The signature data creation terminal
Receiving the server-side verification result, generating the signature data including the electronic signature and the received server-side verification result, and transmitting the generated signature data to a predetermined terminal system. The signature data creation system further includes:
A signature verification terminal that receives the signature data transmitted by the signature data creation terminal and verifies the electronic signature included in the received signature data based on the server-side verification result included in the received signature data; A signature data creation system characterized by comprising. In a signature data creation terminal that creates an electronic signature and creates data including the created electronic signature,
A certificate data storage unit for storing certificate data used to create the electronic signature;
A verification result storage unit that stores a verification result indicating whether the certificate data stored in the certificate data storage unit is valid;
A signature that creates the electronic signature using the certificate data stored in the certificate data storage unit and generates signature data including the generated electronic signature and the verification result stored in the verification result storage unit The creation department;
A signature data creation terminal, comprising: a signature creation side communication unit that transmits the signature data created by the signature creation unit to a predetermined terminal. The signature creation side communication unit
The certificate data stored in the certificate data storage unit is transmitted to a certificate verification server that verifies the certificate data, and a verification result of the certificate data is received as a server-side verification result from the certificate verification server. ,
The verification result storage unit
Storing the server side verification result received by the signature creation side communication unit;
The signature creation unit
4. The signature data creation terminal according to claim 3, wherein the server-side verification result stored in the verification result storage unit is included in the signature data as the verification result included in the signature data. The signature creation side communication unit
Receiving a server-side signature indicating an electronic signature created by the certificate verification server from the server-side verification result as a signature target, from the certificate verification server;
The signature creation unit
5. The signature data creation terminal according to claim 4, wherein the server side signature received by the signature creation side communication unit is included in the signature data. The signature creation side communication unit
When receiving the server-side verification result and the server-side signature, server-side signature inclusion data including the server-side verification result and the server-side signature is received from the certificate verification server,
The signature creation unit
The electronic signature is created by using the certificate data stored in the certificate data storage unit as a signature object for the server side signature inclusion data and the predetermined data received by the signature creation side communication unit, and the created 6. The signature data creation terminal according to claim 5, wherein the signature data including the electronic signature, the server-side signature inclusion data, and the predetermined data is created. The server side signature inclusion data received by the signature creation side communication unit further includes:
7. The signature data creation terminal according to claim 6, further comprising time information indicating a date and time when the certificate verification server verifies the certificate data. In the certificate verification server that verifies the certificate data,
A server-side communication unit that receives the certificate data from a signature data creation terminal that requests verification of the certificate data used to create the electronic signature when creating an electronic signature;
A certificate verification unit that verifies the certificate data received by the server-side communication unit;
The server side communication unit
A certificate verification server, wherein a verification result of the certificate data by the certificate verification unit is transmitted to the signature data creation terminal as a server-side verification result. In a signature verification terminal that receives data including the electronic signature from a signature data generation terminal that generates an electronic signature using certificate data, and verifies the electronic signature included in the received data,
The verification terminal side that receives the signature data including the electronic signature created by the signature data creation terminal using the certificate data and the verification result indicating whether the certificate data is valid from the signature data creation terminal A communication department;
A signature verification terminal comprising: a terminal-side verification unit that verifies the electronic signature included in the signature data based on the verification result included in the signature data received by the verification terminal-side communication unit . The verification result included in the signature data received from the signature data creation terminal by the verification terminal side communication unit is:
A server-side verification result verified by a certificate verification server that verifies the certificate data;
The signature data that the verification terminal side communication unit receives from the signature data creation terminal further includes:
Including a server-side signature indicating an electronic signature created by using the server-side certificate data owned by the certificate verification server as a signature target;
The terminal side verification unit
The signature verification terminal according to claim 9, wherein the server-side signature included in the signature data received by the verification terminal-side communication unit is verified. The signature verification terminal further includes:
A signature verification storage unit for storing the server certificate data;
The terminal side verification unit
The signature verification terminal according to claim 10, wherein the server-side signature is verified based on the server-side certificate data stored in the signature verification-side storage unit. In a signature verification terminal that receives data including the electronic signature from a signature data generation terminal that generates an electronic signature using certificate data, and verifies the electronic signature included in the received data,
The digital signature created using unverified certificate data which is certificate data that has not been verified by the signature data creation terminal, and a certificate that verifies the unverified certificate data and outputs it as verified certificate data The signature data including the verified certificate data output from the certificate verification server and the server-side verification result that is the verification result of the verified certificate data by the certificate verification server is received from the signature data creation terminal. Verification terminal side communication part,
A terminal-side verification unit that verifies the electronic signature included in the signature data based on the verified certificate data and the server-side verification result included in the signature data received by the verification terminal-side communication unit; A signature verification terminal characterized by comprising. The signature data that the verification terminal side communication unit receives from the signature data creation terminal further includes:
Including the unverified certificate data;
The terminal side verification unit
The electronic signature included in the signature data is verified using the unverified certificate data, and when the verification of the electronic signature is successful, the unverified certificate data and the verified certificate included in the signature data 13. The signature verification terminal according to claim 12, wherein the signature verification terminal further verifies whether the electronic signature included in the signature data is valid based on a comparison result. The terminal side verification unit
14. The signature verification terminal according to claim 13, further comprising a binary value comparison unit that compares the unverified certificate data with the verified certificate data as a binary value.

Images