CN116893939A - Firmware testing method, system, storage medium and equipment - Google Patents
Firmware testing method, system, storage medium and equipment Download PDFInfo
- Publication number
- CN116893939A CN116893939A CN202310980172.9A CN202310980172A CN116893939A CN 116893939 A CN116893939 A CN 116893939A CN 202310980172 A CN202310980172 A CN 202310980172A CN 116893939 A CN116893939 A CN 116893939A
- Authority
- CN
- China
- Prior art keywords
- firmware
- trusted
- recording function
- trusted firmware
- response
- 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.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 70
- 238000000034 method Methods 0.000 claims abstract description 43
- 238000012795 verification Methods 0.000 claims abstract description 32
- 230000004044 response Effects 0.000 claims abstract description 22
- 230000008569 process Effects 0.000 claims abstract description 19
- 230000006870 function Effects 0.000 claims description 46
- 238000004590 computer program Methods 0.000 claims description 8
- 230000003068 static effect Effects 0.000 claims description 3
- 230000007246 mechanism Effects 0.000 description 10
- 238000011156 evaluation Methods 0.000 description 9
- 230000002159 abnormal effect Effects 0.000 description 8
- 238000011084 recovery Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 238000010998 test method Methods 0.000 description 6
- 238000013112 stability test Methods 0.000 description 4
- 238000010276 construction Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003449 preventive effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2247—Verification or detection of system hardware configuration
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2273—Test methods
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2289—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing by configuration test
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a firmware testing method, a system, a storage medium and equipment, wherein the method comprises the following steps: constructing a firmware image, uploading the firmware image to the BMC through an out-of-band management interface, and judging whether the corresponding firmware is a trusted firmware or not by the BMC based on the firmware image; responding to the firmware as the trusted firmware, refreshing the trusted firmware to the system, and checking the trusted firmware in the refreshing process; in response to the verification passing, restarting the system, and verifying whether the recording function is normal in the restarting process; responding to normal recording function, successfully loading and starting the trusted firmware, and judging whether loading and starting time is within a preset time range or not; responding to the fact that the system is restarted after the core data in the trusted firmware are tampered within a preset time range; and in response to continued restart success, determining that the trusted firmware is stable in boot-up. The application improves the testing efficiency and the testing accuracy and the comprehensive coverage.
Description
Technical Field
The present application relates to the field of firmware technologies, and in particular, to a firmware testing method, system, storage medium, and device.
Background
The server serving as a key information infrastructure has the characteristics of large existing quantity, high potential safety hazard, frequent safety problems and the like, the server has very limited preventive capability on internal attacks in a starting stage, the reliability of the firmware serving as a key core for earliest mastering of system authorities is a key core, the security test on the reliability of the firmware and the like is important, and meanwhile, the requirements on the security of the firmware are also included in the industry standards such as the server security technical requirements, the evaluation standards and the like, wherein the integrity and the authenticity of the firmware are required to be checked in support of firmware design, the refreshing, starting and even recovery processes after damage of the firmware are covered, and the test on the trusted firmware is naturally more comprehensive and accurate.
The current test of the trusted firmware covers the test of the aspects of trusted firmware refreshing, starting integrity check, flash memory reading check, authenticity check and the like, is mainly based on functional scenes, is low in efficiency, only the final result is checked, the comprehensiveness of the test check is insufficient, the problem cannot be found timely and early, meanwhile, the evaluation of the starting performance of the trusted firmware is lacked, the stability of the trusted firmware checking mechanism is lacked, the abnormal scene is mainly tested, and the accuracy is low; the problem of insufficient test coverage exists due to the lack of sufficient test for abnormal recovery, the lack of evaluation for the influence of starting performance, the lack of reliability mechanism stability test; in addition, the image construction efficiency is low, the development is limited to the modification and recompilation of codes, the construction of test scenes is limited, the universality is not achieved, and the efficiency is low.
Disclosure of Invention
Therefore, the present application is directed to a firmware testing method, system, storage medium and device, which are used for solving the problems of insufficient coverage of boot performance, insufficient mechanism stability verification and low testing efficiency in the prior art.
Based on the above object, the present application provides a firmware testing method, comprising the following steps:
constructing a firmware image, uploading the firmware image to the BMC through an out-of-band management interface, and judging whether the corresponding firmware is a trusted firmware or not by the BMC based on the firmware image;
responding to the firmware as the trusted firmware, refreshing the trusted firmware to the system, and checking the trusted firmware in the refreshing process;
in response to the verification passing, restarting the system, and verifying whether the recording function is normal in the restarting process;
responding to normal recording function, successfully loading and starting the trusted firmware, and judging whether loading and starting time is within a preset time range or not;
responding to the fact that the system is restarted after the core data in the trusted firmware are tampered within a preset time range;
and in response to continued restart success, determining that the trusted firmware is stable in boot-up.
In some embodiments, the method further comprises:
responding to the fact that the firmware is non-trusted firmware or the verification of the trusted firmware is not passed, restarting the system, and verifying whether the recording function is normal;
and in response to the normal recording function, determining that the verification function and the recording function of the untrusted firmware meet preset requirements.
In some embodiments, the method further comprises:
and uploading the new firmware image to the BMC to perform corresponding new firmware test in response to the verification function and the recording function of the untrusted firmware meeting preset requirements.
In some embodiments, the method further comprises:
and responding to the loading start time exceeding the preset range, determining that the loading start time of the trusted firmware does not meet the preset requirement, and generating a related report.
In some embodiments, the record content corresponding to the record function includes a log type, a serial port record, a CPU state, and a memory state.
In some embodiments, the system is a BIOS or BMC.
In some embodiments, the core data is data of a static area of a kernel area in the flash memory.
In another aspect of the present application, there is also provided a firmware test system, including:
the trusted judgment module is configured to construct a firmware image, upload the firmware image to the BMC through the out-of-band management interface, and judge whether the corresponding firmware is trusted firmware or not based on the firmware image by the BMC;
the refreshing verification module is configured to respond to the fact that the firmware is the trusted firmware, refresh the trusted firmware to the system, and verify the trusted firmware in the refreshing process;
the restarting module is configured to restart the system in response to the passing of the verification and verify whether the recording function is normal in the restarting process;
the time judging module is configured to respond to the normal recording function, the loading and starting of the trusted firmware are successful, and whether the loading and starting time is within a preset time range or not is judged;
a continuous restarting module configured to restart the system continuously after tampering with the core data in the trusted firmware in response to the fact that the core data is within a preset time range; and
and the determining module is configured to determine that the trusted firmware is stable in starting in response to the success of the continuous restarting.
In yet another aspect of the present application, there is also provided a computer readable storage medium storing computer program instructions which, when executed by a processor, implement the above-described method.
In yet another aspect of the present application, there is also provided a computer device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, performs the above method.
The application has at least the following beneficial technical effects:
according to the firmware testing method, the integrity test of the integrity, the legality and the authenticity safety check of the trusted firmware is automatically finished through refreshing, starting and loading and abnormal recovery processes, and the automatic mirror image structure, the performance influence evaluation, the stability test and the abnormal recovery test are increased, so that the comprehensive test of the trusted firmware is realized, and the high level of the trusted firmware test is achieved; the boot performance influence evaluation and the boot stability verification of the trusted verification mechanism are added in the trusted firmware test, so that the coverage comprehensiveness is effectively perfected, deeper problems can be identified, the trusted mechanism is ensured not to influence the core function, and the test accuracy is greatly improved; and the testing efficiency is improved, and the labor cost is greatly reduced.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are necessary for the description of the embodiments or the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application and that other embodiments may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a firmware testing method according to an embodiment of the present application;
FIG. 2 is a flowchart of a firmware testing method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a firmware testing system according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a computer readable storage medium implementing a firmware test method according to an embodiment of the present application;
fig. 5 is a schematic hardware structure of a computer device for executing a firmware test method according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the following embodiments of the present application will be described in further detail with reference to the accompanying drawings.
It should be noted that, in the embodiments of the present application, all the expressions "first" and "second" are used to distinguish two non-identical entities with the same name or non-identical parameters, and it is noted that the "first" and "second" are only used for convenience of expression, and should not be construed as limiting the embodiments of the present application. Furthermore, the terms "comprise" and "have," and any variations thereof, are intended to cover a non-exclusive inclusion, such as a process, method, system, article, or other step or unit that comprises a list of steps or units.
Based on the above objects, a first aspect of the embodiments of the present application proposes an embodiment of a firmware testing method. Fig. 1 is a schematic diagram of an embodiment of a firmware testing method provided by the present application. As shown in fig. 1, the embodiment of the present application includes the following steps:
s10, constructing a firmware image, uploading the firmware image to the BMC through an out-of-band management interface, and judging whether the corresponding firmware is a trusted firmware or not by the BMC based on the firmware image;
step S20, responding to the firmware as the trusted firmware, refreshing the trusted firmware to the system, and checking the trusted firmware in the refreshing process;
step S30, restarting the system in response to the verification, and verifying whether the recording function is normal in the restarting process;
step S40, responding to normal recording function, successfully loading and starting the trusted firmware, and judging whether loading and starting time is within a preset time range;
step S50, responding to the fact that the system is restarted after the core data in the trusted firmware are tampered within a preset time range;
and step S60, responding to success of continuous restarting, and determining that the trusted firmware is started stably.
According to the firmware testing method, the integrity test of the integrity, the legality and the authenticity safety check of the trusted firmware is automatically completed through refreshing, starting loading and abnormal recovery processes, the automatic mirror image structure, the performance influence evaluation, the stability test and the abnormal recovery test are increased, the comprehensive test of the trusted firmware is realized, and the high level of the trusted firmware test is achieved; the boot performance influence evaluation and the boot stability verification of the trusted verification mechanism are added in the trusted firmware test, so that the coverage comprehensiveness is effectively perfected, deeper problems can be identified, the trusted mechanism is ensured not to influence the core function, and the test accuracy is greatly improved; and the testing efficiency is improved, and the labor cost is greatly reduced.
In some embodiments, the method further comprises: responding to the fact that the firmware is non-trusted firmware or the verification of the trusted firmware is not passed, restarting the system, and verifying whether the recording function is normal; and in response to the normal recording function, determining that the verification function and the recording function of the untrusted firmware meet preset requirements.
In some embodiments, the method further comprises: in response to the verification function and the record function of the untrusted firmware meeting preset requirements, the new firmware image is uploaded to the BMC (Baseboard Management Controller ) for a corresponding new firmware test.
In the above embodiment, after determining that the verification function and the recording function of the untrusted firmware meet the preset requirements, the new firmware image may be uploaded to perform a new firmware test, and subsequently after testing the verification function and the recording function of the new firmware, the new firmware image may smoothly pass through, so that the subsequent procedure is prejudged in advance, and the test time is saved.
In some embodiments, the method further comprises: and responding to the loading start time exceeding the preset range, determining that the loading start time of the trusted firmware does not meet the preset requirement, and generating a related report.
In some embodiments, the record content corresponding to the record function includes log type, serial port record, CPU (Central Process Unit, central processing unit) status, and memory status.
In some embodiments, the system is a BIOS (Basic Input Output System ) or BMC.
In some embodiments, the core data is data of a static area of a kernel area in the flash memory.
In this embodiment, the system is restarted to determine the starting stability of the trusted firmware by tampering with the core data in the trusted firmware, which is equivalent to testing the stability of the trusted firmware after being invaded from outside, so that the starting stability of the trusted firmware can be determined more comprehensively and fully.
Fig. 2 is a flowchart of a firmware testing method according to an embodiment of the application. As shown in fig. 2, in this embodiment, the mirror image is automatically constructed, the refreshing script is scheduled to be refreshed, the refreshing process, the starting process and the restored log (and the restored log) and result are detected by the automatic script, the stability and the starting time are repeatedly restarted, the complete test of the function and the stability of the trusted firmware is completed, a test report is given, and the flow is as follows:
the script firstly writes or falsifies data into a specific image address such as a kernel area automatically through a command or a binary file editing tool, completes the construction of an illegal image according to the requirement of a test scene, subsequently dispatches a restful (Representational State Transfer, a design style and a development mode of a network application program) script to enter an automatic refreshing process, firstly tests whether the checking function of the integrity and the legality of the image is ok, wherein the checking function comprises checking whether the illegal image can be checked out and corresponding records are made, and meanwhile, the illegal image is verified, after the illegal image is checked, the refreshing of the legal image is not influenced, whether the legal image verification can pass through the checking and gives a prompt of successful checking, the checking of the refreshing and starting up complete process is verified, the starting time is judged to judge whether the starting performance is influenced, the result is automatically judged, a loop test is carried out after the single verification, the stability and the robustness verification mechanism is verified, the script loop is automatically completed and a verification report is given through setting a test standard, and the complete verification is completed.
In a second aspect of the embodiment of the present application, a firmware test system is also provided. FIG. 3 is a schematic diagram of an embodiment of a firmware test system provided by the present application. As shown in fig. 3, a firmware test system includes: the trusted judgment module 10 is configured to construct a firmware image, upload the firmware image to the BMC through the out-of-band management interface, and judge whether the corresponding firmware is trusted firmware or not based on the firmware image by the BMC; the refreshing verification module 20 is configured to respond to the firmware being the trusted firmware, refresh the trusted firmware to the system, and verify the trusted firmware in the refreshing process; a restarting module 30 configured to restart the system in response to the verification passing, and verify whether the recording function is normal during the restarting; a time judging module 40 configured to respond to the normal recording function, successfully load and start the trusted firmware, and judge whether the load start time is within a preset time range; a continuing restart module 50 configured to continue restarting the system after tampering with the core data in the trusted firmware in response to a predetermined time frame; and a determination module 60 configured to determine that the trusted firmware is bootable stable in response to continued restart success.
According to the firmware testing system provided by the embodiment of the application, the integrity test of the integrity, the legality and the authenticity safety check of the trusted firmware is automatically completed through refreshing, starting loading and abnormal recovery processes, the automatic mirror image structure, the performance influence evaluation, the stability test and the abnormal recovery test are increased, the comprehensive test of the trusted firmware is realized, and the high level of the trusted firmware test is achieved; the boot performance influence evaluation and the boot stability verification of the trusted verification mechanism are added in the trusted firmware test, so that the coverage comprehensiveness is effectively perfected, deeper problems can be identified, the trusted mechanism is ensured not to influence the core function, and the test accuracy is greatly improved; and the testing efficiency is improved, and the labor cost is greatly reduced.
In a third aspect of the embodiment of the present application, a computer readable storage medium is provided, and fig. 4 is a schematic diagram of a computer readable storage medium for implementing a firmware testing method according to an embodiment of the present application. As shown in fig. 4, the computer-readable storage medium 3 stores computer program instructions 31. The computer program instructions 31 when executed by a processor implement the method of any of the embodiments described above.
It should be understood that all of the embodiments, features and advantages set forth above with respect to the firmware testing method according to the present application apply equally to the firmware testing system and storage medium according to the present application, without conflicting therewith.
In a fourth aspect of the embodiment of the present application, there is also provided a computer device, including a memory 402 and a processor 401 as shown in fig. 5, where the memory 402 stores a computer program, and the computer program is executed by the processor 401 to implement the method of any one of the embodiments above.
Fig. 5 is a schematic hardware structure of an embodiment of a computer device for executing a firmware test method according to the present application. Taking the example of a computer device as shown in fig. 5, a processor 401 and a memory 402 are included in the computer device, and may further include: an input device 403 and an output device 404. The processor 401, memory 402, input device 403, and output device 404 may be connected by a bus or otherwise, for example in fig. 5. Input device 403 may receive entered numeric or character information and generate key signal inputs related to user settings and function control of the firmware test system. The output 404 may include a display device such as a display screen.
The memory 402 is used as a non-volatile computer readable storage medium for storing non-volatile software programs, non-volatile computer executable programs, and modules, such as program instructions/modules corresponding to the firmware test method in the embodiment of the present application. Memory 402 may include a storage program area that may store an operating system, at least one application program required for functionality, and a storage data area; the storage data area may store data created by use of the firmware test method, and the like. In addition, memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 402 may optionally include memory located remotely from processor 401, which may be connected to the local module via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The processor 401 executes various functional applications of the server and data processing, that is, implements the firmware test method of the above-described method embodiment, by running nonvolatile software programs, instructions, and modules stored in the memory 402.
Finally, it should be noted that the computer-readable storage media (e.g., memory) herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. By way of example, and not limitation, nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM), which acts as external cache memory. By way of example, and not limitation, RAM may be available in a variety of forms such as synchronous RAM (DRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The storage devices of the disclosed aspects are intended to comprise, without being limited to, these and other suitable types of memory.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. 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 disclosure.
The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with the following components designed to perform the functions herein: a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP and/or any other such configuration.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that as used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items. The foregoing embodiment of the present application has been disclosed with reference to the number of embodiments for the purpose of description only, and does not represent the advantages or disadvantages of the embodiments.
Those of ordinary skill in the art will appreciate that: the above discussion of any embodiment is merely exemplary and is not intended to imply that the scope of the disclosure of embodiments of the application, including the claims, is limited to such examples; combinations of features of the above embodiments or in different embodiments are also possible within the idea of an embodiment of the application, and many other variations of the different aspects of the embodiments of the application as described above exist, which are not provided in detail for the sake of brevity. Therefore, any omission, modification, equivalent replacement, improvement, etc. of the embodiments should be included in the protection scope of the embodiments of the present application.
Claims (10)
1. A method for testing firmware, comprising the steps of:
constructing a firmware image, uploading the firmware image to a BMC through an out-of-band management interface, and judging whether the corresponding firmware is a trusted firmware or not by the BMC based on the firmware image;
responding to the firmware as the trusted firmware, refreshing the trusted firmware to a system, and checking the trusted firmware in the refreshing process;
restarting the system in response to the verification passing, and verifying whether the recording function is normal in the restarting process;
responding to the normal recording function, successfully loading and starting the trusted firmware, and judging whether loading and starting time is within a preset time range or not;
responding to the fact that the system is restarted after the core data in the trusted firmware are tampered within the preset time range;
and in response to continued restart success, determining that the trusted firmware is stable in boot-up.
2. The method as recited in claim 1, further comprising:
restarting the system and verifying whether the recording function is normal in response to the firmware being untrusted firmware or the trusted firmware failing to verify;
and responding to the normal recording function, and determining that the verification function of the untrusted firmware and the recording function meet preset requirements.
3. The method as recited in claim 2, further comprising:
and uploading a new firmware image to the BMC to perform a corresponding new firmware test in response to the verification function and the recording function of the untrusted firmware meeting preset requirements.
4. The method as recited in claim 1, further comprising:
and responding to the loading start time exceeding the preset range, determining that the loading start time of the trusted firmware does not meet the preset requirement, and generating a related report.
5. The method of claim 1, wherein the record content corresponding to the record function includes a log type, a serial port record, a CPU state, and a memory state.
6. The method of claim 1, wherein the system is a BIOS or BMC.
7. The method of claim 1, wherein the core data is data of a static area of a kernel area in the flash memory.
8. A firmware testing system, comprising:
the trusted judgment module is configured to construct a firmware image, upload the firmware image to the BMC through an out-of-band management interface, and judge whether the corresponding firmware is trusted firmware or not based on the firmware image by the BMC;
the refreshing verification module is configured to respond to the fact that the firmware is the trusted firmware, refresh the trusted firmware to a system, and verify the trusted firmware in the refreshing process;
a restarting module configured to restart the system in response to the verification passing, and verify whether the recording function is normal in the restarting process;
the time judging module is configured to respond to the normal recording function, the trusted firmware is loaded and started successfully, and whether the loading start time is within a preset time range or not is judged;
a continuous restarting module configured to restart the system continuously after tampering with the core data in the trusted firmware in response to the preset time range; and
and the determining module is configured to determine that the trusted firmware starts stably in response to the success of the continuous restart.
9. A computer readable storage medium, characterized in that computer program instructions are stored, which, when executed by a processor, implement the method of any one of claims 1-7.
10. A computer device comprising a memory and a processor, wherein the memory has stored therein a computer program which, when executed by the processor, performs the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310980172.9A CN116893939A (en) | 2023-08-03 | 2023-08-03 | Firmware testing method, system, storage medium and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310980172.9A CN116893939A (en) | 2023-08-03 | 2023-08-03 | Firmware testing method, system, storage medium and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116893939A true CN116893939A (en) | 2023-10-17 |
Family
ID=88312108
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310980172.9A Pending CN116893939A (en) | 2023-08-03 | 2023-08-03 | Firmware testing method, system, storage medium and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116893939A (en) |
-
2023
- 2023-08-03 CN CN202310980172.9A patent/CN116893939A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110992992B (en) | Hard disk test method, device and storage medium | |
| CN110704304B (en) | Application program testing method and device, storage medium and server | |
| CN109299015B (en) | Software testing method, device and system | |
| CN109766230A (en) | Single-deck SSD powered-off fault test method, device and computer equipment | |
| CN108171041B (en) | Method and apparatus for authenticating an application accessing memory | |
| CN115952757A (en) | Register testing method and device | |
| CN108595323B (en) | System testing method and related device | |
| CN112215593A (en) | Payment method, payment device, server and storage medium | |
| US20230315620A1 (en) | System and Method for Diagnosing a Computing Device in Safe Mode | |
| CN111930579A (en) | Test machine deployment permission verification method and device, computer equipment and storage medium | |
| CN108647119A (en) | The startup method, apparatus and equipment of linux system | |
| CN116893939A (en) | Firmware testing method, system, storage medium and equipment | |
| CN111859402A (en) | Safe boot method and device based on UEFI BIOS start | |
| CN115328814B (en) | Fault injection method, device, equipment and storage medium based on mirror pair | |
| CN115659296A (en) | File verification method, device and equipment and readable storage medium | |
| CN115344445A (en) | Abnormal power-down testing method, system, medium and equipment based on solid state disk | |
| CN114037539A (en) | Method and device for detecting single-link failure of insurance | |
| CN111475400A (en) | Verification method of service platform and related equipment | |
| CN112114908A (en) | Hardware platform, starting method and device thereof, and electronic equipment | |
| CN111985010A (en) | Interception verification method and device for notebook hard disk, computer equipment and storage medium | |
| CN111597101A (en) | SDK access state detection method, computer device and computer readable storage medium | |
| CN117574352B (en) | Software and hardware combined anti-counterfeiting method, system, equipment and storage medium | |
| CN112468296B (en) | Key programming method, system, electronic equipment and storage medium | |
| CN112560035B (en) | Application detection method, device, equipment and storage medium | |
| CN109901799B (en) | Log reading and writing method and device |
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 |