File burning method, device, equipment and computer readable storage medium

Abstract

The present disclosure relates to a file burning method, device, equipment and computer readable storage medium, the method comprising: when it is found that a burning software burns a target file, judging whether the burning software has burning authority according to configuration information in the application layer; if the burning software has burning authority, burning the target file through the burning software and obtaining burning related information in the burning process of the burning software; judging whether the burning related information conforms to a preset rule; if the burning related information does not conform to the preset rule, preventing the burning software from burning the target file. The present disclosure monitors the burning by judging whether the burning software has authority and whether the burning information conforms to the preset rule, prevents the burning behavior which does not have burning authority or the burning information does not conform to the preset rule in time, effectively avoids important material or data leakage caused by burning, and improves the security and controllability of file burning.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a file burning method, apparatus, device and computer-readable storage medium. Background Technology

[0002] Burning is the process of transferring desired data onto media such as CDs or CDs using burning tools. Burning software is typically used during the file burning process.

[0003] For some companies or users, certain files require strict confidentiality. To ensure the confidentiality of these files during the burning process, it is necessary to monitor the burning software and its burning behavior.

[0004] In Windows systems, existing technology can already strictly monitor both data input and output. However, there is currently no good way to monitor burning activities performed in Linux systems. Burning activities may lead to the leakage of important data or information, causing losses to enterprises. Summary of the Invention

[0005] To address the aforementioned technical issues, this disclosure provides a file burning method, apparatus, device, and computer-readable storage medium to ensure the security and controllability of file burning and prevent the leakage of important file information.

[0006] In a first aspect, embodiments of this disclosure provide a file burning method, including:

[0007] When the burning operation of the burning software is detected, it is determined whether the burning software has burning permissions based on the configuration information in the application layer.

[0008] If the burning software has burning permissions, the target file is burned using the burning software, and relevant burning information is obtained during the burning process.

[0009] Determine whether the recorded information conforms to preset rules;

[0010] If the burning information does not conform to the preset rules, the burning software will be prevented from burning the target file.

[0011] In some embodiments, determining whether the burning software has burning permissions based on the configuration information in the application layer includes:

[0012] Search for the information of the burning software in the blacklist of burning software. If the information is found, it is determined that the burning software does not have burning permissions.

[0013] Search for the information of the burning software in the whitelist of burning software. If it is found, it is determined that the burning software has burning permissions.

[0014] If the burning software is not found in either the burning software blacklist or the burning software whitelist, then the burning software is determined to lack burning permissions.

[0015] In some embodiments, after determining whether the burning software has burning permissions, the method further includes:

[0016] If the burning software does not have burning permissions, then the burning software is prevented from burning the target file.

[0017] In some embodiments, preventing the burning software from burning the target file includes:

[0018] Close the relevant processes of the burning software, or modify the information of the burning software.

[0019] In some embodiments, after preventing the burning software from burning the target file, the method further includes:

[0020] The burning-related information is reported to the server so that the server can audit the burning-related information.

[0021] Secondly, embodiments of this disclosure provide a file burning device, the device being located at the application layer, the device comprising:

[0022] The first judgment module is used to determine whether the burning software has burning permissions based on the configuration information in the application layer when it detects the burning operation of the burning software burning the target file.

[0023] The processing module is used to burn the target file through the burning software when the burning software has burning permissions, and to obtain burning-related information during the burning process of the burning software;

[0024] The second judgment module is used to determine whether the burning-related information conforms to preset rules;

[0025] The blocking module is used to prevent the burning software from burning the target file if the burning-related information does not conform to preset rules.

[0026] In some embodiments, the first determination module is further configured to: search for information about the burning software in the burning software blacklist; if found, determine that the burning software does not have burning permissions; search for information about the burning software in the burning software whitelist; if found, determine that the burning software has burning permissions; if the information about the burning software is not found in either the burning software blacklist or the burning software whitelist, determine that the burning software does not have burning permissions.

[0027] In some embodiments, the blocking module is also configured to prevent the burning software from burning the target file if the burning software does not have burning permissions.

[0028] In some embodiments, the blocking module is also used to close the relevant processes of the burning software, or to modify the information of the burning software.

[0029] In some embodiments, the file burning device further includes a reporting module for reporting the burning-related information to a server so that the server can audit the burning-related information.

[0030] Thirdly, embodiments of this disclosure provide an electronic device, including:

[0031] Memory;

[0032] Processor; and

[0033] Computer programs;

[0034] The computer program is stored in the memory and configured to be executed by the processor to implement the method as described in the first aspect.

[0035] Fourthly, embodiments of this disclosure provide a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the method described in the first aspect.

[0036] Fifthly, this disclosure also provides a computer program product, which includes a computer program or instructions that, when executed by a processor, implement the file burning method described above.

[0037] The file burning method, apparatus, device, and computer-readable storage medium provided in this disclosure monitor the burning process by determining whether the burning software has the necessary permissions and whether the burning-related information conforms to preset rules. Burning activities without proper permissions or whose burning-related information does not conform to preset rules are promptly blocked, effectively preventing the leakage of important data or information caused by burning, and improving the security and controllability of the file burning method. Attached Figure Description

[0038] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0039] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 A flowchart of a file burning method provided in this embodiment of the disclosure;

[0041] Figure 2 A schematic diagram illustrating an application scenario provided by an embodiment of this disclosure;

[0042] Figure 3 A flowchart of a file burning method provided in another embodiment of this disclosure;

[0043] Figure 4 This is a schematic diagram of the structure of the file burning device provided in the embodiments of this disclosure;

[0044] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0045] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0046] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.

[0047] In Windows systems, existing technologies can strictly monitor data input and output by installing drivers and calling the corresponding Application Programming Interface (API). However, since Linux systems lack API interfaces, existing monitoring methods are inapplicable. Therefore, there is currently no good way to monitor burning activities performed on Linux systems. Some unauthorized burning activities may lead to the leakage of important data or information, causing losses to enterprises. To address this problem, this disclosure provides a file burning method, which is described below with reference to specific embodiments.

[0048] Figure 1 A flowchart illustrating a file burning method provided in this embodiment of the disclosure. This method can be applied to... Figure 2 The application scenario shown includes a server 21 and a device 22. Specifically, device 22 can be a terminal; in this embodiment, device 22 can be a computer running a Linux operating system. It is understood that the file burning method provided in this embodiment can also be applied to other scenarios.

[0049] The following is combined Figure 2 The application scenarios shown are for Figure 1 The file burning method shown is described below. This method is applied to the application layer under the Linux operating system, and the specific steps included in the method are as follows:

[0050] S101. When the burning operation of the burning software is detected, determine whether the burning software has burning permission based on the configuration information in the application layer.

[0051] For each protected target file in device 22, the status of each target file is monitored in real time through the system's file monitoring mechanism. For example, the inotify mechanism can monitor file changes, such as file modification, addition, deletion, and access, and can notify the application of the corresponding events. Alternatively, the inotify mechanism can also monitor a fixed optical disc path. When the burning software wants to burn a target file, it first needs to obtain the image file of the target file to establish a connection between the optical disc and the target file to be burned. When the operation of obtaining the image file of the target file is monitored, such as the creation of files or folders in a specified directory, it is confirmed that the target file is about to be burned. Configuration information is pre-written in the application layer. The configuration information includes at least the burning software permission information, but is not limited to it. When the file monitoring mechanism in device 22 detects the burning software's action of obtaining the target file image file by monitoring the file status or optical drive device information, it determines whether the burning software has burning permissions and whether it has the right to burn the target file based on the burning software permission information pre-configured in the application layer.

[0052] S102. If the burning software has burning permissions, then burn the target file using the burning software and obtain the burning-related information during the burning process.

[0053] If the burning software has permission to burn the target file, it is allowed to obtain the image file of the target file. While the burning software is copying the image file of the target file, the file monitoring mechanism in device 22 obtains relevant information about burning the target file by monitoring the behavior of the burning software.

[0054] S103. Determine whether the burning information conforms to the preset rules.

[0055] Burning-related information may include the target file's filename, file path, file size, file type, file creation time, Message-Digest Algorithm 5 (MD5) information, and number of burns. Burning-related information may also include the type of disc to be burned, such as Compact Disc Read-Only Memory (CD-ROM), Compact Disk-Rewritable (CD-RW), or DVD-Rewritable (DVD-RW). Burning-related information may also include the file burning time and whether the file was burned locally or remotely. After acquiring burning-related information, the file monitoring mechanism in device 22 analyzes various information in real time. For example, it determines whether the filename or file content contains preset sensitive words. If no preset sensitive words are detected in the file, it confirms that the burning-related information conforms to the preset rules for sensitive words; if preset sensitive words are detected in the file, it confirms that the burning-related information does not conform to the preset rules for sensitive words. Alternatively, it determines whether the file format conforms to a preset format. If the burning information conforms to a certain preset rule, continue to determine whether the burning information conforms to the next preset rule, until it is confirmed that the burning information conforms to any preset rule; or, it is confirmed that the burning information does not conform to any preset rule.

[0056] S104. If the information to be burned does not conform to the preset rules, then prevent the burning software from burning the target file.

[0057] If the burning information does not conform to any preset rule, it is assumed that the target file corresponding to the burning information may contain confidential information, and burning it is not allowed. In this case, the burning software will be prevented from burning the target file.

[0058] This embodiment of the disclosure monitors the burning of a target file by listening to the burning operation of the burning software. It determines whether the burning software has burning permissions. If the burning software has burning permissions, it burns the target file and obtains relevant burning information during the burning process. It then determines whether the relevant burning information conforms to preset rules. If the relevant burning information does not conform to the preset rules, it prevents the burning software from burning the target file. By monitoring the burning process by determining whether the burning software has permissions and whether the relevant burning information conforms to the rules, it promptly blocks burning activities without proper permissions or where the relevant burning information does not conform to the preset rules. This effectively avoids the leakage of important data or information caused by burning, improving the security and controllability of the file burning method.

[0059] Furthermore, since the file burning method provided in this embodiment is applied at the application layer of the operating system, it does not require the installation of drivers or the calling of corresponding API interfaces, thus enabling control over file burning behavior under the Linux system.

[0060] Based on the above embodiments, determining whether the burning software has burning permissions includes: searching for information about the burning software in the burning software blacklist; if found, it is determined that the burning software does not have burning permissions; searching for information about the burning software in the burning software whitelist; if found, it is determined that the burning software has burning permissions; if no information about the burning software is found in either the burning software blacklist or the burning software whitelist, it is determined that the burning software does not have burning permissions.

[0061] Because the target files need to be kept confidential, only a limited number of designated burning software programs are allowed to burn the target files, or only internally developed special burning software is allowed. In other words, only burning software listed in the burning software whitelist is permitted. Information on commonly used burning software on the market is collected in advance, obtaining the corresponding application process names and application process paths, forming a burning software blacklist stored on server 21. This blacklist is updated periodically. When device 22 needs to use the burning software blacklist, it downloads the latest version from server 21 and writes it into the application layer as configuration information.

[0062] When the file monitoring mechanism in device 22 detects the burning software attempting to acquire a target file, it retrieves the burning software's information and searches for it in the burning software blacklist. If the burning software is found in the blacklist, it is confirmed that the software is a commonly used burning software on the market, cannot guarantee the confidentiality of the target file, and does not have burning permissions; therefore, the burning activity of the software is immediately blocked. If the burning software is not found in the blacklist, the system further searches for the burning software in the burning software whitelist.

[0063] If the burning software is found in the whitelist, it confirms that the burning software is one of the designated allowed burning software programs and has burning permissions, allowing it to burn the target file. If the burning software is not found in either the blacklist or the whitelist, it is confirmed that the burning software is unknown, its security cannot be confirmed, and it does not have burning permissions; therefore, the burning activity of the burning software should be immediately blocked. Device 22 can upload the burning software information to server 21, where relevant maintenance personnel will analyze the information and further update the blacklist and whitelist on server 21 to update the configuration information related to burning software permissions in the application layer of device 22.

[0064] This embodiment of the disclosure searches for information about the burning software in a blacklist. If found, the burning software is determined to lack burning permissions. It then searches for information in a whitelist. If found, the burning software is determined to have burning permissions. If neither the blacklist nor the whitelist is found, the burning software is determined to lack burning permissions. The blacklist is used to quickly block many common burning software programs from burning files, and the whitelist is used for secondary verification of the burning software's permissions. This maximizes the security of the burning software and prevents some powerful burning software from engaging in covert and unauthorized burning activities against the target file. This improves both the efficiency and security of the file burning method.

[0065] Figure 3 A flowchart of a file burning method provided in another embodiment of this disclosure is shown below. Figure 3 As shown, the method includes the following steps:

[0066] S301, Monitoring the operation of burning target files using burning software.

[0067] S302. Determine if the burning software has burning permissions. If yes, proceed to S303; otherwise, proceed to S307.

[0068] Specifically, the system searches for information about the burning software in the blacklist. If found, the burning software is determined to lack burning permissions. It also searches for information about the burning software in the whitelist. If found, the burning software is determined to have burning permissions. If no information about the burning software is found in either the blacklist or the whitelist, the burning software is determined to lack burning permissions.

[0069] For unknown burning software that cannot be found in either the burning software blacklist or the burning software whitelist, the relevant configuration information of the unknown burning software is obtained by querying the installation directory, and the relevant configuration information is written into the application layer, and the burning software blacklist is updated accordingly.

[0070] S303. Burn the target file using burning software and obtain relevant burning information during the burning process.

[0071] S304. Determine whether the burning information conforms to the preset rules. If yes, proceed to S305; otherwise, proceed to S307.

[0072] Specifically, the implementation process and principle of S301~S304 and S101~S103 are the same, and will not be repeated here.

[0073] S305. Report the relevant information about burning to the server so that the server can audit the relevant information about burning.

[0074] During the burning process, device 22 acquires relevant burning information and reports it to the server or server 21. Relevant personnel can audit the relevant burning information through the server, analyze user habits, or trace the source of burning behavior.

[0075] S306. Obtain the burning result.

[0076] After confirming that the burning software has burning permissions and that the burning information conforms to preset rules, the burning software is allowed to burn the target file. Once burning is complete, the burning result is obtained to indicate whether the burning was successful or failed, and the specific reason for failure. In reality, even if the burning software has burning permissions and the burning information conforms to preset rules, burning may still fail due to other objective reasons, such as the target file size exceeding the storage capacity of the disc to be burned. If burning is successful, the burning result for a successful burn is obtained; if burning fails, the burning result for a failed burn and the reason for the failure are obtained. The burning result and the reason for the failure are uploaded to server 21 for maintenance personnel to view and perform subsequent operations.

[0077] S307, Prevents burning software from burning target files.

[0078] Specifically, close the relevant processes of the burning software, or modify the information of the burning software.

[0079] When it is confirmed that the burning software does not have burning permissions, or that the burning-related information does not conform to preset rules, the burning software is immediately prevented from burning the target file to avoid leakage of important data. Specifically, device 22 can locate the burning software in the system's running process list based on configuration information pre-written in the application layer, and forcibly close the process to prevent the burning software from continuing to run; alternatively, device 22 can locate the relevant running files of the burning software through its information, and modify or delete one or more of these files, causing the burning software to malfunction; or device 22 can reduce the permissions of the burning software by changing the path file name corresponding to the burning software, thus preventing the software from running. Preferably, device 22 can upload information about burning software without burning permissions to server 21 for backup and storage in a blacklist, or notify maintenance personnel to update the burning software blacklist in a timely manner; device 22 can also upload burning-related information that does not conform to preset rules to server 21 for maintenance personnel to refer to and determine whether the preset rules need to be adjusted or optimized.

[0080] S308, End.

[0081] This embodiment of the disclosure monitors the burning operation of burning software on a target file; determines whether the burning software has burning permissions; burns the target file using the burning software and obtains burning-related information during the burning process; determines whether the burning-related information conforms to preset rules; prevents the burning software from burning the file; reports the burning-related information to the server so that the server can audit the burning-related information; obtains the burning result; and through the auditing and analysis of the burning-related information and the burning result, it statistically analyzes user habits to minimize the probability of burning failure, save burning materials, and ensure that the burning behavior can be traced, further improving the security and controllability of file burning.

[0082] Figure 4 This is a schematic diagram of the structure of a file burning device provided in an embodiment of this disclosure. The file burning device can be a computer running a Linux operating system as described in the above embodiment, or the file burning device can be a component or part of that computer. The file burning device provided in this embodiment of the disclosure can execute the processing flow provided in the file burning method embodiment, such as... Figure 4As shown, the file burning device 400 includes: a first judgment module 410, a processing module 420, a second judgment module 430, and a blocking module 440; wherein, the first judgment module 410 is used to determine whether the burning software has burning permissions based on the configuration information in the application layer when it detects the burning software's operation of burning a target file; the processing module 420 is used to burn the target file through the burning software if the burning software has burning permissions, and to obtain burning-related information during the burning process; the second judgment module 430 is used to determine whether the burning-related information conforms to preset rules; the blocking module 440 is used to prevent the burning software from burning the target file if the burning-related information does not conform to the preset rules.

[0083] Optionally, the first judgment module 410 is further configured to: search for information about the burning software in the burning software blacklist; if found, determine that the burning software does not have burning permissions; search for information about the burning software in the burning software whitelist; if found, determine that the burning software has burning permissions; if the information about the burning software is not found in either the burning software blacklist or the burning software whitelist, determine that the burning software does not have burning permissions.

[0084] Optionally, the blocking module 440 is further configured to prevent the burning software from burning the target file if the burning software does not have burning permissions.

[0085] Optionally, the blocking module 440 can also be used to close the relevant processes of the burning software, or to modify the information of the burning software.

[0086] Optionally, the file burning device 400 further includes a reporting module 450, used to report the burning-related information to the server so that the server can audit the burning-related information.

[0087] Figure 4 The file burning device shown in the embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effect are similar, and will not be repeated here.

[0088] Figure 5 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this disclosure, such as... Figure 5 As shown, the electronic device includes:

[0089] One or more processors 501, Figure 5 Take the 501 processor as an example;

[0090] Memory 502;

[0091] The electronic device may further include an input device 503 and an output device 504.

[0092] The processor 501, memory 502, input device 503, and output device 504 in the electronic device can be connected via a bus or other means. Figure 5 Taking the example of a connection between China and Israel via a bus.

[0093] Memory 502, as a non-transitory computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the file burning method in the embodiments of this disclosure (e.g., appendix). Figure 4 The first judgment module 410, processing module 420, second judgment module 430, blocking module 440, and reporting module 450 are shown. The processor 501 executes various functions and data processing of the server by running software programs, instructions, and modules stored in the memory 502, thereby implementing the file burning method of the above method embodiment.

[0094] Memory 502 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the electronic device. Furthermore, memory 502 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 502 may optionally include memory remotely located relative to processor 501, and these remote memories can be connected to the terminal device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0095] Input device 503 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the electronic device. Output device 504 may include display devices such as a display screen.

[0096] This disclosure also provides a computer-readable storage medium storing a program or instructions that, when executed by a computer, are used to perform a file burning method, the method comprising:

[0097] When the burning operation of the burning software is detected, it is determined whether the burning software has burning permissions;

[0098] If the burning software has burning permissions, the target file is burned using the burning software, and relevant burning information is obtained during the burning process.

[0099] Determine whether the recorded information conforms to preset rules;

[0100] If the burning information does not conform to the preset rules, the burning software will be prevented from burning the target file.

[0101] Optionally, when executed by a computer processor, the computer-executable instructions can also be used to execute the technical solutions of the file burning methods provided in any embodiment of this disclosure.

[0102] Based on the above description of the implementation methods, those skilled in the art will clearly understand that this disclosure can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this disclosure.

[0103] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0104] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A file burning method, characterized in that, The method, applied to the application layer of the Linux operating system, includes: When the burning operation of the burning software to burn the target file is detected by the inotify mechanism, it is determined whether the burning software has burning permission according to the configuration information in the application layer. The burning operation of the burning software to burn the target file includes the action of the burning software to obtain the target file image file. If the burning software has burning permissions, the target file is burned using the burning software, and burning-related information during the burning process is obtained. The burning-related information includes the target file's file name, file path, file size, file type, file creation time, MD5 information, number of burning attempts, file burning time, and file burning method. Determine whether the recorded information conforms to preset rules; If the burning-related information does not conform to the preset rules, the burning software will be prevented from burning the target file; The determination of whether the burning-related information conforms to preset rules includes: if the burning-related information conforms to a certain preset rule, continuing to determine whether the burning-related information conforms to the next preset rule, until it is confirmed that the burning-related information conforms to any preset rule, and the burning-related information conforms to the preset rule; or, confirming that the burning-related information does not conform to any preset rule, and the burning-related information does not conform to the preset rule.

2. The method according to claim 1, characterized in that, Determining whether the burning software has burning permissions based on the configuration information in the application layer includes: Search for the information of the burning software in the blacklist of burning software. If the information is found, it is determined that the burning software does not have burning permissions. Search for the information of the burning software in the whitelist of burning software. If it is found, it is determined that the burning software has burning permissions. If the burning software is not found in either the burning software blacklist or the burning software whitelist, then the burning software is determined to lack burning permissions.

3. The method according to claim 1, characterized in that, After determining whether the burning software has burning permissions, the method further includes: If the burning software does not have burning permissions, then the burning software is prevented from burning the target file.

4. The method according to claim 1 or 3, characterized in that, The method of preventing the burning software from burning the target file includes: Close the relevant processes of the burning software, or modify the information of the burning software.

5. The method according to claim 1 or 3, characterized in that, After preventing the burning software from burning the target file, the method further includes: The burning-related information is reported to the server so that the server can audit the burning-related information.

6. A file burning device, characterized in that, The device is located in the application layer of the Linux operating system, and the device includes: The first judgment module is used to determine whether the burning software has burning permissions based on the configuration information in the application layer when the burning software is detected to be burning a target file through the inotify mechanism. The burning software's operation of burning a target file includes the burning software's action of obtaining a target file image file. The processing module is used to burn the target file through the burning software when the burning software has burning permissions, and to obtain burning-related information during the burning process of the burning software. The burning-related information includes the target file's file name, file path, file size, file type, file creation time, MD5 information, number of burning attempts, file burning time, and file burning method. The second judgment module is used to determine whether the burning-related information conforms to preset rules; The blocking module is used to prevent the burning software from burning the target file if the burning-related information does not conform to preset rules; Specifically, the second judgment module is used to determine whether the burning-related information conforms to the next preset rule if the burning-related information conforms to a certain preset rule, until it is confirmed that the burning-related information conforms to any preset rule; or, it is confirmed that the burning-related information does not conform to any preset rule.

7. The apparatus according to claim 6, characterized in that, The blocking module is also used to prevent the burning software from burning the target file if the burning software does not have burning permissions.

8. The apparatus according to claim 6 or 7, characterized in that, The device further includes: The reporting module is used to report the burning-related information to the server so that the server can audit the burning-related information.

9. An electronic device, characterized in that, include: Memory; processor; as well as Computer programs; The computer program is stored in the memory and configured to be executed by the processor to implement the method as described in any one of claims 1-5.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-5.

Images