Source: https://patents.google.com/patent/JP2007535761A/en
Timestamp: 2020-04-09 02:11:25
Document Index: 534228729

Matched Legal Cases: ['art 300', 'art 300', 'art 400', 'art 400', 'art 400', 'art 500', 'art 500', 'art 600', 'art 600', 'art 700', 'art 800', 'art 900', 'art 1000']

JP2007535761A - System and method for generating anti-tamper code - Google Patents
System and method for generating anti-tamper code Download PDF
JP2007535761A
JP2007535761A JP2007510781A JP2007510781A JP2007535761A JP 2007535761 A JP2007535761 A JP 2007535761A JP 2007510781 A JP2007510781 A JP 2007510781A JP 2007510781 A JP2007510781 A JP 2007510781A JP 2007535761 A JP2007535761 A JP 2007535761A
JP2007510781A
バットソン，ジェームス，ディー．
2005-04-14 Application filed by アップル インコーポレイテッド filed Critical アップル インコーポレイテッド
2005-04-14 Priority to PCT/US2005/012835 priority patent/WO2005111761A2/en
2007-12-06 Publication of JP2007535761A publication Critical patent/JP2007535761A/en
A system and method for generating anti-tamper code is described herein. In one embodiment, the method comprises receiving a first object code block. The method also comprises translating a first object code block into a second code block, the translation applying an anti-tamper technique to the first object code block or the second object code block. Including that. The method also comprises executing a second object code block.
The present invention relates generally to the field of computer data processing, and more particularly to techniques for generating anti-tamper-resistant software.
Anti-tamper software is software that is difficult to change, tamper with, and / or attack. Code obfuscation is one technique for achieving anti-tamper software. In general, the goal of code obfuscation is to make it difficult for an attacker to determine what is happening in a block of code. If an attacker uses a debugger or emulator, code obfuscation can make the code difficult to understand or modify.
According to some code obfuscation techniques, additional instructions are added to the program. This instruction is added to confuse the attacker and / or generate ancillary results and must be confirmed before execution can proceed past a certain point. . One problem with this code obfuscation method is that it generally requires code that must be changed manually. Furthermore, it requires existing software that must be completely rebuilt, especially if some of the software must operate in an anti-tamper interpretive environment with limited system services. There is also a case.
This describes a system and method for generating anti-tamper codes. In one embodiment, the method comprises receiving a first object code block. The method also comprises translating the first object code block into a second object code block, the translation applying an anti-tamper technique to the first object code block or the second object code block. including. The method also comprises executing a second object code block.
In one embodiment, the system includes a processor and a memory unit connected to the processor. In this system, the memory unit includes a translation unit that translates the block of the first object code program into the block of the second object code program at runtime, and the block of the second object code program is obtained as a result of the translation. The block of the second object code program is obfuscated and contains system calls. The memory part also includes a runtime support part that provides services for some of the system calls, this runtime support part rejects services for the rest of the system calls, and the service is in anti-tamper policy. Rejected based on.
Hereinafter, an example of the present invention will be described with reference to the drawings. However, the present invention is not limited to the illustrated configuration.
This describes a system and method for generating an anti-tamper code. In the following description, numerous special details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
In this description, the term “one embodiment” or “embodiment” means that the referenced configuration is included in at least one embodiment of the invention. Further, the individual terms “one embodiment” in this description do not necessarily refer to the same embodiment, but neither is mutually exclusive, and this is not stated as such. Both are very obvious to those skilled in the art. Accordingly, the present invention may include various combinations and / or integrations of the embodiments described herein. Further, in this description, the phrase “exemplary embodiment” means that the referenced embodiment is an example or illustration.
Here, the block diagram illustrates an exemplary embodiment of the present invention. Also here, the flowchart illustrates the operation of an exemplary embodiment of the invention. The operation of the flowchart will be described with reference to the exemplary embodiment shown in the block diagram. However, the operations of the flowchart may also be performed by embodiments of the invention other than those discussed with reference to the block diagrams, and the embodiments discussed with reference to the block diagrams It should be understood that operations different from those discussed with reference to can be performed. Further, although the flowchart depicts a sequence of operations, it should be understood that some embodiments may perform some of these operations in parallel.
The following description of the example is divided into four sections. In the first section, a system level overview is described. In the second section, an exemplary implementation is described. In the third section, a method using an exemplary embodiment is described. The fourth section describes an exemplary hardware and operating environment.
<System level overview>
This section provides a system configuration of an exemplary embodiment of the present invention. 1-2 show two selectable systems for generating anti-tamper codes. The operation of each functional unit in FIGS. 1-2 is described in the sections that follow. In the following, several anti-tamper techniques are discussed, including techniques for obfuscating the code. This code obfuscation technique can be used alone or in combination with other code obfuscation techniques or anti-tamper techniques that limit system calls or confirm auxiliary results.
FIG. 1 is a block diagram illustrating a system for generating anti-tamper code using dynamic translation, according to an exemplary embodiment of the present invention. As shown in FIG. 1, the anti-tamper code system 100 includes a translation environment 132, which includes a translator 110, an execution unit 112, a translation cache 114, and a runtime support unit 116. The system 100 also includes a compiler 102, which is connected to the object code storage unit 103. The object code storage unit 103 is connected to a loader 104, and the loader 104 is connected to a translator 110. The translator 110 is connected to the translation cache 114. The translator 110 is also connected to the execution unit 112, and this execution unit 112 is connected to the runtime support unit 116. The runtime support unit 116 is connected to the system resource 118.
According to one embodiment, compiler 102 is a high-level language compiler (eg, an Objective C compiler, a C ++ compiler, a Java compiler, a C compiler, etc.). The compiler 102 compiles the high-level source code program into one or more object code blocks and stores it in the object code storage unit 103. The object code storage unit 103 may be any appropriate storage medium (for example, RAM, ROM, disk, etc.).
The loader 104 loads the object code block into the translator 110.
The operation of this system 100 is described below.
FIG. 2 is a block diagram illustrating a system for generating anti-tamper code using static translation, according to an exemplary embodiment of the present invention. As shown in FIG. 2, the anti-tamper code system 200 includes a runtime environment 216. The runtime environment 216 includes an execution unit 210 and a runtime support unit 212. The anti-tamper code system 200 also includes a compiler 208, which is connected to the object code storage unit 204. This object code storage unit 204 is connected to a translator 206. The object code storage unit 204 is also connected to a loader 202, and the loader 202 is connected to the execution unit 210. The execution unit 210 is connected to the runtime support unit 212. The runtime support unit 212 is connected to the system resource 214.
According to one embodiment, the compiler 208 is a high-level language compiler (eg, Objective C compiler, C ++ compiler, Java compiler, C compiler, etc.). The compiler 208 compiles the high level source code into one or more object code blocks. The compiler 208 also stores the object code block in the object code storage unit 204. The compiler 208 can be remotely located on a network server, while other elements of the system 200 are stored locally on the network client (see the description of the compiler 102 above). In one embodiment, the object code storage unit 204 also stores the object code generated by the translator 206. According to the embodiment of the present invention, the object code storage unit 204 may be any suitable storage medium (eg, RAM, ROM, disk, etc.).
In one embodiment, the runtime environment 216 includes an execution unit 210 and a runtime support unit 212. According to an embodiment, execution unit 210 may be any suitable mechanism for executing program instructions. For example, the execution unit 210 can include any processor and / or memory necessary to execute program instructions. The program instructions may be byte code or object code instructions. Further, the program instructions may include system calls that are serviced by the runtime support unit 212. In one embodiment, the runtime support unit 212 includes software and / or hardware for servicing system calls. The operation of the execution unit 210 and the runtime support unit 212 will be described in more detail below (see next section).
According to the embodiment of the present invention, each functional unit of FIGS. 1 and 2 (for example, the translator 110, the runtime support unit 116, etc.) is integrated or separated, so that a smaller or larger number of functions are provided. It is also possible to form a part. According to embodiments, each functional unit may include a queue, stack, or other data structure necessary to perform the functions described herein. Furthermore, each functional unit may be coupled so as to be able to communicate using any appropriate communication method (message transmission, parameter transmission, signal, etc.). In addition, each functional unit can be connected according to any suitable interconnection structure (fully connected, hypercube, etc.). Any of the functional units used in conjunction with embodiments of the present invention may include a machine readable medium (machine readable medium) containing instructions for performing the operations described herein. A machine-readable medium includes any mechanism for providing (ie, storing and / or transmitting) information in a form readable by a machine (eg, a computer). For example, a machine readable medium may be a read only memory (ROM), a random access memory (RAM), a magnetic disk recording medium, an optical recording medium, a flash memory device, an electrical / optical / acoustic or other transmission signal form (e.g., Carrier wave, infrared signal, digital signal, etc.). According to the embodiment of the present invention, each functional unit may be another type of logic (for example, digital logic) for executing an operation of generating an anti-tamper code.
<Exemplary realization>
This section describes exemplary operations performed by the system described above. In this section, Figures 3-7 are shown. In the following discussion, FIG. 3 describes the general operations for compiling, translating, and executing anti-tamper code. 4 and 5 describe a method for dynamically and statically translating object code into anti-tamper object code. FIG. 6 describes the runtime support operation and FIG. 7 describes a method for obfuscating the object code.
FIG. 3 is a flowchart illustrating operations for generating, translating, and executing software according to an exemplary embodiment of the present invention. This flowchart describes the general operation of the anti-tamper code system, and the detailed operation of each element of this system is described in subsequent flowcharts. The operation of flowchart 300 will be described with reference to the exemplary anti-tamper code system of FIG. The flowchart 300 begins at block 302.
At block 302, the source code is compiled to generate the initial object code. For example, the compiler 102 compiles the source code program to generate the first object code program. In one embodiment, the initial object code includes bytecode that is executable on the virtual machine. In one embodiment, the initial object code is in a format suitable for execution on a special processor structure (eg, PowerPC, MIPS, Intel Pentium®, etc.). According to embodiments, the object code may be in any suitable loader format. The flow continues at block 304.
In block 304, the initial object code is translated into anti-tamper object code. For example, the translator 110 translates the initial object code into anti-tamper object code. In one embodiment, the loader 104 retrieves the first object code from a storage (not shown) and passes this first object code to the translator 110. After receiving the first object code, the translator 110 performs the anti-tamper technique during translation to translate the initial object code into the anti-tamper object code. In one embodiment, the translator 110 can translate the initial object code into a different anti-tamper object code each time translation is performed. In one embodiment, the anti-tamper technique includes obfuscating the object code. The operation of obfuscating the object code will be described in more detail later with reference to FIG. The flow continues at block 306.
As shown in block 306, the anti-tamper code object is executed. For example, the execution unit 112 executes anti-tamper object code. In one embodiment, the translator 110 sends anti-tamper object code to the execution unit 112, where the anti-tamper object code is executed. The operation of translating and executing the anti-tamper object code will be described in more detail later with reference to FIGS. The flow ends at block 306. As described above, FIG. 3 describes the general operation of the system for generating anti-tamper code, while FIGS. 4 and 5 describe the more detailed operation of the translator and execution unit.
FIG. 4 is a flowchart illustrating operations for dynamically translating and executing object code according to an exemplary embodiment of the present invention. The operation of flowchart 400 will be described with reference to the exemplary system of FIG. In particular, the flowchart 400 mainly describes operations performed by the translator 110 and the execution unit 112. Flowchart 400 shows block 40.
As shown in block 402, the first object code block is selected. For example, the translator 110 selects the first object code block for performing an operation. In one embodiment, the initial object code block contains bytecode that is executable on a virtual machine, but alternative embodiments require an object code block that is executable on the processor. The flow continues at block 404.
At block 404, it is determined whether the first object code block has already been translated. For example, the translator 110 determines whether the first object code block has already been translated. In one embodiment, translator 110 examines translation cache 114 to determine if the first object block has already been translated. If the first object code block has not yet been translated, flow continues to block 406. Otherwise, flow continues to block 416.
At block 416, it is determined if there are no translated anti-tamper object code blocks. For example, the translator 110 looks for a translated anti-tamper object code block in the translation cache 114 and determines whether it is gone. The translated anti-tamper block disappears after being stored in the translation cache 114 for longer than a predetermined period. For example, if a translated anti-tamper block is stored in the cache for more than 5 time units, it disappears. If there are no more translated anti-tamper code blocks, the flow continues to block 406. If not, continue to block 410. In some embodiments, the translated anti-tamper object code block is not lost, and therefore, in these embodiments, block 416 may be omitted from the flow. In such a case, the “YES” path from block 404 will continue to block 410.
At block 410, the anti-tamper object code block is retrieved from the translation cache. For example, the translator 110 retrieves the anti-tamper object code block from the translation cache 114. From block 410, the flow continues to block 412.
At block 406, the first object code block is translated into an anti-tamper object code block. For example, the translator 110 translates the first object code block into an anti-tamper object code block. In one embodiment, the translator 110 obfuscates the first object code block before translating it into an anti-tamper object code block. Thus, as a result of obfuscating the first object code block, the translation produces an obfuscated object code block (ie, the anti-tamper object code block contains obfuscated code). In an alternative embodiment, the translator 110 translates the first object code block into a second object code block that is obscured to form an anti-tamper object code block. In an alternative embodiment, translator 110 translates and obfuscates the first object code block in the same process. That is, the translator 110 translates and obfuscates the first object code block instruction-by-instruction when generating the anti-tamper object code. In some embodiments, each time an object code block is translated, the translator 110 generates a different object code. For example, when there is no translated and cached object code, the translator 110 generates a translated object code block that is different from the missing block.
In one embodiment, the translator 110 translates the initial object code block into an anti-tamper object code block and uses means to prove this anti-tamper object code block. For example, the translator 110 calculates and stores the checksum of the anti-tamper object code block. Alternatively, the translator 110 digitally signs the anti-tamper object code block. Prior to executing the anti-tamper object code block, the execution unit 112 may verify the checksum or verify the digital signature to verify that the anti-tamper object code block has not been modified. In addition, the execution unit 112 may confirm that a certain auxiliary result is generated by an instruction added to the original object code. Although only checksums, digital signatures, and verification of auxiliary results have been described, any suitable technique for proving anti-tamper object code blocks can be used in embodiments of the present invention. The flow continues to block 408.
At block 408, the anti-tamper object code block is stored in the translation cache. For example, the translator 110 stores the anti-tamper object code block in the translation cache 114. The flow continues to block 412.
As shown in block 412, the anti-tamper object code block is executed. For example, the execution unit 112 extracts and executes the anti-tamper object code block. In one embodiment, the execution unit 112 uses the runtime support unit 116 to execute a system call included in the anti-tamper object code block. The operation of the runtime support unit 116 will be described in more detail later in the discussion of FIG. The flow continues to block 414.
At block 414, any desired changes are made to the cached anti-tamper object code block. For example, if desired, the translator 110 can further modify the object blocks stored in the translation cache 114. At block 414, the flow ends. Although flow 400 is shown as translating and executing a single object code block, flow 400 may be repeated for additional object code blocks.
The operation of flow 400 allows for high speed code execution. Because the code is translated into native processor instructions, the result is faster than the anti-tamper interpreter environment.
FIG. 5 is a flowchart illustrating operations for statically translating and executing an object code program according to an exemplary embodiment of the present invention. The flowchart of FIG. 5 will be described with reference to the exemplary translation system of FIG. In particular, the flowchart 500 mainly describes the operations of the translator 206 and the execution unit 210. The flowchart 500 begins at block 502.
At block 502, an initial object code program is received. For example, the translator 206 takes out the object code program from the object code storage unit 204. In one embodiment, the translator 206 receives an object code program from the object code store 204 while the software installation process (i.e., the process of storing software and configuring it for execution) is in progress. In an alternative embodiment, the translator 206 receives the object code program over a network connection during the software installation process. The flow continues to block 504.
At block 504, the initial object code program is translated into an anti-tamper object code program. For example, the translator 206 translates the object code program into an anti-tamper object code program. In one embodiment, this includes obscuring the initial object program, which will be described in more detail later (see FIG. 7). As described above, in one embodiment, the translator 206 determines a checksum or digital signature for the anti-tamper object code program. The checksum is used by the execution unit 210 to determine if the anti-tamper object code program has been modified. The flow continues to block 506.
At block 506, an anti-tamper object code program is stored. For example, the translator 206 stores the anti-tamper object code program in the object code storage unit 204. The flow continues to block 508.
At block 508, the anti-tamper object code program is loaded. For example, the loader 202 loads the anti-tamper object code program into the execution unit 210. The flow continues to block 510.
At block 510, an anti-tamper object code program is executed. For example, the execution unit 210 executes an anti-tamper object code program. In one embodiment, the object program includes a system call that requests access to system resources 214. In one embodiment, the execution unit 210 cooperates with the runtime support unit 212 to service system calls. The operation of servicing system calls will be described in more detail later in the discussion of FIG. In one embodiment, the anti-tamper object code program can be executed on a different computer system. For example, the load operation (block 508) loads the anti-tamper object code into a computer system other than the computer system that performs the translation (block 504). At block 510, the flow ends.
4 and FIG. 5 described the operation of generating the anti-tamper object code dynamically or statically, FIG. 6 shows the operation of servicing the system call.
FIG. 6 is a flowchart illustrating an operation of servicing a system call based on an anti-tamper policy according to an exemplary embodiment of the present invention. The operation of the flowchart 600 shows the operation of the runtime support unit 116. The operation of the flowchart of FIG. 6 will be described with reference to the exemplary system described in FIG. The flowchart 600 begins at block 602.
As indicated at block 602, a system call is received. For example, the runtime support unit 116 receives a system call from the execution unit 112. In one embodiment, a system call is a mechanism that requests resources from the operating system. According to an embodiment, a system call is an object code instruction or byte that causes the execution unit 112 to perform limited operations such as providing access to system resources (eg, disk drives, memory management units, etc.). Code. The flow continues to block 604.
At block 604, it is determined whether the system call is authorized to service. For example, the runtime support unit 116 determines whether the system call service is permitted. In one embodiment, the runtime support unit 116 checks the anti-tamper policy to determine if it is authorized to service system calls. According to embodiments, the anti-tamper policy may be represented by a data structure stored within the runtime support 116. The runtime support unit 116 examines the data structure to determine whether the anti-tamper policy is taking into account servicing system calls. If runtime support 116 is authorized to service the system call, flow continues to block 608. Otherwise, flow continues to block 606.
As indicated at block 606, an error is transmitted. For example, the runtime support unit 116 transmits an error to the execution unit 112. At 606, the flow ends.
At block 608, the system call is serviced. For example, the runtime support unit 116 services system calls. In one embodiment, the rantam support 116 services system calls by providing access to system resources 118. In one embodiment, execution unit 112 and system resources 118 are controlled by a first operating system, while system calls are formatted for use by a second operating system. Accordingly, the runtime support unit 116 determines which services the second operating system must provide in order to service system calls formatted for the first operating system. In other words, the runtime support unit 116 maps system calls from another operating system onto services of the current operating system (ie, the operating system that controls the execution unit 112). In one embodiment, the first and second operating systems are generally the same, but the second operating system supports a limited portion of system calls. At block 608, the flow ends.
Some embodiments may obfuscate the code by performing one or more of the operations described below. In one embodiment, code obfuscation is accomplished by determining an obfuscation identifier and performing one or more actions based on the identifier. The identification name may be a machine-specific attribute such as a ROM serial number, hardware address, clock value, etc. Alternatively, the identification name can be determined from user attributes such as a user identification name, a computer identification name, an account identification name, or other user related information. After determining the distinguished name, extraneous code generated based on the distinguished name can be inserted into the object code. Furthermore, object code features that do not have an equivalent to a direct source code can be generated based on the identifier, and such object code features can then be inserted into the object code.
As another obscuring technique, additional code that generates auxiliary results can be generated based on the distinguished name. This additional code can then be inserted into the object code. Anti-tampering is improved if code is not executed when the distinguished name is different.
Although several code obfuscation and anti-tamper techniques have been described herein, embodiments of the present invention allow for any code obfuscation or anti-tamper technique to be applied during translation. .
This section describes the methods performed by embodiments of the present invention. In some embodiments, the method is performed by instructions (eg, software) stored on a machine-readable medium, while in other embodiments, the method is performed by hardware or other logic (eg, digital logic). Carried out.
In this section, FIGS. 7-10 are discussed. In particular, FIG. 7 describes the operations performed by a dynamic translator that generates anti-tamper code, while FIG. 8 illustrates the operation of generating anti-tamper code using code obfuscation based on distinguished names. Describes the operation of an intelligent translator. FIG. 9 describes the operation of servicing a system call based on the anti-tamper policy. Further, FIG. 10 describes an operation for obscuring the object code at the time of introduction.
FIG. 7 is a flowchart illustrating a method for generating anti-tamper code using dynamic translation, according to an exemplary embodiment of the present invention. The flowchart 700 begins at block 702 where a first object code block is received. The flow continues to block 704. At block 704, the first object code block is translated into a second object code block. The flow continues to block 706. At block 706, the second code block is executed. At block 706, the flow ends.
FIG. 8 is a flowchart illustrating operations for generating an anti-tamper code using code obfuscation based on distinguished names according to an exemplary embodiment of the present invention. The flowchart 800 begins at block 802. At block 802, an identification name is determined based on the state of the machine. The flow continues to block 804. At block 804, the first object code block is translated into a second object code block, and the second object code block is obscured using the identifier. The flow continues to block 906. In block 806, the first block is executed. At block 806, the flow ends.
FIG. 9 is a flowchart illustrating an operation of servicing a system call based on an anti-tamper policy according to an exemplary embodiment of the present invention. The flowchart 900 begins at block 902. At block 902, a system call for a first object code block is received, where the system call is formatted to request a service from the first operating system. The flow continues to block 904. As shown in block 904, it is determined which system call service of the second operating system is required to provide the service. The flow continues to block 906. At block 906, it is determined based on the anti-tamper policy whether the system call service for servicing the system call is disabled. The flow continues to block 908. As indicated at block 908, if the system call to service the system call is not disabled, the system call is serviced. At block 908, the flow ends.
FIG. 10 is a flowchart illustrating operations for translating and obscuring object code when the object code is installed, according to an exemplary embodiment of the present invention. The flowchart 1000 begins at block 1002. In block 1002, a first object code program is installed, the first object code program is translated into a second object code program, and the first object code program or the second object code program is ambiguous. It becomes. The flow continues to block 1004. As shown in block 1004, a second object code program is stored for its execution. At block 1004, the flow ends.
<Hardware and operating environment>
This section provides an overview of exemplary hardware and operating environments in which embodiments of the present invention may be implemented.
FIG. 11 is a diagram illustrating an exemplary computer system for use with certain embodiments of the present invention. As shown in FIG. 11, the computer system 1100 includes one or more processors 1102. Computer system 1100 also includes a memory portion 1130, a processor bus 1122, and an input / output controller (IOC) 1124. The processor 1102, the memory unit 1130, and the IOC 1124 are connected to the processor bus 1122. The processor 1102 may comprise any suitable processor structure. Computer system 1100 may comprise one, two, three, or more processors, any of which may execute a sequence of instructions according to embodiments of the present invention.
The memory unit 1130 includes a translation environment 132. The memory unit 1130 stores data and / or instructions, and may include any suitable memory such as dynamic random access memory (DRAM). Computer system 1100 also includes an IDE drive and / or other suitable recording device. The graphics controller 1104 controls the display of information on the display device 1106 according to an embodiment of the present invention.
Input / output controller (IOC) 1124 provides an interface to I / O devices or peripherals for computer system 1100. The IOC 1124 may include any suitable interface controller to provide any suitable communication link with the processor 1102, the memory portion 1130, and / or any suitable device or component that communicates with the IOC 1124. In one embodiment of the present invention, the IOC 1124 provides appropriate arbitration and buffering for each interface.
In one embodiment of the invention, the IOC 1124 may be in one or more suitable integrated drive electronics (IDE) drives 1108, such as a hard disk drive (HDD) or a compact disk read only memory (CD ROM) drive, or one An interface is provided to an appropriate universal serial bus (USB) device via the USB port 1110 described above. In one embodiment, the IOC 1124 also provides an interface to the keyboard 1112, mouse 1114, CD-ROM drive 1118, and one or more suitable devices via one or more FIREWIRE ports 1116. In one embodiment of the invention, the IOC 1124 also provides a network interface 1120 through which the computer system 1100 can communicate with other computers and / or devices.
In one embodiment, the computer system 1100 is machine readable that stores a sequence of instructions (eg, software) that implement any one or all of the methodologies for dynamically loading the object modules described herein. Contains media. Further, the software can reside entirely or at least in part within the memory portion 1130 and / or the processor 1102.
Thus, a system and method for generating an anti-tamper code has been described. Although the invention has been described with reference to specific exemplary embodiments, various changes and modifications may be made to these embodiments without departing from the broad spirit and scope of the invention. Is clear. Accordingly, the description and drawings are to be regarded as illustrative rather than restrictive.
1 is a block diagram illustrating a system for generating anti-tamper code using dynamic translation, according to an exemplary embodiment of the present invention. FIG. 1 is a block diagram illustrating a system for generating anti-tamper code using static translation, according to an exemplary embodiment of the present invention. FIG. 6 is a flowchart illustrating operations for generating, translating, and executing software, according to an exemplary embodiment of the present invention. 6 is a flowchart illustrating operations for translating and executing object code, according to an exemplary embodiment of the present invention. 4 is a flowchart illustrating operations for statically translating and executing an object code program according to an exemplary embodiment of the present invention. 6 is a flowchart illustrating an operation of servicing a system call based on an anti-tamper policy according to an exemplary embodiment of the present invention. 3 is a flowchart illustrating a method for generating anti-tamper code using dynamic translation, according to an exemplary embodiment of the present invention. 6 is a flowchart illustrating an operation of generating an anti-tamper code using code obfuscation based on an identifier according to an exemplary embodiment of the present invention. 6 is a flowchart illustrating an operation of servicing a system call based on an anti-tamper policy according to an exemplary embodiment of the present invention. 6 is a flowchart illustrating operations for translating and obscuring object code when the object code is installed, according to an exemplary embodiment of the present invention. FIG. 2 illustrates an exemplary computer system for use with certain embodiments of the present invention.
Translating the first object code block into a second object code block;
Executing the second object code block;
The translation includes applying an anti-tamper technique to the first object code block or the second object code block;
The anti-tamper technique includes determining an identification name based on a machine attribute or a user attribute and inserting additional code into the first object code block or the second object code block, the identification The method of claim 1, wherein if there is no name, the second object code block is not executed.
The anti-tamper technique includes adding an object code that generates an auxiliary result to the first object code block or the second object code block, and if there is no auxiliary result, the second object code block The method of claim 1, wherein: is not performed.
The method of claim 1, wherein the first object code block includes bytecode in a format suitable for execution on a first machine.
The method of claim 4, wherein the first machine is a virtual machine.
5. The method of claim 4, wherein the second object code block is in a format suitable for execution on a second machine.
The method of claim 1, wherein the anti-tamper technique includes obfuscating the first object code block or the second object code block.
The method of claim 1, wherein the second machine is a virtual machine.
The translation includes determining a checksum or digital signature based on the second object code block, wherein the checksum or digital signature is verified before or during execution of the second object code. The method of claim 1, characterized in that:
Determining a distinguished name based on one or more machine attributes or user attributes;
Translating a first object code block into a second object code block at runtime;
Storing the second object code block for later execution;
The translation includes obfuscating the second object code block, the obfuscation being based on the distinguished name;
11. The method according to claim 10, wherein the anti-tamper technique is applied by not executing the second object block later when the identification names are different.
12. The method of claim 11, wherein the machine attribute includes a hardware address or a read-only memory serial number.
The method of claim 11, wherein the user attribute is selected from a set consisting of a user identification name, a user password, a user account name, and a user account number.
The method of claim 10, wherein the obscuring comprises inserting additional code into the first object code block or the second object code block.
The anti-tamper technique includes adding an object code that generates an auxiliary result to the first object code block or the second object code block, and if there is no auxiliary result, the second object code block The method of claim 10, wherein: is not performed.
The method of claim 10, wherein the machine attribute is based on a clock.
11. The method of claim 10, wherein the machine attribute includes a hardware address or a read only memory serial number.
The method of claim 10, wherein the user attribute is selected from the set consisting of a user identifier, a user password, a user account name, and a user account number.
The method of claim 10, wherein the first machine is a virtual machine.
Receiving a system call formatted to request a service from the first operating system, the system call included in the first object code block being a runtime translation of the second object code block; ,
Determining which system call service of the second operating system is required to provide the service;
Determining whether a system call service for servicing the system call is disabled based on an anti-tamper policy;
If the system call service for servicing the system call is not disabled, servicing the system call;
The method of claim 20, wherein the anti-tamper policy disables a system call service that accesses system resources.
21. The method of claim 20, wherein the first operating system is selected from the set consisting of Mac OS X, Linux, and Microsoft Windows.
21. The method of claim 20, wherein the second operating system is selected from the set consisting of Mac OS X, Linux, and Microsoft Windows.
Installing a first object code program;
Storing a second object code program for execution by the machine,
The installation includes statically translating the first object code program into the second object code program executable on the machine;
The static translation is
Determining an identifier based on the machine state or user attributes;
Obscuring the first object code program or the second object code program based on the identifier;
25. The method of claim 24, wherein the obscuring comprises inserting additional code into the first object code program or the second object code program.
26. The method of claim 25, wherein the inserted additional code generates an auxiliary result.
The method of claim 24, wherein the first object code program is not executable on the machine.
25. The method of claim 24, wherein the static translation is performed on a network server and the second object code program is stored on a network client.
The method of claim 24, wherein the machine includes an operating system selected from the set consisting of Microsoft Windows, Linux, and Mac OS X.
The method of claim 24, wherein the first object code program or the second object code program is received via a network connection.
25. The method of claim 24, wherein the machine is selected from the set consisting of an Apple Macintosh and a Windows PC.
25. The method of claim 24, wherein the machine state is based on machine specific attributes selected from the group consisting of a clock, a ROM serial number, and a hardware address.
A translation unit that translates a block of a first object code program into a block of a second object code program at runtime, wherein the block of the second object code program is obscured as a result of the translation; A translation part in which a block of two object code programs includes a system call;
A runtime support unit that provides services for some of the system calls and rejects services for others of the system calls based on anti-tamper policies;
34. The apparatus of claim 33, wherein the first object code program includes byte code.
34. The apparatus of claim 33, wherein the second object code program is executable on an Apple Macintosh or a Windows (registered trademark) PC.
34. The apparatus of claim 33, wherein the first object code is executable on a virtual machine.
A translation unit that translates a first object code program into a second object code program, wherein the second object code program includes a system call to a first operating system, and the second object code block includes A translation unit containing object code obfuscated as a result of the translation;
An execution unit for executing the second object code program and transmitting the system call;
A runtime support unit that receives the system call from the execution unit and services a system call having a system call service routine of a second operating system;
The apparatus of claim 37, wherein the obfuscated object code is based on machine attributes.
The obfuscated code is based on a user attribute, and the user attribute is selected from the set consisting of a user identifier, a user password, a user account number, and a user account name. Item 37. The apparatus according to Item 37.
38. The apparatus of claim 37, wherein the second operating system is selected from the set consisting of an Apple Macintosh operating system and a Windows operating system.
A system comprising a processor and a memory unit connected to the processor,
43. The system of claim 42, wherein the first object code program includes byte code.
43. The system of claim 42, wherein the second object code program is executable on a computer selected from the set consisting of an Apple Macintosh and a Windows (registered trademark) PC.
43. The system of claim 42, wherein the first object code is executable on a virtual machine.
A machine-readable medium that provides instructions that, when executed by a machine, cause the machine to perform an action, the action comprising:
A machine-readable medium characterized by:
The anti-tamper technique includes determining an identification name based on a machine attribute or a user attribute and inserting additional code into the first object code block or the second object code block, the identification 47. The method of claim 46, wherein if there is no name, the second object code block is not executed.
The anti-tamper technique includes adding an object code that generates an auxiliary result to the first object code block or the second object code block, and if there is no auxiliary result, the second object code block 49. The method of claim 48, wherein: is not performed.
The machine-readable medium of claim 46, wherein the first object code block includes bytecode in a format suitable for execution on a first machine.
The machine-readable medium of claim 46, wherein the first machine is a virtual machine.
50. The machine-readable medium of claim 49, wherein the second object code block is in a format suitable for execution on a second machine.
The machine-readable medium of claim 46, wherein the anti-tamper technique includes obscuring the object code block.
The machine-readable medium of claim 46, wherein the second machine is a virtual machine.
The translation includes determining a checksum or digital signature based on the second object code block, wherein the checksum or digital signature is verified before executing the second object code. 48. The machine-readable medium of claim 46.
56. The method of claim 55, wherein the anti-tamper technique is applied by not executing the second object block later if the distinguished names are different.
57. The method of claim 56, wherein the machine attribute includes a hardware address or a read only memory serial number.
The method of claim 56, wherein the user attribute is selected from the set consisting of a user identifier, a user password, a user account name, and a user account number.
The machine-readable medium of claim 55, wherein the machine attribute is based on a clock.
The machine-readable medium of claim 55, wherein the machine attribute is based on machine specific information.
61. The machine readable medium of claim 60, wherein the machine specific information includes a hardware address or a read only memory serial number.
56. The machine-readable medium of claim 55, wherein the first machine is a virtual machine.
The machine-readable medium of claim 55, wherein the user attribute is selected from a set consisting of a user identification name, a password, a user account number, and a user account name.
The machine-readable medium of claim 64, wherein the anti-tamper policy disables a system call service that accesses system resources.
The machine-readable medium of claim 64, wherein the first operating system is selected from the group consisting of Microsoft Window, Linux, and Mac OS X.
The machine-readable medium of claim 64, wherein the second operating system is selected from the set consisting of an Apple Macintosh operating system, Linux, and Microsoft Windows.
69. The machine-readable medium of claim 68, wherein the static translation is performed on a network server and the second object code program is stored on a network client.
69. The machine-readable medium of claim 68, wherein the first object code program or the second object code program is received via a network connection.
69. The machine-readable medium of claim 68, wherein the machine is selected from the set consisting of an Apple Macintosh and a Windows PC.
JP2007510781A 2004-04-30 2005-04-14 System and method for generating anti-tamper code Granted JP2007535761A (en)
JP2007535761A true JP2007535761A (en) 2007-12-06
JP2007510781A Granted JP2007535761A (en) 2004-04-30 2005-04-14 System and method for generating anti-tamper code
FR2903508B1 (en) 2006-07-10 2008-10-17 Sagem Defense Securite Protection of a program interpreted by a virtual machine
JP2003067191A (en) * 2001-06-26 2003-03-07 Aladdin Knowledge Systems Gmbh & Co Kg Method for extending application installed using installation program on its function and computer software product
AU6211899A (en) * 1998-10-10 2000-05-01 Victoria University Of Manchester, The Program code conversion
DE60025570T2 (en) 1999-07-14 2006-09-21 Luxembourg Patent Co. S.A. Safety valve for pressure vessels
US20050246554A1 (en) 2005-11-03
US9767292B2 (en) 2017-09-19 Systems and methods to identify security exploits by generating a type based self-assembling indirect control flow graph
US20190108008A1 (en) 2019-04-11 Generating and caching software code
US7650418B2 (en) 2010-01-19 System and method for controlling the usage of digital objects
US8762928B2 (en) 2014-06-24 Method and system for containment of usage of language interfaces
2007-12-26 RD02 Notification of acceptance of power of attorney