CN101364876B - A method for realizing entity's public key acquisition, certificate verification and authentication - Google Patents

Abstract

The invention relates to a method for achieving public key acquisition, certificate validation and authentication of an entity. The method comprises the following steps: (1) transmitting a message 2 to an entity A by an entity B; (2) transmitting a message 3 to a credible third party TP by the entity A after receiving the message 2; (3) determining response RepTA after the credible third party TPreceives the message 3; (4) returning a message 4 to the entity A by the credible third party TP; (5) executing step (6) after the entity A receives the message 4 from the credible third party TP; (6) returning a message 5 to the entity B by the entity A; and (7) processing the message 5 after the entity B receives the message 5 from the entity A to obtain the authentication result of the entity A. The method can achieve public key acquisition, certificate validation and authentication of the entity by fusing in one protocol, thereby facilitating the execution efficiency and the effect of theprotocol and facilitating the combination with various public acquisition and public key certificate state enquiry protocols. The method suits with a user-access point-server network structure accessed to the network to meet the authentication requirement of the access network.

Description

A method for realizing entity's public key acquisition, certificate verification and identification

technical field

The invention relates to a method for realizing public key acquisition, certificate verification and identification of entities.

Background technique

In the current computer network and communication network, before the user logs into the network for secure communication, entity authentication between the user and the network must be completed, either one-way authentication or two-way authentication. The authentication mechanism used is generally divided into two categories: based on symmetric key algorithm and based on public key (asymmetric key) algorithm.

The authentication mechanism based on the public key algorithm and technology requires that the participant entity must have a pair of keys, that is, a public-private key pair, and the public key needs to be notified to other participant entities. Available notification methods include out-of-band notification method and certificate method, among which the out-of-band notification method is less used because it is difficult to update, and the certificate method is widely used.

Entity authentication methods using public key certificates generally need to be based on public key infrastructure. Public key infrastructure is a universal security infrastructure that uses the concept and technology of public keys to implement and provide security services. It can provide Authentication, integrity, confidentiality and other security services. Two very important concepts in public key infrastructure are public key certificates and certificate authorities, where public key certificates are usually issued by certificate authorities, signatures in public key certificates are provided by certificate authorities, and certificate authorities verify public key certificates by providing signatures The binding relationship between the holder and the holder's public key.

The public key certificate verified by the certificate authority usually has a lifetime, and the certificate becomes invalid after the lifetime expires. If the private key corresponding to the public key certificate is leaked, the public key certificate will also be invalid. In addition, there are some other situations that make the public key certificate invalid, such as job changes that cause it to become invalid.

Entities participating in authentication in network communication usually refuse to establish secure communication with entities holding invalid public key certificates, so public key acquisition and certificate verification usually revolve around the entity authentication process and provide services for it. Before or during the operation of the existing authentication mechanism, the verifier must have the valid public key of the claimant or know the state of the public key certificate of the claimant, otherwise the authentication process will be damaged or cannot be completed successfully. As shown in Figure 1, where entity A and entity B need to complete the authentication between them by executing an authentication protocol, the trusted third party TP (Trusted third Party) is a third-party entity trusted by entity A and entity B, and entity A and entity B Entity B must obtain the valid public key or public key certificate status of the peer entity through the trusted third party TP before authentication.

Currently, the status of the public key certificate is obtained in the following two ways:

1) CRL: Download the certificate revocation list CRL (Certificate Revocation List) to obtain the status of the public key certificate, including downloading all certificate lists and incremental certificate lists. When an entity needs to verify the status of a public key certificate, it downloads the latest certificate revocation list from the server, and then checks whether the public key certificate to be verified is in the latest certificate revocation list CRL.

2) Online query to obtain the status of the public key certificate. For example: Online Certificate Status Protocol OCSP (Online Certificate Status Protocol). Online Certificate Status Protocol OCSP mainly involves two entities, client and server, and is a typical client/server structure. The client sends a request to the server, and the server returns a response. The request contains the series of certificates that need to be verified, and the response contains the status and verification interval of the series of certificates.

Obtain the valid public key or public key certificate status of the peer entity in advance. This guarantee requirement cannot be met in many application environments, such as access networks with a ternary structure of users, access points, and servers. In most of the communication networks, the entity authentication mechanism is usually used to realize the user access control function. Before the authentication mechanism is successfully completed, the user is prohibited from accessing the network, so the user cannot use the certificate revocation list CRL and the online certificate status protocol OCSP before the authentication. Verify the validity of the access point certificate or obtain the valid public key of the access point by other methods. Therefore, if you want to complete the authentication completely and successfully, you can only rely on the user to authenticate after completing the authentication and establishing network communication, such as the key management PKM (Privacy Key Management) protocol in IEEE802.11i and IEEE802.16(e). Get the status of the access point's valid public key or public key certificate. Regardless of obtaining the valid public key or the status of the public key certificate of the peer entity in advance or after the event, the authentication process and the process of obtaining the valid public key and public key certificate status are separated into two separate processes, which is not conducive to improving protocol execution. Efficiency, even in some application environments will introduce unsafe factors, affecting the authenticity of authentication.

In addition, in some applications, it is difficult for users to use certificate revocation list CRL, online certificate status protocol OCSP and other methods in the process of authentication. First of all, the user equipment may have limited storage resources, or the user may not be willing to store the CRL at all, which makes it impossible to download the CRL periodically. Although there is no resource limitation in the access network, there may be problems such as policy restrictions in the access network. Secondly, when the user uses an online query mechanism such as the online certificate status protocol OCSP, the user needs to execute a separate online certificate status protocol OSCP and other protocols through the background server. These protocols often run on the HTTP protocol and belong to the application layer protocol. Using these protocols directly will be very complicated until the authentication of the network is completed. Even if it can be used, it needs to be completed through the structure of user-server and access point-server, which does not conform to the structure of user-access point-server, and cannot be directly and conveniently applied.

Contents of the invention

In order to solve the above-mentioned technical problems existing in the background technology, the present invention proposes a method for realizing the integration of entity public key acquisition, certificate verification and identification.

The technical solution of the present invention is: the present invention is a method for realizing public key acquisition, certificate verification and identification of entities, and its special feature is that the method includes the following steps:

1) Entity B sends message 2 to entity A, message 2 includes random number _RB , request ReqB and optional text Text3;

2) After receiving message 2, entity A sends message 3 to trusted third party TP, message 3 includes identity ID _A , request ReqAT and optional text Text4;

3) After receiving the message 3, the trusted third party TP determines to respond to RepTA, and executes step 4);

4) The trusted third party TP returns message 4 to entity A, message 4 includes response RepTA and optional text Text5;

5) After entity A receives message 4 from the trusted third party TP, it executes step 6);

6) Entity A returns message 5 to entity B, message 5 includes token TokenAB and response RepB;

7) After receiving the message 5 from entity A, entity B processes it and obtains the authentication result of entity A.

The method for the trusted third party TP to determine the response RepTA in the above step 3) is as follows: check the validity of the public key certificate Cert _A according to the identity ID _A of the entity A or search for the valid public key of the entity A through the entity identifier A.

The steps for entity B to process message 5 in the above step 7) are as follows:

7.1) Verify the response RepB according to the public key verification protocol or distribution protocol used, if the verification is passed, proceed to step 7.2);

7.2) Obtain the state of entity A's public key or public key certificate, verify the signature of entity A contained in the token TokenAB, and then check whether the random number R _B sent to entity A in step 1) is consistent with that contained in the token The random number _RB in TokenAB is consistent, and the identification result of entity A is obtained. So far, entity B completes the one-way authentication process for entity A.

The above method also includes step 0) before step 1), entity A sends message 1 to entity B, message 1 includes random number R _A , identity ID _A and optional text Text1; after entity B receives message 1, execute step 1). At this time, the above message 2 also includes the identity ID _B ; in the above step 3), the trusted third party TP determines the method of responding to RepTA as follows: according to the identity ID _A and ID _B of entity A and entity B, check the public key certificate Cert _A and the validity of Cert _B or search for the effective public keys of entity A and entity B through entity identifiers A and B; the processing steps of entity A to message 4 in the above step 5) are as follows:

5.1) Verify the response RepTA according to the public key verification protocol or distribution protocol used, if the verification is passed, proceed to step 5.2);

5.2) Obtain the state of entity B's public key or public key certificate, verify the signature of entity B contained in token TokenBA; then check whether the identity field ID _A contained in the signature data of token TokenBA is consistent with entity A's The identity marks are consistent, check whether the random number R _A sent to the entity B in step 0) is consistent with the random number R _A contained in the token TokenBA, and obtain the authentication result of the entity B.

The steps for entity B to process message 5 in the above step 7) are as follows:

7.1) Verify the response RepB according to the public key verification protocol or distribution protocol used, if the verification is passed, proceed to step 7.2);

7.2) Obtain the state of the public key or public key certificate of entity A, and verify the signature of entity A contained in the token TokenAB. Then check whether the identity field ID _B contained in the signature data of the token TokenAB is consistent with the identity field of entity B, and check whether the random number _RB sent to entity A in step 1) is consistent with that contained in the token TokenAB. The random number _RB in is consistent, and the identification result of entity A is obtained.

The above ReqB and ReqAT are the requests generated by entity B and entity A respectively, requesting information such as the valid public key of the peer entity or the original state of the public key certificate; the above RepTA and RepB are the responses to the requests ReqAT and ReqB respectively.

The forms and definitions of the above-mentioned ReqB, ReqAT, RepTA, and RepB are determined according to the specific public key authentication protocol or distribution protocol used. These public key authentication protocols or distribution protocols are certificate status protocols (see GB/T19713), server-based certificate authentication protocols (see IETF RFC5055) or other public key distribution or verification protocols.

The present invention adopts a three-entity framework. Entity A and entity B need to obtain the public key or certificate of a trusted third party before authentication, and obtain the user certificate issued by the trusted third party or hand over their public key to the trusted third party. Three-party escrow without prior knowledge of the status of the peer entity's valid public key or public key certificate. The present invention integrates the entity's public key acquisition, certificate verification and identification functions into one protocol, which is beneficial to improve the efficiency and effect of protocol execution, and is convenient to combine with various public key acquisition and public key certificate status query protocols, and is suitable for accessing The user-access point-server network structure of the access network meets the authentication requirements of the access network.

Description of drawings

Fig. 1 is a working schematic diagram of the authentication mechanism in the prior art;

Fig. 2 is the schematic diagram of the method of embodiment 1 of the present invention;

3 is a schematic diagram of the method of Embodiment 2 of the present invention;

Fig. 4 is a schematic diagram of the method of the third embodiment of the present invention.

Detailed ways

The method of the present invention involves three security elements, that is, two entities A and B and a trusted third party TP, through the online trusted third party TP, the authentication between entities A and B is completed, and the valid The status of the public key or public key certificate.

Entity A or B is represented by entity X; then R _X represents the random number generated by entity X; Cert _X is the public key certificate of entity X; ID _X is the identity of entity X, which is represented by certificate Cert _X or entity identifier X ; ReqX represents the request generated by entity X, requesting information such as the valid public key of the peer entity or the state of the public key certificate; ReqXT represents the request generated by entity X or forwarded to the trusted third party TP; RepX represents the request for ReqX to The response sent by entity X is to respond to entity X with information such as the valid public key of the requested entity or the status of the public key certificate; RepTX indicates the response to ReqXT generated by the trusted third party TP; Token is the token field; Text is an optional text field. The symbols are defined as follows:

ID _A = Aor CertA

ID _B ＝B or CertB

The forms of ReqB, ReqAT, RepTA, and RepB are determined according to the specific public key verification protocol or distribution protocol used. These online public key verification protocols or distribution protocols include certificate status protocol (see GB/T19713), server-based certificate verification protocol (see IETF RFC5055) or other public key distribution or verification protocols.

Referring to Fig. 2, the specific method flow of the present invention to realize the two-way identification between entity A and entity B is as follows:

1) Entity A sends message 1 to entity B, message 1 includes random number R _A , identity ID _A and optional text Text1;

2) Entity B sends message 2 to entity A after receiving message 1. Message 2 includes token TokenBA, identity ID _B , request ReqB and optional text Text3, where TokenBA= _{RA ‖RB} ‖ID _A ‖sSB (R _A ‖R _B ‖ID _B ‖ID _A ‖Text2);

3) After receiving message 2, entity A sends message 3 to the trusted third party TP. Message 3 includes request ReqAT and optional text Text4, where ReqAT needs to contain the content of ReqB;

4) After receiving the message 3, the trusted third party TP checks the validity of the public key certificates Cert _A and Cert _B according to the identity ID _A and ID _{B of entity A and entity B} or searches for entities through entity identifiers A and B Valid public keys of A and entity B, determine the response RepTA, where RepTA needs to contain the content of RepB, execute step 5);

5) The trusted third party TP returns message 4 to entity A, message 4 includes response RepTA and optional text Text5;

6) After entity A receives message 4 from the trusted third party TP, it completes the following steps:

6.1) Verify the response RepTA according to the public key verification protocol or distribution protocol used, if the verification is passed, proceed to step 6.2);

6.2) Obtain the state of entity B's public key or public key certificate, verify the signature of entity B contained in token TokenBA; then check whether the identity field ID _A contained in the signature data of token TokenBA is consistent with entity A's The identity is consistent, check whether the random number R _A sent to entity B in step 1) is consistent with the random number R _A contained in the token TokenBA., and obtain the identification result of entity B;

7) Entity A returns message 5 to entity B, message 5 includes token TokenAB and response RepB, where TokenAB=Text7∥sSA(R _{B∥ID B∥Text6} );

8) After entity B receives message 5 from entity A, it performs the following steps:

8.1) Verify the response RepB according to the public key verification protocol or distribution protocol used, if the verification is passed, proceed to step 8.2);

8.2) Obtain the state of entity A's public key or public key certificate, and verify the signature of entity A contained in token TokenAB. Then check whether the identity field ID _B contained in the signature data of the token TokenAB is consistent with the identity field of entity B, and check whether the random number RB sent to entity A in step 2) is the same as that contained in the token TokenAB. The random number _RB is consistent, and the authentication result of entity A is obtained; so far, the two-way authentication process is completed between entity A and entity B.

Referring to FIG. 3 , if only one-way authentication of entity A to entity B is implemented, steps 7) and 8) can be omitted based on the two-way authentication process, and some fields in messages 1 to 5 can also be omitted.

Referring to Figure 4, if only the one-way authentication of entity B to entity A is realized, step 1) can be omitted on the basis of the two-way authentication process, and some fields in message 2 to message 5 can also be omitted, the specific working process as follows:

2) Entity B sends message 2 to entity A, message 2 includes random number _RB , request ReqB and optional text Text3;

3) After receiving message 2, entity A sends message 3 to trusted third party TP, message 3 includes identity ID _A , request ReqAT and optional text Text4, wherein ReqAT is equal to ReqB;

4) After receiving the message 3, the trusted third party TP checks the validity of the public key certificate Cert _A according to the identity ID _A of the entity A or searches for the valid public key of the entity A through the entity identifier A, and determines the response RepTA, where RepTA is equal to RepB, execute step 5);

5) The trusted third party TP returns message 4 to entity A, message 4 includes response RepTA and optional text Text5;

6) After entity A receives message 4 from the trusted third party TP, it executes step 7);

7) Entity A returns message 5 to entity B, message 5 includes token TokenAB and response RepB, where TokenAB=Text7∥sSA(R _B ∥Text6);

8) After entity B receives message 5 from entity A, it performs the following steps:

8.1) Verify the response RepB according to the public key verification protocol or distribution protocol used, if the verification is passed, proceed to step 8.2);

8.2) Obtain the state of entity A's public key or public key certificate, verify the signature of entity A contained in the token TokenAB, and then check whether the random number R _B sent to entity A in step 2) is consistent with that contained in the token The random number R _B in TokenAB. is consistent, and the identification result of entity A is obtained. So far, entity B completes the one-way authentication process for entity A.

Claims (12)

1. A method for realizing public key acquisition, certificate verification and identification of an entity, characterized in that: the method comprises the following steps: 1) Entity B sends message 2 to entity A, message 2 includes random number R _R , request ReqB and optional text Text3; 2) After receiving message 2, entity A sends message 3 to trusted third party TP, message 3 includes identity ID _A , request ReqAT and optional text Text4; 3) After receiving the message 3, the trusted third party TP determines to respond to RepTA, and executes step 4); 4) The trusted third party TP returns message 4 to entity A, message 4 includes response RepTA and optional text Text5; 5) After entity A receives message 4 from the trusted third party TP, it executes step 6); 6) Entity A returns message 5 to entity B, message 5 includes token TokenAB and response RepB; 7) After receiving the message 5 from entity A, entity B processes it and obtains the authentication result of entity A. 2. the method for realizing the public key acquisition, certificate verification and identification of the entity according to claim 1, is characterized in that: in the described step 3), the trusted third party TP determines that the method for responding to RepTA is as follows: according to the identity of entity A To identify ID _A , check the validity of the public key certificate Cert _A or search for a valid public key of entity A by entity discriminator A. 3. the method for obtaining the public key of the realization entity according to claim 2, certificate verification and identification, is characterized in that: the processing steps of entity B to message 5 in the step 7) are as follows: 7.1) Verify the response RepB according to the public key verification protocol or distribution protocol used, if the verification is passed, proceed to step 7.2); 7.2) Obtain the state of entity A's public key or public key certificate, verify the signature of entity A contained in the token TokenAB, and then check whether the random number R _B sent to entity A in step 1) is consistent with that contained in the token The random number _RB in TokenAB is consistent, and the identification result of entity A is obtained. 4. The method for realizing the public key acquisition, certificate verification and authentication of an entity according to claim 1, characterized in that: the method also includes step 0) before step 1) Entity A sends message 1 to entity B, and message 1 Including random number R _A , identity ID _A and optional text Text1; after entity B receives message 1, then execute step 1). 5 . The method for realizing public key acquisition, certificate verification and authentication of an entity according to claim 4 , wherein the message 2 further includes an identity ID _B . 6. The method for realizing the public key acquisition, certificate verification and identification of the entity according to claim 5, characterized in that: the trusted third party TP in the step 3) determines that the method for responding to RepTA is as follows: according to entity A and entity A B's identity identifies ID _A and ID _B , check the validity of public key certificates Cert _A and Cert _B or search for valid public keys of entity A and entity B through entity discriminators A and B. 7. The method for obtaining the public key of the realization entity, certificate verification and identification according to claim 6, characterized in that: the processing steps of entity A to message 4 in the step 5) are as follows: 5.1) Verify the response RepTA according to the public key verification protocol or distribution protocol used, if the verification is passed, proceed to step 5.2); 5.2) Obtain the state of entity B's public key or public key certificate, verify the signature of entity B contained in token TokenBA; then check whether the identity field ID _A contained in the signature data of token TokenBA is consistent with entity A's The identity marks are consistent, check whether the random number R _A sent to the entity B in step 0) is consistent with the random number R _A contained in the token TokenBA, and obtain the authentication result of the entity B. 8. The method for obtaining the public key of the realization entity, certificate verification and identification according to claim 7, characterized in that: the processing steps of entity B to message 5 in the step 7) are as follows: 7.1) Verify the response RepB according to the public key verification protocol or distribution protocol used, if the verification is passed, proceed to step 7.2); 7.2) Obtain the state of entity A's public key or public key certificate, verify the signature of entity A contained in token TokenAB, and then check whether the identity field ID _B contained in the signature data of token TokenAB is consistent with entity B's The identity field is consistent, check whether the random number _RB sent to entity A in step 1) is consistent with the random number _RB contained in the token TokenAB, and obtain the authentication result of entity A. 9. The method according to any one of claims 1 to 8 to achieve public key acquisition, certificate verification and authentication of an entity, wherein: said ReqB and ReqAT are requests generated by entity B and entity A respectively, request The valid public key of the peer entity or the original state information of the public key certificate; the RepTA and RepB are responses to the requests ReqAT and ReqB respectively. 10. The method for realizing public key acquisition, certificate verification and identification of an entity according to claim 9, characterized in that: the form and definition of said ReqB, ReqAT, RepTA and RepB are based on the specific use of the public key verification protocol or distribution The protocol determines that the public key authentication protocol or distribution protocol is a certificate status protocol or a server-based certificate authentication protocol. 11. The method for realizing the public key acquisition, certificate verification and authentication of an entity according to any one of claims 1 to 3, characterized in that: said ReqAT is equal to ReqB, and RepTA is equal to RepB. 12. The method according to any one of claims 4 to 8 for realizing public key acquisition, certificate verification and authentication of an entity, characterized in that: the ReqAT includes the content of ReqB, and the RepTA includes the content of RepB.

Images