CN112214415B - Trusted management method for executable files of airborne embedded system - Google Patents
Trusted management method for executable files of airborne embedded system Download PDFInfo
- Publication number
- CN112214415B CN112214415B CN202011215012.8A CN202011215012A CN112214415B CN 112214415 B CN112214415 B CN 112214415B CN 202011215012 A CN202011215012 A CN 202011215012A CN 112214415 B CN112214415 B CN 112214415B
- Authority
- CN
- China
- Prior art keywords
- information
- file
- abstract
- list
- curing
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
- G06F11/3608—Software analysis for verifying properties of programs using formal methods, e.g. model checking, abstract interpretation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- 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)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Stored Programmes (AREA)
- Storage Device Security (AREA)
Abstract
The application provides a trusted management method for executable files of an airborne embedded system, which comprises the following steps: when an executable file of the airborne embedded software is put in storage, an upper computer end generates a first information abstract corresponding to the executable file, and an information abstract list is generated according to the first information abstract of all the executable files; when an executable file of airborne embedded software is exported, an upper computer end generates a second information abstract corresponding to the executable file, and whether the first information abstract and the second information abstract are consistent or not is checked; if the information is consistent with the information, the upper computer end generates a curing information list for the airborne embedded software; and at the target terminal, solidifying the solidification information list and the airborne embedded software into an airborne embedded system.
Description
Technical Field
The invention belongs to the field of embedded system software, and particularly relates to a trusted management method for an executable file of an airborne embedded system.
Background
The onboard embedded system is used as a high-reliability and high-security embedded system, and the software code of the onboard embedded system requires high quality, high reliability and high security. To improve execution speed and system reliability, the software of the on-board embedded system is generally fixed in a memory chip or a memory inside the processor, and is not stored in an external carrier such as a disk.
For an airborne embedded system, when software is delivered from a factory or upgraded in an outfield, the condition that the state of a product is uncontrollable due to filling of informal version software is easy to occur; in addition, the Flash property determines that certain bits jump with a certain probability in the operation process, and an unknown result is caused.
Disclosure of Invention
Aiming at the problems, the invention provides a credible management method for executable files of an airborne embedded system by closely combining with a software development process, and carries out correctness check on the executable files needing to be solidified of the airborne embedded system. Through the inspection process, the problem of uncontrollable software filling caused by manual misoperation or not strictly following the flow is greatly reduced, a great deal of troubleshooting time is saved, the product quality is improved, and the difficulty of field upgrading is reduced.
The application provides a trusted management method for executable files of an airborne embedded system, which comprises the following steps:
when executable files of airborne embedded software are put in storage, an upper computer terminal generates first information summaries corresponding to the executable files, and an information summary list is generated according to the first information summaries of all the executable files;
when an executable file of the airborne embedded software is delivered out of a warehouse, an upper computer end generates a second information abstract corresponding to the executable file, and whether the first information abstract and the second information abstract are consistent or not is checked;
if the information is consistent with the information, the upper computer end generates a curing information list for the airborne embedded software;
and at the target terminal, solidifying the solidification information list and the airborne embedded software into an airborne embedded system.
Specifically, the upper computer end generates a first information abstract corresponding to the executable file, and generates an information abstract list according to the first information abstract of all the executable files, which specifically includes:
the upper computer generates a first information abstract corresponding to the executable file by adopting a message abstract algorithm;
and generating an information abstract list according to the file names of all executable files and the first information abstract.
Specifically, the generation of the curing information list of the airborne embedded software by the upper computer terminal specifically comprises the following steps:
presetting solidification information of each executable file, wherein the solidification information comprises a file name, a file solidification starting address and a file length;
and the upper computer generates a curing information list for the airborne embedded software according to the curing information and the second information abstract, wherein the curing information list comprises the curing information, the number of executable files, the second information abstract and the serial number of the executable files.
Specifically, the method further comprises:
according to the solidification information list, determining whether the current version is the latest version;
and if not, updating the version of the onboard embedded software.
Specifically, determining whether the current version is the latest version according to the solidification information list specifically includes:
acquiring the curing information list at the designated address of the target machine;
reading out an executable file according to the file curing starting address and the file length in the curing information list;
generating a third message abstract corresponding to the read executable file by adopting a message abstract algorithm;
comparing the third information abstract with the second information abstract, and judging whether the files are consistent;
if the version is consistent with the current version, the current version is determined to be the latest version; otherwise, the current version is not the latest version.
Specifically, when the onboard embedded software is debugged, whether the executable file in the onboard embedded software is a controlled file is verified.
Specifically, when the onboard embedded software is debugged, verifying whether an executable file therein is a controlled file specifically includes:
acquiring the curing information list at the designated address of the target machine;
reading out an executable file according to the file curing starting address and the file length in the curing information list;
generating a third information abstract corresponding to the read executable file by adopting a message abstract algorithm;
comparing the third information abstract with the second information abstract, and judging whether the files are consistent;
if the two files are consistent, the executable file is a controlled file; otherwise, the executable file is not a controlled file.
Specifically, after checking whether the first information digest and the second information digest are consistent, before generating the solidified information list, the method further includes:
before the on-board embedded software is filled, an upper computer end generates a fourth information abstract corresponding to the executable file, and whether the fourth information abstract is consistent with the first information abstract or not is checked;
and if the information is consistent with the information, the upper computer terminal generates a curing information list for the airborne embedded software.
In summary, the invention is based on the file message digest algorithm, and the functions of calculating the file message digest, generating the file message digest list, checking the message digest list and generating the solidified message list are realized in the upper computer design; the calculation of the file information abstract and the verification function of the solidified information list are realized at the design of a target machine end, so that the correctness and the transportability of all executable files are ensured in the whole software development process.
The invention has the following advantages and effects:
1) The problem of uncontrollable software filling caused by manual misoperation or not strictly following the process is greatly reduced;
2) A large amount of troubleshooting time is saved, and the quality of the product is improved;
3) The difficulty of external field upgrading is reduced;
drawings
FIG. 1 is a software development stage application instruction;
FIG. 2 is a list of file information summaries;
fig. 3 is a table of curing information.
Detailed Description
The invention belongs to the field of embedded system software, and particularly relates to a trusted management method for an executable file of an airborne embedded system.
The invention provides a file credible management method based on a file message digest algorithm, which is closely combined with software development and development processes according to the specific requirements of high quality, high reliability and high safety of software codes of an airborne embedded system. The method mainly aims at the executable file of the airborne embedded system after engineering verification, the correctness of the executable file is checked in each stage of warehouse entry and exit, solidification and upgrading, the problem of uncontrollable software filling caused by manual misoperation or not strictly according to the flow is greatly reduced through the checking process, a large amount of troubleshooting time is saved, the product quality is improved, and the difficulty of field upgrading is reduced. The method mainly comprises the following steps:
1. in the product warehouse control stage, in order to verify and confirm the warehouse-in and warehouse-out process of the product and facilitate subsequent processing, a file message abstract algorithm is used for calculation and generating an information abstract list of warehouse-in software during warehouse-in; and when the software is delivered out of the warehouse, calculating and comparing the software with the list, and checking the correctness of the software delivered out of the warehouse to determine whether the software is the version to be delivered out of the warehouse.
2. And a software delivery stage, wherein pre-delivery inspection is carried out and software information is filled together with the software executable file. Before filling, verifying the information abstract and confirming whether the information abstract is consistent with the state of the ex-warehouse software; and during delivery, filling the software passing the inspection and verifying the filling result.
3. And in the software maintenance stage, whether the solidified software is a controlled file or not, and whether human tampering or bit jump occurs or not is checked and verified at any time in the ground loading and debugging states. When the version is updated, checking the curing information list and confirming the current version; when the software is debugged, whether the solidified software is a controlled file is verified.
Example one
In the process of software development and development, the invention mainly assists developers through the following steps to ensure the correctness of executable files:
1) When the product is put in storage, generating an information abstract list of the software to be put in storage;
2) When the product is delivered out of the warehouse, checking the correctness of the delivery software, and judging whether the correctness is consistent with that of the delivery software when the product is delivered into the warehouse;
3) Before filling the product, verifying the information abstract and confirming whether the information abstract is consistent with the ex-warehouse software;
4) When the product is delivered, generating a curing information list for the software passing the inspection, and curing the curing information list into the product along with the software;
5) When the product version is updated, checking the curing information list and confirming the current version;
6) And when the product software is debugged, verifying whether the solidified software is a controlled file.
As shown in figure 1.
The design is carried out from two angles of an upper computer and a target machine end respectively.
Host computer terminal
The invention designs and realizes the function requirements of the product library management and control stage and the software delivery stage developed by software on the upper computer, and the specific functions comprise:
and (3) calculating the file information abstract: when the software is verified to be controlled to be put in storage, the information abstract of the executable file is calculated by adopting a file information abstract algorithm, and a 128-bit file information abstract is obtained through calculation and can be used as a check code for file checking.
Generating a file information abstract list: and performing batch processing on all executable files contained in the software to generate a file information abstract list in the txt format. The information stored in the list includes file names of all executable files in the warehousing software, information abstracts corresponding to all the files and specific time for generating the list. As shown in fig. 2.
Checking the information abstract list: after the software is delivered from the warehouse and before the software is filled, file information abstract calculation is carried out on all executable files, and comparison and verification are carried out on a file information abstract list generated before the software is delivered into the warehouse, so that the correctness of all files is ensured.
Generating a curing information list: before filling, batch processing is carried out on all executable files contained in software, and a solidification information list in a bin format is generated. The information stored in the list comprises the number of files in the list, the serial number, the file name, the file curing starting address, the file length and the information abstract check code of each curing file. For the convenience of reading at the target end, the list is stored in binary format, and the specific format is shown in fig. 3.
Target machine end
The invention is designed and realized at a target machine end according to the functional requirements in the software maintenance stage, and the specific functions are as follows:
and (3) calculating the file information abstract: on the target machine, the information abstract of the solidified file is calculated by adopting a file information abstract algorithm, and a solidified file information abstract of 128bit is obtained through calculation, namely the solidified file information abstract can be used as a check code for checking the solidified file.
And (4) checking a curing information list: and during filling, the software and a corresponding curing information list generated on the upper computer are cured into the product. And comparing the information abstract obtained by calculating the solidified file with the record in the solidified information list during version verification and software updating, and outputting a comparison result. Displaying the name of the output file, the storage address of the file and a verification result, and outputting the information abstract of the file if the verification result is consistent; and if the verification results are inconsistent, outputting the list storage abstract and the specific file calculation abstract together.
In order to realize the above functions on the target machine, during filling, the software and the corresponding curing information list generated on the upper computer need to be cured into a product, and the functions of summary calculation of file information and verification of the curing information list are integrated into a BOOT program (BOOT). In the ground loading and debugging states, the calculation of the file information abstract and the display of the verification result can be realized through the BOOT menu.
Example two
The specific work implementation steps are as follows:
step 1, when the product is put in storage, an information abstract list of the storage software is generated.
Generating the information abstract of each executable file by adopting a file information abstract calculation function, wherein the input is all files required to be subjected to information abstract calculation; and outputting the file name and the calculation result of the corresponding check code.
And carrying out batch processing operation on all executable files in the software and calculation results thereof to generate a txt format information abstract list. The information stored in the list includes file names of all executable files in the warehousing software, information abstracts corresponding to all the files and specific time for generating the list.
And 2, when the product is delivered out of the warehouse, checking the correctness of the delivery software, and judging whether the product is consistent with the product delivered in the warehouse.
And calculating the file information abstract of the file needing to be delivered by adopting a file information abstract calculating function.
And (3) comparing and verifying the calculation result obtained in the step (1) with the information abstract list generated before the software is put in storage by adopting an information abstract list verification function, and ensuring the correctness of all files. The input of the function is a file information abstract list and files needing to be verified in the list; and outputting the specific checking result. If The verification is correct, the result is displayed as "The file is corrected! "; if The files are not consistent, the result is displayed as "The file is fake! "; if The file to be verified is not in The input verification list, the result is displayed as "The file files not have had Digest in this list! ".
In practical application, the message digest algorithm is a widely used cryptographic hash function, and can be used for file information verification, cryptographic management, electronic signature, spam screening and the like. The basic principle of the file information summarization algorithm is as follows: taking file information with any finite length as input, dividing the input information into N groups by taking 512bit as a unit, and dividing each group into 16 32-bit sub-groups. Defining four link variables, wherein each group participates in four rounds of operation on the link variables, outputting four 32-bit message digests at last, and outputting a 128-bit hash value after cascading the four message digests.
And 3, before filling the product, verifying the information abstract and confirming whether the information abstract is consistent with ex-warehouse software.
And calculating the file information abstract of the file to be filled by adopting a file information abstract calculating function.
And (3) comparing and verifying the calculation result in the step (1) with an information abstract list attached when the software is delivered out of the warehouse by adopting an information abstract list checking function, and ensuring the correctness of all files. The input of the function is a file information abstract list and files needing to be verified in the list; and outputting a specific checking result. If The verification is correct, the result is displayed as "The file is corrected! "; if The files are not consistent, the result is displayed as "The file is fake! "; if The file to be verified is not in The input verification list, the result is displayed as "The file files not have had Digest in this list! ".
And 4, when the product is delivered, generating a curing information list for the software passing the inspection, and curing the curing information list into the product along with the software.
Inputting file solidification information in The solidified file information filling, wherein The file verification result is' The file is correct! "is a curable document.
Selecting a file needing curing, and inputting relevant curing information. If the address format of the input information is correct and the file storage space is available, displaying the input information in a solidifiable file list; if the input information is wrong, the wrong prompt is displayed in a text box of the generation condition of the solidification list.
And selecting the files needing to be solidified in the solidifiable list, and clicking the 'generation of the solidified list' to realize the function of generating the solidified information list.
The generate solidification list function will perform a batch operation on all successfully verified executables to generate a. Bin formatted solidification information list. The information stored in the list comprises the number of files in the list, the serial number, the file name, the file curing starting address, the file length and the information abstract check code of each curing file. For the convenience of reading at the target end, the list is stored in a binary form, so the readability is poor compared with the file information summary list.
And during filling, the software and a corresponding curing information list generated on the upper computer are cured to a product at the end of a target machine.
And 5, checking the curing information list when the product version is updated, and confirming the current version.
Acquiring a curing information list generated by an upper computer at a designated address;
reading out the files in the list according to the address information in the acquisition list, and performing information abstract calculation of the files;
comparing the calculation result with the file information abstract in the list, and judging whether the files are consistent;
displaying the name of the output file, the storage address of the file and a verification result, and outputting the information abstract of the file if the verification result is consistent; and if the verification results are inconsistent, outputting the list storage abstract and the specific file calculation abstract together.
And judging the updating state of the current version according to the checking display result.
And 6, when the product software is debugged, verifying whether the solidified software is a controlled file.
Acquiring a curing information list generated by an upper computer at a designated address;
reading out the files in the list according to the address information in the acquisition list, and performing information abstract calculation of the files;
comparing the calculation result with the file information abstract in the list, and judging whether the files are consistent;
displaying the name of the output file, the storage address of the file and a verification result, and outputting the information abstract of the file if the verification result is consistent; and if the verification results are not consistent, outputting the list storage abstract and the specific file calculation abstract together.
And judging whether the current software is a controlled file or not, and whether artificial tampering or bit jump occurs or not according to the verification display result.
Claims (6)
1. An executable file trusted management method of an airborne embedded system is characterized by comprising the following steps:
when an executable file of airborne embedded software is put in storage, an upper computer end generates a first information abstract corresponding to the executable file, and an information abstract list is generated according to the first information abstract of all executable files, and the method specifically comprises the following steps:
the upper computer generates a first information abstract corresponding to the executable file by adopting a message abstract algorithm;
generating an information abstract list according to the file names of all executable files and the first information abstract;
when an executable file of the airborne embedded software is delivered out of a warehouse, an upper computer end generates a second information abstract corresponding to the executable file, and whether the first information abstract and the second information abstract are consistent or not is checked;
if the information is consistent with the information, the upper computer end generates a curing information list for the airborne embedded software, and the method specifically comprises the following steps: presetting solidification information of each executable file, wherein the solidification information comprises a file name, a file solidification starting address and a file length; the upper computer generates a curing information list for the airborne embedded software according to the curing information and the second information abstract, wherein the curing information list comprises the curing information, the number of executable files, the second information abstract and the serial number of the executable files;
and at the target terminal, solidifying the solidification information list and the airborne embedded software into an airborne embedded system.
2. The method of claim 1, further comprising:
determining whether the current version is the latest version or not according to the curing information list;
and if not, updating the version of the onboard embedded software.
3. The method according to claim 2, wherein determining whether the current version is the latest version according to the solidification information list specifically includes:
acquiring the curing information list at the designated address of the target machine;
reading out an executable file according to the file curing starting address and the file length in the curing information list;
generating a third information abstract corresponding to the read executable file by adopting a message abstract algorithm;
comparing the third information abstract with the second information abstract, and judging whether the files are consistent;
if the current version is the latest version, confirming that the current version is the latest version; otherwise, the current version is not the latest version.
4. The method of claim 1, wherein: when the embedded software is debugged, verifying whether the executable file in the embedded software is a controlled file.
5. The method according to claim 4, wherein verifying whether the executable file is a controlled file when the onboard embedded software is debugged comprises:
acquiring the curing information list at the designated address of the target machine;
reading out an executable file according to the file curing starting address and the file length in the curing information list;
generating a third information abstract corresponding to the read executable file by adopting a message abstract algorithm;
comparing the third information abstract with the second information abstract, and judging whether the files are consistent;
if the two files are consistent, the executable file is a controlled file; otherwise, the executable file is not a controlled file.
6. The method of claim 1, wherein after checking whether the first message digest and the second message digest are consistent, prior to generating the consolidated message list, the method further comprises:
before the on-board embedded software is filled, an upper computer end generates a fourth information abstract corresponding to the executable file, and whether the fourth information abstract is consistent with the first information abstract or not is checked;
and if the information is consistent with the information, the upper computer terminal generates a curing information list for the airborne embedded software.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011215012.8A CN112214415B (en) | 2020-11-03 | 2020-11-03 | Trusted management method for executable files of airborne embedded system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011215012.8A CN112214415B (en) | 2020-11-03 | 2020-11-03 | Trusted management method for executable files of airborne embedded system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112214415A CN112214415A (en) | 2021-01-12 |
| CN112214415B true CN112214415B (en) | 2023-04-18 |
Family
ID=74058192
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011215012.8A Active CN112214415B (en) | 2020-11-03 | 2020-11-03 | Trusted management method for executable files of airborne embedded system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112214415B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114489831B (en) * | 2021-12-29 | 2024-03-19 | 中国航空工业集团公司西安飞机设计研究所 | Configurable airborne software batch processing and curing method |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102508728A (en) * | 2011-11-29 | 2012-06-20 | 中国航空工业集团公司第六三一研究所 | Error detection and read method of goal document solidified on FLASH carrier |
| CN103235912A (en) * | 2013-04-12 | 2013-08-07 | 福建伊时代信息科技股份有限公司 | Device and method for recognizing trusted processes |
| CN103530121A (en) * | 2013-10-15 | 2014-01-22 | 武汉邮电科学研究院 | Method of compatibility of multiple hardware platforms by RRU single software version |
| CN105930728A (en) * | 2016-06-17 | 2016-09-07 | 浪潮(北京)电子信息产业有限公司 | Application examining method and device |
| CN107992325A (en) * | 2017-11-09 | 2018-05-04 | 北京航空航天大学 | A kind of method that fileinfo is compared by feature code check |
| CN108121554A (en) * | 2017-12-20 | 2018-06-05 | 浙江亿邦通信科技股份有限公司 | A kind of upgrade method and upgrade-system of open air embedded device system |
| CN108762788A (en) * | 2018-05-31 | 2018-11-06 | 四川斐讯信息技术有限公司 | A kind of embedded device firmware encrypting method and system based on server |
| CN110659088A (en) * | 2019-09-20 | 2020-01-07 | 浙江杰芯科技有限公司 | Method and system for expanding program under embedded environment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110154496A1 (en) * | 2009-12-23 | 2011-06-23 | Chun Hsiang Cheng | Removable Apparatus and Method for Verifying an Executable File in a Computing Apparatus and Computer-Readable Medium Thereof |
-
2020
- 2020-11-03 CN CN202011215012.8A patent/CN112214415B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102508728A (en) * | 2011-11-29 | 2012-06-20 | 中国航空工业集团公司第六三一研究所 | Error detection and read method of goal document solidified on FLASH carrier |
| CN103235912A (en) * | 2013-04-12 | 2013-08-07 | 福建伊时代信息科技股份有限公司 | Device and method for recognizing trusted processes |
| CN103530121A (en) * | 2013-10-15 | 2014-01-22 | 武汉邮电科学研究院 | Method of compatibility of multiple hardware platforms by RRU single software version |
| CN105930728A (en) * | 2016-06-17 | 2016-09-07 | 浪潮(北京)电子信息产业有限公司 | Application examining method and device |
| CN107992325A (en) * | 2017-11-09 | 2018-05-04 | 北京航空航天大学 | A kind of method that fileinfo is compared by feature code check |
| CN108121554A (en) * | 2017-12-20 | 2018-06-05 | 浙江亿邦通信科技股份有限公司 | A kind of upgrade method and upgrade-system of open air embedded device system |
| CN108762788A (en) * | 2018-05-31 | 2018-11-06 | 四川斐讯信息技术有限公司 | A kind of embedded device firmware encrypting method and system based on server |
| CN110659088A (en) * | 2019-09-20 | 2020-01-07 | 浙江杰芯科技有限公司 | Method and system for expanding program under embedded environment |
Non-Patent Citations (2)
| Title |
|---|
| "Secured IoT Through Hashing Using MD5";Irfan A. Landge等;《2018 Fourth International Conference on Advances in Electrical, Electronics, Information, Communication and Bio-Informatics (AEEICB)》;20181004;第1-5页 * |
| "创新发展中的可信计算理论与技术";冯登国等;《中国科学:信息科学》;20200831;第50卷(第8期);第1127-1147页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112214415A (en) | 2021-01-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101436141B (en) | Firmware upgrading and encapsulating method and device based on digital signing | |
| CN103473088B (en) | A kind of single-chip microcomputer online upgrading method and system | |
| CN102194048A (en) | Method and device for configuration validation of a complex multi-element system | |
| CN103677898A (en) | Method for checking loaded extension and/or plug-in on server side and server | |
| CN112214415B (en) | Trusted management method for executable files of airborne embedded system | |
| CN106708704A (en) | Method and device for classifying crash logs | |
| CN113590227A (en) | Binary programming format loading method and system under embedded system | |
| CN106709281B (en) | Patch granting and acquisition methods, device | |
| CN111563016A (en) | Log collection and analysis method and device, computer system and readable storage medium | |
| CN111695093A (en) | iOS application-based reinforcement method, electronic device and storage medium | |
| CN111460436B (en) | Unstructured data operation method and system based on blockchain | |
| CN111506330A (en) | Program updating method and device, star affair computer and storage medium | |
| CN108200060B (en) | Single sign-on verification method based on web subsystem, server and storage medium | |
| CN114356680A (en) | Verification method and device and electronic equipment | |
| CN113419734A (en) | Application program reinforcing method and device and electronic equipment | |
| CN112671741A (en) | Network protection method, device, terminal and storage medium | |
| CN112650549A (en) | Page jump method, device, terminal and storage medium | |
| CN110780881A (en) | Software package manufacturing method and device and electronic equipment | |
| CN117910052A (en) | Method and system for verifying data integrity and correctness | |
| CN117544616A (en) | Vehicle-end OTA upgrading method and device, electronic equipment and readable storage medium | |
| CN117093245B (en) | OTA upgrade package verification method, device, equipment and readable storage medium | |
| CN113326055B (en) | Equipment updating method and related device | |
| CN115481445B (en) | Signature verification method, device and equipment for portable document format file and storage medium | |
| CN112860285B (en) | SP upgrade package generation method and device of financial self-service equipment and computer equipment | |
| CN116170169A (en) | Static data extraction method and device, electronic equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |