CN110659488A - SHELL script file integrity protection based method and device - Google Patents
SHELL script file integrity protection based method and device Download PDFInfo
- Publication number
- CN110659488A CN110659488A CN201910861720.XA CN201910861720A CN110659488A CN 110659488 A CN110659488 A CN 110659488A CN 201910861720 A CN201910861720 A CN 201910861720A CN 110659488 A CN110659488 A CN 110659488A
- Authority
- CN
- China
- Prior art keywords
- file
- check code
- check
- code
- integrity
- 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
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/55—Detecting local intrusion or implementing counter-measures
- G06F21/56—Computer malware detection or handling, e.g. anti-virus arrangements
- G06F21/562—Static detection
- G06F21/565—Static detection by checking file integrity
-
- 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/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
Abstract
The disclosure relates to a method and a device for protecting integrity of a script file based on SHELL, electronic equipment and a storage medium. Wherein, the method comprises the following steps: verifying the file to be checked for integrity through an md5 code tool in the server, and generating a check code; when the file is changed, comparing the check codes, and performing file recovery operation according to the comparison result of the check codes; and compiling a SHELL script by the steps of generating the check code, comparing the check code and restoring the file. According to the method and the device, the integrity of the file is protected based on the SHELL script, the tampered file can be quickly positioned, and the time cost is saved.
Description
Technical Field
The present disclosure relates to the field of security technologies, and in particular, to a method and an apparatus for protecting integrity of a script file based on SHELL, an electronic device, and a computer-readable storage medium.
Background
A core file (core file), also called core dump (core dump), is a disk file that the operating system writes out the contents of the process address space and other information about the state of the process when the process terminates its operation by receiving some signal.
The core file is maliciously tampered to influence the server and the normal operation of various services on the server, and the mode for protecting the core file in the prior art is low in efficiency and needs to occupy a large amount of computer resources.
Accordingly, there is a need for one or more methods to address the above-mentioned problems.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
An object of the present disclosure is to provide a method, an apparatus, an electronic device, and a computer-readable storage medium for protecting integrity of a SHELL-based script file, thereby overcoming, at least to some extent, one or more of the problems due to the limitations and disadvantages of the related art.
According to one aspect of the disclosure, a method for protecting integrity of a SHELL-based script file is provided, which includes:
a check code generation step, namely checking the file to be checked for integrity through an md5 code tool in the server and generating a check code;
a check code comparison step, wherein when the file is changed, the check code is compared, and the file recovery operation is carried out according to the check code comparison result;
and a SHELL script generating step, namely compiling the SHELL script through the check code generating step, the check code comparing step and the file restoring step.
In an exemplary embodiment of the present disclosure, the check code generating step further includes:
and verifying the file to be subjected to integrity verification through an md5 code tool in the server, generating a verification code and backing up the file to be subjected to integrity verification.
In an exemplary embodiment of the present disclosure, the check code comparing step further includes:
and if the check codes are compared and the check codes are not stored in the server, judging that the file is a newly added file, and executing newly added operation on the file.
In an exemplary embodiment of the present disclosure, the check code comparing step further includes:
and if the check codes are compared and only the original check codes are stored in the server, judging that the file is a deleted file and executing deletion operation on the file.
In an exemplary embodiment of the present disclosure, the check code comparing step further includes:
and if the check codes are inconsistent with the original check codes stored in the server after comparison, judging that the file is a modified file, and executing modification operation on the file.
In an exemplary embodiment of the present disclosure, the SHELL script generating step further includes:
and an integrity warning step, namely comparing the check codes with results, and realizing a mail warning function to the user through the SHELL script.
In one aspect of the present disclosure, there is provided a SHELL script file integrity protection apparatus, including:
the verification code generation module is used for verifying the file to be verified in integrity through an md5 code tool in the server and generating a verification code;
the check code comparison module is used for comparing check codes when the file is changed and performing file recovery operation according to the check code comparison result;
and the SHELL script generating module is used for compiling the SHELL script by the steps of generating the check code, comparing the check code and restoring the file.
In one aspect of the present disclosure, there is provided an electronic device including:
a processor; and
a memory having computer readable instructions stored thereon which, when executed by the processor, implement a method according to any of the above.
In an aspect of the disclosure, a computer-readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, realizes the method according to any one of the above.
In the SHELL script file integrity protection method based on the exemplary embodiment of the present disclosure, the integrity check file is checked by an md5 code tool in the server, and a check code is generated; when the file is changed, comparing the check codes, and performing file recovery operation according to the comparison result of the check codes; and compiling a SHELL script by the steps of generating the check code, comparing the check code and restoring the file. According to the method and the device, the integrity of the file is protected based on the SHELL script, the tampered file can be quickly positioned, and the time cost is saved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The above and other features and advantages of the present disclosure will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.
FIG. 1 illustrates a flow diagram of a SHELL script file integrity protection based method according to an exemplary embodiment of the present disclosure;
FIG. 2 shows a schematic block diagram of a SHELL script file integrity protection based device according to an example embodiment of the present disclosure;
FIG. 3 schematically illustrates a block diagram of an electronic device according to an exemplary embodiment of the present disclosure; and
fig. 4 schematically illustrates a schematic diagram of a computer-readable storage medium according to an exemplary embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals denote the same or similar parts in the drawings, and thus, a repetitive description thereof will be omitted.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the embodiments of the disclosure can be practiced without one or more of the specific details, or with other methods, components, materials, devices, steps, and so forth. In other instances, well-known structures, methods, devices, implementations, materials, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.
The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in the form of software, or in one or more software-hardened modules, or in different networks and/or processor devices and/or microcontroller devices.
In the present exemplary embodiment, first, a method for protecting integrity of a script file based on SHELL is provided; referring to fig. 1, the method for protecting the integrity of the SHELL-based script file may include the following steps:
a check code generation step S110, verifying the file to be checked for integrity by using an md5 code tool in the server, and generating a check code;
a check code comparison step S120, when the file is changed, performing check code comparison, and performing file recovery operation according to the check code comparison result;
a SHELL script generating step S130, writing the SHELL script according to the check code generating, check code comparing and file restoring steps.
In the SHELL script file integrity protection method based on the exemplary embodiment of the present disclosure, the integrity check file is checked by an md5 code tool in the server, and a check code is generated; when the file is changed, comparing the check codes, and performing file recovery operation according to the comparison result of the check codes; and compiling a SHELL script by the steps of generating the check code, comparing the check code and restoring the file. According to the method and the device, the integrity of the file is protected based on the SHELL script, the tampered file can be quickly positioned, and the time cost is saved.
Next, the SHELL script file based integrity protection method in the present exemplary embodiment will be further described.
In the check code generating step S110, the to-be-checked file may be checked by an md5 code tool in the server, and a check code is generated.
In this exemplary embodiment, the check code generating step further includes:
and verifying the file to be subjected to integrity verification through an md5 code tool in the server, generating a verification code and backing up the file to be subjected to integrity verification.
In the embodiment of the present example, a folder, a file name, or a file type that needs to be integrity-checked is set and written into the custom configuration file. Such as: conf, if we need integrity protection for the files under the/usr/src directory, create the file check.conf, write inside: /usr/src
Conf file content is read, find and combine md5sum command to generate md5 code for file under/usr/src directory and add "file name: and writing the check code into a self-defined md5 code file.
And copying and backing the files under the/usr/src directory by using a find command.
In the check code comparison step S120, when the file is changed, the check code comparison may be performed, and a file recovery operation may be performed according to a check code comparison result.
In this exemplary embodiment, the check code comparing step further includes:
and if the check codes are compared and the check codes are not stored in the server, judging that the file is a newly added file, and executing newly added operation on the file.
In this exemplary embodiment, the check code comparing step further includes:
and if the check codes are compared and only the original check codes are stored in the server, judging that the file is a deleted file and executing deletion operation on the file.
In this exemplary embodiment, the check code comparing step further includes:
and if the check codes are inconsistent with the original check codes stored in the server after comparison, judging that the file is a modified file, and executing modification operation on the file.
In the embodiment of the present example, the file under the/usr/src/directory is modified and deleted, then the check code is generated again for the file under the/usr/src directory, and compared with the previous check code, and according to the comparison result, whether the file is newly added (without the md5 code before), deleted (without the md5 code after), modified (without the md5 code twice being different) can be determined.
In the SHELL script generating step S130, the SHELL script may be written through the check code generating, check code comparing and file restoring steps.
In the embodiment of this example, the SHELL script generating step further includes:
and an integrity warning step, namely comparing the check codes with results, and realizing a mail warning function to the user through the SHELL script.
In the embodiment of the present example, according to the result of the above step and the backup of the above step, the backup content is read, the recovery operation is performed on the modified and deleted file, and the deletion operation is performed on the newly added file. In addition, the integrity check result can be alerted using the mail tool in the linux system.
And writing a SHELL script to realize the steps, and judging whether to generate an integrity check code or perform integrity check or perform file recovery operation by inputting parameters.
In the embodiment of the example, the file integrity protection script based on the SHELL language is easy to develop, easy to maintain, quick to execute and simple to execute, the script can be executed regularly through manual or a mode of setting a timing task, the execution result is alarmed through a mail tool, and tools related to the file integrity protection script are simple and common servers (md5sum, find, mail). The tampered file can be quickly positioned, and time cost is saved.
It should be noted that although the various steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that these steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
In addition, in the present exemplary embodiment, an apparatus for protecting integrity of a SHELL-based script file is also provided. Referring to fig. 2, the device 200 for protecting the integrity of the SHELL-based script file may include: a check code generation module 210, a check code comparison module 220, and a SHELL script generation module 230. Wherein:
the check code generating module 210 is configured to check the to-be-checked file through an md5 code tool in the server, and generate a check code;
the check code comparison module 220 is used for comparing check codes when the file is changed and performing file recovery operation according to the check code comparison result;
a SHELL script generating module 230, configured to write a SHELL script according to the check code generating, check code comparing, and file restoring steps.
The specific details of each SHELL script file integrity protection device module are described in detail in the corresponding SHELL script file integrity protection method, and therefore are not described herein again.
It should be noted that although several modules or units of the SHELL script file based integrity protection apparatus 200 are mentioned in the above detailed description, such partitioning is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
In addition, in an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 300 according to such an embodiment of the invention is described below with reference to fig. 3. The electronic device 300 shown in fig. 3 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 3, electronic device 300 is embodied in the form of a general purpose computing device. The components of electronic device 300 may include, but are not limited to: the at least one processing unit 310, the at least one memory unit 320, a bus 330 connecting different system components (including the memory unit 320 and the processing unit 310), and a display unit 340.
Wherein the storage unit stores program code that is executable by the processing unit 310 to cause the processing unit 310 to perform steps according to various exemplary embodiments of the present invention as described in the above section "exemplary method" of the present specification. For example, the processing unit 310 may perform steps S110 to S130 as shown in fig. 1.
The storage unit 320 may include readable media in the form of volatile storage units, such as a random access memory unit (RAM)3201 and/or a cache memory unit 3202, and may further include a read only memory unit (ROM) 3203.
The storage unit 320 may also include a program/utility 3204 having a set (at least one) of program modules 3205, such program modules 3205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The electronic device 300 may also communicate with one or more external devices 370 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 300, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 300 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 350. Also, the electronic device 300 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 360. As shown, network adapter 360 communicates with the other modules of electronic device 300 via bus 330. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with electronic device 300, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above-mentioned "exemplary methods" section of the present description, when said program product is run on the terminal device.
Referring to fig. 4, a program product 400 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is to be limited only by the terms of the appended claims.
Claims (9)
1. A method for protecting the integrity of a script file based on SHELL, which is characterized by comprising the following steps:
a check code generation step, namely checking the file to be checked for integrity through an md5 code tool in the server and generating a check code;
a check code comparison step, wherein when the file is changed, the check code is compared, and the file recovery operation is carried out according to the check code comparison result;
and a SHELL script generating step, namely compiling the SHELL script through the check code generating step, the check code comparing step and the file restoring step.
2. The method of claim 1, wherein the check code generating step further comprises:
and verifying the file to be subjected to integrity verification through an md5 code tool in the server, generating a verification code and backing up the file to be subjected to integrity verification.
3. The method of claim 1, wherein the check code comparison step further comprises:
and if the check codes are compared and the check codes are not stored in the server, judging that the file is a newly added file, and executing newly added operation on the file.
4. The method of claim 1, wherein the check code comparison step further comprises:
and if the check codes are compared and only the original check codes are stored in the server, judging that the file is a deleted file and executing deletion operation on the file.
5. The method of claim 1, wherein the check code comparison step further comprises:
and if the check codes are inconsistent with the original check codes stored in the server after comparison, judging that the file is a modified file, and executing modification operation on the file.
6. The method of claim 1, wherein the SHELL script generating step further comprises:
and an integrity warning step, namely comparing the check codes with results, and realizing a mail warning function to the user through the SHELL script.
7. An apparatus for protecting integrity of a SHELL-based script file, the apparatus comprising:
the verification code generation module is used for verifying the file to be verified in integrity through an md5 code tool in the server and generating a verification code;
the check code comparison module is used for comparing check codes when the file is changed and performing file recovery operation according to the check code comparison result;
and the SHELL script generating module is used for compiling the SHELL script by the steps of generating the check code, comparing the check code and restoring the file.
8. An electronic device, comprising
A processor; and
a memory having computer readable instructions stored thereon which, when executed by the processor, implement the method of any of claims 1 to 6.
9. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910861720.XA CN110659488A (en) | 2019-09-12 | 2019-09-12 | SHELL script file integrity protection based method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910861720.XA CN110659488A (en) | 2019-09-12 | 2019-09-12 | SHELL script file integrity protection based method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110659488A true CN110659488A (en) | 2020-01-07 |
Family
ID=69038143
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910861720.XA Pending CN110659488A (en) | 2019-09-12 | 2019-09-12 | SHELL script file integrity protection based method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110659488A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101163046A (en) * | 2007-11-22 | 2008-04-16 | 北京金山软件有限公司 | Distributed website log data acquisition method and distributed website system |
| CN104932965A (en) * | 2014-03-18 | 2015-09-23 | 北京奇虎科技有限公司 | Object real-time monitoring method and device |
| US20170046211A1 (en) * | 2015-08-13 | 2017-02-16 | At&T Intellectual Property I, L.P. | Insider Attack Resistant System and Method For Cloud Services Integrity Checking |
-
2019
- 2019-09-12 CN CN201910861720.XA patent/CN110659488A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101163046A (en) * | 2007-11-22 | 2008-04-16 | 北京金山软件有限公司 | Distributed website log data acquisition method and distributed website system |
| CN104932965A (en) * | 2014-03-18 | 2015-09-23 | 北京奇虎科技有限公司 | Object real-time monitoring method and device |
| US20170046211A1 (en) * | 2015-08-13 | 2017-02-16 | At&T Intellectual Property I, L.P. | Insider Attack Resistant System and Method For Cloud Services Integrity Checking |
Non-Patent Citations (1)
| Title |
|---|
| LYKYL: "利用SHELL脚本实现文件完整性检测程序（1.2版更新）", 《博客园（HTTPS://WWW.CNBLOGS.COM/LYKYL/P/3835272.HTML）》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108475223B (en) | Method, system and computer program product for detecting corruption of a stack of a computing environment | |
| KR102236522B1 (en) | Method and apparatus for processing information | |
| CN109906597B (en) | Storing and retrieving restricted and unrestricted data sets to and from a cloud network | |
| US10228993B2 (en) | Data dump for a memory in a data processing system | |
| CN110059456B (en) | Code protection method, code protection device, storage medium and electronic equipment | |
| CN108319575B (en) | Page component checking method, device, server and storage medium | |
| CN107797887B (en) | Data backup and recovery method and device, storage medium and electronic equipment | |
| US20110099431A1 (en) | Relocatable interrupt handler for test generation and execution | |
| AU2021206497B2 (en) | Method and apparatus for authority control, computer device and storage medium | |
| CN109522010B (en) | Initialization code adding method and device, storage medium and electronic equipment | |
| CN112559140A (en) | Transaction control method, system, equipment and storage medium for data consistency | |
| CN105608150A (en) | Business data processing method and system | |
| CN111656325B (en) | Fast recovery from failures in a time-ordered log-structured key-value storage system | |
| CN104331311A (en) | Upgrade package generating method and device | |
| CN108197041B (en) | Method, device and storage medium for determining parent process of child process | |
| CN110659488A (en) | SHELL script file integrity protection based method and device | |
| US9983952B2 (en) | Recovery of local resource | |
| US11163636B2 (en) | Chronologically ordered log-structured key-value store from failures during garbage collection | |
| CN111078570B (en) | Parameter format detection method, device, equipment and medium based on interface framework | |
| Drake et al. | Panic! Unix system crash dump analysis | |
| US9697018B2 (en) | Synthesizing inputs to preserve functionality | |
| CN110681153B (en) | Game archive management system, method, computer device, and medium | |
| CN111061812B (en) | Big data distributed storage method and device, electronic equipment and storage medium | |
| CN111682991B (en) | Bus error message processing method and device | |
| US20230418961A1 (en) | Fine granularity read access to generational safeguarded copy data |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200107 |