CN102831049B - Method and system for detecting software - Google Patents
Method and system for detecting software Download PDFInfo
- Publication number
- CN102831049B CN102831049B CN201110157811.9A CN201110157811A CN102831049B CN 102831049 B CN102831049 B CN 102831049B CN 201110157811 A CN201110157811 A CN 201110157811A CN 102831049 B CN102831049 B CN 102831049B
- Authority
- CN
- China
- Prior art keywords
- matching
- software
- file information
- target folder
- feature
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 16
- 238000001514 detection method Methods 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000009434 installation Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a method for detecting software and a system for detecting the software. The method comprises the following steps: building a software feature base, wherein the software feature base stores key file information, feature file information and matching weight corresponding to the feature file information; scanning a target folder, detecting whether the key file is in a target folder and matched with the target folder successfully according to the key file information, if so, determining a root directory where the target folder belongs, and otherwise, finishing the operation; matching the feature file in the target folder according to the feature file information to obtain the corresponding matching weight, calculating the matching parameter value according to the matched weight; judging whether the calculated matching parameter value is more than or equal to the threshold value, if so, determining the software type where the target folder belongs according to the root directory and the feature file information and obtaining the basic information of the software from the software feature base; and otherwise, finishing the operation. The method and the system for detecting the software do not need a registry and cannot cause the detection leakage phenomenon of the software.
Description
[ technical field ] A method for producing a semiconductor device
The invention relates to the field of computer software application, in particular to a method and a system for detecting software.
[ background of the invention ]
When the conventional software is installed on the terminal, basic information of the software is generated, the basic information is recorded in the registry, and the category of the software can be determined by detecting the basic information in the registry. The basic information of the software comprises an installation path, an uninstallation program path, an icon file, version information and the like, and the software is classified into storm video player software, thunder player software, QQ player software and the like.
However, when the basic information in the registry is destroyed or the basic information generated by installing some software on the terminal is not recorded in the registry, the software class cannot be determined by detecting the basic information in the registry.
[ summary of the invention ]
Based on this, it is necessary to provide a method for detecting software without passing through a registry and without causing a missing detection phenomenon of the software.
A method of testing software, comprising the steps of:
establishing a software feature library, wherein the software feature library stores key file information, feature file information and matching weights corresponding to the feature file information;
scanning a target folder, detecting whether a key file exists in the target folder according to the key file information and matching is successful, if so, determining a root directory to which the target folder belongs, and if not, finishing;
matching the feature files in the target folder according to the feature file information to obtain corresponding matching weights, and calculating matching parameter values according to the matching weights;
and judging whether the calculated matching parameter value is larger than or equal to a threshold value, if so, determining the software category of the target folder according to the root directory and the feature file information, and obtaining the basic information of the software from the software feature library, otherwise, ending.
Preferably, when the feature file information is a plurality of feature file information, matching the feature file in the target folder according to the feature file information to obtain a corresponding matching weight, and calculating the matching parameter value according to the matching weight specifically includes:
matching the feature files one by one in a target folder according to the feature file information, and obtaining corresponding matching weights after matching is successful;
and superposing the obtained matching weights to obtain the matching parameter values.
Preferably, the matching condition for matching the feature file in the target folder according to the feature file information at least includes one of file name matching and file md5 value matching.
Preferably, the matching condition further includes one or both of a version number matching and a digital signature matching.
Preferably, when there are a plurality of pieces of key file information, detecting whether there is a key file in a target folder according to the key file information and the matching is successful, if yes, determining a root directory to which the target folder belongs, otherwise, ending the step: the software feature library stores priorities of a plurality of pieces of key file information which are preset; and matching the key files in the target folder according to the priority levels of the plurality of pieces of key file information, if the matching is successful, determining the root directory to which the target folder belongs, and if not, finishing.
In addition, it is necessary to provide a system for detecting software that does not need to pass through a registry and does not cause a missing detection phenomenon of the software.
A system for detecting software, comprising:
the software feature library is used for storing key file information, feature file information and matching weights corresponding to the feature file information;
the scanning module is used for scanning a target folder, detecting whether a key file exists in the target folder and matching successfully according to the key file information, and determining a root directory to which the target folder belongs when detecting that the key file exists and matching successfully;
the matching module is used for matching the feature files in the target folder according to the feature file information to obtain corresponding matching weights and calculating matching parameter values according to the matching weights;
the judging module is used for judging whether the calculated matching parameter value is greater than or equal to a threshold value;
and the identification module is used for determining the software category of the target folder according to the root directory and the feature file information and obtaining the basic information of the software from the software feature library when the judgment module judges that the matching parameter value is larger than the threshold value.
Preferably, when the feature file information is a plurality of feature file information, the matching module is further configured to match the feature files one by one in the target folder according to the feature file information, obtain corresponding matching weights after the matching is successful, and then superimpose the obtained matching weights to obtain the matching parameter values.
Preferably, the matching condition that the matching module matches the feature file in the target folder according to the feature file information at least includes one of file name matching and file md5 value matching.
Preferably, the matching condition further includes one or both of a version number matching and a digital signature matching.
Preferably, when the number of the key file information is multiple, the software feature library further stores priorities of multiple pieces of key file information which are preset; the scanning module is further configured to match key files in the target folder in sequence according to the priority levels of the plurality of pieces of key file information, and determine the root directory to which the target folder belongs when matching is successful.
According to the method and the system for detecting the software, the software feature library is established, the target folder is scanned, the root directory to which the target folder belongs is determined by matching the key files according to the key file information, the corresponding matching weight is obtained by further matching the feature files in the target folder according to the feature file information, the matching parameter value is calculated, the matching parameter value is compared with the threshold value, and when the matching parameter value is larger than or equal to the threshold value, the software category to which the target folder belongs can be determined according to the root directory and the feature file information, so that the software detection is realized, a registry is not needed, and the phenomenon of missed detection of the software is not caused.
[ description of the drawings ]
FIG. 1 is a flow diagram of a method of detecting software in one embodiment;
FIG. 2 is a detailed flow diagram of the calculation of matching parameter values in one embodiment;
FIG. 3 is a block diagram of a system for detecting software according to an embodiment.
[ detailed description ] embodiments
The following describes the technical solutions of the method and system for detecting software in detail with reference to specific embodiments and drawings.
As shown in FIG. 1, in one embodiment, a method of testing software includes the steps of:
step S110, a software feature library is established, and the software feature library stores the key file information, the feature file information, and the matching weight corresponding to the feature file information.
In order to identify the software, a software feature library is established in advance. The key file information in the software feature library refers to file information for determining a software root directory, such as software startup file information (qq. exe file information); the feature file information refers to file information used for further determining the software, which can be selected by a user, such as bin \ lognpanel.dll (Dynamic Link Library) file information, bin \ mainframe.dll file information, bin \ im.dll file information and the like in the QQ software; the matching weight corresponding to the feature file information is a corresponding weight given when the preset feature file information is matched, for example, the matching weight corresponding to the bin \ loginnpanel.dll file information is 100, and the matching weight corresponding to the bin \ mainframe.dll file information is 100.
The key file information and the profile information may be one or more.
The key file information may include key file names, key file identification numbers, relationships of key files with respect to software root directories, expected root directories, and the like. The relationship between the key file and the software root directory is as follows, the software root directory AB and abc.exe in AB \ Bin \ abc.exe have 2 levels, the root directory relationship value of AB can be set to-2, which means that AB is the father directory of the parent directory of abc.exe, similarly, -1 represents 1 level difference, Bin is the father directory of abc.exe, 0 represents the same level, and so on. The desired root directory is the smallest parent directory to which all files belong, wherein an attribute value may be set to determine whether the root directory of the software must match the desired root directory.
In one embodiment, the software feature library has recorded therein the following information:
wherein, SymbolFile represents a key file, RootRelativePath represents the relation of the file relative to the software root directory, -2 represents the difference of two levels, Priority represents the Priority of a plurality of key file information determining root directories, matching is performed from high to low in sequence, the root directory can be confirmed by matching, RootName represents the expected root directory name, and the Strict attribute represents whether the name is required or not, if so, the root directory is required to be the name.
When the root directory to which the target folder belongs is determined according to the key file information matching key files, the attribute of the field Strict can be matched, for example, the attribute of Strict is 1, which means that the root directory to which the target folder belongs must match the expected root directory, and the attribute of Strict is 0, which means that the root directory to which the target folder belongs does not necessarily match the expected root directory. In addition, different versions may exist in the same software, and the file structure of each version may be different, so that the same software may establish different key file information and feature file information for different versions, or may establish the same key file information and feature file information correspondingly in one version interval.
Step S120, scanning the target folder, detecting whether the key files exist in the target folder according to the key file information and matching is successful, if so, executing step S130, otherwise, ending.
And scanning the target folder, wherein the target folder can be scanned by scanning all the disks, or the target folder can be scanned according to a user-defined scanning path, or a shortcut specified by a user or a position of executable software is acquired.
And detecting the files in the scanned target folder according to the key file information, matching the key files, and determining the root directory to which the target folder belongs if the matching is successful. The matching conditions for matching the key files at least comprise one of file name matching and file Md5 value matching, and also comprise one or two of version number matching and digital signature matching.
When the key file information is multiple, for example, the key file information of the QQ software includes QQ. The software feature library also stores the preset priorities of a plurality of key file information. Step S120 specifically includes: scanning a target folder, sequentially matching key files in the target folder according to the priority levels of a plurality of key file information, and if the matching is successful, determining a root directory to which the target folder belongs. And matching the information priorities of the plurality of key files one by one, and determining the root directory to which the target folder belongs after all the key files are successfully matched.
Step S130, determine the root directory to which the target folder belongs.
And determining the root directory to which the target folder belongs, namely preliminarily determining the category of the software.
And step S140, matching the characteristic files in the target folder according to the characteristic file information to obtain corresponding matching weights, and calculating matching parameter values according to the matching weights.
The matching conditions for matching the feature files in the target folder according to the feature file information at least comprise one of file name matching and file Md5 value matching, and also comprise one or two of version number matching and digital signature matching, and the version number matching and the digital signature matching may not be included.
When the profile information is a plurality of profile information, such as bin \ lognpandel.dll (Dynamic Link Library) file information, bin \ mainframe.dll file information, bin \ im.dll file information, etc. in the QQ software, as shown in fig. 3, step S140 specifically includes:
and step S141, matching the feature files in the target folder one by one according to the feature file information, and obtaining corresponding matching weights after the matching is successful.
After matching is successful, the matching weight corresponding to the feature file information is obtained, for example, 2 pieces of feature file information are successfully matched with bin \ lognpanel.dll file information, the obtained corresponding matching weight is 100, and the obtained corresponding matching weight is 100.
And step S143, overlapping the obtained matching weights to obtain the matching parameter value.
And superposing the matching weights to obtain 200 serving as a matching parameter value.
Step S150, determining whether the calculated matching parameter value is greater than or equal to a threshold value, if so, performing step S160, otherwise, ending.
And when the calculated matching parameter value is larger than or equal to the threshold value, determining the software category of the target folder according to the tracking and characteristic file information. The threshold is set by the system, e.g., 500.
Step S160, determining the software type of the target folder according to the root directory and the characteristic file information, and obtaining the basic information of the software from the software characteristic library.
After the software category is determined, basic information of the software can be obtained from the software feature library, and the basic information comprises the name, the category, the installation path, the uninstallation path, the icon file, the version information and the like of the software.
As shown in FIG. 3, in one embodiment, a system for detecting software comprises: a creation module 310, a scanning module 320, a matching module 330, a determination module 340, and an identification module 350. Wherein,
the creating module 310 is configured to create a software feature library, where the software feature library stores the key file information, the feature file information, and the matching weight corresponding to the feature file information. In order to identify the software, a software feature library is established in advance. The key file information in the software feature library refers to file information for determining a software root directory, such as software startup file information (qq. exe file information); the feature file information refers to file information used for further determining the software, which can be selected by a user, such as bin \ lognpanel.dll (Dynamic Link Library) file information, bin \ mainframe.dll file information, bin \ im.dll file information and the like in the QQ software; the matching weight corresponding to the feature file information is a corresponding weight given when the preset feature file information is matched, for example, the matching weight corresponding to the bin \ loginnpanel.dll file information is 100, and the matching weight corresponding to the bin \ mainframe.dll file information is 100. The key file information and the profile information may be one or more.
The key file information may include key file names, key file identification numbers, the relationship of key files to the software root directory, and the desired root directory. The relationship between the key file and the software root directory is as follows, the software root directory AB and abc.exe in AB \ Bin \ abc.exe have 2 levels, the root directory relationship value of AB can be set to-2, which means that AB is the father directory of the parent directory of abc.exe, similarly, -1 represents 1 level difference, Bin is the father directory of abc.exe, 0 represents the same level, and so on. The desired root directory is the smallest parent directory to which all files belong, wherein an attribute value may be set to determine whether the software root directory must match the desired root directory. In the embodiment of the method, information recorded in a software feature library, symbol file represents key file information, rootrelalativePath represents the relation of the file relative to a software root directory, 2 represents the difference of two levels, Priority represents the Priority of a plurality of pieces of key file information for determining the Priority of the root directory, matching is performed from high to low in sequence, the root directory can be confirmed by matching, RootName represents an expected root directory name, a Stirt attribute represents whether the name is required or not, and if the name is required, the root directory is required to be the name.
Different versions may exist in the same software, and the file structure of each version may be different, so that the same software may establish different key file information and feature file information for different versions, or may establish the same key file information and feature file information correspondingly in one version interval.
The scanning module 320 is configured to scan the target folder, detect whether a key file exists in the target folder according to the key file information and match the key file successfully, and determine a root directory to which the target folder belongs when detecting that the key file exists and match the key file successfully. And scanning the target folder, wherein the target folder can be scanned by scanning all the disks, or the target folder can be scanned according to a user-defined scanning path, or a shortcut specified by a user or a position of executable software is acquired.
The key file information may be multiple, for example, the key file information of the QQ software includes QQ. The software feature library also stores the priority of a plurality of pieces of preset key file information. The scanning module 320 is further configured to match the key files in the target folder according to the priority levels of the plurality of key file information, and determine the root directory to which the target folder belongs when matching is successful. The scanning module 320 matches the plurality of key file information one by one according to the priority, and when all matching is successful, the root directory to which the target folder belongs can be determined. The matching conditions for matching the key files at least comprise one of file name matching and file Md5 value matching, and also comprise one or two of version number matching and digital signature matching.
In addition, when determining the root directory to which the target folder belongs according to the key file information matching key files, the scanning module 320 may match the attribute of the field Strict, where an attribute of Strict is 1 indicates that the root directory to which the target folder belongs must match the expected root directory, and an attribute of Strict is 0 indicates that the root directory to which the target folder belongs does not necessarily match the expected root directory.
The matching module 330 is configured to match the feature file in the target folder according to the feature file information to obtain a corresponding matching weight, and calculate a matching parameter value according to the matching weight. The matching condition that the matching module 330 matches the feature file in the target folder according to the feature file information at least includes one of file name matching and file md5 value matching, and also includes one or both of version number matching and digital signature matching.
When the feature file information is a plurality of feature file information, such as bin \ lognp _ dll (Dynamic Link Library) file information, bin \ mainframe.dll file information, bin \ im.dll file information, etc. in the QQ software, the matching module 330 is further configured to match the feature files in the target folder one by one according to the plurality of feature file information, obtain corresponding matching weights after matching succeeds, and then superimpose the obtained matching weights to obtain the matching parameter values. After matching is successful, matching weights corresponding to the obtained feature file information are obtained, for example, 2 pieces of feature file information, the bin \ lognpanel.dll file information is matched to the corresponding feature file, namely, matching is successful, the obtained corresponding matching weights are 100, the bin \ mainframe.dll file information is matched to the corresponding feature file, namely, matching is successful, and the obtained corresponding matching weights are 100. The matching module 330 superimposes the matching weights to obtain 200 as a matching parameter value.
The determining module 340 is configured to determine whether the calculated matching parameter value is greater than or equal to a threshold.
The identifying module 350 is configured to determine the software category to which the target folder belongs according to the root directory and the feature file information when the determining module 340 determines that the matching parameter value is greater than the threshold, and obtain the basic information of the software from the software feature library. The threshold is set by the system, e.g., 500. The basic information includes the name, category, installation path, uninstallation path, icon file, version information, and the like of the software.
According to the method and the system for detecting the software, the software feature library is established, the target folder is scanned, the root directory to which the target folder belongs is determined by matching the key files according to the key file information, the corresponding matching weight is obtained by further matching the feature files in the target folder according to the feature file information, the matching parameter value is calculated, the matching parameter value is compared with the threshold value, when the matching parameter value is larger than or equal to the threshold value, the software category to which the target folder belongs can be determined according to the root directory and the feature file information, a registry is not needed, and the phenomenon of software omission is avoided.
In addition, the matching conditions for a single file are various and flexible, and different requirements can be met.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method of testing software, comprising the steps of:
establishing a software feature library, wherein the software feature library stores key file information, feature file information and matching weights corresponding to the feature file information, the key file information comprises a key file name, a key file identification number, a relationship between a key file and a software root directory and an expected root directory, and an attribute value is set to determine whether the root directory of the software needs to be matched with the expected root directory;
scanning a target folder, detecting whether a key file exists in the target folder according to the key file information and matching is successful, if so, determining a root directory to which the target folder belongs, and if not, finishing;
matching the feature files in the target folder according to the feature file information to obtain corresponding matching weights, and calculating matching parameter values according to the matching weights;
and judging whether the calculated matching parameter value is larger than or equal to a threshold value, if so, determining the software category of the target folder according to the root directory and the feature file information, and obtaining the basic information of the software from the software feature library, otherwise, ending.
2. The method for detecting software according to claim 1, wherein when the profile information is a plurality of profile information, matching the profile in the target folder according to the profile information to obtain a corresponding matching weight, and calculating the matching parameter value according to the matching weight specifically includes:
matching the feature files one by one in a target folder according to the feature file information, and obtaining corresponding matching weights after matching is successful;
and superposing the obtained matching weights to obtain the matching parameter values.
3. The method for testing software according to claim 1, wherein said matching condition for matching the profile in the target folder according to the profile information includes at least one of a file name matching and a file md5 value matching.
4. The method of testing software of claim 3, wherein said match condition further comprises one or both of a version number match and a digital signature match.
5. The method for detecting software according to claim 1, wherein when there are a plurality of pieces of key file information, according to the key file information, whether there are key files in a target folder is detected and matching is successful, if yes, a root directory to which the target folder belongs is determined, otherwise, the method ends with the steps of: the software feature library stores priorities of a plurality of pieces of key file information which are preset; and matching the key files in the target folder according to the priority levels of the plurality of pieces of key file information, if the matching is successful, determining the root directory to which the target folder belongs, and if not, finishing.
6. A system for testing software, comprising:
the software feature library is used for establishing a software feature library, the software feature library stores key file information, feature file information and matching weights corresponding to the feature file information, the key file information comprises key file names, key file identification numbers, the relationship between key files and a software root directory and an expected root directory, and an attribute value is set to determine whether the root directory of the software needs to be matched with the expected root directory;
the scanning module is used for scanning a target folder, detecting whether a key file exists in the target folder and matching successfully according to the key file information, and determining a root directory to which the target folder belongs when detecting that the key file exists and matching successfully;
the matching module is used for matching the feature files in the target folder according to the feature file information to obtain corresponding matching weights and calculating matching parameter values according to the matching weights;
the judging module is used for judging whether the calculated matching parameter value is greater than or equal to a threshold value;
and the identification module is used for determining the software category of the target folder according to the root directory and the feature file information and obtaining the basic information of the software from the software feature library when the judgment module judges that the matching parameter value is larger than the threshold value.
7. The system for detecting software according to claim 6, wherein when the profile information is a plurality of profile information, the matching module is further configured to match the profiles in the target folder one by one according to the profile information, obtain corresponding matching weights after matching is successful, and then superimpose the obtained matching weights to obtain the matching parameter values.
8. The system for detecting software according to claim 6, wherein the matching condition that the matching module matches the profile in the target folder according to the profile information at least includes one of a file name matching and a file md5 value matching.
9. The system for testing software according to claim 8, wherein said matching condition further comprises one or both of a version number match and a digital signature match.
10. The system for detecting software according to claim 6, wherein when there are a plurality of pieces of key file information, the software feature library further stores priorities for setting a plurality of pieces of key file information in advance; the scanning module is further configured to match key files in the target folder in sequence according to the priority levels of the plurality of pieces of key file information, and determine the root directory to which the target folder belongs when matching is successful.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110157811.9A CN102831049B (en) | 2011-06-13 | 2011-06-13 | Method and system for detecting software |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110157811.9A CN102831049B (en) | 2011-06-13 | 2011-06-13 | Method and system for detecting software |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102831049A CN102831049A (en) | 2012-12-19 |
| CN102831049B true CN102831049B (en) | 2015-05-20 |
Family
ID=47334198
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110157811.9A Active CN102831049B (en) | 2011-06-13 | 2011-06-13 | Method and system for detecting software |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102831049B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107491306A (en) * | 2017-08-11 | 2017-12-19 | 中国地质大学（武汉） | Association and user interface automatic generation method between a kind of Mobile solution of self study |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104252349A (en) * | 2013-06-28 | 2014-12-31 | 北京艾普优计算机系统有限公司 | Method and device for recognizing software |
| CN104133703A (en) * | 2014-07-31 | 2014-11-05 | 珠海市君天电子科技有限公司 | Method and device for determining software not used frequently |
| CN104268464B (en) * | 2014-09-30 | 2017-02-15 | 珠海市君天电子科技有限公司 | Promotion rule for promotion software and determination method, server and communication terminal for promotion software |
| CN105786579B (en) * | 2016-03-28 | 2020-06-23 | 联想(北京)有限公司 | Processing method and device, and method and device for preventing program from starting |
| CN111897773A (en) * | 2019-05-05 | 2020-11-06 | 深圳市云趣网络科技股份有限公司 | Method and device for searching local game starting file of windows system |
| CN113779620A (en) * | 2021-08-19 | 2021-12-10 | 成都鲁易科技有限公司 | Program file checking method and device, storage medium and computer equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101213555A (en) * | 2005-06-30 | 2008-07-02 | 普瑞维克斯有限公司 | Methods and apparatus for dealing with malware |
| CN101350049A (en) * | 2007-07-16 | 2009-01-21 | 珠海金山软件股份有限公司 | Method, apparatus and network device for identifying virus document |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2400932B (en) * | 2003-04-25 | 2005-12-14 | Messagelabs Ltd | A method of,and system for,heuristically determining that an unknown file is harmless by using traffic heuristics |
-
2011
- 2011-06-13 CN CN201110157811.9A patent/CN102831049B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101213555A (en) * | 2005-06-30 | 2008-07-02 | 普瑞维克斯有限公司 | Methods and apparatus for dealing with malware |
| CN101350049A (en) * | 2007-07-16 | 2009-01-21 | 珠海金山软件股份有限公司 | Method, apparatus and network device for identifying virus document |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107491306A (en) * | 2017-08-11 | 2017-12-19 | 中国地质大学（武汉） | Association and user interface automatic generation method between a kind of Mobile solution of self study |
| CN107491306B (en) * | 2017-08-11 | 2019-11-22 | 中国地质大学（武汉） | Association and user interface automatic generation method between a kind of mobile application of self study |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102831049A (en) | 2012-12-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102831049B (en) | Method and system for detecting software | |
| KR101554633B1 (en) | Apparatus and method for detecting malicious code | |
| CN102736978B (en) | A kind of method and device detecting the installment state of application program | |
| CN104573525B (en) | A kind of specific information service software leak repair system based on white list | |
| US9621571B2 (en) | Apparatus and method for searching for similar malicious code based on malicious code feature information | |
| CN107292169B (en) | Threat tracing method and device for malicious software | |
| KR101337874B1 (en) | System and method for detecting malwares in a file based on genetic map of the file | |
| US9535781B2 (en) | System file repair method and apparatus | |
| CN110263545B (en) | Starting process integrity measurement detection method based on Android system | |
| CN110287704B (en) | Vulnerability software dependency relationship construction method based on vulnerability map | |
| KR101055267B1 (en) | Method for identifying distribution sites of activex controls and verifying security weaknesses of activex controls and immunizing activex controls | |
| EP2141598A1 (en) | Software behavior modeling device, software behavior modeling method, software behavior verification device, and software behavior verification method | |
| TW200912696A (en) | Method for verifying application programs and controlling the execution thereof | |
| JP6711000B2 (en) | Information processing apparatus, virus detection method, and program | |
| CN103390130A (en) | Rogue program searching and killing method and device based on cloud security as well as server | |
| KR20130134790A (en) | Method and system for storing the integrity information of application, method and system for checking the integrity of application | |
| WO2015131643A1 (en) | Software detection method and device | |
| CN109711149B (en) | Dynamic updating mechanism judging method and application full life cycle behavior monitoring method | |
| CN112988219B (en) | Deployment method and device of information system | |
| CN104750517A (en) | Information processing method and electronic equipment | |
| KR101907681B1 (en) | Method, apparatus, and system for automatically generating rule for detecting virus code, and computer readable recording medium for reciring the same | |
| CN106445737A (en) | Multi-backup starting method | |
| CN106874759B (en) | Identification method and system for Trojan horse randomized behavior | |
| CN107391185B (en) | Method and device for detecting installation package | |
| WO2015080556A1 (en) | Method for booting an embedded device from an external usb device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |