WO2011075906A1

WO2011075906A1 - Method for achieving public key acquisition, certificate validation and authentication of entity

Info

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

Abstract

A method for achieving public key acquisition, certificate validation and authentication of an entity is provided, and the method adopts the framework of three entities. Before the authentication, an entity A and an entity B need to acquire the public key or the certificate of a trusted third party, and acquire user certificates issued by the trusted third party to them or commit their public keys to the trusted third party's safekeeping without knowing the valid public key or the state of the public key certificate of the entity at the opposite end in advance. The method fuses the functions of the public key acquisition, certificate validation and authentication of the entity in one protocol and accomplishes them, thereby helping the enhancement of the execution efficiency and the effect of the protocol and facilitating the combination with various public key acquisition and public key certificate state enquiry protocols. The method suits with a user-access point-server network structure of the access network and meets the authentication requirement of the access network.

Description

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

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

Background technique

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

The authentication mechanism based on public key algorithm and technology requires that the participant entity must have a pair of keys, namely public and private key pairs, where the public key needs to be notified to other participant entities. The available notification methods 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 entity authentication method using public key certificates generally needs to be based on a public key infrastructure. The public key infrastructure is a universal security infrastructure that implements and provides security services by using the concepts and technologies of public keys. Provide security services such as authentication, integrity, confidentiality, and more. 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 holder's public key.

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 (TP) is a third-party entity trusted by entity A and entity B, and entity A and Entity B must be obtained by a trusted third party TP prior to authentication The status of the effective public key or public key certificate of the end entity.

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

1) CRL: Download Certificate Revocation List CRL (Certificate Revocation List) to obtain the status of 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, it downloads the latest certificate revocation list from the server and then checks if the public key certificate that needs 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 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 of the series certificate and the full certificate interval.

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 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 before authentication. Methods such as OCSP verify the validity of the access point certificate or obtain a valid public key for 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. Hi and IEEE 802.16 (e) Key Management PKM (Privacy Key Management) protocol, that is, afterwards Get the status of a valid public or public key certificate for 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-in-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 public key acquisition, certificate verification and authentication of an entity.

The technical solution of the present invention is: The present invention is a method for realizing public key acquisition, certificate verification and authentication of an entity, including:

Entity B sends message 2 to entity A, message 2 includes random number R _B , request ReqB and 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 identity ID _A , 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 returns a message 5 to the entity B, and the message 5 includes the token TokenAB and the response RepB;

After receiving the message 5 from the entity A, the entity B performs processing to obtain the authentication result of the entity A. The trusted third party TP after receiving the message 3, the method comprising determining a response RepTA: The effectiveness of the active public identity ID _A of the entity A, the public key certificate Cert Control _A check or by the entity distinguishing identifier A search for the entity A key.

The processing of the message 5 by the entity B includes:

Verifying the response RepB according to the public key authentication protocol or distribution protocol used, and obtaining the state of the public key or public key certificate of the entity A if the verification is passed, verifying the signature of the entity A included in the token TokenAB, and checking the message 2 whether the random number R _B contained in the token TokenAB in the random number R _B are consistent, the entity a to obtain the results of discrimination.

Before the entity B sends the message 2 to the entity A, it also includes:

Entity A sends message 1 to entity B, message 1 includes random number R _A , identity ID _A and optional text Text 1; entity B receives message 1. The message 2 includes a token TokenBA, an identity ID _B , a request ReqB, and an optional text Text3.

After receiving the message 3, the trusted third party TP determines that the method for responding to the RepTA includes: checking 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, search for valid public keys of entity A and entity B through entity specifiers A and B.

The processing steps of the entity A for the message 4 include:

Verify the response RepTA according to the public key authentication protocol or distribution protocol used. If the verification succeeds, obtain the status of the entity B public key or public key certificate, verify the signature of the entity B included in the token TokenBA; and then check the inclusion rights. signature data marked TokenBA in the identity field ID _a is consistent with the identity of the entity a, checking the random number R _a if step 0) step is sent to the entity B the random number R _a contained in the token TokenBA in Consistently, the identification result of entity B is obtained.

The processing steps of the entity B to the message 5 include:

The response RepB is verified according to the public key authentication protocol or the distribution protocol used, and the state of the public key or the public key certificate of the entity A is obtained if the verification is passed, and the signature of the entity A included in the token TokenAB is verified. 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 1) is included in the token TokenAB The random numbers R _B are identical, and the identification result of the entity A is obtained.

The ReqB and the ReqAT are respectively a request generated by the entity B and the entity A, requesting the original public information of the valid public key or the public key certificate of the opposite entity; and the RepTA and the RepB are responses generated for requesting the ReqAT and the ReqB, respectively.

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

The ReqTA is equal to ReqB, and RepTA is equal to RepB.

The ReqTA contains the content of ReqB, and the RepTA contains the content of RepB.

The present invention employs a three-entity framework. Entity A and entity B need to obtain a public key or certificate of a trusted third party before authentication, and obtain a user certificate issued by a trusted third party or give their public key to be trusted. The third party keeps the state without knowing the status of the valid public key or public key certificate of the opposite entity in advance. Ben The invention integrates the entity's public key acquisition, certificate verification and authentication functions in one protocol, which is beneficial to improve the efficiency and effect of protocol execution, and is convenient for combination with various public key acquisition and public key certificate status query protocols. The network user's wife enters the network structure of a server to meet the authentication requirements of the access network.

DRAWINGS

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

2 is a schematic diagram of a method according to Embodiment 1 of the present invention;

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

4 is a schematic diagram of a method according to Embodiment 3 of the present invention.

detailed description

The method of the invention involves three security elements, namely two entities Α and Β and a trusted third party TP, through the online trusted third party TP, the entity A and B complete the authentication, and obtain the effective of the peer entity The status of the public or public key certificate.

Entity A or B is represented by entity X; then R _x represents a random number generated by entity X; Cert _x is a public key certificate of entity X; ID _X is an identity of entity X, represented by certificate Certx or entity identifier X; ReqX represents the request generated by the entity X, requesting the status of the valid public key or the public key certificate of the opposite entity; ReqXT represents the request generated by the entity X or forwarded to the trusted third party TP; RepX represents the entity to the ReqX The response sent by X, 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 Optional text field. The symbols are defined as follows: ID _A = A or CertA

ID _B = B or CertB

The forms 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 protocols ( See IETF RFC5055) or other public key distribution or verification protocols.

Referring to FIG. 2, the specific method for implementing the two-way authentication 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 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 ||R _B ||ID _A ||SB (R _A ||R _B ||ID _B ||ID _A ||Text2) , 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 is determined to respond to RepTA, where RepTA needs to include the content of RepB, indicating the status of the valid public key or public key certificate of entity A determined by the trusted third party TP, and the effective public of entity B. Information such as the status of the key or public key certificate, perform 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, the following steps are completed: 6.1) verifying the response RepTA according to the public key authentication protocol or distribution protocol used, and if the verification is passed, proceeding 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 |sS A(R _B | |ID _B | |Text6) , RepB represents the entity determined by the trusted third party TP Information such as the status of A's valid public key or public key certificate;

8) After entity B receives the 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, if the verification passes Then 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; thus, the two-way authentication process is completed between the entity A and the entity B.

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

Referring to FIG. 4, 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 message 2 to message 5 may also be omitted, and the specific working process thereof may be omitted. as follows:

2) The entity B sends a message 2 to the entity A, the message 2 includes a random number R _B , a request ReqB and an optional text Text3, wherein the request ReqB indicates that the entity B requests the peer entity, that is, the state of the valid public key or the public key certificate of the entity A. Information

3) After receiving the message 2, the entity A sends a message 3 to the trusted third party TP, and the message 3 includes the identity ID _A , the request ReqAT, and the optional text Text4, where ReqAT is equal to ReqB, indicating that the entity B requests the valid public entity A. Information such as the status of the key or public key certificate;

4) The trusted third party TP after receiving the message 3, depending on the effectiveness identity ID _A of the entity A, checking or public key certificate Cert Control _A valid public key of the entity A symbol A search by distinguishing the entity, determine a response

RepTA, where RepTA is equal to RepB, and RepB is information indicating the status of the valid public key or public key certificate of the entity A determined by the trusted third party TP, and performing step 5);

6) After entity A receives the message from the trusted third party TP 4, 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.2) Obtain the state of the public key or public key certificate of entity A, 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 included in the token The random number R _B in TokenAB is consistent, and the identification result of entity A is obtained. At this point, entity B completes the one-way authentication process for entity A.

Claims

Rights request

A method for realizing public key acquisition, certificate verification and authentication of an entity, characterized in that it comprises:

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

After receiving the message 5 from entity A, entity B performs processing to obtain the authentication result of entity A.

The method for realizing public key acquisition, certificate verification and authentication of an entity according to claim 1, wherein after the trusted third party TP receives the message 3, the method for determining the response to the RepTA comprises: Identity ID _A , check the validity of the public key certificate Cert _A or search for the valid public key of entity A through the entity specifier A.

The method for implementing the public key acquisition, the certificate verification and the authentication of the entity according to claim 1, wherein the processing of the message 5 by the entity B comprises:

The method for realizing public key acquisition, certificate verification and authentication of an entity according to claim 1, wherein before the entity B sends the message 2 to the entity A, the method further includes:

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

The method for implementing public key acquisition, certificate verification and authentication of an entity according to claim 4, wherein: the message 2 comprises a token TokenBA, an identity ID _B , a request ReqB, and an optional text Text3.

The method for realizing public key acquisition, certificate verification and authentication of an entity according to claim 1, wherein after the trusted third party TP receives the message 3, the method for determining the response to the RepTA comprises: And the identity IDs _A and ID _{B of the} entity B, checking the validity of the public key certificates Cert _A and Cert _B ;

The method for implementing the public key acquisition, the certificate verification and the authentication of the entity according to claim 1, wherein the processing step of the entity A to the message 4 comprises:

The method for implementing the public key acquisition, the certificate verification and the authentication of the entity according to claim 1, wherein the processing step of the entity B to the message 5 comprises:

9. The method for realizing public key acquisition, certificate verification and authentication of an entity according to claim 1 or 2 or 3 or 4 or 5 or 6 or 7 or 8, wherein said ReqB and ReqAT are respectively The request generated by the entity B and the entity A requests the original public information of the valid public key or the public key certificate of the opposite entity; the RepTA and RepB are responses generated for requesting ReqAT and ReqB, respectively.

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

The method for realizing public key acquisition, certificate verification and authentication of an entity according to claim 1 or 2 or 3, wherein the ReqTA is equal to ReqB and RepTA is equal to RepB.

The method for realizing public key acquisition, certificate verification and authentication of an entity according to claim 4 or 5 or 6 or 7 or 8, wherein: said ReqTA includes content of ReqB, and RepTA contains content of RepB.