System control method, device and equipment
The name of the target class and the target method in the system is different from the original name, and the printing of the relevant abnormal stack information is prohibited, which solves the problem of the attacker through the core cracking the software signature verification. Essence
Patent Information
- Application Number
- CN202411509773.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-28
- Publication Date
- 2025-01-28
AI Technical Summary
In the prior art, attackers bypass the verification of software signature or version number through core cracking, resulting in piracy or cracking software in the system, destroying the system ecosystem.
The name of the target class and the target method is different from the original name of the target system and prohibit the printing of anomalian stack information that can position the target class and the target method to prevent the attacker from bypassing the software signature school through the core cracking through the core cracking. Examination.
Effectively increased the difficulty of the system's cracking of the system, so that the attacker could not bypass the software signature or version number verification through the core crack, thereby protecting the system from being cracked by malicious software.
Smart Images
Figure CN119377948A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present invention relate to the field of system security technology, and in particular to a system control method, device, equipment, and computer-readable storage medium. Background Art
[0002] At present, computer systems mainly prevent malware intrusion by detecting the signature of application software (APP). Although there are various methods for detecting APP software signatures, attackers often bypass the verification of signatures or version numbers by cracking the core. For example, in the Android system, the software loads the signature-related library java.security when zygote is initialized. Attackers HOOK security-related classes and HOOK classes and methods related to installation package verification during the Android installation process to bypass the verification of software signatures, allowing pirated or cracked software to survive in the system and destroy the system's own ecology. Summary of the invention
[0003] In view of the above problems, the embodiments of the present invention provide a system control method, device, equipment and computer-readable storage medium, which are used to solve the problem in the prior art that attackers bypass the verification of signatures or version numbers by core cracking.
[0004] According to one aspect of an embodiment of the present invention, a system control method is provided, the method comprising:
[0005] When the target system receives a print request for target exception stack information, the target exception stack information is matched with the target information name;
[0006] The target information name includes at least one of the name of the target class, the name of the target method, the name of the target method call chain, and the name of the target location information; the target location information is used to locate the target class or target method;
[0007] The name of the target class is different from its original name in the target system; the name of the target method is different from its original name in the target system;
[0008] If the target exception stack information matches at least one target information name, the print request is prohibited.
[0009] Specifically, the present invention configures the names of the target class and the target method to be different from their original names in the target system, so that the attacker cannot know the real names of the target class and the target method without knowing the source code, and cannot crack the system target class and the target method, thereby making it impossible for the attacker to bypass the verification of the software signature or version number. Furthermore, the present invention prohibits the operation of printing the exception stack information that can locate the target class and the target method, so that the attacker cannot know the custom names of the target class and the target method by printing the exception stack information, thereby increasing the difficulty of the attacker to crack the system, so that the attacker cannot bypass the verification of the software signature or version number by core cracking.
[0010] In some optional embodiments, before matching the target exception stack information with the target information name, the method further includes:
[0011] checking permissions for the print request;
[0012] If the permission of the print request is prohibited, prohibiting the print request;
[0013] If the permission of the print request is permission, the target exception stack information is matched with the target information name.
[0014] Specifically, when receiving a request to print target exception stack information, the present invention first checks the permission of the print request according to the original standard of the target system. If the permission of the print request is permitted, it triggers the operation of matching the target exception stack information with the target information name to prohibit the operation of printing the exception stack information that can locate the target class and the target method, so that the attacker cannot learn the custom name of the target class and the target method by printing the exception stack information, thereby increasing the difficulty of the attacker to crack the system and preventing the attacker from bypassing the verification of the software signature or version number by core cracking.
[0015] In some optional manners, if the target exception stack information matches at least one target information name, prohibiting the print request includes:
[0016] If at least one target information name is matched, a print request for information corresponding to the target information name in the target exception stack information is prohibited.
[0017] Specifically, if the target exception stack information matches at least one target information name, the printing request of the corresponding information of the target information name in the exception stack information is prohibited to prevent attackers from knowing the custom names of the target class and target method by printing the exception stack information, thereby increasing the difficulty for attackers to crack the system and making it impossible for attackers to bypass the verification of software signatures or version numbers.
[0018] In some optional manners, after prohibiting the printing request of the information corresponding to the target information name in the exception stack information, the method further includes:
[0019] A print request for information corresponding to a non-target information name in the target exception stack information is allowed.
[0020] Specifically, if the target exception stack information matches at least one target information name, the printing request of the information corresponding to the target information name in the exception stack information is prohibited, and the printing request of the information corresponding to the non-target information name in the exception stack information is allowed. Among them, the corresponding information of the non-target information name in the exception stack information cannot locate the target class or target method. While the attacker can obtain part of the exception stack information, he cannot know the custom name of the target class and target method by printing the exception stack information, which increases the difficulty for the attacker to crack the system, and thus makes it impossible for the attacker to bypass the verification of the software signature or version number.
[0021] In some optional manners, if the target exception stack information matches at least one target information name, prohibiting the print request includes:
[0022] If at least one target information name is matched, the printing request of the target exception stack information is prohibited.
[0023] Specifically, if the target exception stack information matches at least one target information name, the printing request of the target exception stack information is prohibited to prevent attackers from knowing the custom names of the target class and target method by printing the exception stack information, thereby increasing the difficulty for attackers to crack the system, and thus making it impossible for attackers to bypass the verification of software signatures or version numbers.
[0024] In some optional ways, if the target exception stack information does not match any target information name, an operation of printing the target exception stack information is performed.
[0025] Specifically, it allows obtaining other exception stack information. This type of exception stack information cannot locate the target class and target method, and the attacker cannot know the custom name of the target class and target method, which increases the difficulty for the attacker to crack the system, and thus makes it impossible for the attacker to bypass the verification of the software signature or version number.
[0026] In some optional ways, receiving a call request of a target class or a target method;
[0027] Determine the name of the target class according to the call request of the target class; and call the target class based on the name of the target class;
[0028] According to the calling request of the target method, the name of the target method is determined; and based on the name of the target method, the target method is called.
[0029] Specifically, the present invention configures the names of the target class and the target method to be different from their original names in the target system, and calls the target class and the target method based on their real names, which can prevent attackers from knowing the custom names of the target class and the target method by printing exception stack information, thereby increasing the difficulty for attackers to crack the system, and further making it impossible for attackers to bypass the verification of software signatures or version numbers.
[0030] In some optional ways, when the target system performs signature verification on any application, a call request of the target class or target method is triggered.
[0031] Specifically, the present invention calls the target class or target method to perform signature verification on the application. Without knowing the source code, the attacker cannot know the custom name of the target class and the target method, thereby making it impossible for the attacker to bypass the verification of the software signature or version number. Therefore, the system can protect the system from being cracked by malicious software by detecting the software signature.
[0032] According to another aspect of an embodiment of the present invention, there is provided a control device of a system, comprising: a matching module and a control module;
[0033] A matching module, configured to match the target exception stack information with the target information name when the target system receives a print request for the target exception stack information;
[0034] The target information name includes at least one of the name of the target class, the name of the target method, the name of the target method call chain, and the name of the target location information; the target location information is used to locate the target class or target method;
[0035] The name of the target class is different from its original name in the target system; the name of the target method is different from its original name in the target system;
[0036] The control module is configured to prohibit the printing request if the target exception stack information matches at least one target information name.
[0037] According to another aspect of an embodiment of the present invention, there is provided a control device of a system, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other through the communication bus;
[0038] The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the operation of the system control method described in the content of the present invention.
[0039] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, wherein the storage medium stores at least one executable instruction, wherein the executable instruction enables a control device / apparatus of a system to execute the operation of the control method of the system as described in the present invention.
[0040] The embodiment of the present invention configures the names of the target class and the target method to be different from their original names in the target system, so that the attacker cannot crack the system target class and the target method without knowing the source code, thereby making it impossible for the attacker to bypass the verification of the software signature or version number. The embodiment of the present invention prohibits the printing of the exception stack information that can locate the target class and the target method, so that the attacker cannot know the custom name of the target class and the target method by printing the exception stack information, thereby increasing the difficulty for the attacker to crack the system, and the attacker cannot bypass the verification of the software signature or version number by core cracking, so that the system can protect the system from being cracked by malicious software by detecting the software signature.
[0041] The above description is only an overview of the technical solution of the embodiment of the present invention. In order to more clearly understand the technical means of the embodiment of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiment of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0042] The accompanying drawings are only used to illustrate the embodiments and are not to be considered as limiting the present invention. In addition, the same reference symbols are used to represent the same components throughout the accompanying drawings. In the accompanying drawings:
[0043] Figure 1 A schematic flow chart showing a first embodiment of a control method for a system provided by the present invention;
[0044] Figure 2 A schematic flow chart of a second embodiment of a control method of a system provided by the present invention is shown;
[0045] Figure 3 A schematic flow chart of a third embodiment of a control method of a system provided by the present invention is shown;
[0046] Figure 4 A schematic structural diagram of an embodiment of a control device of a system provided by the present invention is shown;
[0047] Figure 5 A schematic structural diagram of an embodiment of a control device of the system provided by the present invention is shown. DETAILED DESCRIPTION
[0048] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be limited to the embodiments set forth herein.
[0049] Figure 1 FIG. 1 is a flow chart showing a first embodiment of a control method of the system of the present invention, the method being executed by a control device of the system. Figure 1 As shown, the method comprises the following steps:
[0050] Step 110: When the target system receives a print request for target exception stack information, the target exception stack information is matched with the target information name.
[0051] The target information name includes at least one of the name of the target class, the name of the target method, the name of the target method call chain and the name of the target location information; the target location information is called to locate the target class or target method.
[0052] The name of the target class is different from its original name in the target system; the name of the target method is different from its original name in the target system.
[0053] In some optional embodiments, the system includes an in-vehicle operating system such as a smart cockpit system. The type of the system is an Android system, etc. The intrusion of a cracked version of the APP software into the vehicle system may cause the vehicle system to crash, run unstably, or have security vulnerabilities, making the vehicle system vulnerable to attacks or malware intrusion, endangering the safety of vehicle driving.
[0054] Exception stack information is information generated when an error or exception occurs during the execution of a system program. It is used to locate the exception to help developers locate and fix the exception problem. Exception stack information is generally stored in memory and is used to print to the console or log file when an exception occurs in the program. Exception stack information includes: the method call chain that caused the exception, as well as the specific location and cause of the exception.
[0055] If the name of a target method in the native class of the Android system is A, the control device configures the target method name to B. When the attacker uses name A to HOOK the target method, since there is no method with name A in the system code, the attacker's attack behavior will fail and an error will be reported. The system will generate the exception stack information of the target method B. Through the exception stack information of the target method B, it can be known that the attacker's attack behavior is to execute to the location of the target method B and report an error, thereby obtaining the name of the target method B.
[0056] In some optional embodiments, before matching the target exception stack information with the target information name, the method further includes:
[0057] checking permissions for the print request;
[0058] If the permission of the print request is prohibited, prohibiting the print request;
[0059] If the permission of the print request is permission, the target exception stack information is matched with the target information name.
[0060] In some optional ways, the control device controls the access of the Java program to the system resources through the Java security manager (SecurityManager).
[0061] Specifically, the Java security manager uses the Java standard API to check the permission of the print request. If the permission of the print request is prohibited, the print request is prohibited; if the permission of the print request is permitted, the target exception stack information is matched with the target information name.
[0062] Specifically, the control device enables the security manager, rewrites the checkPermission method to create a custom permission check mode, and performs permission check on the print request based on the custom permission check mode, that is, based on matching the target exception stack information with the target information name.
[0063] The target information name can be used to locate the target class or target method. By matching the target exception stack information with the target information name, it is possible to detect that the target exception stack information requested to be printed contains information that can locate the target class or target method, and it is possible to detect that the target information name corresponds to information in the target exception stack information.
[0064] Step 120: If the target exception stack information matches at least one target information name, the print request is prohibited.
[0065] In some optional manners, if the target exception stack information matches at least one target information name, prohibiting the print request includes:
[0066] If at least one target information name is matched, a print request for information corresponding to the target information name in the target exception stack information is prohibited.
[0067] In some optional manners, after prohibiting the printing request of the information corresponding to the target information name in the exception stack information, the method further includes:
[0068] A print request for information corresponding to a non-target information name in the target exception stack information is allowed.
[0069] Specifically, if at least one target information name is matched, the corresponding information of the target information name in the target exception stack information and the corresponding information of the non-target information name in the target exception stack information are detected. The control device prohibits printing the corresponding information of the target information name in the target exception stack information, and allows printing the corresponding information of the non-target information name in the target exception stack information. Among them, the corresponding information of the non-target information name in the exception stack information cannot locate the target class or target method. While the attacker can obtain part of the exception stack information, he cannot know the custom name of the target class and target method by printing the exception stack information, which increases the difficulty for the attacker to crack the system, and thus makes it impossible for the attacker to bypass the verification of the software signature or version number.
[0070] In some optional manners, if the target exception stack information matches at least one target information name, prohibiting the print request includes:
[0071] If at least one target information name is matched, the printing request of the target exception stack information is prohibited.
[0072] Specifically, if at least one target information name is matched, it is prohibited to print all requested exception stack information, that is, the target exception stack information, to prevent attackers from knowing the custom names of the target class and target method by printing the exception stack information, thereby increasing the difficulty for attackers to crack the system, and thus making it impossible for attackers to bypass the verification of software signatures or version numbers.
[0073] Specifically, if at least one target information name is matched, the control device uses the security manager to throw a SecurityException prompt to prohibit the print request; or uses the security manager to directly prohibit the print request without prompting any information.
[0074] The embodiment of the present invention checks the permission of the print request through a customized security manager, and limits the printing permission of the exception stack information of the target class and the target method, so as to prevent the customized names of the target class and the target method from being exposed by printing the exception stack information, thereby increasing the difficulty for attackers to crack the system. Attackers cannot bypass the verification of software signatures or version numbers by core cracking.
[0075] In some optional ways, if the target exception stack information does not match any target information name, an operation of printing the target exception stack information is performed.
[0076] Specifically, it allows obtaining other exception stack information. This type of exception stack information cannot locate the target class and target method, and the attacker cannot know the custom name of the target class and target method, which increases the difficulty for the attacker to crack the system, and thus makes it impossible for the attacker to bypass the verification of the software signature or version number.
[0077] Figure 2 FIG. 1 is a flow chart showing a second embodiment of a control method of the system of the present invention, the method being executed by a control device of the system. Figure 2 As shown, the method comprises the following steps:
[0078] Step 220: Receive a call request for a target class or a target method.
[0079] Step 221: Determine the name of the target class according to the call request of the target class; and call the target class based on the name of the target class.
[0080] Step 222: Determine the name of the target method according to the call request of the target method; and call the target method based on the name of the target method.
[0081] When the target system performs signature verification on any application, a call request for the target class or target method is triggered.
[0082] In some optional ways, based on the name of the target class and the name of the target method, the target class and the target method are called in the source code of the target system, and the target class and the target method are parsed to obtain a system signature; if the signature of the application is consistent with the system signature, the signature verification of the application passes. If the signature of the application is inconsistent with the system signature, the signature verification of the application fails.
[0083] Before triggering the signature verification of the application, in some optional ways, the control device customizes the names of the target classes and target methods related to the system identity verification in the system source code to distinguish them from the original names of the system source code.
[0084] Exemplarily, in the zygote initialization process of the Android system, the target classes and target methods related to signatures include: all engineVerify methods of the com.android.org.conscrypt.OpenSSLSignature class, the isEqual method of the java.security.MessageDigest class, and the verify method of the java.security.Signature class.
[0085] During the installation process of the Android system, the classes and methods related to installation package verification include: installPackageAsUser, checkUpgradeKeySetLP, verifySignaturesLP, and compareSignatures methods under the com.android.server.pm.PackageManagerService class.
[0086] When the Android system version is updated, the target class and target method will change.
[0087] For example, when the SDK version is greater than 18, the most vulnerable time to cracking is during the zygote initialization process. The target classes include: com.android.org.conscrypt.OpenSSLSignature, and the target methods include: engineVerify.
[0088] When the SDK version number is greater than 21, the vulnerability is most likely to occur during the installation of the Android system. The target classes include: com.android.server.pm.PackageManagerService, and the target methods include: installPackageAsUser.
[0089] Attackers use core cracking to HOOK the target class and target method to bypass the software signature verification, allowing pirated software to be installed and run in the system. This application customizes the names of the target class and target method, so that attackers cannot crack the system target class and target method without knowing the source code, thereby preventing attackers from bypassing the software signature or version number verification.
[0090] In some optional methods, when the user clicks the icon of the application in the user interface, the target system executes the thread running the application, triggering the signature verification of the application.
[0091] In some optional ways, when the application is installed on the target system, the target system executes a thread for installing the application, triggering a signature verification of the application.
[0092] When the signature verification of the application is triggered, the control device obtains the signature of the application and converts the bytes of the signature of the application into an MD5 value. Based on the name of the target class and the custom name of the target method, the control device obtains the target class and the target method in the source code of the target system for parsing to obtain the MD5 value of the system signature. The control device compares the MD5 value of the application signature with the MD5 value of the system signature. If the MD5 values of the two are consistent, the thread running the application or the thread installing the application is allowed to continue to execute; if the MD5 values of the two are inconsistent, the thread running the application or the thread installing the application is not allowed to continue to execute.
[0093] Figure 3 The flowchart of an embodiment of using the control method of the system of the present invention to perform cracking protection is shown. Figure 3 As shown, the control method of the system of the present invention is implemented, when an attacker attempts to install a cracked version of software in a target system, a signature check of the cracked version of software is triggered. Based on the name of the target class and the custom name of the target method, the control device obtains the target class and the target method in the source code of the target system for parsing to obtain the system signature. The control device compares the system signature with the signature of the cracked version of software, detects that the signature of the cracked version of software is inconsistent with the system signature, determines that the signature check fails, and blocks the installation of the cracked version of software, resulting in the failure of the installation of the cracked version of software.
[0094] The attacker will use the original name of the target system's source code to hook the target class and target method involved in the target system's initialization phase and package installation phase. However, since the names of the target class and target method in the system source code are custom names, the attacker's hook fails, and the system generates exception stack information for the target class and target method. Therefore, without knowing the source code, the attacker cannot crack the system's target class and target method, and thus cannot bypass the verification of the software signature or version number.
[0095] The attacker sends a print request to the target system to print the exception stack information, and controls the device to enable the security manager to prohibit the operation of printing the exception stack information that can locate the target class and target method. Therefore, the target system has no information output, the cracked software installation fails, and the attacker cannot bypass the verification of the software signature or version number by core cracking, so that the system can protect the system from being cracked by malware by detecting the software signature.
[0096] Figure 4 FIG. 2 is a schematic diagram showing a structure of an embodiment of a control device of the system of the present invention. Figure 4 As shown, the device 400 includes: a matching module 410 and a control module 420;
[0097] The matching module 410 is used for matching the target exception stack information with the target information name when the target system receives a print request for the target exception stack information;
[0098] The target information name includes at least one of the name of the target class, the name of the target method, the name of the target method call chain, and the name of the target location information; the target location information is used to locate the target class or target method;
[0099] The name of the target class is different from its original name in the target system; the name of the target method is different from its original name in the target system.
[0100] The control module 420 is configured to prohibit the print request if the target exception stack information matches at least one target information name.
[0101] In some optional embodiments, the apparatus 400 further includes: a permission module;
[0102] The permission module is used to check the permission of the print request;
[0103] If the permission of the print request is prohibited, prohibiting the print request;
[0104] If the permission of the print request is permission, the target exception stack information is matched with the target information name.
[0105] In some optional embodiments, the control module 420 includes: a prohibition unit and a permission unit;
[0106] The prohibition unit is used to prohibit the printing request of the information corresponding to the target information name in the target exception stack information if at least one target information name is matched.
[0107] Alternatively, if at least one target information name is matched, the print request of the target exception stack information is prohibited.
[0108] The permission unit is used to allow a print request for information corresponding to a non-target information name in the target exception stack information.
[0109] Alternatively, if the target exception stack information does not match any target information name, an operation of printing the target exception stack information is performed.
[0110] In some optional embodiments, the apparatus 400 further includes: a calling module;
[0111] The calling module is used to receive a calling request of a target class or a target method;
[0112] Determine the name of the target class according to the call request of the target class; and call the target class based on the name of the target class;
[0113] According to the calling request of the target method, the name of the target method is determined; and based on the name of the target method, the target method is called.
[0114] In some optional ways, when the target system performs signature verification on any application, a call request of the target class or target method is triggered.
[0115] The control device of the system provided by the embodiment of the present invention configures the names of the target class and the target method to be different from their original names in the target system, so that the attacker cannot crack the system target class and the target method without knowing the source code, and further the attacker cannot bypass the verification of the software signature or version number. The embodiment of the present invention matches the target exception stack information with the target information name through the matching module 410. If the target exception stack information matches at least one target information name, the printing request is prohibited through the control module 420, so that the attacker cannot know the custom name of the target class and the target method by printing the exception stack information, thereby increasing the difficulty of the attacker to crack the system. The attacker cannot bypass the verification of the software signature or version number by core cracking, so that the system can protect the system from being cracked by malicious software by detecting the software signature.
[0116] Figure 5 The schematic diagram of the structure of an embodiment of the control device of the system of the present invention is shown. The specific embodiment of the present invention does not limit the specific implementation of the control device of the system.
[0117] like Figure 5 As shown, the control device of the system may include: a processor (processor) 502 , a communication interface (Communications Interface) 504 , a memory (memory) 506 , and a communication bus 508 .
[0118] The processor 502, the communication interface 504, and the memory 506 communicate with each other via the communication bus 508. The communication interface 504 is used to communicate with other devices such as a client or other server network elements. The processor 502 is used to execute the program 510, which can specifically execute the relevant steps in the above-mentioned control method embodiment for the system.
[0119] Specifically, the program 510 may include program code including computer-executable instructions.
[0120] The processor 502 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention. The one or more processors included in the control device of the system may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.
[0121] The memory 506 is used to store the program 510. The memory 506 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
[0122] The program 510 may be specifically called by the processor 502 to enable the control device of the system to perform the following operations:
[0123] When the target system receives a print request for target exception stack information, the target exception stack information is matched with the target information name;
[0124] The target information name includes at least one of the name of the target class, the name of the target method, the name of the target method call chain, and the name of the target location information; the target location information is used to locate the target class or target method;
[0125] The name of the target class is different from its original name in the target system; the name of the target method is different from its original name in the target system;
[0126] If the target exception stack information matches at least one target information name, the print request is prohibited.
[0127] In some optional embodiments, before matching the target exception stack information with the target information name, the method further includes:
[0128] checking permissions for the print request;
[0129] If the permission of the print request is prohibited, prohibiting the print request;
[0130] If the permission of the print request is permission, the target exception stack information is matched with the target information name.
[0131] In some optional manners, if the target exception stack information matches at least one target information name, prohibiting the print request includes:
[0132] If at least one target information name is matched, a print request for information corresponding to the target information name in the target exception stack information is prohibited.
[0133] In some optional manners, after prohibiting the printing request of the information corresponding to the target information name in the exception stack information, the method further includes:
[0134] A print request for information corresponding to a non-target information name in the target exception stack information is allowed.
[0135] In some optional manners, if the target exception stack information matches at least one target information name, prohibiting the print request includes:
[0136] If at least one target information name is matched, the printing request of the target exception stack information is prohibited.
[0137] In some optional ways, if the target exception stack information does not match any target information name, an operation of printing the target exception stack information is performed.
[0138] In some optional ways, receiving a call request of a target class or a target method;
[0139] Determine the name of the target class according to the call request of the target class; and call the target class based on the name of the target class;
[0140] According to the calling request of the target method, the name of the target method is determined; and based on the name of the target method, the target method is called.
[0141] In some optional ways, when the target system performs signature verification on any application, a call request of the target class or target method is triggered.
[0142] The control device of the system provided by the embodiment of the present invention configures the names of the target class and the target method to be different from their original names in the target system, so that the attacker cannot know the real names of the target class and the target method without knowing the source code, and cannot crack the system target class and the target method, thereby making it impossible for the attacker to bypass the verification of the software signature or version number. Furthermore, the present invention prohibits the operation of printing the exception stack information that can locate the target class and the target method, so that the attacker cannot know the custom names of the target class and the target method by printing the exception stack information, thereby increasing the difficulty of the attacker to crack the system, so that the attacker cannot bypass the verification of the software signature or version number by core cracking.
[0143] An embodiment of the present invention provides a computer-readable storage medium, which stores at least one executable instruction. When the executable instruction is executed on a control device / apparatus of a system, the control device / apparatus of the system executes a control method of the system in any of the above method embodiments.
[0144] The executable instructions may be used to enable the control device / apparatus of the system to perform the following operations:
[0145] When the target system receives a print request for target exception stack information, the target exception stack information is matched with the target information name;
[0146] The target information name includes at least one of the name of the target class, the name of the target method, the name of the target method call chain, and the name of the target location information; the target location information is used to locate the target class or target method;
[0147] The name of the target class is different from its original name in the target system; the name of the target method is different from its original name in the target system;
[0148] If the target exception stack information matches at least one target information name, the print request is prohibited.
[0149] In some optional embodiments, before matching the target exception stack information with the target information name, the method further includes:
[0150] checking permissions for the print request;
[0151] If the permission of the print request is prohibited, prohibiting the print request;
[0152] If the permission of the print request is permission, the target exception stack information is matched with the target information name.
[0153] In some optional manners, if the target exception stack information matches at least one target information name, prohibiting the print request includes:
[0154] If at least one target information name is matched, a print request for information corresponding to the target information name in the target exception stack information is prohibited.
[0155] In some optional manners, after prohibiting the printing request of the information corresponding to the target information name in the exception stack information, the method further includes:
[0156] A print request for information corresponding to a non-target information name in the target exception stack information is allowed.
[0157] In some optional manners, if the target exception stack information matches at least one target information name, prohibiting the print request includes:
[0158] If at least one target information name is matched, the printing request of the target exception stack information is prohibited.
[0159] In some optional ways, if the target exception stack information does not match any target information name, an operation of printing the target exception stack information is performed.
[0160] In some optional ways, receiving a call request of a target class or a target method;
[0161] Determine the name of the target class according to the call request of the target class; and call the target class based on the name of the target class;
[0162] According to the calling request of the target method, the name of the target method is determined; and based on the name of the target method, the target method is called.
[0163] In some optional ways, when the target system performs signature verification on any application, a call request of the target class or target method is triggered.
[0164] When the executable instructions stored in the storage medium provided by the embodiment of the present invention are run on the control device / apparatus of the system, the control device / apparatus of the system configures the names of the target class and the target method to be different from their original names in the target system, so that the attacker cannot know the real names of the target class and the target method without knowing the source code, and cannot crack the system target class and the target method, thereby making it impossible for the attacker to bypass the verification of the software signature or version number. Furthermore, the present invention prohibits the operation of printing the exception stack information that can locate the target class and the target method, so that the attacker cannot know the custom names of the target class and the target method by printing the exception stack information, thereby increasing the difficulty of the attacker to crack the system, and making it impossible for the attacker to bypass the verification of the software signature or version number by core cracking.
[0165] The algorithms or displays provided herein are not inherently related to any particular computer, virtual system or other device. In addition, the embodiments of the present invention are not directed to any particular programming language.
[0166] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. Similarly, in order to simplify the present invention and help understand one or more of the various inventive aspects, in the above description of exemplary embodiments of the present invention, the various features of the embodiments of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. Wherein, the claims that follow the specific embodiment are hereby expressly incorporated into the specific embodiment, wherein each claim itself is a separate embodiment of the present invention.
[0167] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and further may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive.
[0168] It should be noted that the above embodiments illustrate the present invention rather than limit it, and that those skilled in the art may devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets shall not be construed as a limitation on the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention may be implemented by means of hardware comprising a number of different elements and by means of a suitably programmed computer. In a unit claim enumerating a number of devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.
Claims
1. A system control method, characterized in that: The method comprises: When the target system receives a print request for target exception stack information, the target exception stack information is matched with the target information name; The target information name includes at least one of the name of the target class, the name of the target method, the name of the target method call chain, and the name of the target location information; the target location information is used to locate the target class or target method; The name of the target class is different from its original name in the target system; the name of the target method is different from its original name in the target system; If the target exception stack information matches at least one target information name, the print request is prohibited.
2. The control method of the system according to claim 1, characterized in that: Before matching the target exception stack information with the target information name, the method further includes: checking permissions for the print request; If the permission of the print request is prohibited, prohibiting the print request; If the permission of the print request is permission, the target exception stack information is matched with the target information name.
3. The control method of the system according to claim 1 or 2, characterized in that: If the target exception stack information matches at least one target information name, prohibiting the print request includes: If at least one target information name is matched, a print request for information corresponding to the target information name in the target exception stack information is prohibited.
4. The control method of the system according to claim 3, characterized in that: After prohibiting the printing request of the information corresponding to the target information name in the exception stack information, the method further includes: A print request for information corresponding to a non-target information name in the target exception stack information is allowed.
5. The control method of the system according to claim 1 or 2, characterized in that: If the target exception stack information matches at least one target information name, prohibiting the print request includes: If at least one target information name is matched, the printing request of the target exception stack information is prohibited.
6. The control method of the system according to claim 1, characterized in that: Also includes: If the target exception stack information does not match any target information name, an operation of printing the target exception stack information is performed.
7. The control method of the system according to claim 1, characterized in that: Also includes: Receive a call request for a target class or target method; Determine the name of the target class according to the call request of the target class; Based on the name of the target class, calling the target class; According to the calling request of the target method, the name of the target method is determined; and based on the name of the target method, the target method is called.
8. The control method of the system according to claim 7, characterized in that: Also includes: When the target system performs signature verification on any application, a call request for the target class or target method is triggered.
9. A control device for a system, characterized in that: The device comprises: a matching module and a control module; A matching module, configured to match the target exception stack information with the target information name when the target system receives a print request for the target exception stack information; The target information name includes at least one of the name of the target class, the name of the target method, the name of the target method call chain, and the name of the target location information; the target location information is used to locate the target class or target method; The name of the target class is different from its original name in the target system; the name of the target method is different from its original name in the target system; The control module is configured to prohibit the printing request if the target exception stack information matches at least one target information name.
10. A control device for a system, characterized in that: include: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the operation of the system control method as described in any one of claims 1-8.