CN119376805A - File control method, device, equipment and storage medium - Google Patents

File control method, device, equipment and storage medium Download PDF

Info

Publication number
CN119376805A
CN119376805A CN202310883995.XA CN202310883995A CN119376805A CN 119376805 A CN119376805 A CN 119376805A CN 202310883995 A CN202310883995 A CN 202310883995A CN 119376805 A CN119376805 A CN 119376805A
Authority
CN
China
Prior art keywords
file
started
installation package
package file
executable
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
Application number
CN202310883995.XA
Other languages
Chinese (zh)
Inventor
杨光
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Shizhen Information Technology Co Ltd
Original Assignee
Guangzhou Shizhen Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Guangzhou Shizhen Information Technology Co Ltd filed Critical Guangzhou Shizhen Information Technology Co Ltd
Priority to CN202310883995.XA priority Critical patent/CN119376805A/en
Publication of CN119376805A publication Critical patent/CN119376805A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

本申请公开了一种文件管控方法、装置、设备及存储介质，涉及计算机技术领域。本申请提供的技术方案包括：响应于文件启动操作，在文件启动操作对应的待启动文件为可执行文件的情况下，检测待启动文件为安装包文件或非安装包文件；在待启动文件为安装包文件的情况下，将待启动文件的文件特征与预设的目标安装包文件的文件特征进行匹配；在文件特征相匹配的情况下，禁止启动待启动文件；在待启动文件为非安装包文件或文件特征不匹配的情况下，启动待启动文件。通过上述技术手段，以解决现有技术中缺少管控待安装的安装包文件的环节的问题，提高了用户误操作的容错性。

The present application discloses a file management method, device, equipment and storage medium, and relates to the field of computer technology. The technical solution provided by the present application includes: in response to a file startup operation, when the file to be started corresponding to the file startup operation is an executable file, detecting whether the file to be started is an installation package file or a non-installation package file; when the file to be started is an installation package file, matching the file characteristics of the file to be started with the file characteristics of the preset target installation package file; when the file characteristics match, prohibiting the startup of the file to be started; when the file to be started is a non-installation package file or the file characteristics do not match, starting the file to be started. Through the above-mentioned technical means, the problem of the lack of links in the prior art for controlling the installation package files to be installed is solved, and the fault tolerance of user misoperation is improved.

Description

File management and control method, device, equipment and storage medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for file management and control.
Background
With the rapid development of computer technology, the installation process of application software is simpler and faster, and the computer can complete the installation of the corresponding application program based on the installation package file only by starting the installation package file for running the application program on the computer.
Although the quick installation of the application program brings great convenience to users, the fault tolerance of misoperation of the users is reduced due to the lack of links for controlling the installation package files to be installed. For example, an enterprise does not want staff to install some messy software on the enterprise computer, when a user mistakenly starts an installation package file of the messy software, the messy software can be quickly installed on the computer, so that the user needs to spend time to uninstall the messy software from the computer, otherwise, the messy software occupies the memory of the enterprise computer, and the use and performance of the enterprise computer are affected. Therefore, a technical solution for controlling an application program to be installed on a computer is needed.
Disclosure of Invention
The application provides a file management and control method, device, equipment and storage medium, which are used for solving the problem that links for managing and controlling an installation package file to be installed are lacked in the prior art, and improving the fault tolerance of misoperation of a user.
In a first aspect, the present application provides a method for managing and controlling files, including:
Responding to a file starting operation, and detecting whether a file to be started is an installation package file or not under the condition that the file to be started corresponding to the file starting operation is an executable file;
Under the condition that the file to be started is an installation package file, matching the file characteristics of the file to be started with the file characteristics of a preset target installation package file;
under the condition that the file characteristics are matched, prohibiting starting the file to be started;
And starting the file to be started under the condition that the file to be started is a non-installation package file or the file characteristics are not matched.
In a second aspect, the present application provides a file management and control apparatus, including:
the installation package detection module is configured to respond to file starting operation, and detect whether a file to be started is an installation package file or not under the condition that the file to be started corresponding to the file starting operation is an executable file;
The feature matching module is configured to match the file features of the file to be started with the file features of a preset target installation package file under the condition that the file to be started is the installation package file;
The first file processing module is configured to prohibit starting the file to be started under the condition that the file characteristics are matched;
And the second file processing module is configured to start the file to be started under the condition that the file to be started is a non-installation package file or the file characteristics are not matched.
In a third aspect, the present application provides a file management and control apparatus, including:
One or more processors;
A memory storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the file management method as described in the first aspect.
In a fourth aspect, the present application provides a storage medium containing computer executable instructions which, when executed by a computer processor, are used to perform the file management method according to the first aspect.
In the application, when a user inputs a file starting operation to a computer, the file starting operation is responded, and whether the file to be started is an installation package file is detected under the condition that the file to be started corresponding to the file starting operation is determined to be an executable file. And if the file characteristics of the two files are matched, the file to be started is the installation package file of the application program which is forbidden to be installed by the computer or is not wanted to be installed by the user, so that the file to be started is forbidden to be started. If the file characteristics of the two files are not matched, the file to be started is an installation package file of an application program which can be installed on the computer or the user wants to install, so that the file to be started can be normally started so that the computer can run a process of installing the corresponding application program. By the technical means, when a user inputs a file starting operation, the file to be started is controlled, and the installation operation of the target installation package file is intercepted in time, so that the situation that a computer installs an application program which the user does not want to install or prohibits to install is avoided, and the fault tolerance of misoperation of the user is improved. For the starting operation of other non-target installation package files, the computer responds in time to ensure that the installed application program can normally run, the uninstalled application program can normally install, the non-executable file can normally open, and the running reliability of the computer is ensured.
Drawings
FIG. 1 is a flowchart of a method for managing and controlling files according to an embodiment of the present application;
FIG. 2 is a flowchart of determining whether a file to be started is an installation package file or a non-installation package file according to a file feature provided by an embodiment of the present application;
FIG. 3 is a flowchart of determining, by a header portion, whether a file to be started is an installation package file or a non-installation package file according to an embodiment of the present application;
FIG. 4 is a flowchart of determining whether a file to be started is an installation package file or a non-installation package file according to a resource file provided by an embodiment of the present application;
FIG. 5 is a flow chart of determining whether a file to be started is an installation package file or a non-installation package file by previewing content;
FIG. 6 is a flowchart of an installation package file detection process provided by an embodiment of the present application;
FIG. 7 is a schematic diagram of a file management and control apparatus according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a file management and control device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the following detailed description of specific embodiments of the present application is given with reference to the accompanying drawings. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the matters related to the present application are shown in the accompanying drawings. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart depicts operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently, or at the same time. Furthermore, the order of the operations may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figures. The processes may correspond to methods, functions, procedures, subroutines, and the like.
The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged, as appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the objects identified by "first," "second," etc. are generally of a type, and are not limited to the number of objects, such as the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.
In a more common existing implementation manner, for an installation package file of an uninstalled application program, when a user starts the installation package file, a computer can start to operate an operation of installing the application program, and the installation operation is very convenient. Although the quick installation of the application program brings great convenience to users, the fault tolerance of misoperation of the users is reduced due to the lack of links for controlling the installation package files to be installed. For example, an enterprise does not want staff to install entertainment software such as games or video applications, cluttered software and software developed by competitors on the enterprise computer, but after a user may start the installation package of the software by mistake, the software may be quickly installed on the computer, so that the user needs to take time to uninstall the cluttered software from the computer, otherwise, the cluttered software occupies the memory of the enterprise computer, and affects the use and performance of the enterprise computer.
In order to solve the above problems, the present embodiment provides a file management and control method, so as to solve the problem in the prior art that a link for managing and controlling an installation package file to be installed is not available, and improve the fault tolerance of misoperation of a user.
The file management and control method provided in this embodiment may be executed by a file management and control device, where the file management and control device may be implemented by software and/or hardware, and the file management and control device may be configured by two or more physical entities or may be configured by one physical entity. For example, the file management apparatus may be a computer.
The file management and control device is provided with at least one type of operating system, wherein the operating system comprises, but is not limited to, an android system, a Linux system and a Windows system. The file management and control device may install at least one application program based on the operating system, where the application program may be an application program carried by the operating system, or may be an application program downloaded from a third party device or a server. In one embodiment, the file management apparatus may be provided with an application program that performs the file management method.
For ease of understanding, this embodiment will be described using a computer as a main body for executing the file management method.
Fig. 1 shows a flowchart of a file management and control method according to an embodiment of the present application. Referring to fig. 1, the file management and control method specifically includes:
s110, responding to the file starting operation, and detecting whether the file to be started is an installation package file or not under the condition that the file to be started corresponding to the file starting operation is an executable file.
The file starting operation refers to an operation for starting a file input by a user, the file starting operation may be a file clicking operation or a file clicking operation, and the files mentioned in this embodiment include non-executable files such as pictures, documents, video or audio that cannot be loaded by an operating system, and executable files that can be loaded and executed by the operating system, that is, files accessible on a computer may be regarded as files that can be started by the file starting operation.
The file to be started refers to a file which is started correspondingly by the file starting operation. Because the installation package file is an executable file directly loaded and executed by the operating system, when the file to be started is a non-executable file which cannot be directly loaded by the operating system, such as a picture, a document, video or audio, the file to be started can be confirmed to be a non-installation package file, and then the computer can start the file to be started so as to open the content of the picture, the document, the video or audio, and the like for a user to view.
The installation package file is an executable file, but not all executable files are installation package files, such as whether an executable file may be a dynamic library, a kernel file, and an application program that has completed installation. Therefore, when the file to be started is determined to be the executable file, whether the file to be started is an installation package file or not can be further detected.
In one embodiment, the content stored in the address space corresponding to the header of the executable file and the header of the non-executable file are different, and the file to be started is judged to be the executable file or the non-executable file according to the content stored in the address space corresponding to the header of the file to be started. In an exemplary embodiment, the file to be started is determined to be an executable file under the condition that the file header of the file to be started is confirmed to store the identification information of the executable file in the address space corresponding to the file header. It should be noted that the Executable files executed by different operating systems are different in structure, and for a Windows system, the Executable files are in a PE (Portable Executable, portable Executable Format) file structure, and for a Linux system, the Executable files are in an ELF (Executable and linking Format) file structure. The executable files with different structures have different file header corresponding to the address space and different stored identification information, and in this embodiment, the operating system is a Windows system, and the executable files are PE files. The first two bytes of the PE file head store one address information, the storage space corresponding to the address information stores 'MZ', the offset 0x3c bytes of the file head of the executable file store one address information, and the storage space corresponding to the address information stores 'PE'. Therefore, when the address space corresponding to the first two bytes of the file header of the file to be started and the offset 0x3c bytes is searched to store "MZ" and "PE", the file to be started can be confirmed as an executable file, otherwise, the file to be started is confirmed as a non-executable file.
The embodiment of the application provides a plurality of detection modes for judging whether the file to be started is an installation package file or not so as to respectively judge from the file characteristics, the file size, the file structure and the file preview content of the file to be started, thereby improving the accuracy of the detection of the installation package file.
In one embodiment, the file to be started is detected to be an installation package file or a non-installation package file, and specifically, the file to be started can be judged to be the installation package file or the non-installation package file through the file characteristics of the file to be started. As shown in fig. 2, the step of determining, according to the file characteristics, that the file to be started is an installation package file or a non-installation package file specifically includes S1101-S1103:
s1101, extracting file characteristics of a file to be started, wherein the file characteristics comprise at least one of file names, file signatures and product names.
S1102, determining the file to be started as the installation package file under the condition that the file characteristics of the file to be started are matched with the file characteristics of the installation package file in a preset false detection list.
S1103, determining the file to be started as a non-installation package file under the condition that the file characteristics of the file to be started are matched with the file characteristics of the non-installation package file in a preset false detection list.
The false detection list is generated based on a file in which an error occurs in the previous detection result, for example, when the computer erroneously recognizes the installation package file a as a non-installation package file, the installation package file a may be saved in the false detection list, or when the computer erroneously recognizes the non-installation package file B as an installation package file, the installation package file B may be saved in the false detection list. When the file characteristics of the file to be started are matched with the characteristics of the non-installation file B in the false detection list, the file to be started is indicated to be the non-installation package file B, and therefore the file to be started can be determined to be the non-installation package file. When the file characteristics of the file to be started are not matched with the file characteristics of any file in the false detection list, whether the file to be started is an installation package file or a non-installation package file cannot be confirmed, and the judgment can be carried out by matching with other detection modes. It can be understood that the files in the false detection list are files with higher detection difficulty and lower detection accuracy, and in the embodiment, the file characteristics of the files to be started are matched with the file characteristics of each file in the false detection list, so that the installation package files or the non-installation package files which are difficult to detect are screened out, and the accuracy of detection of the installation package is improved.
In one embodiment, the file to be started is detected to be an installation package file or a non-installation package file, and specifically, the file to be started can be judged to be an installation package file or a non-installation package file through a header part in a file structure of the file to be started. As shown in fig. 3, the step of determining, by the header portion, that the file to be started is an installation package file or a non-installation package file specifically includes S1104 to S1105:
s1104, acquiring a subsystem value of the file to be started according to the header part of the file to be started.
S1105, determining that the file to be started is a non-installation package file under the condition that the subsystem value of the file to be started is not the subsystem value corresponding to the image user interface.
Illustratively, the Header portion of the PE file is a PE Header (PE Header), which is stored in the trailing portion of the Dos Header. The Subsystem (Subsystem) field in the header portion of the PE file stores a Subsystem value of the corresponding PE file, the Subsystem value characterizing the Subsystem of the PE file designated for use interface, the optional subsystems being CUI (command line interface) and GUI (graphical user interface) in the Windows system, and the Subsystem values in the header portion of the PE file including CUI Subsystem and GUI Subsystem, respectively. When the Subsystem value of the file to be started is CUI Subsystem, the designated use interface of the file to be started can be determined to be a command line interface, and when the Subsystem value of the file to be started is GUI Subsystem, the designated use interface of the file to be started can be determined to be a graphical user interface. For the installation package file of the application program, the application program designates the use image user interface, and when the file to be started designates the use interface as a command line interface, the file to be started can be determined to be a non-installation package file. However, other executable file designated usage interfaces besides the installation package file may be graphical user interfaces, i.e., the present embodiment cannot determine that the file to be started is an installation package file, but may be used to quickly filter some non-installation package files. After determining that the Subsystem value of the file to be started is the GUI Subsystem, the file to be started can be further judged to be a non-installation package file or an installation package file by being matched with other detection modes.
In one embodiment, the file to be started is detected to be an installation package file or a non-installation package file, and specifically, the file to be started can be judged to be an installation package file or a non-installation package file through a resource file in a file structure of the file to be started. As shown in fig. 4, the step of determining, by the resource file, that the file to be started is an installation package file or a non-installation package file specifically includes S1106-S1107:
S1106, according to the resource file of the file to be started, acquiring the name of the resource file.
S1107, under the condition that the name of the resource file is matched with a preset package name, determining that the file to be started is an installation package file, wherein the package name is the name of the resource file of the installation package file generated based on the corresponding package software package.
The resource file refers to a manifest resource file with a resource type of rt_ MANIFEST, and the manifest resource file stores description information about a corresponding PE file. The installation package file is generated by packaging a series of files such as executable files, texts, pictures and the like by packaging software, and the name (name value) of the manifest resource file of the installation package file correspondingly characterizes which packaging software packages the installation package file to generate. Because the non-installation package file is not packaged by the packaging software, the name of the manifest resource file of the non-installation package file is not the packaging name corresponding to the packaging software, and therefore whether the PE file is the installation package file can be determined based on whether the name of the manifest resource file of the PE file is matched with the packaging name corresponding to the preset packaging software. Table 1 is packing software and corresponding packing names provided by the embodiment of the present application.
TABLE 1
Packaging software Packing name
Inno Setup JR.Inno.Setup
NSIS Nullsoft.NSIS.exehead
MSP setup.exe
InstallShield InstallShield.Setup
As shown in table 1, when the name of the manifest resource file in the file to be started is jr.ino.setup, nullsoft.nsis.exehead, setup.exe, or installshield.setup, the file to be started is confirmed to be an installation package file. However, since the existing package software is more, it is difficult to list package names corresponding to all package software in an actual detection process to match the names of the manifest resource files in the files to be started, that is, when the names of the manifest resource files in the files to be started are not preset package names, it is impossible to determine whether the files to be started are installation package files or non-installation package files, and the files to be started can be detected in cooperation with other detection modes. It should be noted that most of the existing installation packages are generated based on several common packaging software, so that the accuracy of detecting the file to be started based on the name of the manifest resource file provided by the embodiment can reach 95%, and the preview content of the file to be started does not need to be analyzed, so that the detection speed is high.
In one embodiment, the file to be started is detected to be an installation package file or a non-installation package file, and specifically, the file to be started can be judged to be the installation package file or the non-installation package file according to the file size of the file to be started. The file size refers to the size of the storage space occupied by the corresponding file. In an exemplary embodiment, the file to be started is determined to be an installation package file when the file size of the file to be started is greater than or equal to a preset size threshold. It will be appreciated that the file size of the non-installation package file is small, and thus the present embodiment sets the size threshold to the maximum size of the non-installation package file, which is typically set to 500M. When the file size of the file to be started is larger than 500M, the file to be started can be determined to be an installation package file. However, the file size of the partial installation package file and the file size of the non-installation package file are almost the same, when the file size of the file to be started is smaller than 500M, the file to be started cannot be determined to be the installation package file or the non-installation package file, and the judgment can be carried out in cooperation with other detection modes.
In one embodiment, the file to be started is detected to be an installation package file or a non-installation package file, and specifically, the file to be started can be judged to be the installation package file or the non-installation package file through the preview content of the file to be started. As shown in fig. 5, the step of determining whether the file to be started is an installation package file or a non-installation package file through the preview content specifically includes S1108-S1110:
s1108, obtaining preview content of the file to be started through preset decompression software.
S1109, determining that the file to be started is a non-installation package file in the case that the preview content comprises a preset block structure.
S1110, determining that the file to be started is an installation package file under the condition that the preview content does not comprise a preset block structure.
Illustratively, the installation package file is manufactured by compressing the resource file of the application program by a compression algorithm, and then converting the compressed file into a PE file. The non-installation package file is generated through four processes of preprocessing, compiling, assembling and linking, wherein the non-installation package file can generate text blocks, data blocks, rsrc blocks, reloc blocks and rdata blocks. Therefore, the decompressed preview content of the installation package file and the decompressed non-installation package file are different, the decompressed preview content of the non-installation package file comprises text blocks, data blocks, rsrc blocks, reloc blocks and rdata blocks, and the installation package file does not comprise the block structures. When the preview content of the file to be started comprises a text block, a data block, a rsrc block, a reloc block and a rdata block, the file to be started can be determined to be a non-installation package file, and when the preview content of the file to be started does not comprise the text block, the data block, the rsrc block, the reloc block and the rdata block, the file to be started can be determined to be an installation package file. Compared with other detection modes, the detection mode described in the embodiment judges the file to be started from the file preview content which most reflects the file type, so that the accuracy of detecting the installation package file is improved. Because the embodiment needs to decompress the file to be started, the detection speed is low, the file to be started can be initially screened in other detection modes, and finally accurate judgment is performed based on the preview content of the file to be started, so that the detection accuracy is ensured while the detection efficiency is optimized.
In one embodiment, the method for detecting the file characteristics of the file to be started, the method for detecting the header part in the file structure of the file to be started, the method for detecting the resource file in the file structure of the file to be started, the method for detecting the file size of the file to be started and the method for detecting the preview content of the file to be started, which are provided in the above embodiments, may be combined to perform comprehensive detection on the file to be started. For example, a detection mode based on a file feature of the file to be started, a detection mode based on a header part in a file structure of the file to be started, a detection mode based on a resource file in the file structure of the file to be started, a detection mode based on a file size of the file to be started, and a detection mode based on a preview content of the file to be started may be sequentially operated to determine that the file to be started is an installation package file or a non-installation package file. As shown in fig. 6, the computer reads the identification information of the address space corresponding to the header of the file to be started through the installation package detection program, and judges whether the file to be started belongs to the executable file according to the identification information. Under the condition that the file to be started belongs to the executable file, extracting the file characteristics of the file to be started, sending the extracted file characteristics to the background for false detection list matching, and obtaining a matching result returned by the background. If the matching result is matched with the installation package file in the false detection list, determining that the file to be started is the installation package file, and if the matching result is matched with the non-installation package file in the false detection list, determining that the file to be started is the non-installation package file. If the matching result is not matched with any file in the false detection list, acquiring a subsystem value of the head part of the file to be started. In the case where the Subsystem value is not GUI Subsystem, it is determined that the file to be started is a non-installation package file. And under the condition that the Subsystem value is GUI Subsystem, acquiring the name of the manifest resource file from the manifest resource file of the file to be started, and under the condition that the name of the manifest resource file is matched with the preset package name, determining the file to be started as an installation package file. Under the condition that the name of the manifest resource file is not matched with the preset package name, if the file size of the file to be started is larger than 500M, the file to be started can be determined to be an installation package file. If the file size of the file to be started is smaller than or equal to 500M, the decompression software can be used for acquiring the preview content of the file to be started, the file to be started is determined to be a non-installation package file under the condition that the preview content comprises a preset block structure, and the file to be started is determined to be an installation package file under the condition that the preview content does not comprise the preset block structure.
In another embodiment, the file to be started may be detected by combining any two detection modes of the multiple detection modes provided in the above embodiment. For example, the judgment can be performed based on the subsystem value of the file to be started, and then the judgment is performed by the name of the manifest resource file of the file to be started and/or by the preview content of the file to be started, so that the judgment logic of the file to be started is reduced, the detection efficiency is improved, and the detection accuracy is ensured. In yet another embodiment, the file to be started may be detected by combining any three detection modes of the multiple detection modes provided in the foregoing embodiment. For example, the method may first determine based on a subsystem value of the file to be started, then determine the file to be started by a name of a manifest resource file of the file to be started, and finally determine by preview content of the file to be started. In yet another embodiment, the file to be started may be detected in combination with any four detection modes of the multiple modes in the foregoing embodiment.
In an embodiment, the computer may store the detection result of each file to be started through the background monitoring system, and if the user finds that the detection result of a certain file to be started has an error through the background monitoring system, the file to be started may be manually stored in the error detection list in an accurate file type, so that the computer may accurately detect that the file to be started is an installation package file or a non-installation package file next time.
And S120, matching the file characteristics of the file to be started with the file characteristics of a preset target installation package file under the condition that the file to be started is the installation package file.
The target installation package file refers to an installation package file for prohibiting an application program installed on a computer, and is generally configured in advance by a user. When the file to be started is determined to be the installation package file, the file characteristics of the file to be started and the file characteristics of the target installation package file can be matched so as to further judge whether the file to be started is the installation package file of the application program which is forbidden to be installed on the computer.
S130, under the condition that the file characteristics are matched, the starting of the file to be started is forbidden.
If the file characteristics of the file to be started are matched with the file characteristics of the target installation package file, the file to be started can be determined to be the installation package file of the application program which is forbidden to be installed on the computer, so that the file to be started is forbidden to be started, and the installation of the corresponding application program of the computer is avoided. In this embodiment, the file characteristics include at least one of a file name, a file signature, and a product name, and the file name, the file signature, and/or the product name of the file to be started may be compared with the file name, the file signature, and/or the product name of the target installation package file to determine whether the file to be started matches the file characteristics of the target installation package file.
And S140, starting the file to be started under the condition that the file to be started is a non-installation package file or the file characteristics are not matched.
If the file to be started is a non-installation package file, it can be determined that the file to be started is not an installation package file for prohibiting the application program installed on the computer, and the file to be started can be started at this time so as to ensure that the computer normally runs executable files such as a dynamic library, a kernel file or other installed application programs. Similarly, if the file characteristics of the file to be started are not matched with the file characteristics of the target installation package file, it can be determined that the file to be started is not an installation package file for prohibiting the application program installed on the computer, and the file to be started can be started at this time so as to ensure that the computer can install installation package files except the target installation package file.
It should be noted that, in the embodiment of the present application, whether the file to be started is the installation package file is first determined, instead of directly matching the file characteristics of the file to be started with the file characteristics of the target installation package file, because the file to be started may also be a non-executable file, an executable file of the application program that has been installed, or other types of executable files such as a dynamic library, a kernel file, etc. If the file characteristics of the files and the target installation package file belong to the same provider, the file characteristics of the files and the file characteristics of the target installation package file may be matched, so that the computer cannot execute operations of opening non-executable files or other executable files of running the application programs which are installed completely, and normal running of the computer is affected. Therefore, the embodiment of the application can only prohibit the start of the installation package file matched with the file characteristics of the target installation package file by judging whether the file to be started is the installation package file or not, thereby ensuring the operation reliability of the computer.
In summary, according to the file management and control method provided by the embodiment of the application, when a user inputs a file starting operation to a computer, the file starting operation is responded, and whether the file to be started is an installation package file is detected under the condition that the file to be started corresponding to the file starting operation is determined to be an executable file. And if the file characteristics of the two files are matched, the file to be started is the installation package file of the application program which is forbidden to be installed by the computer or is not wanted to be installed by the user, so that the file to be started is forbidden to be started. If the file characteristics of the two files are not matched, the file to be started is an installation package file of an application program which can be installed on the computer or the user wants to install, so that the file to be started can be normally started so that the computer can run a process of installing the corresponding application program. By the technical means, when a user inputs a file starting operation, the file to be started is controlled, and the installation operation of the target installation package file is intercepted in time, so that the situation that a computer installs an application program which the user does not want to install or prohibits to install is avoided, and the fault tolerance of misoperation of the user is improved. For the starting operation of other non-target installation package files, the computer responds in time to ensure that the installed application program can normally run, the uninstalled application program can normally install, the non-executable file can normally open, and the running reliability of the computer is ensured.
On the basis of the above embodiment, fig. 7 is a schematic structural diagram of a file management and control device according to an embodiment of the present application. Referring to fig. 7, the file management and control apparatus provided in this embodiment specifically includes an installation package detection module 21, a feature matching module 22, a first file processing module 23, and a second file processing module 24.
The installation package detection module is configured to respond to the file starting operation, and detect that the file to be started is an installation package file or a non-installation package file under the condition that the file to be started corresponding to the file starting operation is an executable file;
The feature matching module is configured to match the file features of the file to be started with the file features of a preset target installation package file under the condition that the file to be started is the installation package file;
the first file processing module is configured to prohibit starting of the file to be started under the condition that the file characteristics are matched;
And the second file processing module is configured to start the file to be started under the condition that the file to be started is a non-installation package file or the file characteristics are not matched.
On the basis of the embodiment, the installation package detection module comprises an executable file confirmation unit, a file start unit and a package start unit, wherein the executable file confirmation unit is configured to detect that the file to be started is an installation package file or a non-installation package file under the condition that identification information of the executable file is stored in a file head corresponding address space of the file to be started.
On the basis of the embodiment, the installation package detection module comprises a feature extraction unit, a first judgment unit and a second judgment unit, wherein the feature extraction unit is configured to extract file features of files to be started, the file features comprise at least one of file names, file signatures and product names, the first judgment unit is configured to determine that the files to be started are installation package files when the file features of the files to be started are matched with the file features of the installation package files in a preset false detection list, and the second judgment unit is configured to determine that the files to be started are non-installation package files when the file features of the files to be started are matched with the file features of the non-installation package files in the preset false detection list.
On the basis of the embodiment, the installation package detection module comprises a subsystem value acquisition unit and a third judgment unit, wherein the subsystem value acquisition unit is configured to acquire the subsystem value of the file to be started according to the header part of the file to be started, and the third judgment unit is configured to determine that the file to be started is a non-installation package file under the condition that the subsystem value of the file to be started is not the subsystem value corresponding to the image user interface.
On the basis of the embodiment, the installation package detection module comprises a resource file name acquisition unit and a fourth judgment unit, wherein the resource file name acquisition unit is configured to acquire the name of a resource file according to the resource file of the file to be started, the fourth judgment unit is configured to determine that the file to be started is an installation package file when the name of the resource file is matched with a preset package name, and the package name is the name of the resource file of the installation package file generated based on the corresponding package software package.
On the basis of the embodiment, the installation package detection module comprises a fifth judging unit, wherein the fifth judging unit is configured to determine that the file to be started is an installation package file under the condition that the file size of the file to be started is larger than a preset size threshold.
On the basis of the embodiment, the installation package detection module comprises a preview content acquisition unit, a sixth judgment unit and a seventh judgment unit, wherein the preview content acquisition unit is configured to acquire the preview content of the file to be started through preset decompression software, the sixth judgment unit is configured to determine that the file to be started is a non-installation package file when the preview content comprises a preset block structure, and the seventh judgment unit is configured to determine that the file to be started is an installation package file when the preview content does not comprise the preset block structure.
In the above, according to the file management and control device provided by the embodiment of the present application, when a user inputs a file starting operation to a computer, in response to the file starting operation, if it is determined that a file to be started corresponding to the file starting operation is an executable file, whether the file to be started is an installation package file is detected. And if the file characteristics of the two files are matched, the file to be started is the installation package file of the application program which is forbidden to be installed by the computer or is not wanted to be installed by the user, so that the file to be started is forbidden to be started. If the file characteristics of the two files are not matched, the file to be started is an installation package file of an application program which can be installed on the computer or the user wants to install, so that the file to be started can be normally started so that the computer can run a process of installing the corresponding application program. By the technical means, when a user inputs a file starting operation, the file to be started is controlled, and the installation operation of the target installation package file is intercepted in time, so that the situation that a computer installs an application program which the user does not want to install or prohibits to install is avoided, and the fault tolerance of misoperation of the user is improved. For the starting operation of other non-target installation package files, the computer responds in time to ensure that the installed application program can normally run, the uninstalled application program can normally install, the non-executable file can normally open, and the running reliability of the computer is ensured.
The file management and control device provided by the embodiment of the application can be used for executing the file management and control method provided by the embodiment, and has corresponding functions and beneficial effects.
Fig. 8 is a schematic structural diagram of a file management apparatus according to an embodiment of the present application, and referring to fig. 8, the file management apparatus includes a processor 31, a memory 32, a communication device 33, an input device 34, and an output device 35. The number of processors 31 in the file managing apparatus may be one or more, and the number of memories 32 in the file managing apparatus may be one or more. The processor 31, memory 32, communication means 33, input means 34 and output means 35 of the file managing apparatus may be connected by bus or other means.
The memory 32 is a computer readable storage medium, and may be used to store a software program, a computer executable program, and modules, such as program instructions/modules (e.g., the installation package detection module 21, the feature matching module 22, the first file processing module 23, and the second file processing module 24 in the file management apparatus) corresponding to the file management method according to any embodiment of the present application. The memory 32 may mainly include a storage program area that may store an operating system, application programs required for at least one function, and a storage data area that may store data created according to the use of the device, etc. In addition, memory 32 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some examples, the memory may further include memory remotely located with respect to the processor, the remote memory being connectable to the device through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The communication means 33 are for data transmission.
The processor 31 executes various functional applications of the device and data processing, i.e., implements the file management method described above, by running software programs, instructions, and modules stored in the memory 32.
The input means 34 may be used to receive entered numeric or character information and to generate key signal inputs related to user settings and function control of the device. The output means 35 may comprise a display device such as a display screen.
The file management and control device provided by the embodiment can be used for executing the file management and control method provided by the embodiment, and has corresponding functions and beneficial effects.
The embodiment of the application also provides a storage medium containing computer executable instructions, which are used for executing a file management and control method when being executed by a computer processor, wherein the file management and control method comprises the steps of responding to a file starting operation, and detecting that a file to be started is an installation package file or a non-installation package file under the condition that the file to be started corresponding to the file starting operation is an executable file; the method comprises the steps of matching file characteristics of a file to be started with file characteristics of a preset target installation package file when the file to be started is an installation package file, prohibiting starting the file to be started when the file characteristics are matched, and starting the file to be started when the file to be started is a non-installation package file or the file characteristics are not matched.
Storage media-any of various types of memory devices or storage devices. The term "storage medium" is intended to include mounting media such as CD-ROM, floppy disk or tape devices, computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, lanbas (Rambus) RAM, etc., non-volatile memory such as flash memory, magnetic media (e.g., hard disk or optical storage), registers or other similar types of memory elements, etc. The storage medium may also include other types of memory or combinations thereof. In addition, the storage medium may be located in a first computer system in which the program is executed, or may be located in a second, different computer system connected to the first computer system through a network such as the internet. The second computer system may provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media residing in different locations (e.g., in different computer systems connected by a network). The storage medium may store program instructions (e.g., embodied as a computer program) executable by one or more processors.
Of course, the storage medium containing the computer executable instructions provided in the embodiments of the present application is not limited to the above file management method, and may also perform the related operations in the file management method provided in any embodiment of the present application.
The file management and control device, the storage medium and the file management and control apparatus provided in the foregoing embodiments may execute the file management and control method provided in any embodiment of the present application, and technical details not described in detail in the foregoing embodiments may refer to the file management and control method provided in any embodiment of the present application.
The foregoing description is only of the preferred embodiments of the application and the technical principles employed. The present application is not limited to the specific embodiments described herein, but is capable of numerous modifications, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the application. Therefore, while the application has been described in connection with the above embodiments, the application is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit of the application, the scope of which is set forth in the following claims.

Claims (10)

1.一种文件管控方法，其特征在于，包括：1. A file management method, characterized by comprising: 响应于文件启动操作，在所述文件启动操作对应的待启动文件为可执行文件的情况下，检测所述待启动文件为安装包文件或非安装包文件；In response to a file startup operation, if the file to be started corresponding to the file startup operation is an executable file, detecting whether the file to be started is an installation package file or a non-installation package file; 在所述待启动文件为安装包文件的情况下，将所述待启动文件的文件特征与预设的目标安装包文件的文件特征进行匹配；In the case where the file to be started is an installation package file, matching the file characteristics of the file to be started with the file characteristics of a preset target installation package file; 在文件特征相匹配的情况下，禁止启动所述待启动文件；If the file features match, the startup of the file to be started is prohibited; 在所述待启动文件为非安装包文件或文件特征不匹配的情况下，启动所述待启动文件。When the file to be started is not an installation package file or the file features do not match, the file to be started is started. 2.根据权利要求1所述的文件管控方法，其特征在于，所述在所述文件启动操作对应的待启动文件为可执行文件的情况下，检测所述待启动文件为安装包文件或非安装包文件，包括：2. The file control method according to claim 1, characterized in that when the file to be started corresponding to the file startup operation is an executable file, detecting whether the file to be started is an installation package file or a non-installation package file comprises: 在确认所述待启动文件的文件头对应地址空间存储有可执行文件的标识信息的情况下，检测所述待启动文件为安装包文件或非安装包文件。When it is confirmed that the identification information of the executable file is stored in the address space corresponding to the file header of the file to be started, it is detected whether the file to be started is an installation package file or a non-installation package file. 3.根据权利要求1所述的文件管控方法，其特征在于，所述检测所述待启动文件为安装包文件或非安装包文件，包括：3. The file control method according to claim 1, characterized in that the detecting whether the file to be started is an installation package file or a non-installation package file comprises: 提取所述待启动文件的文件特征，所述文件特征包括文件名、文件签名和产品名称中的至少一个；Extracting a file feature of the file to be started, wherein the file feature includes at least one of a file name, a file signature, and a product name; 在所述待启动文件的文件特征与预设的误检测名单中安装包文件的文件特征相匹配的情况下，确定所述待启动文件为安装包文件；In a case where the file feature of the to-be-started file matches the file feature of the installation package file in the preset false detection list, determining that the to-be-started file is an installation package file; 在所述待启动文件的文件特征与预设的误检测名单中非安装包文件的文件特征相匹配的情况下，确定所述待启动文件为非安装包文件。When the file feature of the to-be-started file matches the file feature of the non-installation package file in the preset false detection list, it is determined that the to-be-started file is a non-installation package file. 4.根据权利要求1所述的文件管控方法，其特征在于，所述检测所述待启动文件为安装包文件或非安装包文件，包括：4. The file control method according to claim 1, characterized in that the detecting whether the file to be started is an installation package file or a non-installation package file comprises: 根据所述待启动文件的头部分，获取所述待启动文件的子系统值；According to the header part of the file to be started, obtaining the subsystem value of the file to be started; 在所述待启动文件的子系统值不为图像用户界面对应的子系统值的情况下，确定所述待启动文件为非安装包文件。When the subsystem value of the file to be started is not the subsystem value corresponding to the graphic user interface, it is determined that the file to be started is a non-installation package file. 5.根据权利要求1所述的文件管控方法，其特征在于，所述检测所述待启动文件为安装包文件或非安装包文件，包括：5. The file control method according to claim 1, characterized in that the detecting whether the file to be started is an installation package file or a non-installation package file comprises: 根据所述待启动文件的资源文件，获取所述资源文件的名称；According to the resource file of the file to be started, obtaining the name of the resource file; 在所述资源文件的名称与预设的打包名称相匹配的情况下，确定所述待启动文件为安装包文件；其中，所述打包名称为基于对应的打包软件打包生成的安装包文件的资源文件的名称。In the case where the name of the resource file matches a preset packaging name, it is determined that the file to be started is an installation package file; wherein the packaging name is the name of the resource file of the installation package file generated based on the corresponding packaging software. 6.根据权利要求1所述的文件管控方法，其特征在于，所述检测所述待启动文件为安装包文件或非安装包文件，包括：6. The file control method according to claim 1, characterized in that the detecting whether the file to be started is an installation package file or a non-installation package file comprises: 在所述待启动文件的文件尺寸大于预设的尺寸阈值的情况下，确定所述待启动文件为安装包文件。When the file size of the file to be started is greater than a preset size threshold, it is determined that the file to be started is an installation package file. 7.根据权利要求1所述的文件管控方法，其特征在于，所述检测所述待启动文件为安装包文件或非安装包文件，包括：7. The file control method according to claim 1, characterized in that the detecting whether the file to be started is an installation package file or a non-installation package file comprises: 通过预设的解压软件获取所述待启动文件的预览内容；Obtaining the preview content of the file to be started through the preset decompression software; 在所述预览内容包括预设的块结构的情况下，确定所述待启动文件为非安装包文件；In a case where the preview content includes a preset block structure, determining that the file to be started is a non-installation package file; 在所述预览内容不包括预设的块结构的情况下，确定所述待启动文件为安装包文件。When the preview content does not include a preset block structure, it is determined that the file to be started is an installation package file. 8.一种文件管控装置，其特征在于，包括：8. A file control device, comprising: 安装包检测模块，被配置为响应于文件启动操作，在所述文件启动操作对应的待启动文件为可执行文件的情况下，检测所述待启动文件为安装包文件或非安装包文件；An installation package detection module is configured to, in response to a file startup operation, detect whether the file to be started corresponding to the file startup operation is an installation package file or a non-installation package file when the file to be started corresponding to the file startup operation is an executable file; 特征匹配模块，被配置为在所述待启动文件为安装包文件的情况下，将所述待启动文件的文件特征与预设的目标安装包文件的文件特征进行匹配；a feature matching module, configured to match the file feature of the file to be started with the file feature of a preset target installation package file when the file to be started is an installation package file; 第一文件处理模块，被配置为在文件特征相匹配的情况下，禁止启动所述待启动文件；A first file processing module is configured to prohibit starting the to-be-started file when the file features match; 第二文件处理模块，被配置为在所述待启动文件为非安装包文件或文件特征不匹配的情况下，启动所述待启动文件。The second file processing module is configured to start the file to be started when the file to be started is not an installation package file or the file feature does not match. 9.一种文件管控设备，其特征在于，包括：9. A file management and control device, comprising: 一个或多个处理器；one or more processors; 存储器，存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-7任一所述的文件管控方法。A memory stores one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement the file management method as described in any one of claims 1-7. 10.一种包含计算机可执行指令的存储介质，其特征在于，所述计算机可执行指令在由计算机处理器执行时用于执行如权利要求1-7任一所述的文件管控方法。10. A storage medium comprising computer executable instructions, wherein the computer executable instructions are used to execute the file management method according to any one of claims 1 to 7 when executed by a computer processor.
CN202310883995.XA 2023-07-18 2023-07-18 File control method, device, equipment and storage medium Pending CN119376805A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310883995.XA CN119376805A (en) 2023-07-18 2023-07-18 File control method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310883995.XA CN119376805A (en) 2023-07-18 2023-07-18 File control method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN119376805A true CN119376805A (en) 2025-01-28

Family

ID=94330997

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310883995.XA Pending CN119376805A (en) 2023-07-18 2023-07-18 File control method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN119376805A (en)

Similar Documents

Publication Publication Date Title
US7058563B1 (en) Device driver auto-load
CN108509215B (en) System software replacing method and device, terminal equipment and storage medium
US10366226B2 (en) Malicious code analysis device and method based on external device connected via USB cable
CN110347571A (en) A kind of crash log acquisition method, analysis method and relevant apparatus
US11474855B2 (en) Information processing apparatus, information processing method, and storage medium
CN114003269A (en) Component processing method and device, electronic equipment and storage medium
CN113553243A (en) remote debug method
CN115951949A (en) Method, device and computing device for recovering configuration parameters of BIOS
US20060282571A1 (en) Multimedia devices with enhanced functionality
CN112162873B (en) Remote calling method, electronic device and storage medium
WO2017020460A1 (en) Method and apparatus for integrating plugin
JP3348430B2 (en) Automatic environment setting method of preinstalled application and storage medium
CN119886088B (en) Methods, devices, electronic equipment, and media for generating BIOS option variable tables.
CN120704955A (en) Operating system installation method, device, equipment and storage medium
CN110337017A (en) Television set and its log processing method, log processing device and readable storage medium storing program for executing
CN119376805A (en) File control method, device, equipment and storage medium
CN113742224A (en) Test system, method, device, computer equipment and storage medium
CN115454856B (en) Multi-application security detection method, device, medium and electronic equipment
CN114911762B (en) A method, apparatus, server, and storage medium for processing data files.
CN113791824B (en) Peripheral driver loading method, system and medium of terminal equipment
CN117520206A (en) Software UI testing methods, systems, equipment and storage media
CN108509252A (en) Virtual machine starter, method and host
CN115129539A (en) Log optimization method, device, equipment and storage medium
CN113986138A (en) Resource deleting method and device, electronic equipment and storage medium
CN114996030A (en) Method, device and equipment for realizing IO multiplexing pseudo terminal based on EPOLL

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