Method, apparatus, device and medium for configuration verification and recovery based on pfr
Patent Information
- Application Number
- CN202211203300.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-09-29
- Publication Date
- 2026-09-25
- Estimated Expiration
- 2042-09-29
AI Technical Summary
[0004]存在的问题是:仅添加了验证模块,缺少验证失败后的动作
[0045]从以上技术方案可以看出,本发明具有以下优点:即对平台的全部信息进行校验。当校验失败后尽可能的恢复原有配置,如有不可恢复项则提示警告。通过PFR固件校验恢复和BMC配置校验恢复能极大地保证配置准确性,提高平台的容错容灾能力,比如对于无校验恢复能力的平台,当刷新损坏版本的BMC时,也会刷新不生效,但会使当前平台的BMC不可用,简而言之就是BMC挂死,后续只能通过人工烧录或连COM口UBOOT的方式进行固件刷新,费事费力。本发明提供的校验恢复能力能大大削弱固件挂死带来的影响,当出现挂死时,只需AC断电,重新进行恢复即可。相较与传统方法,本发明的配置校验不仅仅针对固件,它覆盖这个平台,当平台配置出现错误,会连接部件库服务器实现自动恢复并打印出错误信息。针对非硬件物理层面的错误或非预期结果,提供一键矫正功能,如Firmware和Driver版本不符合预期,会一键升级,降低时间成本。
Smart Images

Figure CN115509814B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of configuration verification and recovery technology, specifically to a method, apparatus, device, and medium for configuration verification and recovery based on PFR. Background Technology
[0002] Platform Firmware Resilience (PFR) is a security technology used to support the security requirements of NISTSP 800-193. PFR aims to protect platform assets, detect malicious or erroneous actions such as corrupted firmware, and restore platform firmware to a healthy state. It provides multi-layered firmware attack protection and recovery mechanisms, thus increasing platform resilience. Through its verification functions, it successfully avoids malicious or erroneous BIOS and BMC firmware flashing, and recovers firmware versions after flashing failures, ensuring the fault tolerance of server products and greatly improving stability.
[0003] Prior art (publication number CN114579982A) discloses a method, system, device, and storage medium for firmware upgrade based on PFR. Specifically, it involves issuing a first command to a management module to perform a firmware upgrade on the device to be updated; in response to receiving the first command, storing the firmware to be upgraded in flash memory according to the first command, and sending a second command to the PFR; in response to receiving the second command, reading the firmware information from the flash memory and verifying it through an internal verification module; and in response to successful verification, performing a firmware upgrade on the device to be updated. The internal verification module verifies the firmware, ensuring the security of the firmware upgrade; and the human-machine interaction module displays the upgrade information, facilitating the upgrade operation for technicians.
[0004] The problem is that only a verification module has been added, lacking actions for verification failures. It only applies to firmware upgrades and cannot provide protection against firmware corruption, firmware crashes, or other issues. The focus is on firmware, failing to provide comprehensive protection for the entire platform. Summary of the Invention
[0005] To address the problems existing in the prior art, the present invention provides a method, apparatus, device, and medium for configuration verification and recovery based on PFR.
[0006] In a first aspect, the present invention provides a method for configuration verification and recovery based on PFR, comprising the following steps:
[0007] After the PFR firmware verification is completed, the required configuration JSON file is copied out from the firmware flash area;
[0008] After firmware activation, collect the actual configuration information of the current machine;
[0009] Compare the collected actual configuration information with the configuration JSON file;
[0010] Recoverable items with different comparison results will be configured for recovery, while unrecoverable items will be output as a warning.
[0011] Furthermore, after the PFR firmware verification is complete, the steps for copying the required configuration JSON file from the firmware flash area include:
[0012] PFR firmware verification passed. Boot the firmware into normal mode and power on to activate.
[0013] Copy the required configuration JSON file from the firmware's valid area;
[0014] If the verification fails, remove the erroneous firmware from the valid area and copy the firmware from the recovery area to the valid area; execution steps: boot the firmware and power on to activate it in normal mode.
[0015] Furthermore, before the step of copying the required configuration JSON file from the firmware flash area after PFR firmware verification is completed, the following steps are included:
[0016] Start the server according to the pre-boot mode settings;
[0017] Perform digital verification on the server firmware; execution steps: After the PFR firmware verification is completed, if the verification passes, boot the firmware into power-on mode to activate it in normal mode.
[0018] Furthermore, the steps for configuring recoverable items with different comparison results to recover, and outputting warnings for unrecoverable items include:
[0019] When the actual configuration information differs from the configuration JSON file, retrieve the items that differ between the actual configuration and the configuration JSON file.
[0020] Connect to the component library server to obtain different configurable items and retrieve the corresponding firmware configuration information online.
[0021] Replace the found recoverable items with the configuration information obtained online;
[0022] Output an alert for items that cannot be recovered.
[0023] Firmware verification and recovery via PFR and BMC configuration verification and recovery greatly ensure configuration accuracy and improve the platform's fault tolerance and disaster recovery capabilities. For example, for platforms without verification and recovery capabilities, refreshing a corrupted version of the BMC will not take effect, rendering the current platform's BMC unusable—in short, the BMC is "hung up." Subsequent firmware updates can only be performed manually or via COM port U-Boot, which is time-consuming and laborious. The verification and recovery capabilities provided by this invention greatly mitigate the impact of firmware hangs. When a hang occurs, simply power off the AC and perform a recovery. Compared to traditional methods, the configuration verification of this invention is not only for the firmware but covers the entire platform. When platform configuration errors occur, it connects to the component library server to achieve automatic recovery and print error information. For non-hardware physical errors or unexpected results, a one-click correction function is provided. For example, if the firmware and driver versions do not meet expectations, a one-click upgrade will be performed, reducing time costs.
[0024] Secondly, the present invention provides a configuration verification and recovery device based on PFR, including a expected requirement configuration acquisition module, a collection module, a comparison module, a configuration recovery module, and an alarm module.
[0025] The expected requirements configuration acquisition module is used to copy the expected requirements configuration JSON file from the firmware flash area after PFR firmware verification is completed.
[0026] The collection module is used to collect the actual configuration information of the current machine after firmware activation;
[0027] The comparison module is used to compare the collected actual configuration information with the configuration JSON file;
[0028] The configuration recovery module is used to configure and recover recoverable items with different comparison results;
[0029] The alarm module is used to output a warning for unrecoverable items.
[0030] Furthermore, the device also includes an execution module and a firmware recovery module;
[0031] The execution module is used to boot the firmware for activation in normal mode after PFR firmware verification passes.
[0032] The expected requirements configuration acquisition module is used to copy the expected requirements configuration JSON file from the firmware valid area;
[0033] The firmware recovery module is used to remove erroneous firmware from the valid area if the verification fails, and to copy the firmware from the recovery area to the valid area to trigger the execution module.
[0034] Furthermore, the device also includes a firmware verification module;
[0035] The execution module is also used to start the server according to the set pre-boot mode;
[0036] The firmware verification module is used to digitally verify the server firmware after the server starts up according to the set pre-boot mode. If the verification passes, the module outputs information to the execution module to guide the firmware to power on and activate in normal mode; if the verification fails, the module outputs information to the firmware recovery module.
[0037] Furthermore, the configuration recovery module includes a configuration item acquisition unit and a configuration recovery unit;
[0038] The configuration item retrieval unit is used to retrieve the items that differ between the actual configuration information and the configuration JSON file when the actual configuration information is different from the configuration JSON file.
[0039] The configuration recovery unit is used to obtain different configurable items by connecting to the component library server and obtaining the corresponding firmware configuration information online; the online obtained configuration information is then used to replace the found recoverable items.
[0040] Thirdly, the present invention also provides an electronic device, the electronic device comprising:
[0041] At least one processor; and,
[0042] A memory communicatively connected to the at least one processor; wherein,
[0043] The memory stores computer program instructions executable by at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the PFR-based configuration verification and recovery method as described in the first aspect.
[0044] Fourthly, the present invention also provides a non-transitory computer-readable storage medium that stores computer instructions that cause the computer to execute the configuration verification and recovery method based on PFR as described in the first aspect.
[0045] As can be seen from the above technical solutions, this invention has the following advantages: it verifies all information of the platform. When verification fails, it restores the original configuration as much as possible; if any items are unrecoverable, a warning is displayed. PFR firmware verification and recovery, along with BMC configuration verification and recovery, greatly ensures configuration accuracy and improves the platform's fault tolerance and disaster recovery capabilities. For example, for platforms without verification and recovery capabilities, refreshing a corrupted version of the BMC will not take effect, but will render the current platform's BMC unusable—in short, the BMC is "hung up." Subsequent firmware updates can only be performed manually or via COM port U-Boot, which is time-consuming and laborious. The verification and recovery capabilities provided by this invention greatly reduce the impact of firmware hangs. When a hang occurs, simply power off the AC and perform a recovery. Compared to traditional methods, the configuration verification of this invention is not only for the firmware but covers the entire platform. When platform configuration errors occur, it connects to the component library server to achieve automatic recovery and print error information. For errors or unexpected results that are not at the hardware physical level, a one-click correction function is provided. For example, if the firmware and driver versions do not meet expectations, a one-click upgrade will be performed, reducing time costs.
[0046] Furthermore, the design principle of this invention is reliable, the structure is simple, and it has a very wide range of application prospects.
[0047] Therefore, it is evident that the present invention has outstanding substantive features and significant progress compared with the prior art, and the beneficial effects of its implementation are also obvious. Attached Figure Description
[0048] To more clearly illustrate the technical solutions in the embodiments of the present invention 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.
[0049] Figure 1 This is a schematic flowchart of a method according to an embodiment of the present invention.
[0050] Figure 2 This is a schematic block diagram of an apparatus according to an embodiment of the present invention. Detailed Implementation
[0051] The system involves issuing a first command to the management module to perform a firmware upgrade on the device to be updated; in response to receiving the first command, storing the firmware to be upgraded in the flash memory according to the first command, and sending a second command to the PFR; in response to receiving the second command, reading the firmware information from the flash memory and verifying it through an internal verification module; and in response to successful verification, upgrading the firmware on the device to be updated. The internal verification module verifies the firmware, ensuring the security of the firmware upgrade; the human-machine interaction module displays the upgrade information, facilitating the upgrade operation for technicians. However, the system has some drawbacks, including the lack of actions after verification failure (only a verification module is added). It only applies to firmware upgrades and cannot provide protection in cases of firmware corruption or firmware crashes. The focus is on the firmware, failing to provide comprehensive protection for the entire platform. To enable those skilled in the art to better understand the technical solutions of this invention, the technical solutions in the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this invention, not all of them. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this invention.
[0052] This invention provides a method for configuration verification and recovery based on PFR, comprising the following steps:
[0053] Step 1: After the PFR firmware verification is completed, copy the required configuration JSON file from the firmware flash area;
[0054] Step 2: After firmware activation, collect the actual configuration information of the current machine;
[0055] Step 3: Compare the collected actual configuration information with the configuration JSON file;
[0056] Step 4: Configure and restore recoverable items with different comparison results, and output warnings for unrecoverable items.
[0057] After PFR firmware verification and recovery, the system boots in normal mode. The PCH, BIOS, and BMC are powered on and activated. The system copies the expected configuration JSON file from the BMC flash area. After successful boot, the BMC collects the actual configuration information of the current machine and compares it with the expected configuration JSON file, verifying motherboard hardware firmware, PCIe device information, such as hard drive model, quantity, firmware, and network card driver version. If verification fails, i.e., the actual configuration information differs from the expected configuration, the machine attempts to restore the configuration as much as possible by connecting to the component library server to obtain the corresponding firmware and drivers online. In cases of unrecoverable issues, such as incorrect component models or quantities, a warning will be issued via the BMC web interface.
[0058] like Figure 1 As shown, this embodiment of the invention provides a configuration verification and recovery method based on PFR, including the following steps:
[0059] S1: Start the server according to the pre-startup mode set;
[0060] S2: Perform digital verification on the server firmware; if the PFR firmware verification passes, proceed to step S3; if the verification fails, proceed to step S11.
[0061] S3: Boot the firmware and power on to activate in normal mode;
[0062] S4: Copy the required configuration JSON file from the firmware valid area;
[0063] S5: Collects the actual configuration information of the current machine;
[0064] S6: Compare the collected actual configuration information with the configuration JSON file;
[0065] If the actual configuration information differs from the configuration JSON file, proceed to step S7; otherwise, end.
[0066] S7: Retrieve items that differ between the actual configuration and the configuration JSON file;
[0067] S8: Connect to the component library server to obtain different configurable items and retrieve the corresponding firmware configuration information online;
[0068] S9: Replace the found recoverable items with the configuration information obtained online;
[0069] S10: Output an alarm for unrecoverable items;
[0070] S11: Remove the erroneous firmware from the valid area, and copy the firmware from the recovery area to the valid area; proceed to step S3.
[0071] Start the server according to the pre-boot mode; perform digital verification of the server firmware; execution steps: after the PFR firmware verification is completed, if the verification passes, boot the firmware into power-on mode for activation.
[0072] In other words, PFR technology is first used to enable the processor to boot in a specific pre-boot mode (T-1). In this mode, only the CPU is active, while all other devices that might interfere with the boot path (such as the PCH / ME and BMC) are in a reset state. Critical boot firmware (such as BIOS, ME, BMC, etc.) requires digital verification in T-1 mode. If firmware verification fails, PFR triggers a firmware recovery event, then removes the erroneous firmware from the SPI Flash Active area and copies a copy of the firmware from Gold to the SPI Flash Active area. Updates from the Gold copy are also performed in T-1 mode. If verification succeeds, the system continues to boot in normal mode.
[0073] The BMC collects the actual configuration information of the current machine and compares it with the expected configuration JSON file. It verifies motherboard hardware firmware, PCIe device information, such as hard drive model, quantity, firmware, and network card driver version. When verification fails, indicating a discrepancy between the actual and expected configuration, the machine attempts to restore its configuration by connecting to the component library server to retrieve the corresponding firmware and drivers online. In cases of unrecoverable issues, such as incorrect component models or quantities, a warning will be issued via the BMC web interface.
[0074] In other words, after the server powers on, it first performs PFR firmware verification. PFR causes the system to boot into a specific trusted operating mode (T-1), performing secure boot, firmware update, and recovery operations. In this pre-boot environment, only CPU0 is powered on in isolation, while other components such as the CPU, PCH, and BMC remain in a reset state. To enter T-1 mode, the PFR CPLD drive signal triggers the board's power-on timing sequence.
[0075] In T-1 mode, the PFR CPLD can fully access all SPI devices. The key operations during this phase are as follows:
[0076] (1) Complete firmware digital signature verification for the effective and recovery areas of PCH and BMC.
[0077] PFR VCM and PFR CPLD assist in calculating SHA256 hash values for verification. It can also check if any firmware needs updating: PCH / BMC recovery gold updates, digital VR / PSU, HSBP firmware updates, etc. It performs the update operation by verifying the authenticity of the update candidate copy. For example, if any valid SPI Flash image of the PCH or BMC is detected as corrupted, this will trigger a recovery operation, i.e., completely deleting the valid backup and restoring from the latest Gold recovery area. Here, CVConfigure Verification is used for configuration verification.
[0078] CR Configure recovery.
[0079] (2) Once these safety operations in T-1 mode are successfully completed, the system continues to boot normally.
[0080] After the system continues to boot normally, the PCH and BMC start. Next, BMC configuration verification is performed. A specific area is defined in the BMC Flash to store the expected configuration information, such as component model and quantity, firmware, and driver. After the BMC powers on, the files in this Flash are copied out. After the BMC is successfully activated, the actual configuration information is collected. This information is compared with the expected requirements. If there are discrepancies, for recoverable items, the component library server is connected to restore the configuration, such as flashing the component firmware or updating the driver version. For unrecoverable items, such as hard drive model or quantity not matching expectations, a warning is issued through the BMC.
[0081] like Figure 2 As shown, this embodiment of the invention provides a configuration verification and recovery device based on PFR, including a expected requirement configuration acquisition module, a collection module, a comparison module, a configuration recovery module, and an alarm module;
[0082] The expected requirements configuration acquisition module is used to copy the expected requirements configuration JSON file from the firmware flash area after PFR firmware verification is completed.
[0083] The collection module is used to collect the actual configuration information of the current machine after firmware activation;
[0084] The comparison module is used to compare the collected actual configuration information with the configuration JSON file;
[0085] The configuration recovery module is used to configure and recover recoverable items with different comparison results;
[0086] The alarm module is used to output a warning for unrecoverable items.
[0087] In some embodiments, the device further includes an execution module and a firmware recovery module;
[0088] The execution module is used to boot the firmware for activation in normal mode after PFR firmware verification passes.
[0089] The expected requirements configuration acquisition module is used to copy the expected requirements configuration JSON file from the firmware valid area;
[0090] The firmware recovery module is used to remove erroneous firmware from the valid area if the verification fails, and to copy the firmware from the recovery area to the valid area to trigger the execution module.
[0091] The device also includes a firmware verification module;
[0092] The execution module is also used to start the server according to the set pre-boot mode;
[0093] The firmware verification module is used to digitally verify the server firmware after the server starts up according to the set pre-boot mode. If the verification passes, the module outputs information to the execution module to guide the firmware to power on and activate in normal mode; if the verification fails, the module outputs information to the firmware recovery module.
[0094] It should be noted that the configuration recovery module includes a configuration item acquisition unit and a configuration recovery unit;
[0095] The configuration item retrieval unit is used to retrieve the items that differ between the actual configuration information and the configuration JSON file when the actual configuration information is different from the configuration JSON file.
[0096] The configuration recovery unit is used to obtain different configurable items by connecting to the component library server and obtaining the corresponding firmware configuration information online; the online obtained configuration information is then used to replace the found recoverable items.
[0097] This invention also provides an electronic device, comprising: a processor, a communication interface, a memory, and a bus, wherein the processor, communication interface, and memory communicate with each other via the bus. The bus can be used for information transmission between the electronic device and sensors. The processor can call logical instructions in the memory to execute the following method: Step 1: After PFR firmware verification is completed, the expected configuration JSON file is copied from the firmware flash area; Step 2: After firmware activation, the actual configuration information of the current machine is collected; Step 3: The collected actual configuration information is compared with the configuration JSON file; Step 4: Recoverable items with different comparison results are restored, and unrecoverable items are output as warnings.
[0098] Furthermore, the logical instructions in the aforementioned memory can be implemented as software functional units and sold or used as independent products, and can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0099] This invention provides a non-transitory computer-readable storage medium storing computer instructions that cause a computer to execute the method provided in the above-described method embodiments, including, for example: S1: starting the server according to a set pre-boot mode; S2: performing digital verification on the server firmware; if the PFR firmware verification passes, proceed to step S3; if the verification fails, proceed to step S11; S3: booting the firmware into power-on activation mode in normal mode; S4: copying the expected configuration JSON file from the firmware's valid area; S5: collecting the actual configuration information of the current machine; S6: comparing the collected actual configuration information with the configuration JSON file; if the actual configuration information differs from the configuration JSON file, proceed to step S7; otherwise, end; S7: obtaining items that differ between the actual configuration and the configuration JSON file; S8: obtaining different configurable items and connecting to the component library server to obtain the corresponding firmware configuration information online; S9: replacing the found recoverable items with the online obtained configuration information; S10: outputting an alarm for unrecoverable items; S11: removing erroneous firmware from the valid area and copying the firmware from the recovery area to the valid area; proceeding to step S3.
[0100] Although the present invention has been described in detail with reference to the accompanying drawings and preferred embodiments, the invention is not limited thereto. Various equivalent modifications or substitutions can be made to the embodiments of the invention by those skilled in the art without departing from the spirit and essence of the invention, and such modifications or substitutions should all be within the scope of the invention. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the invention should also be covered within the protection scope of the invention. Therefore, the protection scope of the invention should be determined by the scope of the claims.
Claims
1. A method for configuration verification and recovery based on PFR, characterized in that, Includes the following steps: After the PFR firmware verification is completed, the required configuration JSON file is copied out from the firmware flash area; After firmware activation, collect the actual configuration information of the current machine; Compare the collected actual configuration information with the configuration JSON file; Recoverable items with different comparison results will be configured for recovery, while unrecoverable items will be output as a warning. The steps involved in copying the required configuration JSON file from the firmware flash area after PFR firmware verification include: PFR firmware verification passed. Boot the firmware into normal mode and power on to activate. Copy the required configuration JSON file from the firmware's valid area; If the verification fails, remove the erroneous firmware from the valid area and copy the firmware from the recovery area to the valid area; Execution steps: Boot the firmware and power on to activate it in normal mode; Before copying the required configuration JSON file from the firmware flash area after PFR firmware verification is complete, the following steps are included: The server is started according to the pre-boot mode. In this boot mode, only the CPU is active, and all other devices that may interfere with the boot path are in a reset state. Perform digital verification on the server firmware; Execution steps: After the PFR firmware verification is completed, if the verification passes, boot the firmware into power-on mode to activate it in normal mode. The steps for configuring and restoring recoverable items that differ in the comparison results, and outputting warnings for unrecoverable items, include: When the actual configuration information differs from the configuration JSON file, retrieve the items that differ between the actual configuration and the configuration JSON file. Connect to the component library server to obtain different configurable items and retrieve the corresponding firmware configuration information online. Replace the found recoverable items with the configuration information obtained online; Output an alert for items that cannot be recovered.
2. A device for configuration verification and recovery based on PFR, characterized in that, It includes a module for obtaining expected requirements configuration, a collection module, a comparison module, a configuration recovery module, and an alarm module; The expected requirements configuration acquisition module is used to copy the expected requirements configuration JSON file from the firmware flash area after PFR firmware verification is completed. The collection module is used to collect the actual configuration information of the current machine after firmware activation; The comparison module is used to compare the collected actual configuration information with the configuration JSON file; The configuration recovery module is used to configure and recover recoverable items with different comparison results; The alarm module is used to output a warning for unrecoverable items; The device also includes an execution module and a firmware recovery module; The execution module is used to boot the firmware for activation in normal mode after PFR firmware verification passes. The expected requirements configuration acquisition module is used to copy the expected requirements configuration JSON file from the firmware valid area; The firmware recovery module is used to remove erroneous firmware from the valid area if the verification fails, and to copy the firmware from the recovery area to the valid area to trigger the execution module. The device also includes a firmware verification module; The execution module is also used to start the server according to the set pre-boot mode, in which only the CPU is active and all other devices that may interfere with the boot path are in a reset state. The firmware verification module is used to digitally verify the server firmware after the server starts up according to the set pre-boot mode. If the verification passes, the module outputs information to the execution module to guide the firmware to power on and activate in normal mode; if the verification fails, the module outputs information to the firmware recovery module. The configuration recovery module includes a configuration item acquisition unit and a configuration recovery unit; The configuration item retrieval unit is used to retrieve the items that differ between the actual configuration information and the configuration JSON file when the actual configuration information is different from the configuration JSON file. The configuration recovery unit is used to obtain different configurable items by connecting to the component library server and obtaining the corresponding firmware configuration information online; the online obtained configuration information is then used to replace the found recoverable items.
3. An electronic device, characterized in that, The electronic device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores computer program instructions that can be executed by at least one processor to enable the at least one processor to perform the PFR-based configuration verification and recovery method as described in claim 1.
4. A non-transitory computer-readable storage medium, characterized in that, The non-transitory computer-readable storage medium stores computer instructions that cause the computer to perform the configuration verification and recovery method based on PFR as described in claim 1.
Citation Information
Patent Citations
PFR-based firmware upgrading method, system and equipment and storage medium
CN114579982A
Automatic recovery method and device for tampered firmware and storage medium
CN113806811A
BIOS firmware recovery method and system based on PFR, terminal and storage medium
CN114116305A