Lightweight negotiation method, apparatus and device for communication network security channel, and medium

Abstract

The invention relates to the technical field of communication network security, and provides a lightweight negotiation method, device and equipment for a communication network security channel and a medium, and the method comprises the steps: receiving a handshake response fed back by a server; the handshake response comprises an index certificate added after the server determines the support state of the client for the index certificate according to the handshake request; obtaining a local cache state of the client side for the complete certificate, and determining the complete certificate and a certificate chain used by the client according to the cache state and the index certificate; and according to the determined complete certificate and certificate chain used by the client, the signature information of the server and the key sharing response field, establishing a secure channel with the server, so that after the index certificate is used in the security protocol, the PQC public key and the PQC signature information which are relatively large in length are not included in the index certificate, and the security of the security protocol is improved. And the increase of packet loss retransmission probability caused by the increase of the data size length in the handshake stage after the PQC algorithm is introduced is avoided.

Description

Technical Field

[0001] This invention relates to the field of communication network security technology, and in particular to a lightweight negotiation method, apparatus, device and medium for communication network security channels. Background Technology

[0002] With the rapid development of Internet technology, the network security risks of information systems continue to increase, and the threats and challenges are becoming increasingly severe. Cryptographic security is an important foundation of information security and can be used to effectively protect the data security of network information systems. Cryptographic technology is a core technology and an important means to protect network information systems.

[0003] Currently, 5G communication networks primarily employ Transport Layer Security (TLS) for encryption protection to ensure secure communication between Network Functions (NFs). TLS is a key exchange mechanism based on public-key cryptography, enabling the establishment of a secure data transmission channel between two communicating entities. Through TLS, 5G networks can effectively resist security threats such as data leakage, tampering, and man-in-the-middle attacks, ensuring reliable communication between network functions. Furthermore, TLS also supports authentication and data integrity verification, further enhancing the security of 5G communication networks.

[0004] With the rapid development of quantum computing technology, traditional public-key cryptosystems, represented by ECC and RSA, face fundamental security threats. The mathematical problems they rely on, such as discrete logarithms and large integer factorization, can be efficiently solved by quantum algorithms, making existing encryption mechanisms vulnerable to quantum attacks. To address this, the international standardization organization NIST has released a modular lattice-based key encapsulation mechanism (ML-KEM) as a standard algorithm for post-quantum cryptography (PQC). Compared to traditional public-key cryptography algorithms, PQC algorithms are more secure and can withstand quantum attacks. Currently, the TLS protocol based on traditional public-key cryptography algorithms can meet security requirements, but PQC algorithms need to be gradually introduced to improve TLS security as quantum computing develops.

[0005] With the introduction of PQC into security protocols such as TLS, the public key length and signature length of PQC are relatively large, resulting in larger certificates. Excessively large certificates lead to an increase in the amount of handshake data in security protocols, which may cause increased transmission latency and packet loss rates, impacting the user experience in low-bandwidth scenarios (such as satellite communications, IoT, and mobile networks). Summary of the Invention

[0006] To address the problems existing in the prior art, the present invention provides a lightweight negotiation method, apparatus, device, and medium for secure communication channels.

[0007] This invention provides a lightweight negotiation method for secure communication channels, applied on the client side, comprising: sending a handshake request to a server, wherein the handshake request comprises a key sharing extension field and a support state of the client for index certificate; receiving a handshake response fed back by the server, wherein the handshake response comprises an index certificate added by the server after determining the support state of the client for index certificate according to the handshake request, and a key sharing response field and server signature information; and the index certificate comprises a hash value of a complete certificate and a download address of the complete certificate; obtaining a local cache state of the client for a target complete certificate, and determining a complete certificate and a certificate chain used by the client according to the cache state and the index certificate; the target complete certificate is a certificate corresponding to the hash value of the complete certificate in the index certificate; establishing a secure channel with the server according to the complete certificate and the certificate chain used by the client, the server signature information and the key sharing response field.

[0008] According to the communication network security channel lightweight negotiation method provided by the application, the method further comprises: when it is determined that the target complete certificate and the certificate chain exist in the cache according to the cache state, comparing the hash value of the index certificate included in the target complete certificate with the hash value of the index certificate in the handshake response; when it is determined that the hash value of the index certificate included in the target complete certificate is consistent with the hash value of the index certificate in the handshake response, determining that the target complete certificate is the complete certificate used by the client, and determining the corresponding certificate chain.

[0009] According to the communication network security channel lightweight negotiation method provided by the application, the method further comprises: when it is determined that the hash value of the index certificate included in the target complete certificate is inconsistent with the hash value of the index certificate in the handshake response, obtaining a new complete certificate and a certificate chain according to the download address of the complete certificate included in the index certificate in the handshake response; comparing the hash value of the index certificate included in the new complete certificate with the hash value of the index certificate in the handshake response; when it is determined that the hash value of the index certificate included in the new complete certificate is consistent with the hash value of the index certificate in the handshake response, determining that the new complete certificate is the complete certificate used by the client, and determining the corresponding certificate chain.

[0010] According to the communication network security channel lightweight negotiation method provided by the application, the method further comprises: After determining the new complete certificate as the complete certificate used by the client and determining the corresponding certificate chain, the new complete certificate and the corresponding certificate chain are stored in the cache locally on the client side and are associated with the index certificate.

[0011] According to the communication network security channel lightweight negotiation method provided by the application, the method further comprises: After obtaining the new complete certificate and the certificate chain according to the complete certificate download link address included in the index certificate in the handshake response, the signature validity of the new complete certificate is checked according to the root certificate and the certificate chain.

[0012] According to the communication network security channel lightweight negotiation method provided by the application, the method further comprises: According to the determined complete certificate and the certificate chain used by the client, the correctness of the server signature information in the handshake response is verified, the key sharing information is obtained according to the key sharing response field and the key sharing extension field, and the session key is generated according to the key sharing information; and the secure channel is established with the server according to the session key.

[0013] According to the communication network security channel lightweight negotiation method provided by the application, the key sharing extension field at least includes a post-quantum cryptography PQC temporary public key.

[0014] According to the communication network security channel lightweight negotiation method provided by the application, the handshake request further includes a network protocol version supported by the client, a cipher suite and a random number.

[0015] According to the communication network security channel lightweight negotiation method provided by the application, if the support state of the index certificate by the client is not included in the handshake request, correspondingly, the method further comprises: receiving the complete certificate and the certificate chain fed back by the server.

[0016] The application further provides a communication network security channel lightweight negotiation method applied to the server side, comprising: receiving the handshake request sent by the client, wherein the handshake request includes a key sharing extension field and a support state of the index certificate by the client; According to the support state of the index certificate by the client included in the handshake request, a handshake response including an index certificate, a key sharing response field and server signature information is fed back to the client, wherein the index certificate includes a hash value of a complete certificate and a complete certificate download link address. establish a secure channel with the server according to the session key sent by the client and the determined complete certificate and certificate chain used by the client; the session key is generated according to key sharing information obtained according to a key sharing response field and a key sharing extension field after the client determines the correctness of the server signature information in the handshake response; the complete certificate used by the client is determined according to the cache status of the target complete certificate on the client side and the index certificate after the client obtains the cache status of the target complete certificate on the client side; and the target complete certificate is a certificate corresponding to the hash value of the complete certificate in the index certificate.

[0017] According to the communication network secure channel lightweight negotiation method provided by the application, the method further comprises: After the handshake response including the index certificate is fed back to the client, the support state of the server for the index certificate is set.

[0018] The application further provides a communication network secure channel lightweight negotiation device applied to the client side and comprising: The sending module is configured to send a handshake request to the server, wherein the handshake request comprises a key sharing extension field and a support state of the client for the index certificate. The first receiving module is configured to receive a handshake response fed back by the server, wherein the handshake response comprises an index certificate added by the server after the support state of the client for the index certificate is determined according to the handshake request, a key sharing response field and server signature information; and the index certificate comprises a hash value of a complete certificate and a download address of the complete certificate. The determining module is configured to obtain a cache status of a target complete certificate on the client side, and determine a complete certificate and a certificate chain used by the client according to the cache status and the index certificate; and the target complete certificate is a certificate corresponding to the hash value of the complete certificate in the index certificate. The first establishing module is configured to establish a secure channel with the server according to the determined complete certificate and certificate chain used by the client, the server signature information and the key sharing response field.

[0019] The application further provides a communication network secure channel lightweight negotiation device applied to the server side and comprising: The second receiving module is configured to receive a handshake request sent by the client, wherein the handshake request comprises a key sharing extension field and a support state of the client for the index certificate. The feedback module is configured to feed back a handshake response including an index certificate, a key sharing response field and server signature information to the client according to a support state of the client to the index certificate included in the handshake request. The second establishing module is configured to establish a secure channel with the client according to a session key sent by the client; the session key is obtained according to a key sharing response field and a key sharing extension field, and is generated according to key sharing information.

[0020] The application further provides an electronic device, including a memory, a processor and a computer program stored in the memory and executable on the processor, and the processor implements the above-mentioned communication network security channel lightweight negotiation method when executing the program.

[0021] The application further provides a non-transitory computer readable storage medium, which stores a computer program, and the computer program is executable on a processor to implement the above-mentioned communication network security channel lightweight negotiation method.

[0022] The application further provides a computer program product, which includes a computer program, and the computer program is executable on a processor to implement the above-mentioned communication network security channel lightweight negotiation method.

[0023] The application provides a communication network security channel lightweight negotiation method, device, equipment and medium, which sends a handshake request to a server by a client, adds an index certificate in a handshake response after determining a support state of the client to the index certificate according to the handshake request, and binds the index certificate and a complete certificate based on the mutual binding technology, so that the client determines a complete certificate and a certificate chain used by the client according to the index certificate, and then establishes a secure channel with the server according to the complete certificate and the certificate chain used by the determined client, server signature information and a key sharing response field, so that the index certificate is used in the security protocol, the PQC public key and the PQC signature information with a large length are not included in the index certificate, the probability of packet retransmission is not increased due to the increase in the length of the data in the handshake stage after introducing the PQC algorithm, and the secure negotiation connection of the communication is ensured. BRIEF DESCRIPTION OF DRAWINGS

[0024] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0025] Figure 1 This is a flowchart illustrating the lightweight negotiation method for secure communication channels provided by the present invention. Figure 1 .

[0026] Figure 2 This is a schematic diagram illustrating the binding information between the index certificate and the complete certificate provided by this invention.

[0027] Figure 3 This is a flowchart illustrating the lightweight negotiation method for secure communication channels provided by the present invention. Figure 2 .

[0028] Figure 4 This is a schematic diagram of the lightweight negotiation device for secure communication channels provided by the present invention. Figure 1 .

[0029] Figure 2 This is a schematic diagram of the lightweight negotiation device for secure communication channels provided by the present invention. Figure 6 .

[0030] Figure 1 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0032] Figure 1 This diagram illustrates a lightweight negotiation method for a secure communication channel provided by the present invention. (See attached diagram.) Figure 2 The method includes the following steps: Step 11: Send a handshake request to the server. The handshake request includes the key sharing extension field and the client's support status for the index certificate.

[0033] Step 12: Receive the handshake response from the server; the handshake response includes the index certificate added by the server after determining the client's support status for the index certificate based on the handshake request, as well as the key sharing response field and server signature information; the index certificate includes the hash value of the complete certificate and the download link for the complete certificate.

[0034] Step 13: Obtain the local cache status of the target full certificate on the client side. Based on the cache status and the index certificate, determine the full certificate and certificate chain used by the client. The target full certificate is the certificate corresponding to the hash value of the full certificate in the index certificate.

[0035] Step 14: Establish a secure channel with the server based on the complete certificate and certificate chain used by the client, the server signature information, and the key sharing response field.

[0036] Regarding steps 11 to 14, it should be noted that a network element (NE) is a basic functional entity of a communication network. It is the smallest functional unit in the network that can be independently configured and managed, capable of performing a specific communication function. Through collaborative work with other network elements, it realizes the information transmission and processing functions of the entire communication network, such as terminals and network functions. Therefore, in this invention, the network element on the client side is the client network element (denoted as NE_C), and the network element on the server side is the server network element (denoted as NE_S).

[0037] In this invention, the method is applicable to the TLS protocol in communication networks (including 5G networks, etc.). The TLS protocol is a negotiation mechanism in the process of establishing a secure channel based on public-key cryptography algorithms (ECC, RSA, etc.), which can establish a secure data transmission channel between two communication entities and can also support secure communication protocols such as TLS / SSL / HTTPS. The following uses the TLS protocol as an example to explain the process of the method: In this invention, during the establishment of a secure channel between the client NE_C and the server NE_S, the client network element NE_C sends a handshake request (i.e., a ClientHello message) to the server. This handshake request includes a key-sharing extension field (i.e., the key_share extension, which includes at least the post-quantum cryptography PQC public key and may also include a traditional temporary public key), and the client's support status for indexed certificates (i.e., indx_cert_c_support). The client's support status for indexed certificates means that the client has the processing function to retrieve complete certificates based on the indexed certificate. In addition, the handshake request also includes the network protocol version supported by the client (such as the TLS protocol version), cipher suites (such as those including the PQC algorithm), and a random number.

[0038] Index certificate (index_cert): A lightweight certificate that includes only essential basic certificate information, a complete certificate hash value, and a download link for the complete certificate. The complete certificate hash value is used by network elements to retrieve the corresponding complete certificate locally based on the index certificate. The download link for the complete certificate provides a certificate acquisition channel when the network element cannot find the complete certificate locally.

[0039] In this invention, after receiving the handshake request (i.e., the ClientHello message), the server-side network element NE_S sends a handshake response (i.e., the ServerHello message) to the client based on the handshake request. The handshake response includes the index certificate added by the server after determining the client's support status for the index certificate based on the handshake request, as well as the key sharing response field and the server's signature information. The index certificate includes the hash value of the complete certificate and the download link address of the complete certificate.

[0040] It's important to note that since the server can learn from the handshake request that the client supports indexed certificates, it doesn't need to directly send the complete certificate and certificate chain to the client; sending the indexed certificate is sufficient. Simultaneously, the server itself configures its support for indexed certificates. Conversely, if the client doesn't configure its support for indexed certificates in the handshake request, it will only receive the complete certificate and certificate chain directly from the server.

[0041] In this invention, after the client network element NE_C receives the handshake response including the index certificate, it needs to process the index certificate in order to obtain the complete certificate used by the client.

[0042] The client has a local cache that stores some complete certificates, but this does not mean that these complete certificates will match the index certificate. If they do not match, it may indicate that the index certificate has been tampered with or that the complete certificate on the server has been updated.

[0043] Specifically, when the client network element NE_C detects that the ServerHello message returned by NE_S uses an index certificate, it retrieves the full certificate hash value `full_cert_hash` from the index certificate. Based on `full_cert_hash`, it checks its local cache to see if a complete certificate and certificate chain corresponding to the index certificate exist. This can be described as the client-side local caching status of the target full certificate. The target full certificate is the certificate corresponding to the hash value of the full certificate in the index certificate. In other words, the certificate retrieved based on the index certificate is temporarily considered the target full certificate, and its use will be determined later.

[0044] The further method described above mainly explains the process of determining the complete certificate and certificate chain used by the client based on the cache status and index certificate, as follows: When it is determined from the cache status that the target complete certificate and certificate chain exist in the cache, the hash value of the index certificate included in the target complete certificate is compared with the hash value of the index certificate in the handshake response; When the hash value of the index certificate included in the target complete certificate is consistent with the hash value of the index certificate in the handshake response, the target complete certificate is determined to be the complete certificate used by the client, and the corresponding certificate chain is determined.

[0045] Furthermore, when the hash value of the index certificate included in the target complete certificate is inconsistent with the hash value of the index certificate in the handshake response, a new complete certificate and certificate chain are obtained based on the complete certificate download link address included in the index certificate in the handshake response. Compare the hash value of the index certificate included in the new complete certificate with the hash value of the index certificate in the handshake response; When the hash value of the index certificate included in the new complete certificate matches the hash value of the index certificate in the handshake response, the new complete certificate is determined to be the complete certificate used by the client, and the corresponding certificate chain is determined.

[0046] Specifically, if there is corresponding cached information locally (i.e., the target complete certificate is cached), the index certificate hash value is obtained from the cached complete certificate and compared with the hash value of the index certificate in ServerHello.

[0047] If they match, it means that the index certificate in ServerHello has not been tampered with, and the complete certificate and certificate chain will be used for subsequent processing.

[0048] If there is a discrepancy, it indicates that the index certificate in ServerHello may have been tampered with or the certificate of the server-side NE_S may have been updated. In this case, the local cache on the client side will be marked as not having the corresponding complete target certificate.

[0049] At this point, if there is no corresponding cached information locally, or if it is considered that there is no corresponding cached information locally, a new complete certificate and certificate chain are obtained from the Certificate Authority (CA) through the complete certificate download link address in the index certificate.

[0050] Then, the index certificate hash value is obtained from the complete certificate and compared with the hash value of the index certificate in ServerHello.

[0051] If they match, it means that the index certificate in ServerHello has not been tampered with, and the complete certificate and certificate chain will be used for subsequent processing.

[0052] If there is a discrepancy, it indicates that the index certificate in ServerHello may have been tampered with, and an error will be returned.

[0053] Additionally, after determining that the new complete certificate is the one used by the client, and after determining the corresponding certificate chain, the new complete certificate and the corresponding certificate chain are stored in the client's local cache and associated with the index certificate. See also Figure 2 This is a diagram illustrating the binding information between the index certificate and the full certificate. Figure 3 The complete certificate includes the hash value of the index certificate, and the index certificate includes the hash value of the complete certificate and the download link for the complete certificate.

[0054] It should also be noted that after obtaining the new complete certificate and certificate chain based on the complete certificate download link address included in the index certificate in the handshake response, the signature validity of the new complete certificate is checked based on the root certificate and certificate chain to ensure that the complete certificate can be obtained securely.

[0055] The further method described above mainly explains the process of establishing a secure channel with the server based on the complete certificate and certificate chain used by the client, the server's signature information, and the key sharing response field, as follows: The correctness of the server signature information in the handshake response is verified based on the complete certificate and certificate chain used by the client. Key sharing information is obtained based on the key sharing response field and key sharing extension field. A session key is generated based on the key sharing information. A secure channel is established with the server based on the session key.

[0056] The lightweight negotiation method for secure communication channels provided by this invention involves a client sending a handshake request to a server. After determining the client's support for indexed certificates based on the handshake request, the server adds the indexed certificate to the handshake response. Based on the binding technology between the indexed certificate and the full certificate, the client determines the full certificate and certificate chain it uses based on the indexed certificate. Then, based on the determined full certificate and certificate chain used by the client, the server's signature information, and the key sharing response field, a secure channel is established with the server. This ensures that after using the indexed certificate in the security protocol, since the indexed certificate does not contain the long PQC public key and PQC signature information, it avoids the increased probability of packet loss and retransmission caused by the increased data length during the handshake phase after introducing the PQC algorithm, while ensuring a secure negotiation connection for communication.

[0057] This method is suitable for communication network environments where secure channels are frequently established over a long period. In the core network of a communication network, secure connections based on network protocols are frequently established between various communication entities. After adopting a network protocol based on indexed certificates, the complete certificate and certificate chain of the other communication entity only need to be downloaded during the first establishment of a secure connection. As long as the complete certificate and certificate chain are not updated, the locally cached complete certificate and certificate chain can be used, reducing the amount of data during the handshake phase. Simultaneously, the use of a binding technology between indexed certificates and complete certificates effectively ensures the binding between them, guarantees the security of the indexed certificate, prevents its tampering, and provides high compatibility.

[0058] The lightweight negotiation method for secure communication channels provided by this invention is described below. The lightweight negotiation method for secure communication channels described below is applied to the server side and can be referred to in correspondence with the lightweight negotiation method for secure communication channels described above.

[0059] Figure 3 This diagram illustrates a lightweight negotiation method for a secure communication channel provided by the present invention. (See attached diagram.) Figure 4 The method includes the following steps: Step 31: Receive the handshake request sent by the client. The handshake request includes the key sharing extension field and the client's support status for the index certificate.

[0060] Step 32: Based on the client's support status for the index certificate included in the handshake request, send a handshake response to the client that includes the index certificate, key sharing response field, and server signature information; the index certificate includes the hash value of the complete certificate and the download link for the complete certificate.

[0061] Step 33: Establish a secure channel with the client based on the session key sent by the client; the session key is generated by the client after verifying the correctness of the server signature information in the handshake response based on the key sharing response field and the key sharing extension field, based on the complete certificate and certificate chain used by the client.

[0062] In a further method of the above method, the method further includes: After sending a handshake response to the client, including the index certificate, set the server's support status for the index certificate.

[0063] Since the method in this embodiment of the invention is based on the same principle as the method in the above embodiments, more detailed explanations will not be repeated here.

[0064] The lightweight negotiation device for a secure communication channel provided by the present invention will be described below. The lightweight negotiation device for a secure communication channel described below can be referred to in correspondence with the lightweight negotiation method for a secure communication channel described above.

[0065] Figure 4 A schematic diagram of a lightweight negotiation device for a secure communication channel provided by the present invention is shown below. Figure 5 The device includes a transmitting module 41, a first receiving module 42, a determining module 43, and a first establishing module 44, wherein: The sending module is used to send a handshake request to the server. The handshake request includes the key sharing extension field and the client's support status for the index certificate. The first receiving module is used to receive the handshake response from the server. The handshake response includes the index certificate added by the server after determining the client's support status for the index certificate based on the handshake request, as well as the key sharing response field and the server's signature information. The index certificate includes the hash value of the complete certificate and the download link for the complete certificate. The determination module is used to obtain the local cache status of the target full certificate on the client side, and determine the full certificate and certificate chain used by the client based on the cache status and the index certificate; the target full certificate is the certificate corresponding to the hash value of the full certificate in the index certificate; The first module is used to establish a secure channel with the server based on the complete certificate and certificate chain used by the client, the server signature information, and the key sharing response field.

[0066] Figure 5 A schematic diagram of a lightweight negotiation device for a secure communication channel provided by the present invention is shown below. Figure 6 The device includes a second receiving module 51, a feedback module 52, and a second establishing module 54, wherein: The second receiving module is used to receive handshake requests sent by the client. The handshake request includes a key sharing extension field and the client's support status for the index certificate. The feedback module is used to send a handshake response to the client, based on the client's support status for the index certificate included in the handshake request. The response includes the index certificate, key sharing response fields, and server signature information. The index certificate includes the hash value of the complete certificate and the download link for the complete certificate. The second module is used to establish a secure channel with the client based on the session key sent by the client. The session key is generated by the client after verifying the correctness of the server's signature information in the handshake response based on the key sharing response field and the key sharing extension field.

[0067] Since the apparatus of this embodiment is based on the same principle as the method of the above embodiment, more detailed explanations will not be repeated here.

[0068] It should be noted that, in the embodiments of the present invention, the relevant functional modules can be implemented by a hardware processor.

[0069] The lightweight negotiation device for secure communication channels provided by this invention involves a client sending a handshake request to a server. After determining the client's support for index certificates based on the handshake request, the server adds the index certificate to the handshake response. Based on the binding technology between the index certificate and the full certificate, the client determines the full certificate and certificate chain it uses based on the index certificate. Then, based on the determined full certificate and certificate chain used by the client, the server's signature information, and the key sharing response field, a secure channel is established with the server. This ensures that after using the index certificate in the security protocol, since the index certificate does not include the long PQC public key and PQC signature information, it avoids the increased probability of packet loss and retransmission caused by the increased data length during the handshake phase after the introduction of the PQC algorithm, while ensuring a secure negotiation connection for communication.

[0070] Figure 6 An example is a schematic diagram of the physical structure of an electronic device, such as... ​ As shown, the electronic device may include: a processor 61, a communication interface 62, a memory 63, and a communication bus 64, wherein the processor 61, the communication interface 62, and the memory 63 communicate with each other through the communication bus 64. The processor 61 can call logical instructions in the memory 63 to execute a lightweight negotiation method for a secure communication channel, the method including: The system sends a handshake request to the server, which includes a key-sharing extension field and the client's support status for the index certificate. It then receives a handshake response from the server. This response includes the index certificate added by the server after determining the client's support status based on the handshake request, as well as a key-sharing response field and server signature information. The index certificate includes the hash value of the complete certificate and a download link for the complete certificate. The system retrieves the client's local cache status for the target complete certificate. Based on the cache status and the index certificate, it determines the complete certificate and certificate chain used by the client. The target complete certificate is the certificate corresponding to the hash value of the complete certificate in the index certificate. Finally, based on the determined complete certificate and certificate chain used by the client, the server signature information, and the key-sharing response field, a secure channel is established with the server.

[0071] Or, The system receives a handshake request from a client, which includes a key-sharing extension field and the client's support status for the index certificate. Based on the client's support status for the index certificate included in the handshake request, the system sends a handshake response to the client, including the index certificate, a key-sharing response field, and server signature information. The index certificate includes the hash value of the complete certificate and the download link for the complete certificate. The system establishes a secure channel with the client based on the session key sent by the client. The session key is generated by the client after verifying the correctness of the server signature information in the handshake response using the confirmed complete certificate and certificate chain used by the client, based on the key-sharing response field and the key-sharing extension field.

[0072] Furthermore, the logical instructions in the aforementioned memory 63 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0073] On the other hand, the present invention also provides a computer program product, the computer program product comprising a computer program that can be stored on a non-transitory computer-readable storage medium, wherein when the computer program is executed by a processor, the computer is capable of executing a lightweight negotiation method for a secure communication channel, the method comprising: The system sends a handshake request to the server, which includes a key-sharing extension field and the client's support status for the index certificate. It then receives a handshake response from the server. This response includes the index certificate added by the server after determining the client's support status based on the handshake request, as well as a key-sharing response field and server signature information. The index certificate includes the hash value of the complete certificate and a download link for the complete certificate. The system retrieves the client's local cache status for the target complete certificate. Based on the cache status and the index certificate, it determines the complete certificate and certificate chain used by the client. The target complete certificate is the certificate corresponding to the hash value of the complete certificate in the index certificate. Finally, based on the determined complete certificate and certificate chain used by the client, the server signature information, and the key-sharing response field, a secure channel is established with the server.

[0074] Or, The system receives a handshake request from a client, which includes a key-sharing extension field and the client's support status for the index certificate. Based on the client's support status for the index certificate included in the handshake request, the system sends a handshake response to the client, including the index certificate, a key-sharing response field, and server signature information. The index certificate includes the hash value of the complete certificate and the download link for the complete certificate. The system establishes a secure channel with the client based on the session key sent by the client. The session key is generated by the client after verifying the correctness of the server signature information in the handshake response using the confirmed complete certificate and certificate chain used by the client, based on the key-sharing response field and the key-sharing extension field.

[0075] In another aspect, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to perform a lightweight negotiation method for a secure communication channel, the method comprising: The system sends a handshake request to the server, which includes a key-sharing extension field and the client's support status for the index certificate. It then receives a handshake response from the server. This response includes the index certificate added by the server after determining the client's support status based on the handshake request, as well as a key-sharing response field and server signature information. The index certificate includes the hash value of the complete certificate and a download link for the complete certificate. The system retrieves the client's local cache status for the target complete certificate. Based on the cache status and the index certificate, it determines the complete certificate and certificate chain used by the client. The target complete certificate is the certificate corresponding to the hash value of the complete certificate in the index certificate. Finally, based on the determined complete certificate and certificate chain used by the client, the server signature information, and the key-sharing response field, a secure channel is established with the server.

[0076] Or, The system receives a handshake request from a client, which includes a key-sharing extension field and the client's support status for the index certificate. Based on the client's support status for the index certificate included in the handshake request, the system sends a handshake response to the client, including the index certificate, a key-sharing response field, and server signature information. The index certificate includes the hash value of the complete certificate and the download link for the complete certificate. The system establishes a secure channel with the client based on the session key sent by the client. The session key is generated by the client after verifying the correctness of the server signature information in the handshake response using the confirmed complete certificate and certificate chain used by the client, based on the key-sharing response field and the key-sharing extension field.

[0077] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0078] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0079] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A lightweight negotiation method for secure communication channels, characterized in that, Applied to the client side, including: Send a handshake request to the server, the handshake request including the key sharing extension field and the client's support status for the index certificate; The server receives a handshake response; the handshake response includes the index certificate added by the server after determining the client's support status for the index certificate based on the handshake request, as well as a key sharing response field and server signature information; the index certificate includes the hash value of the complete certificate and the download link for the complete certificate; Obtain the local cache status of the target full certificate on the client side, and determine the full certificate and certificate chain used by the client based on the cache status and the index certificate; the target full certificate is the certificate corresponding to the hash value of the full certificate in the index certificate; Establish a secure channel with the server based on the complete certificate and certificate chain used by the client, the server signature information, and the key sharing response field.

2. The lightweight negotiation method for secure communication channels according to claim 1, characterized in that, The step of determining the complete certificate and certificate chain used by the client based on the cache status and the index certificate includes: When it is determined from the cache status that the target complete certificate and certificate chain exist in the cache, the hash value of the index certificate included in the target complete certificate is compared with the hash value of the index certificate in the handshake response; When the hash value of the index certificate included in the target complete certificate is consistent with the hash value of the index certificate in the handshake response, the target complete certificate is determined to be the complete certificate used by the client, and the corresponding certificate chain is determined.

3. The lightweight negotiation method for secure communication channels according to claim 2, characterized in that, The method further includes: If the hash value of the index certificate included in the target complete certificate is inconsistent with the hash value of the index certificate in the handshake response, a new complete certificate and certificate chain are obtained according to the complete certificate download link address included in the index certificate in the handshake response. The hash value of the index certificate included in the new complete certificate is compared with the hash value of the index certificate in the handshake response; When the hash value of the index certificate included in the new complete certificate is found to be consistent with the hash value of the index certificate in the handshake response, the new complete certificate is determined to be the complete certificate used by the client, and the corresponding certificate chain is determined.

4. The lightweight negotiation method for secure communication channels according to claim 3, characterized in that, The method further includes: After determining that the new complete certificate is the complete certificate used by the client, and after determining the corresponding certificate chain, the new complete certificate and the corresponding certificate chain are stored in the local cache on the client side and associated with the index certificate.

5. The lightweight negotiation method for secure communication channels according to claim 3 or the method described above, characterized in that, The method further includes: After obtaining the new complete certificate and certificate chain based on the complete certificate download link address included in the index certificate in the handshake response, the signature validity of the new complete certificate is checked based on the root certificate and certificate chain.

6. The lightweight negotiation method for secure communication channels according to claim 3 or the method described above, characterized in that, The step of establishing a secure channel with the server based on the determined complete certificate and certificate chain used by the client, the server signature information, and the key sharing response field includes: The correctness of the server signature information in the handshake response is verified based on the complete certificate and certificate chain used by the client. Key sharing information is obtained based on the key sharing response field and key sharing extension field. A session key is generated based on the key sharing information. A secure channel is established with the server based on the session key.

7. The lightweight negotiation method for secure communication channels according to claim 1, characterized in that, The key-sharing extension field includes at least the post-quantum cryptography PQC temporary public key.

8. The lightweight negotiation method for secure communication channels according to claim 1 or 7, characterized in that, The handshake request also includes a network protocol version supported by the client, a cipher suite, and a random number.

9. The lightweight negotiation method for secure communication channels according to claim 8, characterized in that, If the handshake request does not include the client's support status for the index certificate, the method further includes receiving the complete certificate and certificate chain returned by the server.

10. A lightweight negotiation method for secure communication channels, characterized in that, Applied to the server side, including: Receive a handshake request sent by the client, the handshake request including a key sharing extension field and the client's support status for the index certificate; Based on the client's support status for the index certificate included in the handshake request, a handshake response including the index certificate, a key sharing response field, and server signature information is sent back to the client; the index certificate includes the hash value of the complete certificate and the download link for the complete certificate; A secure channel is established with the client based on the session key sent by the client. The session key is generated by the client after verifying the correctness of the server signature information in the handshake response based on the key sharing response field and the key sharing extension field, based on the key sharing information.

11. The lightweight negotiation method for secure communication channels according to claim 10, characterized in that, The method further includes: After sending a handshake response to the client that includes the index certificate, the server sets the support status for the index certificate.

12. A lightweight negotiation device for a secure communication channel, characterized in that, Applied to the client side, including: The sending module is used to send a handshake request to the server. The handshake request includes a key sharing extension field and the client's support status for the index certificate. The first receiving module is used to receive the handshake response from the server; the handshake response includes the index certificate added by the server after determining the client's support status for the index certificate based on the handshake request, as well as a key sharing response field and server signature information; the index certificate includes the hash value of the complete certificate and the download link address of the complete certificate; The determination module is used to obtain the local cache status of the target complete certificate on the client side, and determine the complete certificate and certificate chain used by the client based on the cache status and the index certificate; the target complete certificate is the certificate corresponding to the hash value of the complete certificate in the index certificate; The first module is used to establish a secure channel with the server based on the complete certificate and certificate chain used by the client, the server signature information, and the key sharing response field.

13. A lightweight negotiation device for a secure communication channel, characterized in that, Applied to the server side, including: The second receiving module is used to receive a handshake request sent by the client, the handshake request including a key sharing extension field and the client's support status for the index certificate; The feedback module is used to send a handshake response to the client, including the index certificate, a key sharing response field, and server signature information, based on the client's support status for the index certificate included in the handshake request; the index certificate includes the hash value of the complete certificate and the download link for the complete certificate; The second establishment module is used to establish a secure channel with the client based on the session key sent by the client. The session key is generated by the client after verifying the correctness of the server signature information in the handshake response using the determined complete certificate and certificate chain used by the client, based on the key sharing response field and the key sharing extension field. The complete certificate used by the client is determined by the client after obtaining the local cache status of the target complete certificate on the client side, based on the cache status and the index certificate. The target complete certificate is the certificate corresponding to the hash value of the complete certificate in the index certificate.

14. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the lightweight negotiation method for a secure communication channel as described in any one of claims 1-9, or the lightweight negotiation method for a secure communication channel as described in claim 10 or 11.

15. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the lightweight negotiation method for a secure communication channel as described in any one of claims 1-9, or the lightweight negotiation method for a secure communication channel as described in claim 10 or 11.

16. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the lightweight negotiation method for a secure communication channel as described in any one of claims 1-9, or the lightweight negotiation method for a secure communication channel as described in claim 10 or 11.

Images