WO2011075907A1

WO2011075907A1 - Method for implementing public key acquirement, certificate validation and bi-directional authentication of entities

Info

Publication number: WO2011075907A1
Application number: PCT/CN2009/076047
Authority: WO
Inventors: 铁满霞; 曹军; 赖晓龙; 黄振海
Original assignee: 西安西电捷通无线网络通信股份有限公司
Priority date: 2009-12-25
Filing date: 2009-12-25
Publication date: 2011-06-30

Abstract

A method system for implementing the public key acquirement, certificate validation and bi-directional authentication of entities, adopts a tri-entity architecture. Before an authentication, an entity A and an entity B need to acquire the public key or the certificate of a trusted third party, and to acquire their own user certificate authorized by the trusted third party issuing to themselves or submit their own public keys to the trusted third party for storing, without the need of knowing the valid public key or the public key certificate state of the opposite side entity in advance. The present invention integrates the public key acquirement, the certificate validation and the authentication function of the entities into a protocol for implement, is beneficial to improve the efficiency and effect of the protocol execution, facilitates to combine with various protocols for the public key acquirement and the public key certificate state query, adapts for the user-access point-server network structure of the access network, and satisfies the authentication requirement of the access network.

Description

Method for realizing public key acquisition, certificate verification and two-way authentication of an entity

The present invention relates to the field of network security, and in particular, to a method for implementing public key acquisition, certificate verification, and two-way authentication of an entity.

Background technique

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

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

The public key algorithm based on public key algorithm generally needs to be implemented based on public key infrastructure. The public key infrastructure is full infrastructure, which can provide security services such as authentication, integrity and confidentiality. Two important concepts in public key infrastructure are public key certificates and certificate authorities. Public key certificates are usually issued by the certificate authority. The signature in the public key certificate is provided by the certificate authority. The certificate authority verifies the public key certificate by providing a signature. The binding relationship between the holder and the public key held by the holder.

A public key certificate that has been verified by a certificate authority usually has a lifetime, and the certificate fails after the end of the lifetime. If the private key corresponding to the public key certificate is leaked, the public key certificate also fails. There are also other cases where the public key certificate is invalidated, such as a job change that causes it to fail.

Entities participating in authentication in network communications typically refuse to establish secure communications with entities holding expired public key certificates, so public key acquisition and certificate verification typically surround and provide services for the entity authentication process. Currently, the existing authentication mechanism must have a valid public key of the claimant or know the public key certificate status of the claimant before or during the operation. Otherwise, the authentication process may be damaged or cannot be successfully completed. As shown in Figure 1, entity A and entity B need to complete the authentication between them by performing an authentication protocol. Trusted third party trusts entity A and entity B. The third party entity, and entity A and entity B must obtain the status of the valid public key or public key certificate of the peer entity through the trusted third party TP before authentication.

Currently, the status of obtaining a public key certificate is usually in two ways:

1) Download Certificate Revocation List (CRL): Download the status of the CRL to obtain the public key certificate, including all certificate list downloads and incremental certificate list downloads. When an entity needs to verify the status of a public key certificate, download the latest certificate revocation list from the server and check if 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). OCSP mainly involves two entities, client and server. It is a typical client/server architecture. The client sends a request to the server and the server returns a response. The request contains a series of certificates that need to be verified. The response contains the status and verification interval of the series of certificates.

Obtaining the status of the effective public key or public key certificate of the peer entity in advance, this guarantee requirement condition cannot be satisfied in many application environments, for example, the network structure is the access network of the user, the access point, and the server ternary structure. Including most of the communication networks, the entity authentication mechanism is usually implemented to implement the user access control function. Before the authentication mechanism is successfully completed, the user is prohibited from accessing the network. Therefore, the user cannot use the certificate revocation list CRL or the online certificate status protocol OCSP before the authentication. The method verifies the validity of the access point certificate or obtains a valid public key of the access point. Therefore, if you want to complete the authentication completely successfully, you can only rely on the user to complete the authentication and establish the network communication, such as IEEE 802.11i and IEEE 802.16 (e) Key Management PKM (Privacy Key Management) protocol, that is, afterwards The status of the effective public key or public key certificate of the access point. Whether obtaining the status of a valid public key or public key certificate of the opposite entity in advance or afterwards, the process of obtaining the valid public key and the public key certificate is separated into two separate processes, which is not conducive to improving the protocol execution. Efficiency, even in some application environments, introduces unsafe factors that affect the authenticity of the authentication.

In addition, in some applications, the user is also difficult to use the certificate revocation list CRL, the online certificate status protocol OCSP, etc. in the process of authentication. First, the user equipment may have limited storage resources, or the user is not willing to store the certificate revocation list CRL, which may result in the periodic download certificate revocation list CRL being impossible. Although there is no resource limitation in the access network, there may be problems such as policy restrictions on the access network. Secondly, when the user uses the 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 Running on the HTTP protocol, belonging to the application layer protocol, it is very complicated to use these protocols directly before the authentication of the access network has not been completed. Even if it can be used, it needs to be completed by the structure of the user-server and the access point-server. It does not conform to the structure of the user-input-one server, and cannot be directly and conveniently applied.

Summary of the invention

The present invention solves the above technical problems existing in the background art, and proposes a method for realizing entity public key acquisition, certificate verification, and two-way authentication.

The technical solution of the present invention is: The present invention is a method for realizing public key acquisition, certificate verification and two-way authentication of an entity, the method comprising the following steps:

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

After receiving the message 1, the entity B sends a message 2 to the entity A, and the message 2 includes the token TokenBA, the identity ID _B , the request ReqB, and the optional text Text3;

After receiving the message 2, the entity A sends a message 3 to the trusted third party TP, and the message 3 includes the request ReqAT and the optional text Text4;

After receiving the message 3, the trusted third party determines to respond to RepTA and returns a message 4 to entity A, which includes a response RepTA and an optional text Text5;

After receiving the message 4 from the trusted third party TP, the entity A processes the result of the entity B, and returns a message 5 to the entity B. The message 5 includes the token TokenAB and the response RepB; the entity B receives the entity A. After message 5, processing is performed to obtain the identification result of entity A. After receiving the message 3, the trusted third party TP determines that the response RepTA includes:

Check the validity of the public key certificates Cert _A and Cert _B according to the identity IDs A and ID _{B of} entity A and entity B;

Or, search for valid public keys of entity A and entity B through entity specifiers A and B.

After the entity A receives the message 4 from the trusted third party TP, the processing includes: the entity A verifies the response RepTA according to the used public key authentication protocol or the distribution protocol, and obtains the entity B public key or public if the verification succeeds. The state of the key certificate, verifying the signature of the entity B contained in the token TokenBA; then checking whether the identity field ID _A included in the signature data of the token TokenBA is consistent with the identity of the entity A, checking the randomness in the message 1. Whether the number R _A is included or not The random number R _A in the token TokenBA is consistent, and the identification result of the entity B is obtained.

After the entity B receives the message 5 from the entity A, the processing includes:

Entity B verifies the response RepB according to the public key authentication protocol or distribution protocol used. If the verification succeeds, the state of the public key or the public key certificate of the entity A is obtained, and the signature of the entity A included in the token TokenAB is verified, and the check is included in whether the signature data token TokenAB in the identity field ID _B with the identity of the entity B identify correspondingly, to check whether the message 2 of the random number R _B contained a random number R _B in the token TokenAB in consistent, to give entity a Identification results.

The ReqB and the ReqAT are respectively a request generated by the entity B and the entity A, requesting the status information of the valid public key or the public key certificate of the opposite entity, and the ReqTA includes the content of the ReqB; the RepTA and the RepB are respectively for the request ReqAT and ReqB produces a response, and RepTA contains the contents of RepB.

The forms and definitions of the ReqB, ReqAT, RepTA, and RepB are determined according to a public key authentication protocol or a distribution protocol that is specifically used. The public key authentication protocol or distribution protocol is a line certificate status protocol or a server-based certificate verification protocol.

A system for implementing public key acquisition, certificate verification, and two-way authentication of an entity, including a first entity, a second entity, and a trusted third party, wherein:

The first entity is configured to send a message 1 to a second entity, where the message 1 includes a random number R _A , an identity ID _A, and an optional text Textl;

After receiving the message 1, the second entity sends a message 2 to the first entity, where the message 2 includes a token TokenBA, an identity ID _B , a request ReqB, and an optional text Text3;

After receiving the message 2, the first entity sends a message to the trusted third party TP 3, the message 3 includes the request ReqAT and the optional text Text4;

After receiving the message 3, the trusted third party determines to respond to RepTA and returns a message 4 to the first entity. The message 4 includes a response RepTA and an optional text Text5;

After receiving the message 4 from the trusted third party TP, the first entity performs processing to obtain the authentication result of the second entity, and returns a message 5 to the second entity, where the message 5 includes the token TokenAB and the response RepB; After the message 5 from the first entity, processing is performed to obtain the authentication result of the first entity. a first checking unit, configured to check validity of the public key certificates Cert _A and Certs according to the identity IDs _A and ID _{B of the} first entity and the second entity;

Or,

And a second checking unit, configured to search for a valid public key of the first entity and the second entity by using the entity identifier.

The first entity includes:

a first verification unit, configured to verify the response RepTA according to the public key authentication protocol or the distribution protocol used after receiving the message 4, and obtain the state of the public key or the public key certificate of the second entity if the verification succeeds;

a second verification unit, configured to verify a signature of the second entity included in the token TokenB A; a third checking unit, configured to check whether the identity identifier field ID _A included in the signature data of the token TokenBA is related to the first entity consistent identity, whether a check message of the random number R _a and the random number R _a contained in the token TokenBA in the consistent results obtained authentication of the second entity.

The second entity includes:

a third verification unit, configured to: after receiving the message 5 from the first entity, verify the response RepB according to the public key authentication protocol or the distribution protocol used, and obtain the state of the public key or the public key certificate of the first entity if the verification succeeds;

a fourth verification unit, configured to verify a signature of the first entity included in the token TokenAB; a fourth checking unit, configured to check whether the identity identifier field ID _B included in the signature data of the token TokenAB is related to the second entity consistent identity, to check whether the random number message 2 comprising a random number R _B and R _B in the token TokenAB in the consistent results obtained authentication of the first entity.

The ReqB and the ReqAT are respectively a request generated by the second entity and the first entity, requesting the original public information of the valid public key or the public key certificate of the opposite entity, and the ReqTA includes the content of the ReqB; the RepTA and the RepB are respectively targeted The response generated by requesting ReqAT and ReqB, and RepTA contains the content of RepB.

The invention adopts a three-entity framework, and entity A and entity B need to obtain a trusted third party before authentication. The public key or certificate, and obtain the user certificate issued by the trusted third party to the user or hand over the public key to the trusted third party without prior knowledge of the status of the valid public key or public key certificate of the opposite entity. The invention integrates the public key acquisition, certificate verification and authentication functions of the entity in one protocol, which is beneficial to improving the efficiency and effect of the protocol execution, and is convenient for combining with various public key acquisition and public key certificate status query protocols, and is suitable for connection. The network user enters the network structure of the server and meets the authentication requirements of the access network.

DRAWINGS

1 is a schematic diagram of the operation of the authentication mechanism in the prior art;

Figure 2 is a schematic view of the method of the present invention;

3 is a schematic structural diagram of a system according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of a workflow of a system according to an embodiment of the present invention.

detailed description

Referring to FIG. 2, the method of the present invention involves three security elements, namely, two entities A and B and a trusted third party TP, through the online trusted third party TP, entity A and B complete two-way authentication, and obtain The status of a valid public key or public key certificate for the peer entity.

Entity A or B is represented by entity X; then R _x represents the random number generated by entity X; Certx is the public key certificate of entity X; ID _X is the identity of entity X, represented by certificate Certx or entity identifier X; ReqX Represents a request generated by entity X, requesting information such as the status of a valid public key or public key certificate of the opposite entity; ReqXT indicates a request generated by entity X or forwarded to a trusted third party TP; RepX indicates to RexX to entity X The response sent, that is, information such as the status of the valid public key or public key certificate of the entity requested by the entity X; RepTX indicates the response generated by the trusted third party TP for ReqXT; Token is the token field; Text is Select the text field. The symbols are defined as follows: ID _A = A or CertA

ID _B = B or CertB

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

The specific working process of the method of the present invention is as follows: 1) Entity A sends message 1 to entity B, and message 1 includes random number R _A , identity ID _A and optional text Textl;

2) After receiving the message 1, entity B sends a message 2 to entity A, which includes token TokenBA, identity ID _B , request ReqB, and optional text Text3, where TokenBA = R _A I IR _B I IID AI ISSB( R _A I IR _b I IID _B I IID _A l IText2) , request ReqB indicates that entity B requests the peer entity, that is, the status of the valid public key or public key certificate of entity A;

3) After receiving the message 2, the entity A sends a message 3 to the trusted third party TP. The message 3 includes the request ReqAT and the optional text Text4, wherein the ReqAT needs to contain the content of the ReqB, and the request ReqAT indicates that the entity B requests the effective public of the entity A. Information such as the status of the key or public key certificate, and information such as the status of the valid public key or public key certificate of entity B requesting entity B;

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 IDs _A and ID _{B of the} entity A and the entity B, or searches for entities through the entity identifiers A and B. The valid public key of A and entity B determines the response RepTA, where RepTA needs to contain the content of RepB, RepTA represents the information of the valid public key or public key certificate of entity A determined by trusted third party TP, and the validity of entity B Information such as the status of the public key or the public key certificate, and performing step 5);

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

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

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

6.2) Obtaining the status of the public key or public key certificate of the entity B, verifying the signature of the entity B included in the token TokenBA; and then checking whether the identity field ID _A included in the signature data of the token TokenBA is related to the entity A consistent identity check consistent whether the random number R _a in step 1) to step the entity B transmits a random number R _a contained in the token TokenBA, the results obtained authentication entity B;

7) Entity A returns message 5 to entity B, message 5 includes token TokenAB and response RepB, where TokenAB = Text71 IsS A(R _B I IID _B I IText6) , RepB indicates that the trusted third party TP determines the validity of entity A Information such as the status of the public key or public key certificate;

8) After entity B receives message 5 from entity A, perform the following steps: 8.1) verify the response RepB according to the public key authentication protocol or distribution protocol used, and if the verification is passed, proceed to step 8.2);

8.2) Obtain the status of entity A's public or public key certificate and verify the signature of entity A contained in token TokenAB. Then, it is checked whether the identity field ID _B included in the signature data of the token TokenAB is consistent with the identity field of the entity B, and whether the random number R _B sent to the entity A in step 2) is included in the token TokenAB The random number R _B is consistent, and the identification result of the entity A is obtained. So far, the two-way authentication process is completed between entity A and entity B.

If only one-way authentication of entity A to entity B is implemented, steps 7) and 8) may be omitted on the basis of the above-described two-way authentication process, and some fields in messages 1 through 5 may also be omitted. If only one-way authentication of entity B to entity A is implemented, step 1) may be omitted on the basis of the two-way authentication process, and some fields in messages 2 through 5 may also be omitted.

Referring to FIG. 3 and FIG. 4, another embodiment of the present invention further provides a system for implementing public key acquisition, certificate verification, and two-way authentication of an entity, where the system includes a first entity 301, a second entity 302, and a trusted third party 303. The structure of the system can be seen in Figure 3. The working principle of the system can be seen in Figure 4, specifically:

The first entity 301 is configured to send a message 1 to a second entity, where the message 1 includes a random number R _A , an identity ID _A, and an optional text Textl;

After receiving the message 2, the first entity sends a message to the trusted third party TP 3, and the message 3 includes the request.

ReqAT and optional text Text4;

After receiving the message 4 from the trusted third party TP, the first entity performs processing to obtain the authentication result of the second entity, and returns a message 5 to the second entity, where the message 5 includes the token TokenAB and the response RepB; After the message 5 from the first entity, processing is performed to obtain the authentication result of the first entity.

Specifically, the trusted third party TP 303 may include:

A first checking unit for identifying the ID _A and ID _B according to the identity of the first entity and a second entity, the subject Check the validity of the public key certificates Cert _A and Certs;

Or,

The first entity 301 can include:

The second entity includes:

In the embodiment of the present invention, the ReqB and the ReqAT are respectively a request generated by the second entity and the first entity, requesting the original public information of the valid public key or the public key certificate of the opposite entity, and the ReqTA includes the content of the ReqB; RepTA and RepB are responses generated for requesting ReqAT and ReqB, respectively, and RepTA contains the contents of RepB.

In the embodiment of the present invention, the forms and definitions of the ReqB, ReqAT, RepTA, and RepB are determined according to a public key authentication protocol or a distribution protocol that is specifically used, and the public key authentication protocol or distribution protocol is a line certificate status protocol or a server-based Certificate Verification Protocol.

While the present invention has been described by the embodiments of the present invention, it will be understood by those skilled in the art Without departing from the application of ^ ^ ₍

Claims

Rights request

A method for realizing public key acquisition, certificate verification, and two-way authentication of an entity, the method comprising the following steps:

After receiving the message 4 from the trusted third party TP, the entity A processes the result of the entity B, and returns a message 5 to the entity B. The message 5 includes the token TokenAB and the response RepB; the entity B receives the entity A. After message 5, processing is performed to obtain the identification result of entity A.

The method for realizing public key acquisition, certificate verification and two-way authentication of an entity according to claim 1, wherein after the trusted third party TP receives the message 3, determining that the response RepTA comprises: according to the entity A and Entity B's identity ID A and ID _B , check the validity of the public key certificates Cert _A and Cert _B ;

3. The method for realizing public key acquisition, certificate verification and two-way authentication of an entity according to claim 1, wherein:

After the entity A receives the message 4 from the trusted third party TP, the processing includes: the entity A verifies the response RepTA according to the used public key authentication protocol or the distribution protocol, and obtains the entity B public key or public if the verification succeeds. The status of the key certificate, verifying the signature of the entity B contained in the token TokenBA; then checking the identity field contained in the signature data of the token TokenBA

Whether the entity identity ID _A and A coincide identification, checks whether a message in the random number R _A and the random number R _A contained in the token TokenBA in the consistent results obtained authentication entity B.

4. The method for realizing public key acquisition, certificate verification and two-way authentication of an entity according to claim 1, wherein: After the entity B receives the message 5 from the entity A, the processing includes:

The method for realizing public key acquisition, certificate verification and two-way authentication of an entity according to claim 1 or 2 or 3 or 4, wherein: said ReqB and ReqAT are requests generated by entity B and entity A, respectively. Requesting status information of a valid public key or public key certificate of the peer entity, and ReqTA includes the content of ReqB; the RepTA and RepB are responses generated for requesting ReqAT and ReqB, respectively, and RepTA includes the content of RepB.

The method for realizing public key acquisition, certificate verification and bidirectional authentication of an entity according to any one of claims 1 to 4, characterized in that: the forms and definitions of the ReqB, ReqAT, RepTA and RepB are according to specific use. The public key authentication protocol or distribution protocol determines that the public key authentication protocol or distribution protocol is a line certificate status protocol or a server-based certificate verification protocol.

7. A system for implementing public key acquisition, certificate verification, and two-way authentication of an entity, comprising: a first entity, a second entity, and a trusted third party, wherein:

After receiving the message 1, the second entity sends a message 2 to the first entity, and the message 2 includes the token

TokenBA, identity ID _B , request ReqB, and optional text Text3;

The system for implementing public key acquisition, certificate verification, and two-way authentication of an entity according to claim 7, wherein the trusted third party TP includes:

a first checking unit, configured to check validity of the public key certificates Cert _A and Certs according to the identity IDs _A and ID _{B of the} first entity and the second entity;

Or,

9. The system for implementing public key acquisition, certificate verification and two-way authentication of an entity according to claim 7, wherein:

The first entity includes:

10. The system for implementing public key acquisition, certificate verification and two-way authentication of an entity according to claim 7, wherein:

The second entity includes:

The system for realizing public key acquisition, certificate verification and two-way authentication of an entity according to any one of claims 7 to 10, wherein: the ReqB and the ReqAT are a second entity and a first The request generated by the entity requests the original public information of the valid public key or public key certificate of the opposite entity, and ReqTA includes the content of ReqB; the RepTA and RepB are respectively responses for requesting ReqAT and ReqB, and RepTA includes RepB Content.

The system for realizing public key acquisition, certificate verification and two-way authentication of an entity according to any one of claims 7 to 10, characterized in that: the forms and definitions of the ReqB, ReqAT, RepTA and RepB are according to specific use. The public key authentication protocol or distribution protocol determines that the public key authentication protocol or distribution protocol is a line certificate status protocol or a server-based certificate verification protocol.