Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the devices, modules or units to be determined as different devices, modules or units, and are not used for limiting the sequence or interdependence relationship of the functions executed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
An embodiment of the present disclosure provides a component data extraction method of an operating system, as shown in fig. 1, the method may include:
step S110, determining version information corresponding to an operating system on which the terminal device to be tested depends, as target version information.
In this disclosure, the operating system refers to a processing system of the terminal device to be tested, and may be an android processing system or an IOS (apple mobile operating system) processing system, for example, in an embodiment of the present disclosure, the operating system on which the terminal device depends may be the android operating system. The version information is used for representing a currently-used version of the operating system, and multiple versions can exist in the same operating system, for example, when the operating system is an android version, the used version can be an android 5.0 version or an android 9.0 version.
Step S120, obtaining an installation package file of the application program to be tested in the terminal equipment to be tested, and determining the file type of the installation package file according to the target version information.
In practical applications, when the versions of the operating systems are different, the file types of the installation package files of the application programs included in the operating systems are also different. For example, when the operating system of the terminal device is an Android system (Android), if the installed version is any one of Android 1 to Android 4, the format of the installation package existing in the system is a dex type file and an apk type file, if the installed version is any one of Android 5 to Android 7, the format of the installation package existing in the system is an optimized odex type file and an optimized apk type file, in the Android 8 version, the odex type file is changed into a vdex type file, and the version after the Android 9 changes the odex type file into a cdex type file. Based on this, in the embodiment of the present disclosure, after knowing the version information corresponding to the operating system on which the terminal device to be tested depends, the file type of the acquired installation package file of the application program to be tested may be determined according to the corresponding version information.
And step S130, according to the file type, performing decompiling processing on the installation package file to obtain a code text.
In practical application, when the file types of the installation package files are different, the decompiling modes of the installation package files are different, and after the file types of the installation package files are known, the decompiling processing mode corresponding to the type can be selected to decompile the installation package files to obtain the code texts. Wherein the code text may be a smali code.
In step S140, system component data is extracted from the code file.
In practical application, each component of the application program to be extracted usually exists under a System/app, a priv-app and a frame, and correspondingly, when the code text corresponding to the installation package file is obtained, the data in the System/app, the priv-app and the frame is embodied in the code text, so that the System component data corresponding to the application program to be extracted can be obtained from the code file. The embodiment of the present disclosure is not limited to the implementation of extracting system component data from a code file, and an alternative implementation may be to invoke a text editor to extract system component data from a code file.
In the embodiment of the disclosure, when extracting system component data corresponding to an application program to be tested, a file type of an installation package file of the application program to be tested can be determined according to version information corresponding to an operating system on which a terminal device to be tested depends, and then decompiling is performed in a decompiling mode corresponding to the file type, at this time, decompiling can be performed on each version related to the system, and compatibility of each version of the operating system is improved; in addition, in the embodiment of the disclosure, after the code text corresponding to the installation package file is obtained through decompiling, the system component data can be quickly, quickly and efficiently extracted based on the code text, so that quick safety test can be realized, and the low test efficiency is improved.
In an embodiment of the present disclosure, the system component data includes a component type and action data corresponding to the component; the component types include a broadcast component, an active component, and a service component.
In practical application, the system component data corresponding to the application to be tested may include multiple types, such as a broadcast component, an activity component, a service component, and the like, and each component further includes action (action) data, and at this time, when the system component data corresponding to the application to be tested is obtained, the system component data may include each component type and action data corresponding to each component type.
In the embodiment of the present disclosure, the action data corresponding to each component type is the action data corresponding to the class name included in each component type.
In practical application, each component type includes a class name, each class name has corresponding action data, and the action data corresponding to each component type extracted at this time is the action data corresponding to the class name included in each component name.
In an embodiment of the disclosure, extracting system component data from a code file includes:
searching Manifest files in the code text, and extracting component data of activity components, component data of service components and component data of a broadcast register form of a broadcast component from the Mainfest files;
and searching a register field in the code text, and extracting the component data of the broadcast registration form of the broadcast component.
In practical application, when the system component data corresponds to different component types, the implementation modes of obtaining the system component data corresponding to the application program to be tested based on the code text extraction are different. For example, component data of an activity component, component data of a service component, and component data of a broadcast registration form of a broadcast component may be extracted based on a Manifest file in a code text. Further, in practical application, since the component data of the dynamic broadcast registration form of the broadcast component is not embodied in the Manifest file in the code text, the register field in the code text may be scanned, and the component data of the dynamic broadcast registration form of the broadcast component may be extracted.
In the embodiment of the present disclosure, according to the type of the file type, performing decompiling processing on the installation package file to obtain a code text, including:
if the file type is a first type, decompiling the installation package file by adopting a decompiling tool corresponding to the first type, wherein the first type comprises an APK file type and a dex file type;
if the file type is not the first type, converting the installation package file into an installation package file of the first type to obtain a converted installation package file; and decompiling the converted installation package file by adopting a decompiling tool corresponding to the first type.
In practical application, when the file types of the installation package files are different, the decompilation modes of the installation package files are also different, and at this time, the decompilation of the installation package files can be carried out according to the file types. In the embodiment of the present disclosure, various file types may be divided into a first type and a non-first type, and the first type may include an APK (android package) file type and a dex file type.
Further, when the installation package file is decompiled according to the file type, the file type of the installation package file can be determined, if the file type is determined to be the first type, the decompiling tool corresponding to the first type can be directly adopted to decompile the installation package file, if the file type is determined to be not the first type, the installation package file can be converted into the installation package file of the first type (namely converted into the APK file type or the dex file type), and then the decompiling tool corresponding to the first type is adopted to decompile the converted installation package file. When the first type of APK file is of the type, the corresponding decompilation tool is an apktool tool, and when the first type of dex file is of the type, the corresponding decompilation tool is an apktoolbackskmali tool.
When the file type is not the first type, different implementation modes can be adopted according to the file type when the installation package file is converted into the installation package file of the first type. For example, when the file type is the odex file type, the backsmamli tool may directly perform decompiling on the installation package file of the dex file type after converting the installation package file from the odex file type to the dex file type; when the file type is a vdex file type, a vdex extra tool can be adopted to convert the installation package file from the vdex file type to a dex file type, and then a backsmali tool is adopted to perform decompiling on the installation package file of the dex file type obtained after conversion; when the file type is the cdex file type, the installation package file can be converted into the dex file type from the cdex file type by adopting a compact _ dex _ coverters tool, and then the installation package file of the dex file type obtained after conversion is decompiled based on backsmali.
In addition, in practical applications, the installation package file of the application program to be tested in the operating system may be stored in various forms, for example, in a 32-bit form or a 64-bit form. Based on this, in the embodiment of the present disclosure, before the installation package file of the application program to be tested is decompiled, the form adopted by the installation package file during storage may also be determined, and the installation package file is correspondingly processed according to the form adopted during storage, for example, the installation package file stored in the form of 64 is moved to a specified directory (e.g., a frame directory), or the installation package file stored in the form of 32 is deleted in order to reduce the data amount.
In an embodiment of the present disclosure, based on the code text, the method further includes:
performing duplicate removal processing on all the extracted component data;
and storing the de-duplicated component data in a plurality of files in a classified manner, wherein the files are used for performing security test of the unauthorized and denial of service types.
In practical application, repeated component data may exist in component data extracted based on a code text, and if an application program to be tested is directly tested on the basis of the extracted component data, due to the fact that the repeated component data exists, data processing amount may be increased, so that in the embodiment of the present disclosure, each extracted component data may be subjected to deduplication processing, the deduplicated component data is obtained, and the deduplicated component data is classified and stored in a plurality of files based on component types included in the component data, so that subsequent security tests of override and/or denial of service types may be performed.
Further, in order to better understand the scheme provided by the embodiments of the present disclosure, the methods provided by the embodiments of the present disclosure are further described below with reference to specific embodiments. In this example, the operating System of the terminal device is an android System, the component data of the installation package file of the installed application program is stored under System/app, priv-app, System/frame (as shown in fig. 2), and accordingly, the configuration environment of the terminal device is as shown in fig. 3, which includes backsmami, apttool, vdexsector, compact _ dex _ counters, and Java8, where when the types of the installation package file in the operating System are all the first type, the configuration environment may only include backsmami, apttool, and Java 8.
In this example, as shown in fig. 4, when extracting component data, version information corresponding to an operating system on which a terminal device to be tested depends may be first used as target version information, and then according to the target version information, an installation package file of an application program to be tested is decompiled to obtain a code text corresponding to the installation package file, which may specifically include the following steps:
step S401, the version information corresponding to the operating system depended by the terminal equipment to be tested is taken as target version information;
step S402, moving the 64-bit installation package file to a frame directory;
step S403, deleting the 32-bit installation package file;
step S404, determining the file type of the installation package file of the application program to be tested according to the target version information;
step S405, if the file type is the first type, judging whether the file type of the installation package file is an APK file type or a dex file type;
step S406, if the file type of the installation package file is the APK file type in the first type, performing decompilation by using an apktool decompilation tool to obtain a code text;
step S407, if the file type of the installation package file is the dex file type in the first type, performing decompiling by adopting a backsmali decompiling tool to obtain a code text;
step S408, if the file type is not the first type, judging whether the file type of the installation package file is specifically an odex file type, a vdex file type or a cdex file type;
step S409, if the file type of the installation package file is the odex file type, performing decompiling by adopting a backsmali decompiling tool to obtain a code text;
step S410, if the file type of the installation package file is a vdex file type, adopting a vdex Extractor to convert the installation package file from the vdex file type to a dex file type;
step S411, a backsmali decompiling tool is adopted to decompile the installation package file of the dex file type obtained after conversion, and a code text is obtained;
step S412, if the file type of the installation package file is the cdex file type, converting the installation package file from the cdex file type to the vdex file type by adopting a compact _ dex _ coverters tool;
step S413, a vdex Extractor is adopted to convert the vdex file type into a dex file type;
and S414, adopting a backsmali decompiling tool to decompile the converted mounting package file of the dex file type to obtain a code text.
Further, as shown in fig. 5, after obtaining the code text corresponding to the installation package file, the system component data may be extracted from the code file, and the extracting may specifically include:
step S501, extracting a broadcast component, an activity component and a service component based on a Manifest file in a code text;
step S502, respectively determining class names included in the broadcast component, the activity component and the service component;
step S503, extracting action data corresponding to various names;
step S504, the register field in the code text is scanned, and the component data of the dynamic broadcast registration form of the broadcast component is extracted and obtained.
Based on the same principle as the method shown in fig. 1, an embodiment of the present disclosure further provides an extracting apparatus 30 of system component data, as shown in fig. 6, the extracting apparatus 30 of system component data may include a version information determining module 310, a file type determining module 320, a code text determining module 330, and a component data extracting module 340, where:
the version information determining module 310 is configured to determine version information corresponding to an operating system on which the terminal device to be tested depends, and use the version information as target version information;
the file type determining module 320 is configured to perform decompiling processing on the installation package file according to the file type to obtain a code text;
the code text determination module 330 is configured to perform decompiling on the installation package file of the application program to be extracted according to the version information to obtain a code text corresponding to the installation package file;
and the component data extraction module 340 is used for extracting system component data from the code file.
In an optional embodiment of the present application, an operating system on which the terminal device depends is an android operating system.
In an alternative embodiment of the present application, the system component data includes a component type and action data corresponding to the component type; the component types include a broadcast component, an active component, and a service component.
In an optional embodiment of the present application, when the component data extraction module extracts system component data from the code file, the component data extraction module is specifically configured to:
searching Manifest files in the code text, and extracting component data of activity components, component data of service components and component data of a broadcast register form of a broadcast component from the Mainfest files;
and searching a register field in the code text, and extracting the component data of the broadcast registration form of the broadcast component.
In an alternative embodiment of the present application, when the code text determining module performs decompiling processing on the installation package file according to the type of the file type to obtain the code text, the code text determining module is specifically configured to:
if the file type is a first type, decompiling the installation package file by adopting a decompiling tool corresponding to the first type, wherein the first type comprises an APK file type or a dex file type;
if the file type is not the first type, converting the installation package file into an installation package file of the first type to obtain a converted installation package file; and decompiling the converted installation package file by adopting a decompiling tool corresponding to the first type.
In an optional embodiment of the present application, when the component data extraction module extracts system component data from the code file, the component data extraction module is specifically configured to:
invoking a text editor to extract system component data from a code file
In an optional embodiment of the present application, the apparatus further includes a duplicate removal processing module, configured to:
performing duplicate removal processing on all the extracted component data;
and storing the de-duplicated component data in a plurality of files in a classified manner, wherein the files are used for performing security test of the unauthorized and denial of service types.
The system component data extraction device of the embodiment of the present disclosure may execute the system component data extraction method provided in the embodiment of the present disclosure, and the implementation principle is similar, the actions performed by each module in the system component data extraction device of each embodiment of the present disclosure correspond to the steps in the system component data extraction method of each embodiment of the present disclosure, and for the detailed functional description of each module of the system component data extraction device, reference may be specifically made to the description in the corresponding system component data extraction method shown in the foregoing, and details are not repeated here.
Based on the same principle as the method shown in the embodiments of the present disclosure, embodiments of the present disclosure also provide an electronic device, which may include but is not limited to: a processor and a memory; a memory for storing computer operating instructions; and the processor is used for executing the method shown in the embodiment by calling the computer operation instruction.
Based on the same principle as the method shown in the embodiment of the present disclosure, an embodiment of the present disclosure further provides a computer-readable storage medium, where at least one instruction, at least one program, a code set, or an instruction set is stored in the computer-readable storage medium, and the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the method shown in the embodiment, which is not described herein again.
Referring now to FIG. 7, a block diagram of an electronic device 600 suitable for use in implementing embodiments of the present disclosure is shown. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
The electronic device includes: a memory and a processor, wherein the processor may be referred to as the processing device 601 hereinafter, and the memory may include at least one of a Read Only Memory (ROM)602, a Random Access Memory (RAM)603 and a storage device 608 hereinafter, which are specifically shown as follows:
as shown in fig. 7, electronic device 600 may include a processing means (e.g., central processing unit, graphics processor, etc.) 601 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
In general, input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc., output devices 607 including, for example, a liquid crystal display (L CD), speaker, vibrator, etc., storage devices 608 including, for example, magnetic tape, hard disk, etc., and communication devices 609.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 609, or may be installed from the storage means 608, or may be installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of the embodiments of the present disclosure.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network protocol, such as HTTP (HyperText transfer protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communications network). examples of communications networks include local area networks ("L AN"), wide area networks ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
Computer program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including but not limited to AN object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules or units described in the embodiments of the present disclosure may be implemented by software or hardware. Wherein the designation of a module or unit does not in some cases constitute a limitation of the unit itself.
For example, without limitation, exemplary types of hardware logic that may be used include Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CP L D), and so forth.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
According to one or more embodiments of the present disclosure, [ example a1 ] there is provided a system component data extraction method, comprising:
determining version information corresponding to an operating system on which the terminal equipment to be tested depends, and taking the version information as target version information;
acquiring an installation package file of an application program to be tested in terminal equipment to be tested, and determining the file type of the installation package file according to target version information;
according to the file type, performing decompiling processing on the installation package file to obtain a code text;
system component data is extracted from the code file.
A2, according to the method A1, the operating system depended on by the terminal equipment is an android operating system.
A3, according to the method A1, the system component data comprises component types and action data corresponding to the component types; the component types include a broadcast component, an active component, and a service component.
A4, according to the method of A1, extracting system component data from the code file according to file type, including:
searching Manifest files in the code text, and extracting component data of activity components, component data of service components and component data of a broadcast register form of a broadcast component from the Mainfest files;
and searching a register field in the code text, and extracting the component data of the broadcast registration form of the broadcast component.
A5, according to the method of A1, according to the type of the file type, performing decompiling processing on the installation package file to obtain a code text, including:
if the file type is a first type, decompiling the installation package file by adopting a decompiling tool corresponding to the first type, wherein the first type comprises an APK file type or a dex file type;
if the file type is not the first type, converting the installation package file into an installation package file of the first type to obtain a converted installation package file; and decompiling the converted installation package file by adopting a decompiling tool corresponding to the first type.
A6, extracting system component data from the code file according to the method of A1, including:
a text editor is invoked to extract system component data from the code file.
A7, the method according to any one of A1 to 6, further comprising, based on the code text:
performing duplicate removal processing on all the extracted component data;
and storing the de-duplicated component data in a plurality of files in a classified manner, wherein the files are used for performing security test of the unauthorized and denial of service types.
According to one or more embodiments of the present disclosure, [ example B1 ] there is provided an extraction apparatus of system component data, comprising:
the version information determining module 310 is configured to determine version information corresponding to an operating system on which the terminal device to be tested depends, and use the version information as target version information;
the file type determining module 320 is configured to perform decompiling processing on the installation package file according to the file type to obtain a code text;
the code text determination module 330 is configured to perform decompiling on the installation package file of the application program to be extracted according to the version information to obtain a code text corresponding to the installation package file;
and the component data extraction module 340 is used for extracting system component data from the code file.
B2, according to the device of B1, the operating system depended on by the terminal equipment is an android operating system.
B3, according to the device of B1, the system component data comprises component types and action data corresponding to the component types; the component types include a broadcast component, an active component, and a service component.
B4, according to the device of B1, when the component data extraction module extracts the system component data from the code file, the component data extraction module is specifically configured to:
searching Manifest files in the code text, and extracting component data of activity components, component data of service components and component data of a broadcast register form of a broadcast component from the Mainfest files;
and searching a register field in the code text, and extracting the component data of the broadcast registration form of the broadcast component.
B5, according to the apparatus of B1, when the code text determining module performs decompiling processing on the installation package file according to the type of the file type to obtain the code text, the code text determining module is specifically configured to:
if the file type is a first type, decompiling the installation package file by adopting a decompiling tool corresponding to the first type, wherein the first type comprises an APK file type or a dex file type;
if the file type is not the first type, converting the installation package file into an installation package file of the first type to obtain a converted installation package file; and decompiling the converted installation package file by adopting a decompiling tool corresponding to the first type.
B6, according to the device of B1, when the component data extraction module extracts the system component data from the code file, the component data extraction module is specifically configured to:
a text editor is invoked to extract system component data from the code file.
B7, the apparatus according to any one of B1 to B6, further comprising a deduplication processing module for:
performing duplicate removal processing on all the extracted component data;
and storing the de-duplicated component data in a plurality of files in a classified manner, wherein the files are used for performing security test of the unauthorized and denial of service types.
According to one or more embodiments of the present disclosure, [ example C1 ] there is provided an electronic device comprising:
a processor and a memory;
a memory for storing computer operating instructions;
a processor for executing the method of any one of A1-A7 by calling computer operation instructions.
According to one or more embodiments of the present disclosure, [ example D1 ] there is provided a computer readable medium, characterized in that the readable medium stores at least one instruction, at least one program, code set, or set of instructions, which is loaded and executed by a processor to implement the method of any one of a1 to a 7.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.