Post-quantum cryptography algorithm https encryption implementation method, device, equipment, medium and product

Abstract

This application discloses a method, apparatus, device, medium, and product for implementing HTTPS encryption using a post-quantum cryptography algorithm, relating to the field of communication technology. The method is applied to a server and includes: receiving handshake initiation information sent by a client; responding to the handshake initiation information, sending a leaf certificate from a dual-algorithm certificate file to the client; the client verifying the digital signature in the leaf certificate based on the certificate and the encryption algorithm, obtaining a verification result, and sending the verification result and the algorithm information of the encryption algorithm to the server; and establishing a communication connection with the client based on the algorithm information and the verification result. This solves the problem that existing technologies struggle to implement complete post-quantum cryptography algorithm HTTPS encryption and cannot smoothly support both new and old devices, thus improving the efficiency of communication connections.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, device, medium, and product for implementing HTTPS encryption using a post-quantum cryptography algorithm. Background Technology

[0002] Currently, HTTPS encryption on the global internet relies on SSL / TLS certificates based on traditional cryptographic algorithms such as RSA, ECC, and SM2. To prevent quantum computing threats that involve collecting data before decryption, existing technologies employ hybrid post-quantum cryptography (PQC). During the TLS handshake key exchange phase, this involves combining X25519 with MLKEM768, SM2 with MLKEM768, etc., to encapsulate the key and generate a shared key. However, this type of method is limited to the key encapsulation mechanism; server authentication still relies on SSL / TLS certificates signed with traditional cryptographic algorithms. It has not yet achieved complete PQC algorithm-based HTTPS encryption. Current national cryptographic standard upgrades often adopt a dual-certificate independent deployment scheme of SM2 / RSA, returning a single corresponding certificate based on the negotiation result. This is the industry's standard implementation method.

[0003] However, existing technologies have significant drawbacks. First, the hybrid PQC method relies on traditional signatures for server authentication, which are easily cracked once quantum computers mature, making it impossible to achieve complete PQC encryption. Second, pure PQC certificates lack feasible implementation solutions, and direct upgrades suffer from issues such as uneven migration, changes in certificate structure, performance degradation, and incompatibility with older devices. Third, the national cryptographic dual-certificate scheme relies on negotiation mechanisms and cannot adapt to PQC migration requirements. These drawbacks make it difficult for the PQC algorithm to smoothly transition in the server signature stage of HTTPS encryption, thus hindering the complete construction of quantum threat prevention capabilities.

[0004] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main purpose of this application is to provide a method, apparatus, device, medium and product for implementing HTTPS encryption using post-quantum cryptography, aiming to solve the technical problems that existing technologies are unable to implement HTTPS encryption using complete post-quantum cryptography and cannot smoothly support both new and old devices.

[0006] To achieve the above objectives, this application proposes a method for implementing HTTPS encryption using a post-quantum cryptography algorithm. This method is applied to the server side and includes the following components: Receive handshake start information sent by the client; In response to the handshake start information, a leaf certificate from the dual-algorithm certificate file is sent to the client. The client selects an encryption algorithm based on the leaf certificate, verifies the digital signature in the leaf certificate based on the encryption algorithm, obtains the verification result, and sends the verification result and the algorithm information of the encryption algorithm to the server. A communication connection with the client is established based on the algorithm information and the verification results.

[0007] In one embodiment, before the step of sending the leaf certificate from the dual-algorithm certificate file to the client, the method further includes: Obtain the certificate files for traditional cryptographic algorithms and post-quantum cryptographic algorithms issued in the cloud server; Generate a traditional algorithm private key file that matches the traditional cryptographic algorithm certificate file, and generate a post-quantum cryptographic algorithm private key file that matches the post-quantum cryptographic algorithm certificate file; Based on a preset connection order, the private key file of the traditional algorithm and the private key file of the post-quantum cryptography algorithm are superimposed to obtain a dual-algorithm private key file; Based on the preset connection order, the traditional cryptographic algorithm certificate file and the post-quantum cryptographic algorithm certificate file are superimposed to obtain a dual-algorithm certificate file; The dual-algorithm certificate file is deployed in the certificate configuration path of the server, and the dual-algorithm private key file is deployed in the private key configuration path of the server.

[0008] In one embodiment, the step of establishing a communication connection with the client based on the algorithm information and the verification result includes: The communication private key is extracted from the dual-algorithm private key file based on the algorithm information; If the algorithm information is a post-quantum cryptography algorithm, then identify the separator of the post-quantum cryptography algorithm private key in the dual-algorithm private key file, and extract the communication private key based on the separator of the post-quantum cryptography algorithm private key; If the algorithm information is a traditional cryptographic algorithm, then identify the separator of the traditional cryptographic algorithm private key in the dual-algorithm private key file, and extract the communication private key based on the separator of the traditional cryptographic algorithm private key; Generate a certificate verification signature using the communication private key; The certificate verification signature is sent to the client, which then performs identity verification based on the certificate verification signature to obtain the verification result, and sends the verification result to the server. If the confirmation result is successful, a communication connection with the client is established through a transport layer security protocol.

[0009] Furthermore, to achieve the above objectives, this application also proposes a method for implementing HTTPS encryption using a post-quantum cryptography algorithm. This method is applied to a client and includes the following components: Send a handshake start message to the server, and the server responds to the handshake start message by sending the leaf certificate from the dual-algorithm certificate file to the client; An encryption algorithm is selected based on the leaf certificate, and the digital signature in the leaf certificate is verified based on the encryption algorithm to obtain the verification result; The verification result and the algorithm information of the encryption algorithm are sent to the server, and the server establishes a communication connection with the client based on the algorithm information and the verification result.

[0010] In one embodiment, the step of selecting an encryption algorithm based on the leaf certificate and verifying the digital signature in the leaf certificate based on the encryption algorithm to obtain a verification result includes: The leaf certificate is separated based on a pre-agreed certificate delimiter to obtain several sub-leaf certificates; The encryption algorithm is determined by the aforementioned leaf certificates, and the encryption algorithm includes post-quantum cryptography and / or traditional cryptography. If the encryption algorithm is a post-quantum cryptography algorithm, the verification result is obtained by verifying the signature issued by the cloud server in the leaf certificate through the post-quantum cryptography algorithm; If the encryption algorithm is a traditional cryptographic algorithm, then the signature of the cloud server in the leaf certificate is verified by the traditional cryptographic algorithm to obtain the verification result.

[0011] In one embodiment, the step of determining the encryption algorithm through the plurality of leaf certificates includes: Read the algorithm identifier field from the leaf certificates, and identify the encryption algorithm type corresponding to the leaf certificates based on the algorithm identifier field; Query the client's locally pre-configured list of supported algorithms to determine if there is an algorithm that matches the encryption algorithm type. If the judgment result is that a consistent post-quantum cryptography algorithm exists, then the encryption algorithm is determined to be a post-quantum cryptography algorithm; If the judgment result is that there is no consistent post-quantum cryptographic algorithm but there is a consistent traditional cryptographic algorithm, then the encryption algorithm is determined to be a traditional cryptographic algorithm.

[0012] Furthermore, to achieve the above objectives, this application also proposes an implementation apparatus for post-quantum cryptography HTTPS encryption, wherein the post-quantum cryptography HTTPS encryption implementation apparatus is applied to the server side, and the post-quantum cryptography HTTPS encryption implementation apparatus includes: Receiver module 10 is used to receive handshake start information sent by the client; The verification module 20 is used to respond to the handshake start information by sending a leaf certificate from the dual-algorithm certificate file to the client, whereby the client selects an encryption algorithm based on the leaf certificate, verifies the digital signature in the leaf certificate based on the encryption algorithm, obtains a verification result, and sends the verification result and the algorithm information of the encryption algorithm to the server. The connection module 30 is used to establish a communication connection with the client based on the algorithm information and the verification result.

[0013] Furthermore, to achieve the above objectives, this application also proposes an implementation device for post-quantum cryptography algorithm HTTPS encryption, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the post-quantum cryptography algorithm HTTPS encryption implementation method as described above.

[0014] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the post-quantum cryptography algorithm HTTPS encryption method as described above.

[0015] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the post-quantum cryptography algorithm HTTPS encryption implementation method as described above.

[0016] One or more technical solutions proposed in this application have at least the following technical effects: This application proposes a method, apparatus, device, medium, and product for implementing HTTPS encryption using a post-quantum cryptography algorithm. The method is applied to a server, which receives handshake initiation information from a client. In response to the handshake initiation information, the server sends a leaf certificate from a dual-algorithm certificate file to the client. The client selects an encryption algorithm based on the leaf certificate, verifies the digital signature in the leaf certificate based on the encryption algorithm, obtains a verification result, and sends the verification result and the algorithm information of the encryption algorithm to the server. A communication connection is established with the client based on the algorithm information and the verification result. Thus, the server sends a dual-algorithm leaf certificate containing both traditional and post-quantum algorithms. Clients supporting the post-quantum algorithm can choose to verify it, achieving complete post-quantum cryptography HTTPS encryption; clients not supporting it choose the traditional algorithm. No modification to older equipment is required, and the server establishes communication accordingly. This approach balances complete encryption with compatibility between new and old devices, solving the problem that existing technologies struggle to implement complete post-quantum cryptography HTTPS encryption and cannot smoothly support both new and old devices, thereby improving the efficiency of the communication connection. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a flowchart illustrating an embodiment of the implementation method for HTTPS encryption using the quantum cryptography algorithm in this application. Figure 2 This is a flowchart illustrating the second embodiment of the implementation method for HTTPS encryption using the quantum cryptography algorithm in this application. Figure 3 This is a schematic diagram of the module structure of the device for implementing HTTPS encryption using the quantum cryptography algorithm in the embodiments of this application; Figure 4 This is a schematic diagram of the device structure of the hardware operating environment involved in the implementation method of the post-quantum cryptography algorithm HTTPS encryption in the embodiments of this application.

[0020] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0021] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0022] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0023] The main solution of this application embodiment is as follows: Obtain a traditional cryptographic algorithm certificate file and a post-quantum cryptographic algorithm certificate file issued in a cloud server; obtain a traditional algorithm private key file matching the traditional cryptographic algorithm certificate file, and a post-quantum cryptographic algorithm private key file matching the post-quantum cryptographic algorithm certificate file; connect the traditional algorithm private key file and the post-quantum cryptographic algorithm private key file according to a preset connection order to obtain a dual-algorithm private key file; superimpose the traditional cryptographic algorithm certificate file and the post-quantum cryptographic algorithm certificate file according to the preset connection order to obtain a dual-algorithm certificate file; deploy the dual-algorithm certificate file in the certificate configuration path of the server, and deploy the dual-algorithm private key file in the private key configuration path of the server. The communication private key is extracted from the dual-algorithm private key file based on the algorithm information. If the algorithm information is a post-quantum cryptography algorithm, the separator of the post-quantum cryptography algorithm private key in the dual-algorithm private key file is identified, and the communication private key is extracted based on the separator of the post-quantum cryptography algorithm private key. If the algorithm information is a traditional cryptography algorithm, the separator of the traditional cryptography algorithm private key in the dual-algorithm private key file is identified, and the communication private key is extracted based on the separator of the traditional cryptography algorithm private key. A certificate verification signature is generated using the communication private key. The certificate verification signature is sent to the client, and the client performs identity verification based on the certificate verification signature to obtain the verification result, which is then sent to the server. If the verification result is successful, a communication connection with the client is established through a transport layer security protocol. A handshake start message is sent to the server, which responds by sending a leaf certificate from its dual-algorithm certificate file to the client. An encryption algorithm is selected based on the leaf certificate, and the digital signature in the leaf certificate is verified using the encryption algorithm to obtain a verification result. The verification result and the algorithm information of the encryption algorithm are sent to the server, which then establishes a communication connection with the client based on the algorithm information and the verification result. The leaf certificate is separated into several sub-leaf certificates based on a pre-agreed certificate separator. An encryption algorithm is determined using these sub-leaf certificates, including post-quantum cryptography and / or traditional cryptography. If the encryption algorithm is post-quantum cryptography, the signature of the cloud server in the leaf certificate is verified using the post-quantum cryptography algorithm to obtain a verification result; if the encryption algorithm is traditional cryptography, the signature of the cloud server in the leaf certificate is verified using the traditional cryptography algorithm to obtain a verification result.The algorithm identifier field in the leaf certificates is read, and the encryption algorithm type corresponding to the leaf certificates is identified based on the algorithm identifier field. The client's locally pre-configured list of supported algorithms is queried to determine if an algorithm matching the encryption algorithm type exists. If a matching post-quantum cryptography algorithm exists, the encryption algorithm is determined to be a post-quantum cryptography algorithm. If no matching post-quantum cryptography algorithm exists but a matching traditional cryptography algorithm exists, the encryption algorithm is determined to be a traditional cryptography algorithm. This solves the problem that existing technologies struggle to implement complete post-quantum cryptography algorithm HTTPS encryption and cannot smoothly support both new and old devices, thus enabling communication connections and improving communication efficiency. Based on the present invention, this invention addresses the challenges currently faced by HTTPS encryption in addressing quantum computing threats. Existing solutions are either limited by key encapsulation, have difficulties in implementing pure PQC, or are incompatible with PQC migration due to the incompatibility of dual national cryptographic certificates. If the encryption scheme does not take into account both complete PQC encryption and smooth migration, it cannot guarantee the integrity of protection and device compatibility. Starting from the problem restricting the construction of quantum threat prevention capabilities, this invention designs a post-quantum cryptographic algorithm HTTPS encryption implementation method. The effectiveness of the post-quantum cryptographic algorithm HTTPS encryption implementation method of this invention is verified when establishing a communication connection. Finally, the efficiency of communication connection through the method of this invention is significantly improved.

[0024] In this embodiment, for ease of description, the implementation device of the quantum cryptography algorithm HTTPS encryption will be described as the execution subject.

[0025] Due to the limitations of existing post-quantum cryptography (PQC) in HTTPS encryption, the ability to prevent quantum threats and its adaptability to smooth migration still need improvement. One issue is the shortcomings of hybrid PQC methods, which are limited to key encapsulation and rely on traditional signatures for server authentication. These signatures are easily cracked once quantum computers mature, making it impossible to achieve complete PQC encryption. Another issue is the problem with pure PQC certificates, which lack feasible implementation solutions. Direct upgrades result in problems such as uneven migration, incompatibility with older devices, and performance degradation. Furthermore, the limitations of the national cryptographic dual-certificate scheme, which relies on negotiation mechanisms, cannot adapt to the migration requirements of PQC. Therefore, in the current transformation of HTTPS encryption for quantum security, the smooth transition of PQC algorithms also faces difficulties. Since it is necessary to balance complete encryption protection with compatibility between new and old devices and adaptation to national cryptographic scenarios, if the encryption scheme does not comprehensively address the above-mentioned shortcomings, it will be difficult to implement PQC in the server signature stage, thus hindering the complete construction of quantum threat prevention capabilities.

[0026] This application provides a solution in which the server sends a dual-algorithm leaf certificate containing both traditional and post-quantum algorithms. Clients that support the post-quantum algorithm can choose to verify it to achieve complete post-quantum cryptographic HTTPS encryption. Clients that do not support the post-quantum algorithm can choose the traditional algorithm. No modification to old equipment is required. The server establishes communication accordingly, which takes into account both complete encryption and compatibility with new and old devices. This solves the problem that existing technologies are difficult to implement HTTPS encryption with complete post-quantum cryptographic algorithms and cannot smoothly support new and old devices, thus improving the efficiency of communication connections.

[0027] Based on this, embodiments of this application provide a method for implementing HTTPS encryption using a post-quantum cryptography algorithm, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the implementation method of HTTPS encryption using the quantum cryptography algorithm in this application.

[0028] In this embodiment, the implementation method of the post-quantum cryptography algorithm for HTTPS encryption is applied to the server side, and the implementation method of the post-quantum cryptography algorithm for HTTPS encryption includes steps S01 to S03: Step S01: Receive handshake start information sent by the client; Before the implementation of this embodiment, it should be clear that existing HTTPS encryption relies on traditional cryptographic certificates, the hybrid PQC method only covers key exchange, server authentication still relies on traditional cryptographic algorithm signatures, and the national cryptographic dual certificate is an independently deployed negotiated single certificate. It has the defects of incomplete hybrid PQC encryption, poor compatibility of pure PQC upgrades, and national cryptographic schemes are not suitable for PQC migration, which hinders the smooth transition of PQC signatures and restricts the prevention of quantum threats.

[0029] Therefore, in order to solve the above problems, the solution in this embodiment receives handshake start information sent by the client on the server side. The handshake start information usually includes basic parameters used to establish a secure connection, such as the protocol version supported by the client, a list of encryption suites, and a random number.

[0030] Step S02: In response to the handshake start information, a leaf certificate from the dual-algorithm certificate file is sent to the client. The client selects an encryption algorithm based on the leaf certificate, verifies the digital signature in the leaf certificate based on the encryption algorithm, obtains the verification result, and sends the verification result and the algorithm information of the encryption algorithm to the server. In this embodiment, the leaf certificate integrates traditional digital signature algorithms and PQC digital signature algorithms. After receiving the leaf certificate, the client will select the corresponding encryption algorithm from the leaf certificate according to the algorithm type it supports, and perform verification operation on the digital signature on the leaf certificate.

[0031] If the client supports both algorithms, the PQC digital signature algorithm can be selected for verification to improve resistance to quantum attacks. If the client does not support the PQC algorithm, the traditional digital signature algorithm can be selected to complete the verification to ensure compatibility.

[0032] After completing the verification, the client sends the result of whether the verification passed and the specific information of the selected encryption algorithm (such as algorithm identifier, parameters, etc.) back to the server so that the server can perform key negotiation and other operations based on the algorithm information.

[0033] Step S03: Establish a communication connection with the client based on the algorithm information and the verification results.

[0034] During the establishment of a communication connection, the server first judges the verification result returned by the client. If the verification result is successful, the server determines the encryption algorithm used for subsequent key negotiation and data transmission based on the algorithm information sent by the client. If the client chooses the PQC digital signature algorithm, the server will enable the corresponding PQC algorithm SSL certificate and enable the PQC algorithm to negotiate the key with the client, generating a session key, thereby building a secure communication channel with quantum attack resistance throughout the chain. If the client chooses a traditional digital signature algorithm, the server uses a traditional key exchange algorithm for key negotiation to ensure normal communication with clients that do not support the PQC algorithm, ensuring backward compatibility of the system. In this way, the solution in this embodiment can achieve a smooth transition of PQC signatures while effectively preventing quantum threats and taking into account compatibility with existing systems. Of course, if the client supports the PQC algorithm key protocol, the server can use the existing hybrid PQC algorithm to implement the key negotiation mechanism, which is also compatible with the current hybrid PQC algorithm mode.

[0035] Specifically, before step S02 above, which involves sending the leaf certificate from the dual-algorithm certificate file to the client, the method further includes: Step S0201: Obtain the traditional cryptographic algorithm certificate file and the post-quantum cryptographic algorithm certificate file issued in the cloud server; Step S0202: Generate a traditional algorithm private key file that matches the traditional cryptographic algorithm certificate file, and generate a post-quantum cryptographic algorithm private key file that matches the post-quantum cryptographic algorithm certificate file; Step S0203: Based on a preset connection order, the private key file of the traditional algorithm and the private key file of the post-quantum cryptography algorithm are superimposed to obtain a dual-algorithm private key file; Step S0204: Based on the preset connection order, the traditional cryptographic algorithm certificate file and the post-quantum cryptographic algorithm certificate file are superimposed to obtain a dual-algorithm certificate file; Step S0205: Deploy the dual-algorithm certificate file in the certificate configuration path of the server, and deploy the dual-algorithm private key file in the private key configuration path of the server.

[0036] After obtaining traditional cryptographic algorithm SSL certificates and PQC algorithm SSL certificates from the CA, users directly concatenate the two types of private key files at the file level in PEM or DER format according to the preset order of "traditional algorithm first, then PQC algorithm". Only the beginning and end are joined to form a single dual-algorithm private key file. The original encoding structure of the file is not modified and no additional fields are added. The integrity of the file is immediately confirmed by hash verification after concatenation to prevent data corruption during the concatenation process.

[0037] Using the same preset connection order, file-level concatenation is performed on both types of certificate files in the same way to obtain dual-algorithm certificate files. The concatenation order of the private key and the certificate strictly corresponds to avoid the problem of mismatch between the private key and the certificate from the source.

[0038] Finally, deploy the dual-algorithm certificate files to the corresponding certificate configuration path on the server (Nginx, Apache, or IIS server) (such as the ssl_certificate directive path in Nginx), and deploy the dual-algorithm private key files to the corresponding private key configuration path (such as the ssl_certificate_key directive path in Nginx). After deployment, set read-only permissions for the private key files to restrict access, while being fully compatible with the server's regular SSL / TLS certificate deployment logic. No need to modify the server's core configuration parameters, reducing deployment costs.

[0039] More specifically, step S03 above, the step of establishing a communication connection with the client based on the algorithm information and the verification result, includes: Step S031: Extract the communication private key from the dual-algorithm private key file according to the algorithm information; Step S032: If the algorithm information is a post-quantum cryptography algorithm, then identify the separator of the post-quantum cryptography algorithm private key in the dual-algorithm private key file, and extract the communication private key based on the separator of the post-quantum cryptography algorithm private key; Step S033: If the algorithm information is a traditional cryptographic algorithm, then identify the separator of the traditional cryptographic algorithm private key in the dual-algorithm private key file, and extract the communication private key based on the separator of the traditional cryptographic algorithm private key; Step S034: Generate a certificate verification signature using the communication private key; Step S035: The certificate verification signature is sent to the client, and the client performs identity verification based on the certificate verification signature to obtain the verification result, and then sends the verification result to the server. Step S036: If the confirmation result is successful, establish a communication connection with the client through a transport layer security protocol.

[0040] After receiving the verification result and algorithm information sent by the client, the server first performs a hash verification on the dual-algorithm private key file to confirm that the file has not been tampered with and remains intact. Then, using the algorithm information as an index, it locates and separates the communication private key of the corresponding algorithm from the deployed dual-algorithm private key file.

[0041] If the algorithm information is PQC, the server uses its built-in delimiter recognition engine to traverse the dual-algorithm private key files, locate the PEM format standard delimiters (-----BEGIN PRIVATE KEY----- and -----END PRIVATE KEY-----) corresponding to the PQC algorithm private key, and accurately extract the PQC algorithm private key fragment based on the position range marked by the delimiter, automatically eliminating interference from traditional algorithm private key fragments to ensure the accuracy of private key extraction.

[0042] If the algorithm information is a traditional algorithm, the delimiter recognition logic consistent with the PQC algorithm is used to locate the standard delimiter corresponding to the traditional algorithm private key and extract the traditional algorithm private key, ensuring that the extraction logic of the two types of private keys is consistent and unambiguous.

[0043] After the private key is extracted, the server collects the full context data of the current TLS handshake, including core data that has been exchanged between the two parties, such as ClientHello, ServerHello, and dual-algorithm leaf certificate information. Using the extracted communication private key, the server performs a digital signature on the context data in combination with the corresponding algorithm's hash mechanism (such as SHA-256 or SHA-3) to generate a Certificate Verify signature, thereby strengthening the signature's anti-tampering capability.

[0044] The signature is then encapsulated in a standard TLS protocol message and sent to the client without adding any extra communication messages, thus fully reusing the TLS protocol framework and ensuring compatibility.

[0045] After receiving the authorization result from the client via the TLS extension field, if the result is successful, the server and the client exchange keys based on the negotiated algorithm type, using either a traditional cryptographic algorithm or a hybrid PQC algorithm or a PQC algorithm. They then negotiate and generate a session key through the TLS protocol, ultimately establishing an encrypted communication link. All subsequent application layer data is transmitted encrypted using this session key, ensuring data transmission security.

[0046] This embodiment, through the above-described scheme, specifically receives handshake initiation information sent by the client; in response to the handshake initiation information, it sends a leaf certificate from a dual-algorithm certificate file to the client; the client selects an encryption algorithm based on the leaf certificate, verifies the digital signature in the leaf certificate based on the encryption algorithm, obtains a verification result, and sends the verification result and the algorithm information of the encryption algorithm to the server; a communication connection is established with the client based on the algorithm information and the verification result. Thus, the server sends a dual-algorithm leaf certificate containing both traditional and post-quantum algorithms. Clients supporting the post-quantum algorithm can choose to verify it, achieving complete post-quantum cryptographic HTTPS encryption; clients not supporting it choose the traditional algorithm. No modification to older equipment is required, and the server establishes communication accordingly. This approach balances complete encryption with compatibility between new and old devices, solving the problem that existing technologies struggle to achieve complete post-quantum cryptographic HTTPS encryption and cannot smoothly support both new and old devices, thereby improving the efficiency of the communication connection.

[0047] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to the first embodiment described above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2 The post-quantum cryptography algorithm HTTPS encryption implementation method is applied to the client, and the post-quantum cryptography algorithm HTTPS encryption implementation method includes steps S04~S06: Step S04: Send handshake start information to the server, and the server responds to the handshake start information by sending the leaf certificate from the dual-algorithm certificate file to the client; Step S05: Select an encryption algorithm based on the leaf certificate, and verify the digital signature in the leaf certificate based on the encryption algorithm to obtain the verification result; Step S06: The verification result and the algorithm information of the encryption algorithm are sent to the server, and the server establishes a communication connection with the client based on the algorithm information and the verification result.

[0048] The client initiates the TLS handshake process by sending a Client Hello message (i.e., handshake start information) to the server. The message carries a list of locally pre-built algorithm support, covering compatible traditional algorithms and PQC algorithms. At the same time, it uses TLS extension fields to indicate its own PQC algorithm support capabilities and corresponding versions. The core structure and fields of the TLS message are not modified, and it adapts to the existing protocol specifications.

[0049] After the server responds to the message and returns the dual-algorithm leaf certificate, the client first verifies the format of the received certificate to confirm that it is a valid dual-algorithm overlay certificate in PEM format, without any format corruption or missing fields.

[0050] The client then initiates the certificate separation, encryption algorithm determination, and signature verification process, which is executed independently by the local cryptographic engine without relying on third-party components, ensuring verification security and efficiency.

[0051] After verification, the client encapsulates the signature verification result and the selected encryption algorithm information into the extended field of the subsequent TLS negotiation message and sends it to the server. During the information transmission, a simple checksum is attached to verify the integrity of the algorithm information and verification result, preventing data from being tampered with.

[0052] After sending, the client remains in a handshake state, waiting for the server to provide a Certificate Verify signature, in preparation for subsequent identity verification and the establishment of an encrypted communication link.

[0053] Specifically, step S05 above, which involves selecting an encryption algorithm based on the leaf certificate and verifying the digital signature in the leaf certificate based on the encryption algorithm to obtain the verification result, includes: Step S051: The leaf certificate is separated based on a pre-agreed certificate delimiter to obtain several sub-leaf certificates; Step S052: Determine the encryption algorithm through the plurality of leaf certificates, wherein the encryption algorithm includes post-quantum cryptography and / or traditional cryptography. Step S053: If the encryption algorithm is a post-quantum cryptography algorithm, then the verification result is obtained by verifying the signature of the cloud server in the leaf certificate through the post-quantum cryptography algorithm. Step S054: If the encryption algorithm is a traditional cryptographic algorithm, then the signature of the cloud server in the leaf certificate is verified by the traditional cryptographic algorithm to obtain the verification result.

[0054] The client invokes the built-in certificate parsing module, which uses pre-agreed PEM format standard separators (-----BEGIN CERTIFICATE----- and -----END CERTIFICATE-----) to perform byte-by-byte traversal and identification of the received dual-algorithm leaf certificate. By counting the occurrences of the separators (two "start identifiers" and two "end identifiers") and their corresponding positions, two independent leaf certificates are accurately separated, corresponding to the traditional cryptographic algorithm and the PQC algorithm, respectively. Immediately after separation, the format integrity of each leaf certificate is checked to eliminate potential data loss and fragment misalignment issues that may have occurred during the separation process.

[0055] The client then combines the separated leaf certificate information with its own algorithm support capabilities to determine the final encryption algorithm to be used, prioritizing the verification of PQC algorithm support while taking into account both quantum security protection priorities and compatibility requirements.

[0056] If the PQC algorithm is selected, the client uses the local PQC algorithm engine to call the corresponding algorithm's verification logic to verify the issuance signature of the CA module in the PQC leaf certificate. At the same time, it reads the AIA extended field in the leaf certificate and automatically obtains the intermediate root certificate through the URL pointed to by the field, thus building a complete certificate trust chain and verifying the certificate's legitimacy and tamper-proof status at each level.

[0057] If the traditional algorithm is chosen, the client uses a mature traditional cryptographic algorithm verification mechanism to verify the CA-issued signature of the traditional leaf certificate. If the leaf certificate does not have an AIA extension field, the client directly calls the locally pre-built intermediate root certificate to build a complete certificate trust chain, complete the signature verification, and generate the corresponding verification result.

[0058] More specifically, step S052 above, the step of determining the encryption algorithm through the plurality of leaf certificates, includes: Step S0521: Read the algorithm identifier field in the plurality of leaf certificates, and identify the encryption algorithm type corresponding to the plurality of leaf certificates based on the algorithm identifier field; Step S0522: Query the client's locally preset list of supported algorithms to determine whether there is an algorithm that matches the encryption algorithm type; Step S0523: If the judgment result is that there is a consistent post-quantum cryptography algorithm, then the encryption algorithm is determined to be a post-quantum cryptography algorithm; Step S0524: If the judgment result is that there is no consistent post-quantum cryptographic algorithm but there is a consistent traditional cryptographic algorithm, then the encryption algorithm is determined to be a traditional cryptographic algorithm.

[0059] The client performs deep analysis on each separated leaf certificate, reads the algorithm identifier field (OID field) built into the certificate, and accurately identifies the specific encryption algorithm type corresponding to each leaf certificate through a locally preset OID and algorithm type mapping table (such as OID corresponding to SM2, ML-DSA, etc.). At the same time, it extracts the algorithm version parameter to ensure the accuracy of algorithm matching and avoid verification failure due to version inconsistency.

[0060] Then, the client's locally pre-configured list of supported algorithms is queried. This list includes client-compatible traditional algorithms, PQC algorithms, their corresponding version ranges, and applicable scenarios. The identified algorithm types and versions are compared one by one to determine if there is a completely matching algorithm.

[0061] If the comparison results show that there is a consistent PQC algorithm and corresponding version, the client directly determines that the encryption algorithm is the PQC algorithm, prioritizes the quantum security protection mechanism, and records the algorithm parameters (such as key length and hash method) to provide support for subsequent signature verification and data encryption.

[0062] If no matching PQC algorithm exists, but a consistent legacy algorithm and version exist, the client determines that the encryption algorithm is the legacy algorithm, adapting to the algorithm support capabilities of older devices and ensuring communication compatibility.

[0063] If neither algorithm has a match, the client immediately terminates the subsequent handshake process and returns an authentication error message to the user stating "Server certificate algorithm incompatible". The algorithm list can be dynamically updated through client version upgrades, and new compatible PQC algorithm versions can be added to improve the scalability of the solution.

[0064] This embodiment, through the above-described scheme, specifically involves sending a handshake initiation message to the server. In response, the server sends a leaf certificate from a dual-algorithm certificate file to the client. An encryption algorithm is selected based on the leaf certificate, and the digital signature in the leaf certificate is verified using this algorithm to obtain a verification result. The verification result and the algorithm information of the encryption algorithm are then sent to the server, which establishes a communication connection with the client based on the algorithm information and the verification result. Thus, the server sends a dual-algorithm leaf certificate containing both traditional and post-quantum algorithms. Clients supporting the post-quantum algorithm can choose to verify it, achieving complete post-quantum cryptographic HTTPS encryption. Clients not supporting the post-quantum algorithm choose the traditional algorithm. No modification to older equipment is required, and the server establishes communication accordingly. This approach balances complete encryption with compatibility between new and old devices, solving the problem that existing technologies struggle to achieve complete post-quantum cryptographic HTTPS encryption and cannot smoothly support both new and old devices, thereby improving the efficiency of the communication connection.

[0065] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the implementation method of the quantum cryptography algorithm for HTTPS encryption after this application. Any simple transformations based on this technical concept are all within the protection scope of this application.

[0066] This application also provides an implementation device for HTTPS encryption using a post-quantum cryptography algorithm. Please refer to [link / reference]. Figure 3 The implementation device for post-quantum cryptography HTTPS encryption is applied to the server side, and the implementation device for post-quantum cryptography HTTPS encryption includes: The receiving module is used to receive the handshake start information sent by the client; The verification module is used to respond to the handshake start information by sending a leaf certificate from the dual-algorithm certificate file to the client, whereby the client selects an encryption algorithm based on the leaf certificate, verifies the digital signature in the leaf certificate based on the encryption algorithm, obtains a verification result, and sends the verification result and the algorithm information of the encryption algorithm to the server. The connection module is used to establish a communication connection with the client based on the algorithm information and the verification results.

[0067] The apparatus for implementing HTTPS encryption using post-quantum cryptography provided in this application, employing the method described in the above embodiments, solves the technical problems of existing technologies that struggle to implement complete post-quantum cryptography HTTPS encryption and lack smooth compatibility with both new and old devices. Compared to existing technologies, the beneficial effects of the apparatus for implementing HTTPS encryption using post-quantum cryptography provided in this application are the same as those of the method described in the above embodiments, and other technical features in the apparatus are identical to those disclosed in the methods of the above embodiments, and will not be repeated here.

[0068] This application provides an implementation device for HTTPS encryption using a post-quantum cryptography algorithm. The implementation device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the implementation method of HTTPS encryption using the post-quantum cryptography algorithm in Embodiment 1 above.

[0069] The following is for reference. Figure 4 This document illustrates a structural diagram of an implementation device suitable for implementing the post-quantum cryptography algorithm HTTPS encryption in the embodiments of this application. The implementation device for post-quantum cryptography algorithm HTTPS encryption in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 4 The illustrated implementation device for HTTPS encryption using post-quantum cryptography is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments in this application.

[0070] like Figure 4As shown, the device for implementing HTTPS encryption using post-quantum cryptography may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in read-only memory 1002 or a program loaded from storage device 1003 into random access memory 1004. Random access memory 1004 also stores various programs and data required for the operation of the device for implementing HTTPS encryption using post-quantum cryptography. The processing unit 1001, read-only memory 1002, and random access memory 1004 are interconnected via bus 1005. Input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to input / output interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows devices implementing HTTPS encryption using post-quantum cryptography to communicate wirelessly or wiredly with other devices to exchange data. While the figures show devices implementing HTTPS encryption using post-quantum cryptography with various systems, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0071] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0072] The device for implementing HTTPS encryption using post-quantum cryptography provided in this application, employing the method described in the above embodiments, solves the technical problems of existing technologies that struggle to implement complete post-quantum cryptography HTTPS encryption and lack smooth compatibility with both new and old devices. Compared to existing technologies, the beneficial effects of the device for implementing HTTPS encryption using post-quantum cryptography provided in this application are the same as those of the method described in the above embodiments. Furthermore, other technical features of this device for implementing HTTPS encryption using post-quantum cryptography are the same as those disclosed in the previous embodiment, and will not be repeated here.

[0073] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0074] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0075] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the implementation method of the post-quantum cryptography algorithm HTTPS encryption in the above embodiments.

[0076] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0077] The aforementioned computer-readable storage medium may be included in the device implementing HTTPS encryption using post-quantum cryptography; or it may exist independently and not be assembled into the device implementing HTTPS encryption using post-quantum cryptography.

[0078] The aforementioned computer-readable storage medium carries one or more programs. When these programs are executed by a device implementing HTTPS encryption using post-quantum cryptography, the device implementing HTTPS encryption uses the following methods: receives handshake initiation information sent by a client; responds to the handshake initiation information by sending a leaf certificate from a dual-algorithm certificate file to the client; the client selects an encryption algorithm based on the leaf certificate; verifies the digital signature in the leaf certificate based on the encryption algorithm; obtains a verification result; and sends the verification result and the algorithm information of the encryption algorithm to the server; and establishes a communication connection with the client based on the algorithm information and the verification result.

[0079] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0080] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0081] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0082] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described implementation method of HTTPS encryption using the post-quantum cryptography algorithm. This solves the technical problem that existing technologies struggle to implement complete HTTPS encryption using the post-quantum cryptography algorithm and cannot smoothly integrate with both new and old devices. Compared to existing technologies, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the implementation method of HTTPS encryption using the post-quantum cryptography algorithm provided in the above embodiments, and will not be repeated here.

[0083] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the post-quantum cryptography algorithm HTTPS encryption method described above.

[0084] The computer program product provided in this application can solve the technical problems of existing technologies, such as the difficulty in implementing HTTPS encryption with a complete post-quantum cryptography algorithm and the inability to smoothly integrate with both new and old devices. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the post-quantum cryptography algorithm HTTPS encryption implementation method provided in the above embodiments, and will not be repeated here.

[0085] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for implementing HTTPS encryption using a post-quantum cryptography algorithm, characterized in that, The post-quantum cryptography algorithm HTTPS encryption implementation method is applied to the server side, and the implementation method includes: Receive handshake start information sent by the client; In response to the handshake start information, a leaf certificate from the dual-algorithm certificate file is sent to the client. The client selects an encryption algorithm based on the leaf certificate, verifies the digital signature in the leaf certificate based on the encryption algorithm, obtains the verification result, and sends the verification result and the algorithm information of the encryption algorithm to the server. A communication connection with the client is established based on the algorithm information and the verification results.

2. The implementation method of HTTPS encryption using the post-quantum cryptography algorithm as described in claim 1, characterized in that, Before the step of sending the leaf certificate from the dual-algorithm certificate file to the client, the method further includes: Obtain the certificate files for traditional cryptographic algorithms and post-quantum cryptographic algorithms issued in the cloud server; Generate a traditional algorithm private key file that matches the traditional cryptographic algorithm certificate file, and generate a post-quantum cryptographic algorithm private key file that matches the post-quantum cryptographic algorithm certificate file; Based on a preset connection order, the private key file of the traditional algorithm and the private key file of the post-quantum cryptography algorithm are superimposed to obtain a dual-algorithm private key file; Based on the preset connection order, the traditional cryptographic algorithm certificate file and the post-quantum cryptographic algorithm certificate file are superimposed to obtain a dual-algorithm certificate file; The dual-algorithm certificate file is deployed in the certificate configuration path of the server, and the dual-algorithm private key file is deployed in the private key configuration path of the server.

3. The implementation method of HTTPS encryption using the post-quantum cryptography algorithm as described in claim 1, characterized in that, The step of establishing a communication connection with the client based on the algorithm information and the verification result includes: The communication private key is extracted from the dual-algorithm private key file based on the algorithm information; If the algorithm information is a post-quantum cryptography algorithm, then identify the separator of the post-quantum cryptography algorithm private key in the dual-algorithm private key file, and extract the communication private key based on the separator of the post-quantum cryptography algorithm private key; If the algorithm information is a traditional cryptographic algorithm, then identify the separator of the traditional cryptographic algorithm private key in the dual-algorithm private key file, and extract the communication private key based on the separator of the traditional cryptographic algorithm private key; Generate a certificate verification signature using the communication private key; The certificate verification signature is sent to the client, which then performs identity verification based on the certificate verification signature to obtain the verification result, and sends the verification result to the server. If the confirmation result is successful, a communication connection with the client is established through a transport layer security protocol.

4. A method for implementing HTTPS encryption using a post-quantum cryptography algorithm, characterized in that, The post-quantum cryptography algorithm HTTPS encryption implementation method is applied to the client side, and the implementation method includes: Send a handshake start message to the server, and the server responds to the handshake start message by sending the leaf certificate from the dual-algorithm certificate file to the client; An encryption algorithm is selected based on the leaf certificate, and the digital signature in the leaf certificate is verified based on the encryption algorithm to obtain the verification result; The verification result and the algorithm information of the encryption algorithm are sent to the server, and the server establishes a communication connection with the client based on the algorithm information and the verification result.

5. The implementation method of HTTPS encryption using the post-quantum cryptography algorithm as described in claim 4, characterized in that, The steps of selecting an encryption algorithm based on the leaf certificate and verifying the digital signature in the leaf certificate based on the encryption algorithm to obtain the verification result include: The leaf certificate is separated based on a pre-agreed certificate delimiter to obtain several sub-leaf certificates; The encryption algorithm is determined by the aforementioned leaf certificates, and the encryption algorithm includes post-quantum cryptography and / or traditional cryptography. If the encryption algorithm is a post-quantum cryptography algorithm, the verification result is obtained by verifying the signature issued by the cloud server in the leaf certificate through the post-quantum cryptography algorithm; If the encryption algorithm is a traditional cryptographic algorithm, then the signature of the cloud server in the leaf certificate is verified by the traditional cryptographic algorithm to obtain the verification result.

6. The implementation method of HTTPS encryption using the post-quantum cryptography algorithm as described in claim 5, characterized in that, The step of determining the encryption algorithm through the plurality of leaf certificates includes: Read the algorithm identifier field from the leaf certificates, and identify the encryption algorithm type corresponding to the leaf certificates based on the algorithm identifier field; Query the client's locally pre-configured list of supported algorithms to determine if there is an algorithm that matches the encryption algorithm type. If the judgment result is that a consistent post-quantum cryptography algorithm exists, then the encryption algorithm is determined to be a post-quantum cryptography algorithm; If the judgment result is that there is no consistent post-quantum cryptographic algorithm but there is a consistent traditional cryptographic algorithm, then the encryption algorithm is determined to be a traditional cryptographic algorithm.

7. A device for implementing HTTPS encryption using a post-quantum cryptography algorithm, characterized in that, The implementation device for post-quantum cryptography HTTPS encryption is applied to the server side, and the implementation device for post-quantum cryptography HTTPS encryption includes: The receiving module is used to receive the handshake start information sent by the client; The verification module is used to respond to the handshake start information by sending a leaf certificate from the dual-algorithm certificate file to the client, whereby the client selects an encryption algorithm based on the leaf certificate, verifies the digital signature in the leaf certificate based on the encryption algorithm, obtains a verification result, and sends the verification result and the algorithm information of the encryption algorithm to the server. The connection module is used to establish a communication connection with the client based on the algorithm information and the verification results.

8. A device for implementing HTTPS encryption using a post-quantum cryptography algorithm, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the post-quantum cryptography algorithm HTTPS encryption implementation method as described in any one of claims 1 to 6.

9. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the post-quantum cryptography algorithm HTTPS encryption method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the steps of the post-quantum cryptography algorithm HTTPS encryption method as described in any one of claims 1 to 6.

Images