CN113590404A - Simulator detection method, device, equipment and computer storage medium - Google Patents
Simulator detection method, device, equipment and computer storage medium Download PDFInfo
- Publication number
- CN113590404A CN113590404A CN202110909308.8A CN202110909308A CN113590404A CN 113590404 A CN113590404 A CN 113590404A CN 202110909308 A CN202110909308 A CN 202110909308A CN 113590404 A CN113590404 A CN 113590404A
- Authority
- CN
- China
- Prior art keywords
- simulator
- detected
- architecture
- file
- determining
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000001514 detection method Methods 0.000 title claims abstract description 88
- 238000000034 method Methods 0.000 claims abstract description 46
- 238000004891 communication Methods 0.000 claims description 15
- 238000010998 test method Methods 0.000 claims 1
- 238000012545 processing Methods 0.000 abstract description 5
- 238000013459 approach Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 3
- 238000013519 translation Methods 0.000 description 2
- 230000014616 translation Effects 0.000 description 2
- 241000282414 Homo sapiens Species 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000004134 energy conservation Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2273—Test methods
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
- G06F9/4451—User profiles; Roaming
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention relates to the technical field of computer processing, and discloses a detection method, a device, equipment and a computer readable storage medium of a simulator, wherein the method comprises the following steps: acquiring an environment configuration file of an application to be detected; identifying the environment configuration file, and determining the architecture characteristic information corresponding to the operating environment of the application to be detected; and when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining the operating environment as the simulator to be detected. Through the mode, the detection accuracy of the simulator is improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computer processing, in particular to a simulator detection method, a simulator detection device, simulator detection equipment and a computer storage medium.
Background
In current android applications, situations often arise in which android applications are run in a simulator environment for purposes of gaming, cheating, and other human beings to achieve long-term hang-up, perform scripting operations, and the like. It is therefore necessary to detect whether the environment in which the android application runs is a simulator environment.
At present, hardware detection of a detection sensor, loading of a specific file, or execution of a specific binary code at a memory address, etc. are generally adopted for detecting a simulator.
The inventor finds that the existing simulator detection scheme has the problems of low accuracy and low compatibility in the process of implementing the invention.
Disclosure of Invention
In view of the foregoing problems, embodiments of the present invention provide a method, an apparatus, a device, and a computer storage medium for detecting a simulator, so as to solve the problem in the prior art that the detection accuracy and compatibility of the simulator are low.
According to an aspect of an embodiment of the present invention, there is provided a method for detecting a simulator, the method including:
acquiring an environment configuration file of an application to be detected;
identifying the environment configuration file, and determining the architecture characteristic information corresponding to the operating environment of the application to be detected;
and when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining the operating environment as the simulator to be detected.
In an optional mode, when the application to be detected is an application in an android system, the method is implemented based on a native layer of the android system; the environment configuration file comprises a plurality of binary library files; the architecture characteristic information comprises an architecture field value of each binary library file; the method comprises the following steps:
matching each architecture field value with a target field value corresponding to the simulator to be detected respectively;
and when the architecture field value is matched with the target field value, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment configuration file includes a plurality of binary library files; the architecture characteristic information comprises a library file type of each binary library file; the method comprises the following steps:
respectively matching each library file type with the characteristic library file type corresponding to the simulator to be detected;
and when the library file type is matched with the characteristic library file type, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment profile comprises a system profile; the architecture feature information comprises a file interpretation mode corresponding to the system configuration file; the method comprises the following steps:
determining interpreter configuration information according to the system configuration file;
determining the file interpretation mode according to the interpreter configuration information;
and when the file interpretation mode is a mixed binary mode, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment profile comprises a system profile; the architecture feature information comprises a file registration identifier corresponding to the system configuration file; the method comprises the following steps:
determining interpreter configuration information according to the system configuration file;
determining the file registration identification according to the interpreter configuration information;
acquiring a target registration identifier corresponding to the native architecture of the application to be detected;
and when the file registration identification is matched with the target registration identification, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment profile comprises a system profile; the architecture feature information comprises instruction identification program configuration information corresponding to the system configuration file; the instruction identification program is used for converting the instruction under the architecture of the simulator to be detected into the instruction under the native architecture of the application to be detected; the method comprises the following steps:
and when the instruction identification program configuration information is non-empty, determining that the operating environment is the simulator to be detected.
In an optional mode, the environment configuration file comprises a system configuration file and a plurality of binary library files; the architecture feature information comprises library file types and architecture field values of the binary library files, and file interpretation modes, file registration identifiers and instruction recognition program configuration information corresponding to the system configuration files; the method comprises the following steps:
when the binary library file meets a first preset condition, if the system configuration file meets a second preset condition, determining that the operating environment is the simulator to be detected; wherein the first preset condition is that the architecture field value is matched with a target field value and the library file type is matched with a feature library file type; the second preset condition is that the file interpretation mode is at least one of a mixed binary mode, the file registration identifier is matched with a target registration identifier, and the instruction recognition program configuration information is not null.
According to another aspect of the embodiments of the present invention, there is provided a detection apparatus of a simulator, including:
the acquisition module is used for acquiring an environment configuration file corresponding to the application to be detected;
the identification module is used for identifying the environment configuration file and determining the architecture characteristic information corresponding to the operating environment of the application to be detected;
and the determining module is used for determining the operating environment as the simulator to be detected when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected.
According to another aspect of the embodiments of the present invention, there is provided a detection apparatus of a simulator, including: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus; the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the operation of the detection method of the simulator.
According to still another aspect of the embodiments of the present invention, there is provided a computer-readable storage medium having at least one executable instruction stored therein, the executable instruction causing a detection apparatus of a simulator to perform the operations of the detection method of the simulator described below.
The method comprises the steps of firstly, acquiring an environment configuration file of an application to be detected; identifying the environment configuration file, and determining the architecture characteristic information corresponding to the operating environment of the application to be detected; and when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining the operating environment as the simulator to be detected.
Different from interfaces of hardware such as a detection sensor and the like in a system adopted in the prior art, the simulator is easy to forge, read information detected by loading a specific file is easy to modify, so that the detection accuracy is low, and the compatibility problem that the execution of a specific binary code in a memory address easily triggers the collapse of an application process and is difficult to ensure is solved, by matching the architecture characteristic information with the target architecture condition corresponding to the simulator to be tested, therefore, the detection of the simulator to be detected is completed, and the detection is completed at the bottom layer of the system, so that specific files or codes do not need to be loaded, and the read information is not easy to modify, thereby improving the accuracy and compatibility of the detection of the simulator.
The foregoing description is only an overview of the technical solutions of the embodiments of the present invention, and the embodiments of the present invention can be implemented according to the content of the description in order to make the technical means of the embodiments of the present invention more clearly understood, and the detailed description of the present invention is provided below in order to make the foregoing and other objects, features, and advantages of the embodiments of the present invention more clearly understandable.
Drawings
The drawings are only for purposes of illustrating embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a schematic flow chart illustrating a detection method of a simulator provided in an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a simulator to be tested according to an embodiment of the present invention;
FIG. 3 is a flow chart illustrating a detection method of a simulator according to another embodiment of the present invention;
FIG. 4 is a schematic structural diagram of a detection device of a simulator provided in an embodiment of the present invention;
fig. 5 shows a schematic structural diagram of a detection device of a simulator provided in an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein.
Before the description of the detection method of the simulator of the embodiment of the present invention is made, the terms are explained:
ARM: advanced RISC Machine, Advanced reduced instruction set Machine, is a 32-bit Reduced Instruction Set (RISC) processor architecture that is widely used in many embedded system designs. Due to the characteristic of energy conservation, the ARM architecture processor is very suitable for the field of mobile communication and meets the characteristic that the main design target is low power consumption. The architecture adopted by the android system is generally an ARM.
X86: the X86 architecture (The X86 architecture) is a set of computer language instructions executed by a microprocessor, referred to as The standard number abbreviation of The Intel general computer column, which also identifies a common set of computer instructions. The majority of current PC architectures are Intel's X86 architectures. The architecture of a general android simulator adopts X86, and the structure of an android simulator with an X86 architecture can refer to FIG. 2.
ARM interpreter: the ARM interpreter and the android simulator need to run normal android programs, and need to interpret an ARM C library of the bridge android application through the ARM interpreter. The binary library file of the ARM runs on the ARM interpreter, and the slave simulator obtains the information of the ARM library file by calling the ARM interpreter during running.
binfmt _ misc: namely, the Miscellaneous Binary Format (binfmt _ misc), hybrid Binary Format. The file interpretation mode is used for selecting which program is used to open the file on the Linux platform according to the characteristics of the file to be opened. It can determine the type and manner in which the file needs to be opened by the extension of the file or a special byte at the beginning of the file.
Native Bridge: when running code for a heterogeneous CPU (e.g., ARM) in a system of the X86 architecture, the code is used to identify the ARM machine code as a program of X86 instructions.
Houdini: intel provides an ARM Binary Translation library for converting ARM instructions to X86 instructions, which is capable of performing Binary translations from ARM instructions to X86 instructions. Native bridge for hook of native code is also provided in android system.
Libnativehelper: android startup starts with the Zygote process, and the Zygote process needs to initialize some dynamic libraries when loading, and the initialization work is completed by libnativehelper. libnativehelper loads the required dynamic libraries from/system/etc/public. libraries. txt, so that processes subsequently hatched from the zygate process do not need to be reloaded.
Magic Number: the magic number, which is an identifier placed in the file information block in the directory of linux, is typically the first several bytes, such as the first 4 bytes in the header of ELF file, and is used to identify the file type of the ELF file, the application that can be used, and the like.
e _ machine: the field for identifying the CPU architecture to which the binary library file belongs exists in the ELF file header of the binary library file of Linux, and if it is illegally tampered with, the operating system cannot identify the binary library file.
The following description is made of an embodiment in which a target operating system in which an application to be detected is located is an android system, and an architecture of a simulator to be detected is an X86 architecture.
Fig. 1 shows a flow chart of a detection method of a simulator, which is executed by a computer processing device, according to an embodiment of the present invention. The computer processing device may include a cell phone, a notebook computer, etc. As shown in fig. 1, the method comprises the steps of:
step 101: and acquiring an environment configuration file of the application to be detected.
In an embodiment of the present invention, the application to be detected may be an application in a target operating system, and the target operating system may be an android system, a hong meng system, an IOS system, or the like. The environment configuration file may be a configuration file required to enable the application to be detected to correctly run in the target system, such as various binary library files, a system configuration file of an architecture-compatible tool of the application to be detected, and the like.
The binary library file refers to some basic runtime files required by the non-ARM-architecture simulator to run in the ARM-architecture system, such as the Houdini library file and the Libnativehelper library file.
The architecture compatible tool can comprise tools such as an ARM interpreter and a native bridge, wherein the ARM interpreter is used for bridging an ARM C library of the application to be detected in a simulator; native bridge is a facility for translating binary code under the ARM architecture into the X86 instruction set so that it can be executed on the CPU of the X86 architecture.
In yet another embodiment of the present invention, the binary library file in the environment configuration file may include a so file included in a/system/lib/ARM directory, and the system configuration file may include a file included in a/proc/self/mourninfo directory and a default.
In still another embodiment of the present invention, when the target operating system is an android system, the method may be implemented based on a native layer of the android system. Because the reverse difficulty of the native layer is greater than that of the java layer, data acquired through the native layer are difficult to capture and tamper by the simulator to be detected, authenticity of an environment configuration file is guaranteed, and detection accuracy of the simulator is improved.
Step 102: and identifying the environment configuration file, and determining the architecture characteristic information corresponding to the operating environment of the application to be detected.
Consider the principle of operation of the simulator as follows:
in one aspect, a non-ARM architecture (e.g., X86 architecture) simulator may have some specific basic library files that are needed to run under the ARM architecture, and these specific basic library files may be identified by file type or file name.
And because the architecture of the simulator is a non-ARM architecture, two different types of CPU architecture information can be read in the binary library file of the simulator, and the architecture information is contained in the ELF file header of the binary library file.
Thus, in one embodiment of the present invention, when the environment configuration file is a binary library file, the architectural feature information may include an architectural field value in an ELF file header of the binary library file, and a file type of the binary library file.
On the other hand, the simulator needs to run a normal application program, needs to interpret an ARM C library (refer to fig. 2) of the bridge application through an ARM interpreter, and a configuration file of the ARM interpreter needs to be registered in the Linux kernel like other system files, and in order to enable a binary file of a non-ARM architecture to be successfully registered and loaded, a file registration identifier corresponding to the ARM architecture needs to be included.
Also, according to the system binary file identification registration principle of Linux, the file registration id of ARM architecture is different from the id format of non-ARM architecture, and therefore, ARM interpolator needs to be configured as binfmt _ misc (i.e., hybrid binary interpretation mode).
In addition, in order to run code instructions of heterogeneous CPUs (such as ARM) in a simulator system with a non-ARM architecture, an identification interpreter of binary instructions under the ARM architecture, such as a native bridge, must be configured in the simulator system.
Therefore, in a further embodiment of the present invention, when the environment configuration file is a system configuration file, the architecture feature information may include file interpretation mode information, file registration identification, and instruction recognition program configuration information, for example, contained in the system configuration file.
Step 103: and when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining the operating environment as the simulator to be detected.
In one embodiment of the invention, the environment configuration file comprises a plurality of binary library files; the architecture feature information includes an architecture field value of each of the binary library files.
Specifically, the architecture field value refers to an e _ machine field in an ELF Header (ELF Header) of a binary library file, which is used to identify CPU architecture information, such as X86 or ARM, etc.
The simulator and the native system correspond to different CPUs, so that the values of the architecture fields are different, the field is illegally tampered, an operating system cannot identify the field, and the system cannot be normally started.
Thus, step 103 comprises: step 1031: and respectively matching each architecture field value with a target field value corresponding to the simulator to be detected.
And respectively reading the architecture field value under the e _ machine field in the ELF Header (ELF file Header) of each binary library file, and matching the architecture field value with the target field value. The target field value is an architecture field value corresponding to the simulator architecture.
Step 1032: and when the architecture field value is matched with the target field value, determining the operating environment as the simulator to be detected.
When the architecture field value includes the target field value, the two are considered to match.
For example, the architecture field value contained in the ELF file header of a binary library file is Advanced Micro Devices X86-64, which includes a target field value X86, so that there is a match, and the running environment is determined to be the simulator to be tested with the CPU architecture X86.
In yet another embodiment of the present invention, the environment configuration file comprises a plurality of binary library files; the architecture characteristic information comprises a library file type of each binary library file;
step 103 further comprises: step 1033: and respectively matching each library file type with the characteristic library file type corresponding to the simulator to be detected.
In one embodiment of the present invention, the feature library file is a basic library file required for the simulator to be tested to run under the ARM architecture, and may include at least one of/system/lib/ARM/houdii,/system/lib/ARM/libhoudii.so,/system/lib/ARM/libnative bridge.so,/system/lib/ARM/lib/lib.so,/system/lib/ARM/lib.so, and/system/lib/ARM/lib android.so.
The file name of each binary library file can be used as the library file type, the file name of the characteristic library file can be used as the characteristic library file type, and the two types are matched.
Step 1034: and when the library file type is matched with the characteristic library file type, determining the operating environment as the simulator to be detected.
In one embodiment of the invention, when at least one binary library file exists, the corresponding library file type is the same as the characteristic library file type, and the two types are regarded as matching.
In yet another embodiment of the present invention, the environment profile comprises a system profile; the architecture feature information comprises a file interpretation mode corresponding to the system configuration file.
Step 103 comprises: step 1035: and determining interpreter configuration information according to the system configuration file.
In one embodiment of the invention, mount information of the current system process is obtained, a/proc/self/moutnfo directory file is read, and/proc/sys/fs/binfmt _ misc information under the/proc/self/moutnfo directory file is read as interpreter configuration information.
Step 1036: and determining the file interpretation mode according to the interpreter configuration information.
In one embodiment of the present invention, when the proc/sys/fs/binfmt _ misc information is non-empty, it indicates that there is configuration-related information of binfmt _ misc, and thus the file interpretation mode is determined to be the Miscelaneous Binary Format (binfmt _ misc), i.e., the hybrid Binary mode.
In yet another embodiment of the present invention, when the proc/sys/fs/binfmt _ misc information is empty, the file interpretation mode is determined to be the non-hybrid binary mode.
Step 1037: and when the file interpretation mode is a mixed binary mode, determining the operating environment as the simulator to be detected.
In yet another embodiment of the present invention, the environment profile comprises a system profile; the architecture feature information comprises a file registration identifier corresponding to the system configuration file; the file registration flag may include the magic number in the linux system.
Step 103 comprises: step 1038: determining interpreter configuration information according to the system configuration file; and determining the file registration identification according to the interpreter configuration information.
In one embodiment of the present invention, the/proc/sys/fs/binfmt _ misc information is interpreter configuration information, and the presence of the ARM _ dyn file and the ARM _ exe file is found by reading the contents of the/proc/sys/fs/binfmt _ misc information.
When the ARM _ dyn file and the ARM _ exe file exist, the field value under the magic field is read from the ARM _ dyn file and the ARM _ exe file to serve as a file registration identifier. The ARM _ dyn file and the ARM _ exe file are used for storing file basic information of the current binary file. In another embodiment of the present invention, the ARM _ dyn file may include the following contents:
enabled
interpreter/system/lib/ARM/houdini
flags:P
offset 0
magic 7f454c46010101000000000000000000030028
wherein, the magic mark magic number is the file registration identification.
Step 1039: and acquiring a target registration identifier corresponding to the native architecture of the application to be detected.
In an embodiment of the present invention, the target registration identifier is a magic number obtained by registering a file system in a kernel under an ARM architecture, and generally includes 7f454c 460101010000000000000000000000030028 and/or 7f454c 4601010100000000000000020028.
Step 1040: and when the file registration identification is matched with the target registration identification, determining the operating environment as the simulator to be detected.
According to the principle of Linux, whether the magic number of the binary file is an identification value obtained when the file system is successfully registered needs to be checked in the loading process of the binary file, and if the registration identification corresponding to the file system of the ARM architecture cannot be found, the binary file cannot be loaded. Therefore, in order to identify and load the binary file under the ARM architecture in the simulator, the ARM-related file (i.e., the file containing the file registration identifier) needs to be placed under the hybrid binary interpretation script for interpretation.
Therefore, when the file registration identifier found in the ARM _ dyn file and the ARM _ exe file under the directory of/proc/sys/fs/binfmt _ misc is the same as the target registration identifier, the two files are considered as matching.
In yet another embodiment of the present invention, the environment profile comprises a system profile; the architecture feature information comprises instruction identification program configuration information corresponding to the system configuration file; the instruction identification program is used for converting the instruction under the architecture of the simulator to be detected into the instruction under the native architecture of the application to be detected; in one embodiment of the invention, the instruction recognition program may include native bridge.
Step 103 comprises: step 1041: and when the instruction identification program configuration information is non-empty, determining that the operating environment is the simulator to be detected.
In an embodiment of the invention, a ro.dalvik.vm.native.bridge configuration item in a default.prop configuration file of a system is inquired, whether the configuration item has a value or not is checked, if the configuration item has the value, a corresponding directory file is opened by using a dlopen instruction, whether a native bridge itf symbol exists or not is searched by using dlsym, and when the native bridge itf symbol exists, the configuration information of the instruction recognition program is determined to be non-null.
In yet another embodiment of the present invention, when there is no value in the ro.dalvik.vm.native.bridge configuration item or no native bridge identifier under the corresponding directory, it is determined that the approximate instruction recognition program configuration information is empty.
In yet another embodiment of the present invention, the aforementioned architecture compatible tool may only operate if the binary library file is configured to complete, taking into account that the binary library file characterizes more fundamental environmental operational configuration information, thereby completing the interpretation and identification between the simulator instructions and the native system instructions. Therefore, in order to further improve the accuracy of the simulator detection, in a further embodiment of the present invention, step 103 may also be the flow shown in fig. 3:
referring to fig. 3, when the binary library file meets a first preset condition, if the system configuration file meets a second preset condition, determining that the operating environment is the simulator to be tested;
wherein the first preset condition is that the architecture field value is matched with a target field value and the library file type is matched with a feature library file type. Wherein the target field value is described in step 1031, and the feature library file type is described in step 1033.
The second preset condition is that the file interpretation mode is at least one of a mixed binary mode, the file registration identifier is matched with a target registration identifier, and the instruction recognition program configuration information is not null. Wherein the target registration identification is as described in step 1039.
It should be noted that, the execution order for determining whether the architecture field value matches the target field value and determining whether the library file type matches the feature library file type is limited to that shown in fig. 3, and the execution order may be exchanged without affecting the detection effect of the simulator according to the embodiment of the present invention.
Different from interfaces of hardware such as a detection sensor and the like in a system adopted in the prior art, the simulator is easy to forge, read information detected by loading a specific file is easy to modify, so that the detection accuracy is low, and the compatibility problem that the execution of a specific binary code in a memory address easily triggers the collapse of an application process and is difficult to ensure is solved, by matching the architecture characteristic information with the target architecture condition corresponding to the simulator to be tested, therefore, the detection of the simulator to be detected is completed, and the detection is completed at the bottom layer of the system, so that specific files or codes do not need to be loaded, and the read information is not easy to modify, thereby improving the accuracy and compatibility of the detection of the simulator.
Fig. 4 shows a schematic structural diagram of a detection device of a simulator provided in an embodiment of the present invention. As shown in fig. 2, the apparatus 200 includes: an acquisition module 201, a recognition module 202 and a determination module 203.
The acquiring module 201 is configured to acquire an environment configuration file corresponding to an application to be detected;
the identification module 202 is configured to identify the environment configuration file, and determine architecture feature information corresponding to the operating environment of the application to be detected;
a determining module 203, configured to determine that the operating environment is the simulator to be detected when the architecture feature information meets a target architecture condition corresponding to the simulator to be detected
In an optional mode, when the application to be detected is an application in an android system, the method is implemented based on a native layer of the android system; the environment configuration file comprises a plurality of binary library files; the architecture characteristic information comprises an architecture field value of each binary library file;
the determining module 203 is further configured to: matching each architecture field value with a target field value corresponding to the simulator to be detected respectively;
and when the architecture field value is matched with the target field value, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment configuration file includes a plurality of binary library files; the architecture characteristic information comprises a library file type of each binary library file;
the determining module 203 is further configured to: respectively matching each library file type with the characteristic library file type corresponding to the simulator to be detected;
and when the library file type is matched with the characteristic library file type, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment profile comprises a system profile; the architecture feature information comprises a file interpretation mode corresponding to the system configuration file; the determining module 203 is further configured to:
determining interpreter configuration information according to the system configuration file;
determining the file interpretation mode according to the interpreter configuration information;
and when the file interpretation mode is a mixed binary mode, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment profile comprises a system profile; the architecture feature information comprises a file registration identifier corresponding to the system configuration file; the determining module 203 is further configured to:
determining interpreter configuration information according to the system configuration file;
determining the file registration identification according to the interpreter configuration information;
acquiring a target registration identifier corresponding to the native architecture of the application to be detected;
and when the file registration identification is matched with the target registration identification, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment profile comprises a system profile; the architecture feature information comprises instruction identification program configuration information corresponding to the system configuration file; the instruction identification program is used for converting the instruction under the architecture of the simulator to be detected into the instruction under the native architecture of the application to be detected; the determining module 203 is further configured to:
and when the instruction identification program configuration information is non-empty, determining that the operating environment is the simulator to be detected.
In an optional mode, the environment configuration file comprises a system configuration file and a plurality of binary library files; the architecture feature information comprises library file types and architecture field values of the binary library files, and file interpretation modes, file registration identifiers and instruction recognition program configuration information corresponding to the system configuration files; the determining module 203 is further configured to:
when the binary library file meets a first preset condition, if the system configuration file meets a second preset condition, determining that the operating environment is the simulator to be detected; wherein the first preset condition is that the architecture field value is matched with a target field value and the library file type is matched with a feature library file type; the second preset condition is that the file interpretation mode is at least one of a mixed binary mode, the file registration identifier is matched with a target registration identifier, and the instruction recognition program configuration information is not null.
The implementation principle of the detection device of the simulator provided by the embodiment of the invention is the same as the steps of the detection method of the simulator in the previous embodiment, and the description is omitted.
Different from interfaces of hardware such as a detection sensor and the like in a system adopted in the prior art, the simulator is easy to forge, read information detected by loading a specific file is easy to modify, so that the detection accuracy is low, and the compatibility problem that the execution of a specific binary code in a memory address easily triggers the collapse of an application process and is difficult to ensure is solved, by matching the architecture characteristic information with the target architecture condition corresponding to the simulator to be tested, therefore, the detection of the simulator to be detected is completed, and the detection is completed at the bottom layer of the system, so that specific files or codes do not need to be loaded, and the read information is not easy to modify, thereby improving the accuracy and compatibility of the detection of the simulator.
Fig. 5 is a schematic structural diagram illustrating a detection device of a simulator according to an embodiment of the present invention, where the specific embodiment of the present invention does not limit a specific implementation of the detection device of the simulator.
As shown in fig. 5, the detection device of the simulator may include: a processor (processor)302, a communication Interface 304, a memory 306, and a communication bus 308.
Wherein: the processor 302, communication interface 304, and memory 306 communicate with each other via a communication bus 308. A communication interface 304 for communicating with network elements of other devices, such as clients or other servers. The processor 302 is configured to execute the program 310, and may specifically perform relevant steps in the above-described detection method embodiment for the simulator.
In particular, program 310 may include program code comprising computer-executable instructions.
The processor 302 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement an embodiment of the present invention. The detection device of the simulator comprises one or more processors, which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.
And a memory 306 for storing a program 310. Memory 306 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
Specifically, the program 310 may be invoked by the processor 302 to cause the detection device of the simulator to perform the following operations:
acquiring an environment configuration file of an application to be detected;
identifying the environment configuration file, and determining the architecture characteristic information corresponding to the operating environment of the application to be detected;
and when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining the operating environment as the simulator to be detected.
In an optional mode, when the application to be detected is an application in an android system, the method is implemented based on a native layer of the android system; the environment configuration file comprises a plurality of binary library files; the architecture characteristic information comprises an architecture field value of each binary library file; the program 310 is invoked by the processor 302 to cause the detection device of the simulator to perform the following operations:
matching each architecture field value with a target field value corresponding to the simulator to be detected respectively;
and when the architecture field value is matched with the target field value, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment configuration file includes a plurality of binary library files; the architecture characteristic information comprises a library file type of each binary library file; the program 310 is invoked by the processor 302 to cause the detection device of the simulator to perform the following operations:
respectively matching each library file type with the characteristic library file type corresponding to the simulator to be detected;
and when the library file type is matched with the characteristic library file type, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment profile comprises a system profile; the architecture feature information comprises a file interpretation mode corresponding to the system configuration file; the program 310 is invoked by the processor 302 to cause the detection device of the simulator to perform the following operations:
determining interpreter configuration information according to the system configuration file;
determining the file interpretation mode according to the interpreter configuration information;
and when the file interpretation mode is a mixed binary mode, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment profile comprises a system profile; the architecture feature information comprises a file registration identifier corresponding to the system configuration file; the program 310 is invoked by the processor 302 to cause the detection device of the simulator to perform the following operations:
determining interpreter configuration information according to the system configuration file;
determining the file registration identification according to the interpreter configuration information;
acquiring a target registration identifier corresponding to the native architecture of the application to be detected;
and when the file registration identification is matched with the target registration identification, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment profile comprises a system profile; the architecture feature information comprises instruction identification program configuration information corresponding to the system configuration file; the instruction identification program is used for converting the instruction under the architecture of the simulator to be detected into the instruction under the native architecture of the application to be detected; the program 310 is invoked by the processor 302 to cause the detection device of the simulator to perform the following operations:
and when the instruction identification program configuration information is non-empty, determining that the operating environment is the simulator to be detected.
In an optional mode, the environment configuration file comprises a system configuration file and a plurality of binary library files; the architecture feature information comprises library file types and architecture field values of the binary library files, and file interpretation modes, file registration identifiers and instruction recognition program configuration information corresponding to the system configuration files; the program 310 is invoked by the processor 302 to cause the detection device of the simulator to perform the following operations:
when the binary library file meets a first preset condition, if the system configuration file meets a second preset condition, determining that the operating environment is the simulator to be detected; wherein the first preset condition is that the architecture field value is matched with a target field value and the library file type is matched with a feature library file type; the second preset condition is that the file interpretation mode is at least one of a mixed binary mode, the file registration identifier is matched with a target registration identifier, and the instruction recognition program configuration information is not null.
The implementation principle of the detection device of the simulator provided by the embodiment of the invention is the same as the steps of the detection method of the simulator in the previous embodiment, and the description is omitted.
Different from interfaces of hardware such as a detection sensor and the like in a system adopted in the prior art, the simulator is easy to forge, read information detected by loading a specific file is easy to modify, so that the detection accuracy is low, and the compatibility problem that the execution of a specific binary code in a memory address easily triggers the collapse of an application process and is difficult to ensure is solved, by matching the architecture characteristic information with the target architecture condition corresponding to the simulator to be tested, therefore, the detection of the simulator to be detected is completed, and the detection is completed at the bottom layer of the system, so that specific files or codes do not need to be loaded, and the read information is not easy to modify, thereby improving the accuracy and compatibility of the detection of the simulator.
An embodiment of the present invention provides a computer-readable storage medium, where the storage medium stores at least one executable instruction, and when the executable instruction runs on a detection device of a simulator, the detection device of the simulator executes a detection method of the simulator in any method embodiment described above.
The executable instructions may be specifically configured to cause the detection device of the simulator to perform the following operations:
acquiring an environment configuration file of an application to be detected;
identifying the environment configuration file, and determining the architecture characteristic information corresponding to the operating environment of the application to be detected;
and when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining the operating environment as the simulator to be detected.
In an optional mode, when the application to be detected is an application in an android system, the method is implemented based on a native layer of the android system; the environment configuration file comprises a plurality of binary library files; the architecture characteristic information comprises an architecture field value of each binary library file; the executable instructions cause the detection device of the simulator to:
matching each architecture field value with a target field value corresponding to the simulator to be detected respectively;
and when the architecture field value is matched with the target field value, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment configuration file includes a plurality of binary library files; the architecture characteristic information comprises a library file type of each binary library file; the executable instructions cause the detection device of the simulator to:
respectively matching each library file type with the characteristic library file type corresponding to the simulator to be detected;
and when the library file type is matched with the characteristic library file type, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment profile comprises a system profile; the architecture feature information comprises a file interpretation mode corresponding to the system configuration file; the executable instructions cause the detection device of the simulator to:
determining interpreter configuration information according to the system configuration file;
determining the file interpretation mode according to the interpreter configuration information;
and when the file interpretation mode is a mixed binary mode, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment profile comprises a system profile; the architecture feature information comprises a file registration identifier corresponding to the system configuration file; the executable instructions cause the detection device of the simulator to:
determining interpreter configuration information according to the system configuration file;
determining the file registration identification according to the interpreter configuration information;
acquiring a target registration identifier corresponding to the native architecture of the application to be detected;
and when the file registration identification is matched with the target registration identification, determining the operating environment as the simulator to be detected.
In an alternative approach, the environment profile comprises a system profile; the architecture feature information comprises instruction identification program configuration information corresponding to the system configuration file; the instruction identification program is used for converting the instruction under the architecture of the simulator to be detected into the instruction under the native architecture of the application to be detected; the executable instructions cause the detection device of the simulator to:
and when the instruction identification program configuration information is non-empty, determining that the operating environment is the simulator to be detected.
In an optional mode, the environment configuration file comprises a system configuration file and a plurality of binary library files; the architecture feature information comprises library file types and architecture field values of the binary library files, and file interpretation modes, file registration identifiers and instruction recognition program configuration information corresponding to the system configuration files; the executable instructions cause the detection device of the simulator to:
when the binary library file meets a first preset condition, if the system configuration file meets a second preset condition, determining that the operating environment is the simulator to be detected; wherein the first preset condition is that the architecture field value is matched with a target field value and the library file type is matched with a feature library file type; the second preset condition is that the file interpretation mode is at least one of a mixed binary mode, the file registration identifier is matched with a target registration identifier, and the instruction recognition program configuration information is not null.
The implementation principle of the computer storage medium provided by the embodiment of the invention is the same as the steps of the detection method of the simulator in the previous embodiment, and the description is omitted.
Different from interfaces of hardware such as a detection sensor and the like in a system adopted in the prior art, the simulator is easy to forge, read information detected by loading a specific file is easy to modify, so that the detection accuracy is low, and the compatibility problem that the execution of a specific binary code in a memory address easily triggers the collapse of an application process and is difficult to ensure is solved, by matching the architecture characteristic information with the target architecture condition corresponding to the simulator to be tested, therefore, the detection of the simulator to be detected is completed, and the detection is completed at the bottom layer of the system, so that specific files or codes do not need to be loaded, and the read information is not easy to modify, thereby improving the accuracy and compatibility of the detection of the simulator.
The embodiment of the invention provides a detection device of a simulator, which is used for executing the detection method of the simulator.
Embodiments of the present invention provide a computer program that can be invoked by a processor to enable a detection device of a simulator to execute a detection method of the simulator in any of the above method embodiments.
Embodiments of the present invention provide a computer program product comprising a computer program stored on a computer-readable storage medium, the computer program comprising program instructions that, when run on a computer, cause the computer to perform the method of detection of a simulator in any of the above-described method embodiments.
The algorithms or displays presented herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. In addition, embodiments of the present invention are not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the embodiments of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the invention and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names. The steps in the above embodiments should not be construed as limiting the order of execution unless specified otherwise.
Claims (10)
1. A method of testing a simulator, the method comprising:
acquiring an environment configuration file of an application to be detected;
identifying the environment configuration file, and determining the architecture characteristic information corresponding to the operating environment of the application to be detected;
and when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining the operating environment as the simulator to be detected.
2. The method according to claim 1, wherein when the application to be detected is an application in an android system, the method is implemented based on a native layer of the android system; the environment configuration file comprises a plurality of binary library files; the architecture characteristic information comprises an architecture field value of each binary library file; when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining that the operating environment is the simulator to be detected, including:
matching each architecture field value with a target field value corresponding to the simulator to be detected respectively;
and when the architecture field value is matched with the target field value, determining the operating environment as the simulator to be detected.
3. The method of claim 1, wherein the environment configuration file comprises a plurality of binary library files; the architecture characteristic information comprises a library file type of each binary library file; when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining that the operating environment is the simulator to be detected, including:
respectively matching each library file type with the characteristic library file type corresponding to the simulator to be detected;
and when the library file type is matched with the characteristic library file type, determining the operating environment as the simulator to be detected.
4. The method of claim 1, wherein the environment profile comprises a system profile; the architecture feature information comprises a file interpretation mode corresponding to the system configuration file; when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining that the operating environment is the simulator to be detected, including:
determining interpreter configuration information according to the system configuration file;
determining the file interpretation mode according to the interpreter configuration information;
and when the file interpretation mode is a mixed binary mode, determining the operating environment as the simulator to be detected.
5. The method of claim 1, wherein the environment profile comprises a system profile; the architecture feature information comprises a file registration identifier corresponding to the system configuration file; when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining that the operating environment is the simulator to be detected, including:
determining interpreter configuration information according to the system configuration file;
determining the file registration identification according to the interpreter configuration information;
acquiring a target registration identifier corresponding to the native architecture of the application to be detected;
and when the file registration identification is matched with the target registration identification, determining the operating environment as the simulator to be detected.
6. The method of claim 1, wherein the environment profile comprises a system profile; the architecture feature information comprises instruction identification program configuration information corresponding to the system configuration file; the instruction identification program is used for converting the instruction under the architecture of the simulator to be detected into the instruction under the native architecture of the application to be detected; when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining that the operating environment is the simulator to be detected, including:
and when the instruction identification program configuration information is non-empty, determining that the operating environment is the simulator to be detected.
7. The method of claim 1, wherein the environment configuration file comprises a system configuration file and a plurality of binary library files; the architecture feature information comprises library file types and architecture field values of the binary library files, and file interpretation modes, file registration identifiers and instruction recognition program configuration information corresponding to the system configuration files; when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected, determining that the operating environment is the simulator to be detected, including:
when the binary library file meets a first preset condition, if the system configuration file meets a second preset condition, determining that the operating environment is the simulator to be detected; wherein the first preset condition is that the architecture field value is matched with a target field value and the library file type is matched with a feature library file type; the second preset condition is that the file interpretation mode is at least one of a mixed binary mode, the file registration identifier is matched with a target registration identifier, and the instruction recognition program configuration information is not null.
8. A simulator testing apparatus, the apparatus comprising:
the acquisition module is used for acquiring an environment configuration file corresponding to the application to be detected;
the identification module is used for identifying the environment configuration file and determining the architecture characteristic information corresponding to the operating environment of the application to be detected;
and the determining module is used for determining the operating environment as the simulator to be detected when the architecture characteristic information meets the target architecture condition corresponding to the simulator to be detected.
9. A detection apparatus of a simulator, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction which causes the processor to execute the operation of the detection method of the simulator according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that it stores at least one executable instruction that, when run on a detection device of a simulator, causes the detection device of the simulator to perform the operations of the detection method of the simulator according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110909308.8A CN113590404A (en) | 2021-08-09 | 2021-08-09 | Simulator detection method, device, equipment and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110909308.8A CN113590404A (en) | 2021-08-09 | 2021-08-09 | Simulator detection method, device, equipment and computer storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113590404A true CN113590404A (en) | 2021-11-02 |
Family
ID=78256453
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110909308.8A Pending CN113590404A (en) | 2021-08-09 | 2021-08-09 | Simulator detection method, device, equipment and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113590404A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114706630A (en) * | 2022-04-14 | 2022-07-05 | 上海上讯信息技术股份有限公司 | Method and system for identifying simulator based on file format |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7313773B1 (en) * | 2004-05-26 | 2007-12-25 | Coware, Inc. | Method and device for simulator generation based on semantic to behavioral translation |
| CN104134041A (en) * | 2014-07-31 | 2014-11-05 | 北京奇虎科技有限公司 | Anti-detecting method and device of terminal simulator system |
| CN106815058A (en) * | 2016-12-08 | 2017-06-09 | 同盾科技有限公司 | A kind of recognition methods of simulator and system |
| CN110196795A (en) * | 2018-06-21 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Detect the method and relevant apparatus of mobile terminal application operating status |
| CN110457220A (en) * | 2019-08-08 | 2019-11-15 | 北京智游网安科技有限公司 | Simulator detection method, intelligent terminal and storage medium based on android system |
-
2021
- 2021-08-09 CN CN202110909308.8A patent/CN113590404A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7313773B1 (en) * | 2004-05-26 | 2007-12-25 | Coware, Inc. | Method and device for simulator generation based on semantic to behavioral translation |
| CN104134041A (en) * | 2014-07-31 | 2014-11-05 | 北京奇虎科技有限公司 | Anti-detecting method and device of terminal simulator system |
| CN106815058A (en) * | 2016-12-08 | 2017-06-09 | 同盾科技有限公司 | A kind of recognition methods of simulator and system |
| CN110196795A (en) * | 2018-06-21 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Detect the method and relevant apparatus of mobile terminal application operating status |
| CN110457220A (en) * | 2019-08-08 | 2019-11-15 | 北京智游网安科技有限公司 | Simulator detection method, intelligent terminal and storage medium based on android system |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114706630A (en) * | 2022-04-14 | 2022-07-05 | 上海上讯信息技术股份有限公司 | Method and system for identifying simulator based on file format |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4913302B2 (en) | Language subset validation | |
| AU771699B2 (en) | Token-based linking | |
| US9811360B2 (en) | Dynamic determination of application server runtime classloading | |
| US7392371B2 (en) | Method and apparatus for using a volume top file to boot firmware modules | |
| US20030154368A1 (en) | Method and system for linking firmware modules in a pre-memory execution environment | |
| WO2015164439A1 (en) | Structural identification of dynamically-generated, pattern-based classes | |
| CN111324396A (en) | Block chain intelligent contract execution method, device and equipment | |
| CN113961919A (en) | Malicious software detection method and device | |
| CN111949513A (en) | Configuration file loading method and device, electronic equipment and readable storage device | |
| US10534732B2 (en) | Exposing memory-mapped IO devices to drivers by emulating PCI bus and PCI device configuration space | |
| CN113590404A (en) | Simulator detection method, device, equipment and computer storage medium | |
| US11599342B2 (en) | Pathname independent probing of binaries | |
| CN115794259B (en) | Method for generating device tree through ACPI | |
| CN110955566A (en) | Debugging method | |
| CN113590133A (en) | Android system injection detection method, device, equipment and computer storage medium | |
| JP4886188B2 (en) | Information processing apparatus and control method therefor, computer program, and storage medium | |
| CN113867805B (en) | Method and system for constructing measurement chain compatible with trusted root based on firmware | |
| CN117093227B (en) | Method and device for executing intelligent contract | |
| US12008171B2 (en) | Program download method for intelligent terminal with memory card identifier and intelligent terminal with memory card identifier | |
| US20220066911A1 (en) | Virtual machine for developing and testing target code for hardware designs | |
| US20230315213A1 (en) | Program download method for intelligent terminal and intelligent terminal | |
| CN105893092B (en) | COM component processing method and device | |
| CN113986461A (en) | Intrusive semi-localization simulation method for system call on target processor | |
| CN117931145A (en) | Application construction method, device, computing equipment and computer storage medium | |
| CN113641426A (en) | Shelling search and implementation method and system based on source code modification of android terminal |
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 |