CN114579971A - Starting method of safety control module and related device - Google Patents

Starting method of safety control module and related device Download PDF

Info

Publication number
CN114579971A
CN114579971A CN202111629799.7A CN202111629799A CN114579971A CN 114579971 A CN114579971 A CN 114579971A CN 202111629799 A CN202111629799 A CN 202111629799A CN 114579971 A CN114579971 A CN 114579971A
Authority
CN
China
Prior art keywords
verification
memory
starting
data
successful
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
CN202111629799.7A
Other languages
Chinese (zh)
Inventor
段雪珂
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Inspur Intelligent Technology Co Ltd
Original Assignee
Suzhou Inspur Intelligent Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Suzhou Inspur Intelligent Technology Co Ltd filed Critical Suzhou Inspur Intelligent Technology Co Ltd
Priority to CN202111629799.7A priority Critical patent/CN114579971A/en
Publication of CN114579971A publication Critical patent/CN114579971A/en
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/57Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
    • G06F21/572Secure firmware programming, e.g. of basic input output system [BIOS]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/57Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
    • G06F21/575Secure boot
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44505Configuring for program initiating, e.g. using registry, configuration files

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The application discloses a starting method of a safety control module, which comprises the following steps: the platform firmware elastic device enters a starting state; when the starting is successful, verifying the memory of the substrate controller and the memory of the basic input and output system; when the verification is successful, entering a normal starting mode; and when the verification fails, restoring the memory data failed in the verification until the verification is successful and entering a normal starting mode. RoT is realized in the DC-SCM practical application, the safe starting operation is realized, and the safety of the module is improved. The application also discloses a starting device of the safety control module, a computing module and a computer readable storage medium, and the safety control module has the beneficial effects.

Description

Starting method of safety control module and related device
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for starting a security control module, a computing module, and a computer-readable storage medium.
Background
With the continuous development of information technology, more and more controllers are present in the server in order to maintain the operational reliability of the server. The BMC (Baseboard Management Controller) is a small operating system independent of the server system, and performs operations such as remote Management, deployment, and restart in the server system.
In the related art, only the node BMC that receives the Root of Trust (Root of Trust) from the BMC to implement protection and repair of Flash (memory) is defined in the existing DC-SCM2.0(data center-Ready Secure Control Module) specification, and there is no specific implementation manner of the Root of Trust. That is, RoT is only a logical concept, and no specific RoT implementation needs to be given in the DC-SCM practical application.
Therefore, how to apply the secure operation of the root of trust in the DC-SCM is a key issue that those skilled in the art are interested in.
Disclosure of Invention
The application aims to provide a starting method, a starting device, a computing module and a computer readable storage medium of a safety control module, so as to realize the safety starting operation in the safety control module and improve the safety of the module.
In order to solve the above technical problem, the present application provides a method for starting a safety control module, including:
the platform firmware elastic device enters a starting state;
when the starting is successful, verifying the memory of the substrate controller and the memory of the basic input and output system;
when the verification is successful, entering a normal starting mode;
and when the verification fails, restoring the memory data failed in the verification until the verification is successful and entering a normal starting mode.
Optionally, when the verification fails, recovering the memory data that fails to be verified until the verification succeeds and entering a normal start mode, including:
when the verification fails, the platform firmware elastic device erases the memory data which fails in the verification;
and recovering the memory data based on the mirror image file until the verification is successful and entering a normal starting mode.
Optionally, the method further includes:
the platform firmware elastic device monitors and filters the data of the bus to obtain data in accordance with the white list rule;
and writing the data meeting the white list rule into a corresponding memory.
Optionally, the platform firmware elastic device enters a start state, including:
after the equipment is powered on, judging whether the equipment is in a pre-starting state or not;
and if so, starting the platform firmware elastic device.
Optionally, the method further includes:
and when the verification fails, performing verification failure data recording processing to obtain log data.
Optionally, verifying the memory of the substrate controller and the memory of the bios includes:
and verifying the memory of the substrate controller and the memory of the basic input and output system based on a preset verification code.
Optionally, verifying the memory of the substrate controller and the memory of the bios includes:
and verifying the memory of the substrate controller and the memory of the basic input and output system based on the preset verification identification.
The application also provides a starting drive of safety control module group, includes:
the starting processing module is used for entering a starting state;
the data checking module is used for checking the memory of the substrate controller and the memory of the basic input and output system after the starting is successful;
the verification success processing module is used for entering a normal starting mode when verification is successful;
and the verification failure processing module is used for recovering the memory data which is failed in verification when the verification fails until the verification is successful and entering a normal starting mode.
The present application further provides a computing module, including:
a memory for storing a computer program;
a processor for implementing the steps of the startup method as described above when executing the computer program.
The present application also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the startup method as described above.
The application provides a starting method of a safety control module, which comprises the following steps: the platform firmware elastic device enters a starting state; when the starting is successful, verifying the memory of the substrate controller and the memory of the basic input and output system; when the verification is successful, entering a normal starting mode; and when the verification fails, restoring the memory data failed in the verification until the verification is successful and entering a normal starting mode.
After the platform firmware elastic device is started successfully, the memory of the substrate controller and the memory of the basic input and output system are checked, when the checking is successful, a normal starting mode is entered, when the checking is failed, the data of the memory failed in the checking are recovered until the checking is successful and the normal starting mode is entered, RoT is realized in the DC-SCM practical application, the safe starting operation is realized, and the safety of the module is improved.
The application also provides a starting device of the safety control module, a computing module and a computer readable storage medium, which have the beneficial effects, and are not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for starting a safety control module according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of an actuating device of a safety control module according to an embodiment of the present disclosure.
Detailed Description
The core of the application is to provide a starting method, a starting device, a computing module and a computer readable storage medium of a safety control module, so as to realize the safety starting operation in the safety control module and improve the safety of the module.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the related art, only the Flash protection and repair and the like are realized by connecting the BMC to the RoT in the existing DC-SCM2.0 specification, and a specific implementation mode of a trusted root is not provided. That is, RoT is only a logical concept, and no specific RoT implementation needs to be given in the DC-SCM practical application.
Therefore, the application provides a starting method of a safety control module, after the starting is successful, the storage of the substrate controller and the storage of the basic input and output system are checked through the platform firmware elastic device, when the checking is successful, a normal starting mode is entered, when the checking is failed, the data of the storage which is failed in the checking are recovered until the checking is successful and the normal starting mode is entered, RoT is realized in the DC-SCM practical application, the safety starting operation is realized, and the safety of the module is improved.
The following describes a starting method of a safety control module provided by the present application by using an embodiment.
Referring to fig. 1, fig. 1 is a flowchart illustrating a method for starting a safety control module according to an embodiment of the present disclosure.
In this embodiment, the method may include:
s101, enabling the platform firmware elastic device to enter a starting state;
this step is intended to bring the platform firmware spring into a start-up state. The Platform Firmware resilient device may be a PFR CPLD (Complex Programmable logic device) in a DC-SCM module based on PFR (Platform Firmware Resilience) technology.
Further, the step may include:
step 1, after equipment is powered on, judging whether the equipment is in a pre-starting state or not;
and 2, if so, starting the platform firmware elastic device.
It can be seen that the present alternative is primarily illustrative of how the platform firmware elastic means may be enabled. In the alternative, after the equipment is powered on, whether the equipment is in a pre-starting state or not is judged, and if yes, the platform firmware elastic device is started.
S102, after the starting is successful, verifying the memory of the substrate controller and the memory of the basic input and output system;
on the basis of S101, this step is intended to verify the memory of the substrate controller and the memory of the bios after the startup is successful.
Further, the step may include:
and verifying the memory of the substrate controller and the memory of the basic input and output system based on a preset verification code.
It can be seen that the present alternative is mainly illustrative of how the verification is performed. In this alternative, the memory of the substrate controller and the memory of the bios are verified based on a preset verification code.
Further, the step may include:
and verifying the memory of the substrate controller and the memory of the basic input and output system based on the preset verification identification.
It can be seen that the present alternative is mainly illustrative of how the verification is performed. In this alternative, the memory of the substrate controller and the memory of the bios are verified based on a preset verification flag.
S103, entering a normal starting mode when the verification is successful;
on the basis of S102, this step is intended to enter a normal startup mode when the verification is successful. I.e. to perform the subsequent normal start-up procedure.
And S104, when the verification fails, restoring the memory data which is failed to be verified until the verification is successful and entering a normal starting mode.
On the basis of S102, this step aims to recover, when the verification fails, the memory data that failed to be verified until the verification succeeds and a normal start mode is entered.
Further, the step may include:
step 1, when the verification fails, the platform firmware elastic device erases the memory data which fails in the verification;
and 2, restoring the data of the memory based on the mirror image file until the verification is successful and entering a normal starting mode.
It can be seen that the present alternative is primarily illustrative of how recovery may be performed. In the alternative, when the verification fails, the platform firmware elastic device erases the memory data which are failed in the verification, and the memory data are recovered based on the image file until the verification is successful and a normal starting mode is entered.
The embodiment may further include:
and when the verification fails, performing verification failure data recording processing to obtain log data.
It can be seen that the present alternative is primarily illustrative of log data that may also be available. In this alternative, when the verification fails, the data record processing of the verification failure is performed to obtain the log data.
The embodiment may further include:
step 1, a platform firmware elastic device monitors and filters data of a bus to obtain data meeting a white list rule;
and 2, writing the data meeting the white list rule into a corresponding memory.
It can be seen that the present alternative is primarily illustrative of how the white list rules may be used. In this alternative, the platform firmware elastic device performs monitoring processing and filtering processing on the data of the bus to obtain data meeting the white list rule, and writes the data meeting the white list rule into the corresponding memory.
In summary, in this embodiment, after the platform firmware elastic device is successfully started, the memory of the substrate controller and the memory of the bios are verified, and when the verification is successful, the normal start mode is entered, and when the verification is failed, the data of the memory that is failed to be verified are recovered until the verification is successful and the normal start mode is entered, so that RoT is realized in the DC-SCM practical application, a secure start operation is realized, and the security of the module is improved.
The following further describes a starting method of a safety control module provided in the present application by a specific embodiment.
First, a BMC (baseboard management controller) is a small operating system independent of a server system, and performs operations such as remote management, deployment, and reboot in the server system. With the development of the server field, in order to facilitate general software management, the need to separate the BMC management unit from the motherboard and perform BMC modularization is more and more urgent. Compared with the BMC management unit contained in the mainboard, the independent modularization of the BMC management unit has the following advantages: the module is open-source, and is convenient for various manufacturers to use; the application is flexible, and the device configuration and debugging are facilitated; the system can be easily upgraded to the latest BMC chip, is independent of a mainboard for updating and upgrading, and can be rapidly released to the market; the module interface is standardized, can be compatible across the platform, there are many kinds of computational engines to choose from; the design difficulty of the mainboard is reduced, and the use of the mainboard plate is reduced, so that the cost is reduced. In 2020, the open computing project organization formally releases a standard of a server management Module-DC-SCM (data-Ready Secure Control Module), that is, a DC-SCM 1.0 standard. In 2021, the specifications for DC-SCM2.0 were also proposed and are now mature. The DC-SCM module conforms to the trend of BMC modularization, leads the development of BMC modularization and is most likely to be widely applied to various server manufacturers.
The DC-SCM2.0 specification defines, among other things, the interface between the BMC subsystem and an OCP (open computing project) hardware platform (e.g., a network or computing motherboard). The DC-SCM mainly includes a BMC chip, a DRAM (Dynamic Random Access Memory) Memory particle, a CPLD, a RoT, a BMC Flash, a BIOS Flash, a TPM (trusted Platform Module), a PHY (Physical Layer) chip, and the like. The Interface where the DC-SCM module is connected with the motherboard is called DC-SCI (data-ready Secure Control Interface).
Wherein, RoT is a logic concept, which has important meaning in the aspects of system security and platform asset protection, and the realized functions include: 1. the BMC Flash and the BIOS Flash are prevented from being maliciously tampered; 2. if Flash is tampered with, RoT can be repaired. The entity for realizing the RoT function may be the BMC itself, but this occupies interface resources of the BMC and poses a threat to other connections. In the specification of the DC-SCM, it is specified that a Serial Peripheral Interface (SPI) signal is received from the BMC to the RoT entity, and then the BMC Flash and the BIOS Flash are attached to the RoT entity. However, no entity for RoT is specified in the specification of DC-SCM.
Based on the above description, the present embodiment provides a DC-SCM module based on PFR technology, which is consistent with the standard DC-SCM size. In the existing DC-SCM module scheme, the function of RoT is realized by using PFR technology, so that the protection of platform assets, the detection of malicious or wrong behaviors such as damaged firmware and the like and the recovery of platform firmware to a good state are realized.
Wherein, using a CPLD as the entity of RoT is also the core of PFR technology. The PFR first defines a special pre-start state T-1, and after power up, the system first enters the T-1 state. At this time, only the PFR CPLD is enabled, and the other firmware (with the possible enable interface) is in a reset state. After the starting is successful, the PFR CPLD firstly checks the BMC Flash and the BIOS Flash. If the verification is not successful, the PFR CPLD erases the Flash part failed in the verification, and then the Flash data is recovered by using the image file until the verification is successful. And entering a normal starting mode after the verification is successful. And then, the PFR CPLD monitors and filters SMbus (System Management Bus) and SPI data, and the data which do not conform to the white list rule (set by a developer) are prevented from being written into Flash, so that the data input of the Flash is prevented from being maliciously changed.
It can be seen that in this embodiment, after the platform firmware elastic device is successfully started, the memory of the substrate controller and the memory of the bios are verified, when the verification is successful, the normal start mode is entered, and when the verification is failed, the data of the memory that has failed to be verified are recovered until the verification is successful and the normal start mode is entered, so that RoT is realized in the DC-SCM practical application, a secure start operation is realized, and the security of the module is improved.
The following describes a starting device of a safety control module provided in an embodiment of the present application, and the starting device of the safety control module described below and the starting method of the safety control module described above may be referred to correspondingly.
Referring to fig. 2, fig. 2 is a schematic structural diagram of an activating device of a safety control module according to an embodiment of the present disclosure.
In this embodiment, the apparatus may include:
a start processing module 100, configured to enter a start state;
the data verification module 200 is used for verifying the memory of the substrate controller and the memory of the basic input and output system after the starting is successful;
a verification success processing module 300, configured to enter a normal start mode when verification is successful;
and the verification failure processing module 400 is configured to, when the verification fails, recover the memory data that has failed to be verified until the verification succeeds and enter a normal start mode.
Optionally, the verification failure processing module 400 is specifically configured to, when the verification fails, erase, by the platform firmware elastic apparatus, the memory data that fails to be verified; and recovering the memory data based on the mirror image file until the verification is successful and entering a normal starting mode.
Optionally, the apparatus may further include:
the data filtering module is used for monitoring and filtering the data of the bus by the platform firmware elastic device to obtain data meeting the white list rule; and writing the data meeting the white list rule into a corresponding memory.
Optionally, the start processing module 100 is specifically configured to determine whether the device is in a pre-start state after the device is powered on; and if so, starting the platform firmware elastic device.
Optionally, the apparatus may further include:
and the log data recording module is used for recording and processing the verification failure data when the verification fails to obtain the log data.
Optionally, the data verification module 200 is specifically configured to verify a memory of the substrate controller and a memory of the bios based on a preset verification code.
Optionally, the data verification module 200 is specifically configured to verify a memory of the substrate controller and a memory of the bios based on a preset verification identifier.
The embodiment of the present application further provides a computing module, including:
a memory for storing a computer program;
a processor for implementing the steps of the startup method as described in the above embodiments when executing the computer program.
The present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the boot method according to the above embodiments.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The foregoing details describe a starting method, a starting apparatus, a computing module and a computer-readable storage medium for a security control module provided in the present application. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.

Claims (10)

1. A starting method of a safety control module is characterized by comprising the following steps:
the platform firmware elastic device enters a starting state;
when the starting is successful, verifying the memory of the substrate controller and the memory of the basic input and output system;
when the verification is successful, entering a normal starting mode;
and when the verification fails, restoring the memory data failed in the verification until the verification is successful and entering a normal starting mode.
2. The boot method of claim 1, wherein when the verification fails, restoring the memory data that failed the verification until the verification succeeds and entering a normal boot mode comprises:
when the verification fails, the platform firmware elastic device erases the memory data which fails in the verification;
and recovering the memory data based on the mirror image file until the verification is successful and entering a normal starting mode.
3. The startup method according to claim 1, further comprising:
the platform firmware elastic device monitors and filters the data of the bus to obtain data in accordance with the white list rule;
and writing the data meeting the white list rule into a corresponding memory.
4. The boot method of claim 1, wherein the platform firmware resilient means entering the boot state comprises:
after the equipment is powered on, judging whether the equipment is in a pre-starting state or not;
and if so, starting the platform firmware elastic device.
5. The startup method according to claim 1, further comprising:
and when the verification fails, performing verification failure data recording processing to obtain log data.
6. The method of claim 1, wherein verifying the memory of the substrate controller and the memory of the bios comprises:
and verifying the memory of the substrate controller and the memory of the basic input and output system based on a preset verification code.
7. The method of claim 1, wherein verifying the memory of the substrate controller and the memory of the bios comprises:
and verifying the memory of the substrate controller and the memory of the basic input and output system based on the preset verification identification.
8. A starting device of a safety control module is characterized by comprising:
the starting processing module is used for entering a starting state;
the data checking module is used for checking the memory of the substrate controller and the memory of the basic input and output system after the starting is successful;
the verification success processing module is used for entering a normal starting mode when verification is successful;
and the verification failure processing module is used for recovering the memory data which is failed in verification when the verification fails until the verification is successful and entering a normal starting mode.
9. A computing module, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the startup method according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the startup method according to any one of claims 1 to 7.
CN202111629799.7A 2021-12-28 2021-12-28 Starting method of safety control module and related device Withdrawn CN114579971A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111629799.7A CN114579971A (en) 2021-12-28 2021-12-28 Starting method of safety control module and related device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111629799.7A CN114579971A (en) 2021-12-28 2021-12-28 Starting method of safety control module and related device

Publications (1)

Publication Number Publication Date
CN114579971A true CN114579971A (en) 2022-06-03

Family

ID=81772291

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111629799.7A Withdrawn CN114579971A (en) 2021-12-28 2021-12-28 Starting method of safety control module and related device

Country Status (1)

Country Link
CN (1) CN114579971A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024113683A1 (en) * 2022-11-29 2024-06-06 苏州元脑智能科技有限公司 Flash device switching method and apparatus, computer device, and storage medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024113683A1 (en) * 2022-11-29 2024-06-06 苏州元脑智能科技有限公司 Flash device switching method and apparatus, computer device, and storage medium

Similar Documents

Publication Publication Date Title
US7734945B1 (en) Automated recovery of unbootable systems
CN109670319B (en) Server flash safety management method and system thereof
US9703635B2 (en) Method, computer program, and computer for restoring set of variables
CN106020865A (en) System upgrading method and device
CN103718165A (en) BIOS flash attack protection and notification
CN111143132B (en) BIOS recovery method, device, equipment and readable storage medium
CN109582332B (en) System upgrading method and device for Internet camera
CN111625295A (en) Embedded system starting method, device, equipment and storage medium
CN110990124A (en) Cloud host recovery method and device
CN114579971A (en) Starting method of safety control module and related device
CN113806811B (en) Automatic recovery method and device for tampered firmware and storage medium
CN111198832A (en) Processing method and electronic equipment
CN112579179A (en) Partition mounting method of embedded system
CN111090443A (en) Method, equipment and storage medium for guaranteeing safe upgrade of linux system
CN115827069A (en) Starting control method, system and device for server mainboard
CN113094107B (en) Data protection method, device, equipment and computer storage medium
CN111783162B (en) Data protection implementation method and device and computer equipment
CN114153503A (en) BIOS control method, device and medium
CN113297010A (en) Firmware recovery method, device and system based on system on chip and storage medium
CN112363749A (en) Safe starting and upgrading method of MIPS architecture system
CN111258805B (en) Hard disk state monitoring method and device for server and computer device
CN115904516A (en) Trust root based baseboard management controller starting method and related components thereof
TWI789142B (en) Controller, computing device, bios recovery and backup method
CN113867812B (en) Method, system, equipment and medium for BMC to acquire link information
CN117675576A (en) Method and device for upgrading server firmware, server and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
WW01 Invention patent application withdrawn after publication
WW01 Invention patent application withdrawn after publication

Application publication date: 20220603