CN114626067A - Temporary firmware control method - Google Patents
Temporary firmware control method Download PDFInfo
- Publication number
- CN114626067A CN114626067A CN202110710035.4A CN202110710035A CN114626067A CN 114626067 A CN114626067 A CN 114626067A CN 202110710035 A CN202110710035 A CN 202110710035A CN 114626067 A CN114626067 A CN 114626067A
- Authority
- CN
- China
- Prior art keywords
- temporary firmware
- time
- temporary
- firmware
- verification information
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F21/572—Secure firmware programming, e.g. of basic input output system [BIOS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F21/575—Secure boot
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a temporary firmware control method, which comprises the following steps: s1, starting the temporary firmware; s2, judging whether the temporary firmware is started for the first time, if so, writing compiling time for the temporary firmware; s3, judging whether the temporary firmware exceeds a preset trial period according to the current time and the compiling time; and S4, if the temporary firmware exceeds the preset trial period, limiting the system startup. The temporary firmware is written in the compiling time and the trial period of the temporary firmware is set, whether the trial period is exceeded or not is judged according to the difference value between the current starting time of the temporary firmware and the compiling time, the temporary firmware which exceeds the trial period is invalid, and the system cannot be started, so that the temporary firmware is controlled.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a temporary firmware control method.
Background
The main function of the BIOS setup program is to provide the lowest layer, most direct hardware setup and control for the computer, and the setup can be performed only at startup.
In the BIOS debugging process, there are many versions of firmware, and particularly, there are exchanges of debugging motherboards in the actual development process, or temporary firmware generated by temporarily verifying a function, and the temporary firmware is not much different from the formal release version, and careless mistakes are easily generated if careful inspection is not performed.
In addition, the customer can not manage the temporary firmware after going out because of verifying the temporary firmware required by some functions.
In view of the above situation, a method for managing the temporary firmware needs to be developed.
Disclosure of Invention
The invention mainly solves the technical problem of providing a temporary firmware control method to achieve the aim.
In order to solve the technical problems, the invention adopts a technical scheme that:
provided is a temporary firmware management and control method, including:
s1, starting the temporary firmware;
s2, judging whether the temporary firmware is started for the first time, if so, writing compiling time for the temporary firmware;
s3, judging whether the temporary firmware exceeds a preset trial period according to the current time and the compiling time;
and S4, if the temporary firmware exceeds the preset trial period, limiting the system startup.
Further, the compiling time in step S2 refers to a time when the temporary firmware is compiled, and the compiling time is written in a preset area on the temporary firmware.
Further, if the temporary firmware is first started in step S2, the method further includes the following steps:
s11, acquiring verification information;
and S12, storing the verification information into a preset area on the mainboard.
Further, the verification information refers to information generated when the temporary firmware is compiled, and the verification information includes partial information of compilation time and a number.
Further, if the temporary firmware is first started in step S2, the following steps are performed:
s21, comparing the verification information of the temporary firmware preset area with the verification information generated during compiling of the temporary firmware, and judging whether the verification information and the verification information are consistent;
and S22, if the two are consistent, limiting the system start.
Further, before step S3, the method further includes the following steps:
s31, writing the current time for the temporary firmware.
Further, in step S31, the current time refers to the time when the temporary firmware is started this time, and the current time is written into a preset area on the temporary firmware.
Further, before step S31, the method further includes the following steps:
s41, acquiring the last starting time of the preset area of the temporary firmware, and judging whether the last starting time and the current time are reasonable;
and S42, if the system is not reasonable, limiting the system start.
Further, the limiting of the system booting in steps S4, S22, and S42 includes exiting the booting service, performing a corresponding prompt, and reserving the function of entering the BIOS interface or Shell.
Further, the BIOS interface has a function of updating the temporary firmware, the shell has a command of updating the temporary firmware, and the shell also has a function of activating the temporary firmware.
The beneficial effects of the invention are:
1. writing compiling time for the temporary firmware, setting trial period of the temporary firmware, limiting the temporary firmware to be used in the trial period after the compiling is finished, and judging whether the temporary firmware exceeds the trial period or not through the difference value between the current starting time of the temporary firmware and the compiling time;
2. after the trial period function of the temporary firmware is added, the temporary firmware exceeding the trial period is invalid, the system cannot be started, and therefore the temporary firmware is controlled.
Drawings
FIG. 1 is a flow chart of the present invention.
Detailed Description
The following detailed description of the preferred embodiments of the present invention, taken in conjunction with the accompanying drawings, will make the advantages and features of the invention easier to understand by those skilled in the art, and thus will clearly and clearly define the scope of the invention.
The invention provides a temporary firmware control method which is suitable for controlling temporary firmware, in particular to temporary firmware based on UEFI.
In the embodiment of the invention, the temporary firmware is limited to be used in a preset trial period after the compilation is completed, and the functions to be realized are as follows: firstly, checking a trial period; secondly, exceeding the function limit after the trial period; thirdly, activating the realization of the trial period again; fourthly, preventing the trial period from being cracked after the temporary firmware is re-burned; and fifthly, preventing the trial period from being cracked by tampering the system time.
Specifically, the temporary firmware code includes compiling time, verification information and trial period information, which cannot be dynamically modified, the compiling time and the trial period information can be used as a basis for judging the use timeliness of the temporary firmware, and the verification information can be used as a verification basis for judging whether the temporary firmware is re-burned and started.
Specifically, when the temporary firmware needs to reactivate the trial period, the compilation time and trial period information that cannot be dynamically modified is not applicable.
In the embodiment of the invention, a trial period of one month is set for the temporary firmware, and an area is preset on the temporary firmware for storing data required to be used in the management and control process, wherein the data comprises compiling time and starting time, and the compiling time and the starting time can be dynamically modified.
Specifically, when the temporary firmware is started for the first time, the compiling time contained in the temporary firmware code is written into the preset area, and when the temporary firmware needs to reactivate the trial period, the current time is written into the preset area to update the compiling time, so that a new aging basis is provided.
Specifically, an area is preset on the EC of the Loongson motherboard for backing up the verification information included in the temporary firmware code, when the temporary firmware is re-burned, the information stored in the temporary firmware preset area is cleared, and when the temporary firmware is started again, the verification information backed up by the EC end is consistent with the verification information included in the temporary firmware code.
Specifically, at a specific stage after the temporary firmware is started, the current time is recorded into a preset area and is used as a basis for judging whether the system time is accurate or not when the temporary firmware is started next time.
In particular, these check functions regarding the trial period are implemented during the DXE phase of UEFI.
Referring to fig. 1, in the embodiment of the present invention, the temporary firmware management and control process includes:
s1, acquiring compiling time: starting the temporary firmware, and acquiring compiling time from a preset area on the temporary firmware;
s2, judging whether the compiling time is acquired: if the obtained compile time is empty, it indicates that the temporary firmware is first started, and the process proceeds to step S3, and if the obtained compile time is not empty, it indicates that the temporary firmware is not first started, and the process proceeds to step S5;
s3, obtaining and checking information in the EC: acquiring verification information from a preset area on the EC, comparing the verification information with the verification information contained in the temporary firmware code, if the two pieces of verification information are inconsistent, successfully verifying, entering step S4, if the two pieces of verification information are consistent, indicating that the temporary firmware is re-burned, and failing to verify, entering step S7;
s4, writing data necessary for temporary firmware management: writing the compiling time contained in the temporary firmware code into a preset area on the temporary firmware, acquiring the verification information contained in the temporary firmware code and writing the verification information into the preset area on the EC;
s5, acquiring and checking time information: acquiring last starting time from a preset area on the temporary firmware, comparing the last starting time with the current time, if the current time is earlier than the last starting time, indicating that the current time is tampered, failing to check, and entering the step S7, otherwise, successfully checking, and writing the current time into the preset area on the temporary firmware to serve as a check basis for next starting;
s6, judging whether the temporary firmware exceeds the trial period: comparing the compiling time and the current time of the preset area on the temporary firmware, if the temporary firmware is used for a month, the verification fails and the step S7 is entered, otherwise, the verification succeeds and the system is started normally;
s7: and (3) limiting system startup: including exiting the service of booting the temporary firmware, making a corresponding prompt, and retaining the functionality of entering the BIOS interface or Shell.
Specifically, the check information included in the temporary firmware code is formed by combining the compiling time and a number, in step S3, the EC is a single chip microcomputer on the motherboard and is limited by the storage space of the EC, and the check information included in the temporary firmware code is formed by the month and the date of the compiling time and a number.
Specifically, in step S3, there are two possibilities that the verification is successful: when the temporary firmware is started for the first time and is the first temporary firmware used in the debugging process, the checking information preset on the EC is empty and is inconsistent with the checking information contained in the temporary firmware code; and secondly, when the temporary firmware is replaced in the debugging process, the preset verification information on the EC is the verification information of the previous temporary firmware and is inconsistent with the verification information in the replaced temporary firmware code.
Specifically, step S5 further includes the following cases: when the temporary firmware is started for the first time, the starting time of the preset area is empty, and the verification is successful at this time, the current time is written into the preset area on the temporary firmware to be used as a verification basis for the next starting, so that the condition that the verification is successful in step S5 is: the last boot time is empty or current time > = last boot time.
Specifically, in step S6, the condition that the verification is successful is: compile time < = current time < = compile time + trial period.
Specifically, the current time is stored in the RTC, and the normal case is the current beijing time.
Specifically, in step S7, the corresponding prompt refers to a prompt of "system start is limited" to be issued to the user, and may also include a prompt of a specific reason for the system start is limited, for example: "temporary firmware is used" or "temporary firmware trial period has expired".
Specifically, the temporary firmware can be updated under a BIOS interface or Shell to obtain a formal firmware, and can be activated under Shell to have a trial period of one month again.
Specifically, when the temporary firmware is activated, the compiling time of the temporary firmware preset area needs to be updated by the current time, so that the step S2 can smoothly proceed to the step S5, and the trial period can be prolonged in the step S6.
The beneficial effects of the invention are:
1. writing compiling time for the temporary firmware, setting trial period of the temporary firmware, and judging whether the temporary firmware exceeds the trial period or not according to the difference between the current starting time of the temporary firmware and the compiling time;
2. after the trial period function of the temporary firmware is added, the temporary firmware exceeding the trial period is invalid, and the system is not started, so that the temporary firmware is controlled;
3. the verification information of the temporary firmware is backed up in a preset area of the mainboard, so that the trial period of the temporary firmware can be effectively prevented from being refreshed due to repeated programming;
4. the comparison between the current starting time and the last starting time of the temporary firmware is increased, so that the temporary firmware can be effectively prevented from being tampered by the system time and the validity period is prolonged.
The above description is only an embodiment of the present invention, and is not intended to limit the scope of the present invention, and all equivalent structures or equivalent processes performed by the present invention or directly or indirectly applied to other related technical fields are included in the scope of the present invention.
Claims (10)
1. A temporary firmware management and control method comprises the following steps:
s1, starting the temporary firmware;
s2, judging whether the temporary firmware is started for the first time, if so, writing compiling time for the temporary firmware;
s3, judging whether the temporary firmware exceeds a preset trial period according to the current time and the compiling time;
and S4, if the temporary firmware exceeds the preset trial period, limiting the system startup.
2. The method as claimed in claim 1, wherein the compiling time in step S2 refers to a time when the temporary firmware is compiled, and the compiling time is written into a preset area on the temporary firmware.
3. The method according to claim 2, wherein if the temporary firmware is first started in step S2, the method further includes the following steps:
s11, acquiring verification information;
and S12, storing the verification information into a preset area on the mainboard.
4. A temporary firmware management and control method according to claim 3, wherein the verification information includes a part of compilation time information and a number.
5. The method as claimed in claim 3, wherein in step S2, if the temporary firmware is first started, the following steps are performed:
s21, comparing the verification information of the temporary firmware preset area with the verification information generated during compiling of the temporary firmware, and judging whether the verification information and the verification information are consistent;
and S22, if the two are consistent, limiting the system start.
6. The temporary firmware management and control method according to claim 2, further comprising, before step S3, the following steps:
and S31, writing the current time for the temporary firmware.
7. The method as claimed in claim 6, wherein the current time in step S31 refers to a time when the temporary firmware is started this time, and the current time is written into a preset area on the temporary firmware.
8. The temporary firmware management and control method according to claim 7, further comprising, before step S31, the following steps:
s41, acquiring last starting time of the temporary firmware preset area, and judging whether the last starting time and the current time are reasonable;
and S42, if the judgment result is not reasonable, limiting the system starting.
9. The method according to any one of claims 1 to 8, wherein the limiting system boot includes exiting boot services, performing corresponding prompts, and reserving functions to enter a BIOS interface or Shell.
10. The method as claimed in claim 9, wherein the BIOS interface has a function of updating the temporary firmware, the shell has a command to update the temporary firmware, and the shell has a function of activating the temporary firmware.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110710035.4A CN114626067A (en) | 2021-06-25 | 2021-06-25 | Temporary firmware control method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110710035.4A CN114626067A (en) | 2021-06-25 | 2021-06-25 | Temporary firmware control method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114626067A true CN114626067A (en) | 2022-06-14 |
Family
ID=81896670
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110710035.4A Withdrawn CN114626067A (en) | 2021-06-25 | 2021-06-25 | Temporary firmware control method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114626067A (en) |
Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2003279675A (en) * | 2002-03-22 | 2003-10-02 | Seiko Instruments Inc | Time code distributing system and time managing system using the same |
| JP2006126991A (en) * | 2004-10-27 | 2006-05-18 | Matsushita Electric Ind Co Ltd | Trial period limiting apparatus, method, program and medium |
| CN101770557A (en) * | 2008-12-30 | 2010-07-07 | 上海茂碧信息科技有限公司 | Method for calculating service time of software in system |
| CN102779258A (en) * | 2012-07-06 | 2012-11-14 | 苏州阔地网络科技有限公司 | Control method and system for period of validity of software |
| CN103189876A (en) * | 2010-11-12 | 2013-07-03 | 惠普发展公司，有限责任合伙企业 | Determine authorization of a software product based on a first and second authorization item |
| CN103312513A (en) * | 2013-06-19 | 2013-09-18 | 北京华胜天成科技股份有限公司 | Method and system for verifying use authorization in distributed environment |
| US20130247210A1 (en) * | 2012-03-13 | 2013-09-19 | Chi-Chou Huang | Method and System for Protecting Software Authorization |
| CN105046115A (en) * | 2015-09-15 | 2015-11-11 | 北京深思数盾科技有限公司 | Method and apparatus for detecting tampering with software operation time |
| CN105553668A (en) * | 2015-12-21 | 2016-05-04 | 北京飞杰信息技术有限公司 | Method and system for verifying user authorization certificate through verifying authorization time |
| CN105718761A (en) * | 2016-01-19 | 2016-06-29 | 浪潮(北京)电子信息产业有限公司 | Software probation period controlling method and device |
| CN106372462A (en) * | 2016-08-31 | 2017-02-01 | 北京深思数盾科技股份有限公司 | Method for realizing time limitation of software under offline state |
| CN107729069A (en) * | 2017-10-12 | 2018-02-23 | 浪潮(北京)电子信息产业有限公司 | A kind of method, apparatus of clean boot video card, computer-readable recording medium |
| CN107885979A (en) * | 2017-11-08 | 2018-04-06 | 江苏国泰新点软件有限公司 | A kind of method, apparatus of software free trial, equipment on probation and storage medium |
| CN108256297A (en) * | 2016-12-29 | 2018-07-06 | 北京博瑞彤芸文化传播股份有限公司 | The authority checking method on probation of software |
| CN109063489A (en) * | 2018-08-28 | 2018-12-21 | 郑州云海信息技术有限公司 | A kind of starting method and device |
| JP2020053002A (en) * | 2018-09-20 | 2020-04-02 | キヤノン株式会社 | Information processing apparatus, control method thereof, and program |
| CN111611015A (en) * | 2020-05-18 | 2020-09-01 | 歌尔科技有限公司 | Embedded firmware, starting method and storage equipment |
-
2021
- 2021-06-25 CN CN202110710035.4A patent/CN114626067A/en not_active Withdrawn
Patent Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2003279675A (en) * | 2002-03-22 | 2003-10-02 | Seiko Instruments Inc | Time code distributing system and time managing system using the same |
| JP2006126991A (en) * | 2004-10-27 | 2006-05-18 | Matsushita Electric Ind Co Ltd | Trial period limiting apparatus, method, program and medium |
| CN101770557A (en) * | 2008-12-30 | 2010-07-07 | 上海茂碧信息科技有限公司 | Method for calculating service time of software in system |
| CN103189876A (en) * | 2010-11-12 | 2013-07-03 | 惠普发展公司，有限责任合伙企业 | Determine authorization of a software product based on a first and second authorization item |
| US20130247210A1 (en) * | 2012-03-13 | 2013-09-19 | Chi-Chou Huang | Method and System for Protecting Software Authorization |
| CN102779258A (en) * | 2012-07-06 | 2012-11-14 | 苏州阔地网络科技有限公司 | Control method and system for period of validity of software |
| CN103312513A (en) * | 2013-06-19 | 2013-09-18 | 北京华胜天成科技股份有限公司 | Method and system for verifying use authorization in distributed environment |
| CN105046115A (en) * | 2015-09-15 | 2015-11-11 | 北京深思数盾科技有限公司 | Method and apparatus for detecting tampering with software operation time |
| CN105553668A (en) * | 2015-12-21 | 2016-05-04 | 北京飞杰信息技术有限公司 | Method and system for verifying user authorization certificate through verifying authorization time |
| CN105718761A (en) * | 2016-01-19 | 2016-06-29 | 浪潮(北京)电子信息产业有限公司 | Software probation period controlling method and device |
| CN106372462A (en) * | 2016-08-31 | 2017-02-01 | 北京深思数盾科技股份有限公司 | Method for realizing time limitation of software under offline state |
| CN108256297A (en) * | 2016-12-29 | 2018-07-06 | 北京博瑞彤芸文化传播股份有限公司 | The authority checking method on probation of software |
| CN107729069A (en) * | 2017-10-12 | 2018-02-23 | 浪潮(北京)电子信息产业有限公司 | A kind of method, apparatus of clean boot video card, computer-readable recording medium |
| CN107885979A (en) * | 2017-11-08 | 2018-04-06 | 江苏国泰新点软件有限公司 | A kind of method, apparatus of software free trial, equipment on probation and storage medium |
| CN109063489A (en) * | 2018-08-28 | 2018-12-21 | 郑州云海信息技术有限公司 | A kind of starting method and device |
| JP2020053002A (en) * | 2018-09-20 | 2020-04-02 | キヤノン株式会社 | Information processing apparatus, control method thereof, and program |
| CN111611015A (en) * | 2020-05-18 | 2020-09-01 | 歌尔科技有限公司 | Embedded firmware, starting method and storage equipment |
Non-Patent Citations (1)
| Title |
|---|
| 张幼真: "限时软件的伪破解", 《精品科普》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR100750132B1 (en) | Method and system for booting, updating software automatically and recovering update error, and computer readable medium recording the method | |
| TWI384367B (en) | System of updating firmware and method thereof | |
| US9251336B1 (en) | Secure versioning of software packages | |
| US6944867B2 (en) | Method for providing a single preloaded software image with an ability to support multiple hardware configurations and multiple types of computer systems | |
| EP2641175B1 (en) | Networked recovery system | |
| US20050085222A1 (en) | Software updating process for mobile devices | |
| CN107493290B (en) | OTA (over the air) upgrading method for Android smart television system software | |
| US20100058314A1 (en) | Computer System and Related Method of Logging BIOS Update Operation | |
| WO2001059564A2 (en) | Protected boot flow | |
| US6205561B1 (en) | Tracking and managing failure-susceptible operations in a computer system | |
| US20100049961A1 (en) | Update method for basic input/output system and update system thereof | |
| WO2004107169A1 (en) | Dynamic bios execution and concurrent for a blade server | |
| CN113238790B (en) | Firmware program updating method and system based on SD card and EEPROM | |
| CN114895845A (en) | EMmC data storage control method and embedded mainboard | |
| CN106155713B (en) | Startup information management method and device | |
| US20090138865A1 (en) | Performing an operating system upgrade without multiple system interruptions | |
| CN114626067A (en) | Temporary firmware control method | |
| US6772364B1 (en) | Fault tolerant field updating with alternation of memory areas | |
| US7543168B1 (en) | Specifying an operating system level to use after reboot | |
| KR100860402B1 (en) | Device and method for upgradin system using two step bootloader | |
| CN115827069A (en) | Starting control method, system and device for server mainboard | |
| US20060136710A1 (en) | Allowing or disallowing firmware upgrade based on comparison of firmware-related bits | |
| CN111258617B (en) | Electronic equipment | |
| US7490232B2 (en) | Disk device using disk to rewrite firmware and firmware determination method | |
| KR100628176B1 (en) | Method for upgrading program stored in information terminal |
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 |
Application publication date: 20220614 |
|
| WW01 | Invention patent application withdrawn after publication |