OpenSSL repair method, device and electronic device

Abstract

The present application provides an OpenSSL repair method, device and electronic device, the method comprising: determining the problem module in the current OpenSSL library; obtaining the repaired module of the problem module; the repaired module is the module obtained after the problem module is repaired; writing the repaired module into the source code of the project, and replacing the calling interface of the problem module with the calling interface of the repaired module in the project. This makes it possible for subsequent work to transfer the call to the problem module in the project to the newly added repaired module, thereby achieving the repair of OpenSSL without upgrading the entire OpenSSL library. In this way, since the OpenSSL library has not been upgraded, the external related dependencies do not need to be changed, thereby reducing the difficulty of repairing OpenSSL in the project, reducing the repair time, and also avoiding the problem that some parts of the tool chain cannot be upgraded, resulting in the inability to repair OpenSSL.

Description

Technical Field

[0001] The present application relates to the field of network security technology, and in particular to an OpenSSL repair method, device and electronic device. Background Art

[0002] OpenSSL (a secure sockets layer cryptographic library that includes major cryptographic algorithms, commonly used key and certificate encapsulation management functions, and SSL protocols, and provides a variety of applications for testing or other purposes) is often used in programs that handle SSL (Secure Sockets Layer) services and encrypted data. Since encryption and decryption are difficult to implement and require high security, when a product encounters security issues or bugs in the encryption module of the OpenSSL library itself, they need to be repaired in a timely manner.

[0003] Currently, the purpose of fixing cryptographic modules with bugs is usually achieved by upgrading the OpenSSL library. However, in software development projects, the various parts of the development environment or tool chain are interdependent. After upgrading the OpenSSL library, since the upgraded OpenSSL library is often different from the original version in terms of programs and interfaces, the dependencies related to the OpenSSL library in the project will become invalid due to compatibility issues, resulting in the need to upgrade the entire tool chain, making the repair work difficult, time-consuming, and sometimes even impossible to achieve. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide an OpenSSL repair method, device and electronic device to reduce the difficulty of repairing OpenSSL in a project.

[0005] An embodiment of the present application provides an OpenSSL repair method, comprising: determining a problem module in a current OpenSSL library; obtaining a repaired module of the problem module; the repaired module is a module obtained after the problem module is repaired; writing the repaired module into the source code of a project, and replacing the calling interface of the problem module with the calling interface of the repaired module in the project.

[0006] In the above implementation process, the repaired module that has been repaired is obtained, and then the repaired module is written into the source code of the project, and the calling interface of the problem module in the project is replaced with the calling interface of the repaired module. In this way, in subsequent work, the call to the original problem module in the project will be transferred to the newly added repaired module, thereby realizing the repair of OpenSSL without upgrading the entire OpenSSL library. In this way, since the OpenSSL library has not been upgraded, the external related dependencies do not need to be changed, thereby reducing the difficulty of repairing OpenSSL in the project, reducing the repair time, and also avoiding the problem that some parts of the tool chain cannot be upgraded, resulting in the inability to repair OpenSSL.

[0007] Furthermore, the method of obtaining the repaired module of the problematic module includes: obtaining the source code of a target version of the OpenSSL library; the target version is an OpenSSL version in which the problem existing in the problematic module has been fixed; and extracting the repaired module corresponding to the problematic module from the source code of the target version of the OpenSSL library.

[0008] In the above implementation process, by extracting the repaired module corresponding to the problematic module from the source code of the OpenSSL version in which the problem existing in the problematic module has been fixed, the reliability of the extracted repaired module can be guaranteed, and then the effectiveness of the repair can be guaranteed.

[0009] Furthermore, before writing the repaired module into the source code of the project, the method also includes: downloading the source code of the current OpenSSL library; and transplanting the interface of the problem module into the repaired module according to the format of the problem module in the source code of the current OpenSSL library.

[0010] In the above implementation process, the interface of the problem module is transplanted to the repaired module according to the format of the problem module in the source code of the current OpenSSL library, so as to ensure the compatibility of the extracted repaired module in the project, thereby ensuring that the project is still usable after adding the repaired module.

[0011] Furthermore, the method also includes: if the source code of the current OpenSSL library cannot be downloaded, downloading the source code of the official OpenSSL library with the same version number as the current OpenSSL library; and transplanting the interface of the target module to the repaired module according to the format of the target module corresponding to the problem module in the source code of the official OpenSSL library.

[0012] It should be understood that in actual applications, there are OpenSSL libraries currently in use that are non-open-source libraries provided by third parties and whose source code is not open. In this case, the source code of the current OpenSSL library cannot be obtained. Through the above implementation process, the source code of the official OpenSSL library with the same version number as the current OpenSSL library can be downloaded, so that when the source code of the current OpenSSL library cannot be downloaded, the interface of the target module can still be transplanted to the repaired module according to the format of the target module corresponding to the problem module in the source code of the official OpenSSL library, thereby ensuring the compatibility of the extracted repaired module in the project with the greatest probability, thereby ensuring that the project is still usable after the repaired module is added.

[0013] Furthermore, replacing the calling interface of the problematic module with the calling interface of the repaired module in the project includes: replacing the engine interface of the problematic module in the main program of the project with the engine interface of the repaired module.

[0014] In the above implementation process, by replacing the engine interface of the problem module in the main program of the project with the engine interface of the repaired module, it is possible to bypass the problem module and call the repaired module when the project needs to be called during runtime, thereby effectively achieving the repair effect.

[0015] Furthermore, after obtaining the repaired module of the problem module, the method further includes: renaming the unique identifier of the engine of the repaired module so that the unique identifier of the engine of the repaired module is different from the unique identifier of the engine of the problem module.

[0016] In actual application, there is a situation where the engine unique identifier of the repaired module is consistent with the engine unique identifier of the problem module before repair (that is, the engine unique identifier is not modified when the problem module is repaired). At this time, through the above implementation process, the engine unique identifier of the repaired module is renamed, so that when the calling interface of the problem module is replaced with the calling interface of the repaired module, there will be no calling interface conflict, thereby ensuring the reliability of the calling interface replacement.

[0017] Furthermore, after obtaining the repaired module of the problem module, the method also includes: renaming the external function of the repaired module so that the function name of the external function of the repaired module is different from the function name of the external function of the problem module; the external function is a function that provides services to the outside.

[0018] In actual application, there is a situation where the function name of the external function of the repaired module is consistent with the function name of the external function of the problem module (that is, the function name of the external function is not modified when the problem module is repaired). Through the above implementation process, the independence of the function name of the external function can be effectively guaranteed, thereby ensuring that the external function in the repaired module can work normally during the project operation.

[0019] Furthermore, writing the repaired module into the source code of the project includes: compiling the repaired module into lib, and adding the compiled lib into the source code of the project.

[0020] An embodiment of the present application also provides an OpenSSL repair device, including: a determination module, an acquisition module and a repair processing module; the determination module is used to determine the problem module in the current OpenSSL library; the acquisition module is used to obtain a repaired module of the problem module; the repaired module is a module obtained after the problem module is repaired; the repair processing module is used to write the repaired module into the source code of the project, and replace the calling interface of the problem module with the calling interface of the repaired module in the project.

[0021] An embodiment of the present application also provides an electronic device, including a processor, a memory and a communication bus; the communication bus is used to realize connection and communication between the processor and the memory; the processor is used to execute one or more programs stored in the memory to implement any of the above-mentioned OpenSSL repair methods.

[0022] A computer-readable storage medium is also provided in an embodiment of the present application, wherein the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement any of the above-mentioned OpenSSL repair methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0024] Figure 1 A flowchart of an OpenSSL repair method provided in an embodiment of the present application;

[0025] Figure 2 A schematic diagram of the structure of an OpenSSL repair device provided in an embodiment of the present application;

[0026] Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0028] Embodiment 1:

[0029] In order to reduce the difficulty of repairing OpenSSL in the project, an OpenSSL repair method is provided in the embodiment of the present application. Figure 1 As shown, Figure 1 A schematic diagram of the process of the OpenSSL repair method provided in the embodiment of the present application includes:

[0030] S101: Determine a problematic module in the current OpenSSL library.

[0031] It should be noted that the current OpenSSL library in the embodiment of the present application refers to the OpenSSL library currently used in the project.

[0032] It should also be noted that, in the embodiments of the present application, various existing methods can be used to troubleshoot and determine the module with BUG in the OpenSSL library, which is the problem module.

[0033] S102: Obtain a repaired module of the problem module.

[0034] It should be noted that, in the embodiment of the present application, the repaired module refers to a module obtained after the problem module is repaired.

[0035] In the embodiment of the present application, the repaired module corresponding to the problem module can be extracted from the OpenSSL library source code by obtaining the OpenSSL library source code of the OpenSSL version in which the problem of the problem module has been fixed. In this way, since the repaired module is extracted from the OpenSSL library source code of the OpenSSL version in which the problem of the problem module has been fixed, the repair of the problem module is officially repaired, thereby effectively ensuring the reliability of the extracted repaired module.

[0036] It should be understood that in the embodiment of the present application, in addition to the above-mentioned method for obtaining the repaired module, the source code of the current OpenSSL library can also be downloaded to extract the source code of the problematic module, and the engineer can repair it to obtain the repaired module. In the embodiment of the present application, there is no restriction on the method for obtaining the repaired module, as long as the repaired module can be obtained.

[0037] S103: writing the repaired module into the source code of the project, and replacing the calling interface of the problematic module with the calling interface of the repaired module in the project.

[0038] It should be understood that in order to ensure the compatibility of the repaired module in the project, so that after the repaired module is added to the project, it can be effectively compatible with various parts of the project, in the embodiment of the present application, the source code of the current OpenSSL library can be downloaded, and then according to the format of the problem module in the source code of the current OpenSSL library, the interface of the problem module is transplanted to the repaired module. In this way, it can be ensured that after the repaired module is added to the project, it can effectively replace the problem module and realize the connection with various parts of the project.

[0039] It should also be noted that in actual applications, there are OpenSSL libraries currently in use that are provided by third parties and are non-open-source libraries whose source code is not open. In this case, the source code of the current OpenSSL library cannot be obtained. In this regard, in an embodiment of the present application, the source code of the official OpenSSL library with the same version number as the current OpenSSL library can be downloaded, and then the interface of the target module is transplanted to the repaired module according to the format of the target module corresponding to the problem module in the source code of the official OpenSSL library.

[0040] In this way, since most of the OpenSSL libraries provided by third parties are also modified based on the officially released OpenSSL libraries, the source code of the official OpenSSL library with the same version number as the current OpenSSL library is downloaded, and then the interface of the target module is transplanted to the repaired module according to the format of the target module corresponding to the problem module in the source code of the official OpenSSL library, so as to maximize the compatibility of the extracted repaired module in the project.

[0041] In the embodiment of the present application, in order to realize the transfer of the call of the problem module to the call of the repaired module in the project, the engine interface of the problem module in the main program of the project can be replaced with the engine interface of the repaired module. In this way, when the project is running and needs to call the problem module, it can bypass the problem module and call the repaired module instead, effectively achieving the repair effect.

[0042] Exemplarily, when the main program of the project starts loading the OpenSSL library, the engine_load interface of the encryption function is executed, and the engine interface of the problematic module used in the current OpenSSL library is replaced through the ENGINE_set_default_XXX (here XXX represents the specific repaired module, such as calling ENGINE_set_default_RSA, which represents setting the default RSA module engine) interface, thereby achieving the replacement of the engine interface of the problematic module.

[0043] It should be understood that in the actual application process, there is a situation where the engine unique identifier of the repaired module is consistent with the engine unique identifier of the problem module before the repair (that is, the engine unique identifier is not modified when the problem module is repaired). In this case, even if the engine interface of the problem module in the main program of the project is replaced with the engine interface of the repaired module, since the engine unique identifier of the repaired module is consistent with the engine unique identifier of the problem module, even after the replacement, the repaired module cannot be accurately called within the project (because there is an engine with the same unique identifier), which will cause project operation errors.

[0044] To this end, in an embodiment of the present application, after obtaining a repaired module of a problem module, the unique identifier of the engine of the repaired module can be renamed so that the unique identifier of the engine of the repaired module is different from the unique identifier of the engine of the problem module.

[0045] It should be understood that in a feasible implementation of the embodiment of the present application, after obtaining the repaired module of the problem module, it is possible to first determine whether the unique identifier of the engine of the repaired module is the same as the unique identifier of the engine of the problem module. If they are not the same, renaming is not performed. If they are the same, renaming is performed.

[0046] In another feasible implementation of the embodiment of the present application, after obtaining the repaired module of the problem module, it is also possible to directly rename the unique identifier of the engine of the repaired module without determining whether the unique identifier of the engine is the same. The renaming rule for the unique identifier of the engine can be set by the engineer to ensure that the renamed name does not repeat the previous name.

[0047] It should be understood that in actual application, there is a situation where the function name of the external function of the repaired module is consistent with the function name of the external function of the problem module (that is, the function name of the external function is not modified when the problem module is repaired).

[0048] When this happens, it often causes confusion in function calls within the project, resulting in project operation errors. To this end, in an embodiment of the present application, after obtaining the repaired module of the problem module, the external function of the repaired module can also be renamed so that the function name of the external function of the repaired module is different from the function name of the external function of the problem module.

[0049] It should be understood that the external function described in the embodiments of the present application refers to a function that provides services to the outside world.

[0050] Similarly, in a feasible implementation of the embodiment of the present application, after obtaining the repaired module of the problem module, it is possible to first determine whether the function name of the external function of the repaired module is the same as the function name of the external function of the problem module. If they are not the same, renaming is not performed. If they are the same, renaming is performed.

[0051] In another feasible implementation of the embodiment of the present application, after obtaining the repaired module of the problem module, it is also possible to directly rename the function name of the external function of the repaired module without determining whether the function name of the external function is the same. Similarly, the rules for renaming the function name of the external function can be set by the engineer to ensure that the renamed name will not be repeated with the previous name.

[0052] In the embodiment of the present application, when the repaired module is written into the source code of the project, the repaired module can be compiled into lib, and then the compiled lib is added to the source code of the project. In this way, the repaired module is added to the source code of the project as lib, which is convenient for various parts in the project to call.

[0053] It should be noted that in the embodiment of the present application, the repaired module can also be directly added to the source code of the project in the form of source code, and this is not limited in the present application.

[0054] It should also be noted that in the embodiment of the present application, the repaired module added to the project can also be compiled and linked with other libraries and source codes in the project, thereby ensuring that other libraries and source codes in the project can effectively associate with the repaired module and ensure the normal operation of the project.

[0055] It should be noted that in the embodiment of the present application, the problem module and the repaired module can be encryption modules in the OpenSSL library, but this is not a limitation.

[0056] It should also be noted that the OpenSSL repair method provided in the embodiments of the present application can be implemented manually by a person with professional ability such as an engineer. In addition, it can also be implemented automatically by pre-writing a corresponding implementation program.

[0057] When the OpenSSL repair method provided in the embodiment of the present application is automatically implemented by pre-writing a corresponding implementation program, an OpenSSL repair device is also provided in the embodiment of the present application.

[0058] See also Figure 2 As shown, Figure 2 Shows the use of Figure 1 The OpenSSL repair device of the method shown. It should be understood that the specific functions of the device 200 can be referred to the description above. To avoid repetition, the detailed description is appropriately omitted here. The device 200 includes at least one software function module that can be stored in the memory in the form of software or firmware or fixed in the operating system of the device 200. Specifically:

[0059] See also Figure 2 As shown, the device 200 includes: a determination module 201, an acquisition module 202 and a repair processing module 203. Among them:

[0060] The determination module 201 is used to determine the problem module in the current OpenSSL library;

[0061] The acquisition module 202 is used to acquire a repaired module of the problem module; the repaired module is a module obtained after the problem module is repaired;

[0062] The repair processing module 203 is used to write the repaired module into the source code of the project, and replace the calling interface of the problematic module with the calling interface of the repaired module in the project.

[0063] In a feasible implementation of the embodiment of the present application, the acquisition module 202 is specifically used to obtain the source code of the target version of the OpenSSL library, and extract the repaired module corresponding to the problem module from the source code of the target version of the OpenSSL library. The target version is the OpenSSL version in which the problem existing in the problem module has been repaired.

[0064] In a feasible implementation of an embodiment of the present application, the repair processing module 203 is also used to download the source code of the current OpenSSL library before writing the repaired module into the source code of the project, and transplant the interface of the problem module into the repaired module according to the format of the problem module in the source code of the current OpenSSL library.

[0065] In the above-mentioned feasible implementation mode, the repair processing module 203 is also used to download the source code of the official OpenSSL library with the same version number as the current OpenSSL library if the source code of the current OpenSSL library cannot be downloaded, and transplant the interface of the target module to the repaired module according to the format of the target module corresponding to the problem module in the source code of the official OpenSSL library.

[0066] In a feasible implementation of the embodiment of the present application, the repair processing module 203 is specifically used to replace the engine interface of the problematic module in the main program of the project with the engine interface of the repaired module.

[0067] In a feasible implementation of an embodiment of the present application, the repair processing module 203 is also used to rename the unique identifier of the engine of the repaired module after the acquisition module 202 acquires the repaired module of the problem module, so that the unique identifier of the engine of the repaired module is different from the unique identifier of the engine of the problem module.

[0068] In a feasible implementation of an embodiment of the present application, the repair processing module 203 is also used to rename the external function of the repaired module after the acquisition module 202 acquires the repaired module of the problem module, so that the function name of the external function of the repaired module is different from the function name of the external function of the problem module; the external function is a function that provides services to the outside.

[0069] In a feasible implementation of the embodiment of the present application, the repair processing module 203 is specifically used to compile the repaired module into lib, and add the compiled lib to the source code of the project.

[0070] It should be understood that for the sake of brevity, some of the contents described in the previous text will not be repeated in the device section.

[0071] When the OpenSSL repair method provided in the embodiment of the present application is automatically implemented by pre-writing a corresponding implementation program, an electronic device is also provided in the embodiment of the present application.

[0072] See also Figure 3 As shown, the electronic device may include a processor 301, a memory 302 and a communication bus 303. Among them:

[0073] The communication bus 303 is used to realize the connection and communication between the processor 301 and the memory 302 .

[0074] The processor 301 is used to execute one or more programs stored in the memory 302 to implement the above-mentioned OpenSSL repair method.

[0075] Understandably, Figure 3 The structure shown is for illustration only. The electronic device may also include Figure 3 More or fewer components as shown, or with Figure 3 Different configurations shown.

[0076] For example, the electronic device may be a terminal, a server, a host, or other device, which is not limited in the embodiments of the present application.

[0077] When the OpenSSL repair method provided in the embodiment of the present application is automatically implemented by pre-writing the corresponding implementation program, the embodiment of the present application also provides a computer-readable storage medium, such as a floppy disk, a CD-ROM, a hard disk, a flash memory, a USB flash drive, an SD (Secure Digital Memory Card) card, an MMC (Multimedia Card) card, etc.

[0078] The computer-readable storage medium stores one or more programs for implementing the above steps, and the one or more programs can be executed by one or more processors to implement the above OpenSSL repair method, which will not be described in detail here.

[0079] The OpenSSL repair method, device, and electronic device provided in the embodiments of the present application obtain a repaired module that has been repaired, write the repaired module into the source code of the project, and replace the calling interface of the problem module with the calling interface of the repaired module in the project. In this way, in subsequent work, the call to the original problem module in the project will be transferred to the newly added repaired module, thereby realizing the repair of OpenSSL without upgrading the entire OpenSSL library. In this way, since the OpenSSL library has not been upgraded, the external related dependencies do not need to be changed, thereby reducing the difficulty of repairing OpenSSL in the project, reducing the repair time, and also avoiding the problem that some parts of the tool chain cannot be upgraded, resulting in the inability to repair OpenSSL.

[0080] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0081] In addition, the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0082] Furthermore, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0083] In this document, relational terms such as first and second, etc. are used merely to distinguish one entity or operation from another entity or operation, but do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0084] As used herein, a plurality refers to two or more than two.

[0085] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. An OpenSSL repair method, characterized in that: include: Identify the problem modules in the current OpenSSL library; Obtaining a repaired module of the problem module; The repaired module is a module obtained after the problem module is repaired; Writing the repaired module into the source code of the project, and replacing the calling interface of the problematic module with the calling interface of the repaired module in the project; The obtaining of the repaired module of the problem module comprises: obtaining source code of a target version of the OpenSSL library; the target version is an OpenSSL version in which the problem existing in the problem module has been repaired; extracting the repaired module corresponding to the problem module from the source code of the target version of the OpenSSL library; Replacing the calling interface of the problem module with the calling interface of the repaired module in the project includes: replacing the engine interface of the problem module in the main program of the project with the engine interface of the repaired module; After obtaining the repaired module of the problem module, the method further includes: renaming the unique identifier of the engine of the repaired module so that the unique identifier of the engine of the repaired module is different from the unique identifier of the engine of the problem module; After obtaining the repaired module of the problem module, the method further includes: renaming the external function of the repaired module so that the function name of the external function of the repaired module is different from the function name of the external function of the problem module; the external function is a function that provides services to the outside; Writing the repaired module into the source code of the project includes: compiling the repaired module into lib, and adding the compiled lib into the source code of the project.

2. The OpenSSL repair method according to claim 1, characterized in that: Before writing the repaired module into the source code of the project, the method further comprises: Download the source code of the current OpenSSL library; According to the format of the problem module in the source code of the current OpenSSL library, the interface of the problem module is transplanted to the repaired module.

3. The OpenSSL repair method according to claim 2, characterized in that: The method further comprises: If the source code of the current OpenSSL library cannot be downloaded, then download the source code of the official OpenSSL library with the same version number as the current OpenSSL library; According to the format of the target module corresponding to the problem module in the source code of the official OpenSSL library, the interface of the target module is transplanted to the repaired module.

4. An OpenSSL repair device, characterized in that: include: Determine module, obtain module and repair processing module; The determination module is used to determine the problem module in the current OpenSSL library; The acquisition module is used to acquire a repaired module of the problem module; the repaired module is a module obtained after the problem module is repaired; The repair processing module is used to write the repaired module into the source code of the project, and replace the calling interface of the problematic module with the calling interface of the repaired module in the project; The acquisition module is specifically used to acquire the source code of the target version of the OpenSSL library, and extract the repaired module corresponding to the problem module from the source code of the target version of the OpenSSL library; wherein the target version is the OpenSSL version in which the problem existing in the problem module has been repaired; The repair processing module is specifically used to replace the engine interface of the problem module in the main program of the project with the engine interface of the repaired module; The repair processing module is further configured to, after the acquisition module acquires the repaired module of the problem module, rename the unique identifier of the engine of the repaired module so that the unique identifier of the engine of the repaired module is different from the unique identifier of the engine of the problem module; The repair processing module is also used for, after the acquisition module acquires the repaired module of the problem module, renaming the external function of the repaired module so that the function name of the external function of the repaired module is different from the function name of the external function of the problem module; the external function is a function that provides external services; The repair processing module is specifically used to compile the repaired module into lib, and add the compiled lib into the source code of the project.

5. An electronic device, characterized in that: include: Processor, memory and communication bus; The communication bus is used to realize the connection and communication between the processor and the memory; The processor is used to execute one or more programs stored in the memory to implement the OpenSSL repair method as described in any one of claims 1 to 3.

Images