Source: https://patents.google.com/patent/US20100325431A1/en
Timestamp: 2019-12-15 16:55:59
Document Index: 569254750

Matched Legal Cases: ['Application No. 61', 'art 124', 'art 124', 'art 124', 'art 124', 'art 124', 'art 114', 'art 124', 'art 132', 'art 132', 'art 124', 'art 132', 'art 132', 'art 132', 'art 124', 'art 132', 'art 124', 'art 132', 'art 124', 'art 124', 'art 124', 'art 124', 'art 124', 'art 132', 'art 124', 'art 124', 'art.\n7']

US20100325431A1 - Feature-Specific Keys for Executable Code - Google Patents
Feature-Specific Keys for Executable Code Download PDF
US20100325431A1
US20100325431A1 US12/792,206 US79220610A US2010325431A1 US 20100325431 A1 US20100325431 A1 US 20100325431A1 US 79220610 A US79220610 A US 79220610A US 2010325431 A1 US2010325431 A1 US 2010325431A1
US12/792,206
2009-06-19 Priority to US21860209P priority Critical
2010-06-02 Application filed by Uniloc USA Inc filed Critical Uniloc USA Inc
2010-06-02 Priority to US12/792,206 priority patent/US20100325431A1/en
2010-12-23 Publication of US20100325431A1 publication Critical patent/US20100325431A1/en
2012-07-09 Assigned to UNILOC USA, INC. reassignment UNILOC USA, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: Mordetsky, Joseph Martin
2012-10-26 Assigned to UNILOC LUXEMBOURG S.A. reassignment UNILOC LUXEMBOURG S.A. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ETCHEGOYEN, CRAIG S.
2012-11-09 Assigned to UNILOC LUXEMBOURG S.A. reassignment UNILOC LUXEMBOURG S.A. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: UNILOC USA, INC.
A method for protecting software from tampering includes steps for processing first compiled software stored in a computer memory to generate a first key part, the first compiled software configured to perform software protection functions and defined second functions distinct from the software protection functions when executed, and the first key part consisting of a first portion of the first compiled software comprising executable code compiled from the software protection functions, generating an identifier and a second key part for each of the defined second functions, generating a cryptographic key determined from the first key part and the second key part, encrypting a second portion of the first compiled software using the cryptographic key to produce second compiled software comprising the first portion in unencrypted form and the second portion encrypted with the cryptographic key, wherein the second portion comprises executable code compiled from the defined second functions, and storing the second compiled software in a computer memory for distribution to a client device.
This application claims priority to U.S. Provisional Application No. 61/218,602 which was filed Jun. 19, 2009 and which is fully incorporated herein by reference.
The present disclosure relates to methods and systems for protecting and enabling specific features of distributed computer software.
Software may be distributed with various different and independently operable features programmed in the executable code. The executable code may be possessed by individual users, such as by being copied to the users' respective client devices, before user rights to access all of the programmed features have accrued. For example, software may be distributed as shareware with some features enabled at the time of installation while more comprehensive features cannot be accessed until a license fee is paid. Availability of the free features in the shareware enhances the user base for the software without harming the capacity to collect license fees from more serious users. For further example, computer games or other interactive scored processes may require a user to demonstrate a certain level of skill or achievement, such as completing a game objective or achieving a certain score, before unlocking additional game features. In general, controlling access to separate software features may be used to ensure graduated levels of difficulty in the game and provide psychological rewards for successful game play, generally enhancing the desirability or usefulness of the game or other software.
In addition, built-in controls may be placed on use of distributed software to prevent non-compliance with software license restrictions and preserve a healthy and viable market for desired software. Such controls may involve adding built-in software protection functions to distributed software that is to be protected, for the purpose of controlling or limiting use of the distributed software. For example, a common form of control limits the number of times a distributed software object can be installed on a computer system. Other examples of control functions include requiring each installed instance of the software to be registered with a central registry, or requiring entry of a key imprinted on sales packaging or transmitted to the licensee at the time of purchase to enable installation on a client system. Code for controlling access to individual program features, as described in the paragraph above, may be another form of software control functions. These and other software protection functions may be coded, compiled, and released as part of the licensed software program.
Such software protection features are useful, but subject to being modified or disabled. For example, a motivated hacker might tamper with the binary code that constitutes the software release by trial and error, until creating a tampered version that performs like the original release, but with the software protection features of the original release partially or entirely disabled. The hacker can then distribute the tampered version free of the intended software protection features. Access control for individual features may also be disabled; either permitting unauthorized access to the controlled features, or disabling the controlled features for even authorized users.
It would be desirable, therefore, to provide systems and methods for securing the integrity of executable software to prevent use of tampered software and discourage intentional tampering of software security features. Such systems and methods should also permit separated control of different software features at the client nodes.
The present technology uses a cryptographic hash, digital fingerprint, or simple hash operating on a portion of a compiled software executable to generate a cryptographic key. The compiled software executable comprises a discrete software object made up of one or more binary files, and includes code for performing executable software protection features. The portion of the compiled software executable may be selected to include at least a substantial portion of the executable software protection features coded in binary form, and should exclude any variable portions of the software, for example, data tables holding variable values. The following processes may be performed by one or more computers prior to distribution of the software to client nodes.
The cryptographic key may be generated before distribution of the software object using a defined one-way hashing algorithm implemented on a computer. This cryptographic key is referred to herein as a “first key part” to distinguish it from a second key part described below. Code for applying the one-way hashing algorithm to input data to produce the first cryptographic key part, and code for decrypting a data object using a supplied key of the form generated by the hashing algorithm, may be compiled and included as part of the executable software protection for the software object to be distributed. In the alternative, such code may be maintained separately from the distributed software object. The hashing and decryption/encryption algorithms themselves may be selected from any suitable hashing or decryption/encryption algorithm as known in the art of cryptography.
Before distribution of the software object, instructions for performing separate functions or features of the software are identified and selected for control. Functions for control, for example, may include functions that are essential to the software's principal purpose, such as in the case of shareware, or a series of separate functions corresponding to different access or license levels. Several such functions may be identified for control. Once the functions to be controlled are selected, the software object to be distributed is compiled, and a portion or portions of the compiled software necessary for execution of the selected functions are identified. These identified portions of the executable may exclude every portion of the compiled software executable used to generate the cryptographic key.
Each of the separate functions may be assigned an identifier and a unique key part as a data pair. The identifier may be compiled into the binary code for the software object, while each unique key part is maintained in a server database in association with a respective one of the identifiers.
The compiled code for each of the separate functions may then be encrypted using a combination key consisting of data generated by any deterministic combination of the first key part and the second key part. Any definite way of combining separate data to produce a unified data value may be used to determine the combination key. The combination cryptographic key may be a symmetric key useful for both encryption and decryption, or a private key part of a public/private key pair.
The identified separate functions portions of the binary code are thereby encrypted using the combination cryptographic key prior to distribution to provide a protected software object for distribution. After encryption, the protected software object includes an unencrypted portion including at least the executable software protection features, and an encrypted portion including the identified portions of the software object selected for control.
The protected software object may then be distributed and installed on one or more client devices. The software should be installed on each client with its encrypted and unencrypted portions intact. The portions encrypted using the combination cryptographic key should not be decrypted during installation, and should be stored on the client in encrypted form. These code portions are to be decrypted at the client at run time. If the client is unable to decrypt these portions, the controlled software functions will not be operational and the software object will be disabled, at least with respect to the controlled functions.
To decrypt the encrypted software portions and enable full operation of the executable at run time, the client extracts the first cryptographic key part from the unencrypted portion of the software object making up the software control functions. If this portion of the software has been tampered with, the client will be unable to extract the first cryptographic key part and will therefore be unable to decrypt the encrypted software portions to unlock the protected software features at run time. Conversely, if the software control functions have not been tampered with, these functions will continue to operate according to their intended purpose and the first cryptographic key part will be recoverable by the client. The client will therefore be able to decrypt the encrypted software portions to access protected software functions, provided that the client also possesses the second key part with which the combination key can be determined.
As noted above, the second key part is stored on a server database in association with an identifier for the software portion that is encrypted using it. The client may be provided access to the data table and second key portions via a secure connection to the server database. In the alternative, or in addition, the server may encrypt the data file using the first key part and/or other cryptographic key and transmit it to the client at the time the software object is activated at the client. The client recovers the identifier for the feature to be unlocked and queries the data table to recover the second key part. The client then generated the combination cryptographic key using the first key part and the second key part, and decrypts the protected feature using the combination key.
Generally, the client should be enabled to recognize and decrypt the encrypted software features at run time. For example, the software may be supplied with code that extracts the first key part from a stored executable file, recognizes one or more files or portions of files that require decryption and the identifier corresponding to such data, queries the data table using the identifier to determine the second key part, generates the combination key using the first key part and second key part, decrypts the protected feature data using the combination key, and causes the decrypted executable data to be loaded into processor memory in the correct sequence for execution by the client processor.
The first cryptographic key part may be hidden in the unencrypted code portion so that it is practically undiscoverable. During the decryption process, the key may be retained only in temporary processor memory and beyond ready discovery by a casual hacker. Even if a skilled hacker is able to discover the key, it cannot readily be used to enable the protected software functions at runtime. Such enablement requires the operation of the key discovery and decryption functions built into the software protection functions. Selectively disabling the software protection functions without disrupting the run-time key discovery and decryption functions would involve fairly arduous reverse engineering and programming tasks, effectively destroying, or at least greatly diminishing, the economic incentives for disabling selected parts of the software protection functions. Thus, the software may be distributed with a greater assurance that its software protection functions will not be disabled, including feature-specific control. This result may be accomplished without requiring additional hardware for software protection, without disrupting the self-contained nature of the distributed software object, and with minimal computational overhead on the client device.
A more complete understanding of the system and method for securing the integrity of executable code using an auto-derived key part in combination with a feature-specific second key part will be afforded to those skilled in the art, as well as a realization of additional advantages and objects thereof, by a consideration of the following detailed description. Reference will be made to the appended sheets of drawings which will first be described briefly.
FIG. 1 is a schematic diagram showing elements of a system for securing the integrity of executable code using an auto-derived first key part in combination with an assigned second key part.
FIG. 2 is block diagram showing elements of a system for executing executable code protected by an auto-derived key in combination with an assigned second key part.
FIG. 3 is a flow chart showing an example of a method for securing the integrity of executable code using an auto-derived key in combination with an assigned second key part.
FIG. 4 is a flow chart showing an example of a method for executing executable code protected by an auto-derived key in combination with an assigned second key part.
The present technology provides for securing the integrity of executable code using an auto-derived key in combination with an assigned second key part. FIG. 1 shows a server-side system 100 which may be used to configure executable software for distribution. System 100 may comprise a computer 102, also referred to herein as a “server.” Computer 102 comprises a processor 108 connected to a memory 110 holding instructions 111 configured to cause actions as described herein. Server 102 may be in use by a person providing control input through an interface device 104 and viewing output from output device 106 to guide and direct processing by processor 208 of operating software 114. Processor 108 may be operably associated with a file storage device 112 on which is stored a software executable object 114, comprising one or more files. The processor 108 and memory 110 with these instructions comprise means for performing the described actions. The instructions 111 may be stored in a computer memory or computer-readable medium and loaded into memory 110 prior to processing the input executable object 114. A computer-readable medium may include but is not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical discs (e.g., compact disc (CD), digital versatile disc (DVD), etc.), smart cards, and flash memory devices (e.g., Erasable Programmable Read Only Memory (EPROM), card, stick, key drive, etc.). Additionally, various storage media described herein can represent one or more devices and/or other computer-readable media for storing information.
The software object 114 may comprise a code compiled from source code and configured to perform various functions when executed by a computer. A first portion 116 is compiled from source code for performing software protection functions. Software protection functions are performed by input/output activities that are designed to protect the software 114 from unauthorized use. A simple example of such activities is requiring entry of a serial number or authorization code to enable installation or operation of the software object, using a hardware fingerprint to identify client-side installations, or limiting the number of copies of the software object that can be made. Software protection functions may also include code for managing an controlling access to protected software features using a combination key as described herein. These and other such activities use computing resources to serve the purpose of preventing or discouraging use of the software object that, for example, may be not in compliance with terms of use specified in a license or other agreement, or otherwise undesirable. The first portion 116 comprises compiled code for software protection functions, but not necessarily all software protection functions included in software 114.
Software 114 may further comprise second portion 118 distinct from the protection function portion 116. Second portion 118 may include code for performing any functions. Functions performed by second portion 118 should include a function that it is desired to control independently of other functions of code 114. It should be appreciated that code 114 may include additional portions (not shown) to be configured for independent access control, portion 118 being one of many possible code portions that it is desired to control access to independently of other parts of code 114. For example, if object 114 is a computer game, such independently controlled features may include unlocking of game objects, setting player customization parameters, accessing the game environment, or unlocking levels of play. These examples are not intended to limit the scope of functions that may be included in portion 118 and other independently controlled portions. In some embodiments, these independently controlled portions including portion 118 may be selected to comprise a relatively small but critical part of functions performed by software 114. In other embodiments, independently controlled portions may comprise most or all functions in software 114 except those included in the first portion 116.
Software 114 may further comprise a third portion 120 distinct from the first portion 116 and second portion 118. The third portion 120, if present, may comprise code for performing functions that are not selected for independent control or functions for which a lower level of protection, or a different type of protection, is desired.
Processor 108, under control of instructions stored in memory 110, processes the first code portion 116 to read and extract a definite part 124 of the code portion 116. The part 124 may be selected from the code portion using any defined and reproducible algorithm, for example, extracting every Nth bit between specified bit positions to obtain a data signature of definite size. To “extract” here means to read and copy data to generate a definite data object (e.g., part 124) in a computer memory, and does not require removing or altering any data in code portion 116. Software object 114 should be unaltered by the extraction of part 124. Part 124 may comprise the entirety of code portion 116, or some smaller part. It may be extracted from contiguous, or non-contiguous data comprising the compiled code 114. Key part 114 should comprise some minimum non-zero number of bits, for example, 128, 256 or 512 bits. A greater number of bits decreases the risk of brute-force attempts to discover the key value.
Processor 108 may further extract or generate an identifier 130 compiled as part of code portion 116 or other part of code 114 exclusive of the controlled portion 118. The processor may generate the identifier and compile it into code 114. In the alternative, the processor may extract the identifier 130 from compiled code in a manner similar to the first key part 124. The identifier may comprise any discrete data object configured for identification purposes, such as by being unique while using an efficient number of data bits for the applicable set of items to be identified. In the present case, the items to be identified comprise a set of second key parts, for example second key part 132 shown in data table 134.
Processor 132 may generate or otherwise obtain the second key part 132, comprising a defined non-zero number of bits, for example, 128, 256, or 512 bits. The second key part may be stored in a data table or data base accessible to processor 108, in association with the key identifier 130.
Processor 108 and memory 11 may be further programmed to compute a data signature for a combination of the extracted first key part 124 and the second key part 132. The key parts may be combined in any definite fashion, including but not limited to sequencing the first key part and the second key part together to form a unified data sequence. The processor may then further process the combined key data, such as using a one-way hash, data signature, cryptographic hash, or similar procedure, to produce a cryptographic key 136. Suitable cryptographic and other hash functions, for example, SHA-256/224, are known in the art of cryptography.
After computing the data signature, the processor under control of instructions in memory 110, uses the cryptographic key 136 to encrypt the second data portion 118 to provide an encrypted second data portion 138. The processor may use the key 136 as a symmetrical encryption key, useful for both encryption and decryption. In the alternative, the processor may use the key 136 as the private part of a public/private key pair. The processor replaces the unencrypted code portion 118 with the encrypted output 138 in software object 114, to generate a new software object 115 (shown in FIG. 2) comprising the portions 116, 138 and 120, and excluding the unencrypted portion 118.
The processor may repeat the processes of defining an identifier, second key part, combination key data, and cryptographic key for encrypting any additional portions of the software that, like portion 118, are to be configured for independent control. It should be appreciated that any additional identifiers and second key parts that the processor defined for additional code portions will be have values that are distinct from each other and from the values of identifier 130 and second key part 132 discussed above. These additional values may be included in the data table 134, which may be compiled or otherwise included with code package 114 by processor 108. In the alternative, or in addition, the data table 134 may be maintained at a secure server for access by remote clients. The processor 108 may obfuscate and/or encrypt the data table 134 to prevent and discourage decompiling or other unauthorized use.
Software object 114 and/or the new software object 115 may also include a code portion 122 comprising instructions and/or data for use in encrypting and/or decrypting portion 118/119. For example, code portion 122 may comprise: data that defines the various portions 116, 118 (or 119), and 120; data defining the location and extent of the first key data 124 extracted for generating a cryptographic key; data defining the location and extent of identifier 130; instructions for obtaining the second key part 132 from a data base or data table (which may be separately encrypted); an algorithm defining computational steps for combining and determining the cryptographic key 136 from the first key part 124 and the second key part 132; an algorithm defining computational steps for encrypting the code portion 118; an algorithm defining computational steps for decrypting the code portion 119; and/or information for assembling or coordinating execution of decrypted data with portions 116, 120 to provide executable program instructions. In some embodiments, code portion 122 may be packaged with software object 114 and processed by processor 108 to generate the software 115. In the alternative, or in addition, the parameters defined by the code portion 122 may be determined by processor 108 as part of its programmed data processing, and appended to the original code package 114 after processing. Like other portions of software 114 and 115, code portion 122 may be compiled as executable binary data. Like other parts of code package 114 and 115, it may be obfuscated and/or encrypted to prevent and discourage decompiling or other unauthorized use.
After the second portion 118 is encrypted to become encrypted portion 119, the code package 115 may be distributed in any suitable way for installation and use on a client computing device. For example, FIG. 2 shows elements of a client computer 202 comprising a processor 208 connected to a memory 210 holding instructions 211 configured to cause actions as described herein. Processor 208 may be operably associated with a file storage device 212 on which is stored a software executable object 115, comprising one or more files. The processor 208 and memory 210 with these instructions 211 may comprise means for performing the described actions. The instructions 211 may comprise part of the protected code 115, for example code portion 122, and may be stored in a computer memory or computer-readable medium and loaded into memory 210 during or prior to processing the software object 115.
Executable object 115 may comprise the elements discussed above for executable software 114, except that encrypted code portion 138 replaces the unencrypted binary code 118 processed by server 102 and the combination key functions 122 may be added. Client 202 may be in use by a person providing control input through an interface device 204 to achieve a desired output from output device 206, via interaction with processor 208 operating software 115. To successfully operate software 115, the processor must at some time or times decrypt the encrypted portion 119. To avoid creating decrypted stored executable files, the processor 208 may, according to a predetermined scheme, decrypt the encrypted portion only at a specified time or times during operation of executable 115, and maintain the unencrypted data 118 exclusively in a buffer or other temporary memory until the program 115 is terminated, at which time the processor 208 may delete the unencrypted code 118 or allow it to be lost as memory space is overwritten with other data or powered down.
To decrypt the encrypted portion 118, client 202 may access decryption instructions 122. Using the instructions and/or data encoded in code portion 122, the processor may locate and read the first key data 124 located in code portion 116 and the identifier 130. The processer 208 then queries the data table 134, which may be sited locally or remotely, to obtain the second key part needed to generate the decryption key 136. If additional code portions (not shown) require independent decryption, processor 208 may obtain additional identifiers and second key parts in a corresponding manner. The processor may then combine the first key part 124 with the second key part 132 to obtain combination key data according to instructions 122, which the processor may then hash using a designated technique to obtain the required cryptographic key 136 needed to decrypt portion 138. Each different second key part may be combined by the processor with the first key part 124 to generate independent combination data that may be hashed to obtain additional keys for decrypting independently encrypted portions (not shown) of code 115. Different features of code 115 may thereby be independently protected using independent decryption keys, all of which require the first key part 124 to generate at the client. Each decryption key also requires an independently obtained second key part obtained using a predesignated identifier in the manner described above.
Accordingly, if code portion 116 encoding software protection functions has been altered in any meaningful way, the first key part 124 will not be intact and client 202 will be unable to decrypt code portion 119. If code portion 116 is unaltered, the first key part 124 will be intact. In either case, processor 208 may process combination key data derived from the first key part 124 and second key part 132 using the designated cryptographic hash, which is designated by code portion 122 or by some other means, such as with a separately distributed protection scheme. By applying the designated hash to the combination key data, the processor will obtain the necessary cryptographic key for decrypting the encrypted code portion 118. If the first key part 124 is not perfectly intact, the processor will not obtain a useful key. Likewise, if the code portion 116 is intact, it will control the ability of the processor to obtain the identifiers and/or second key parts needed to complete the decryption of designated functions. Therefore these functions will, with the assurance provided by the first key part 124, be unlocked only if the user meets requirements encoded in code portion 116.
The processor 208 may decrypt code portion 119 to obtain unencrypted code 118, which the processor may maintain in a temporary storage buffer and execute as required to perform the actions coded by portion 118. Decryption instruction 122 or other code portion may enable coordination of the buffered decrypted code portion 118 and the remainder of executable 115. If the decrypted data is not functional, this indicates that the decryption key is not valid and that, thus, the software protection functions have been altered. Conversely, if the functions coded by portion 118 execute normally, this means that the software protection portion 116 is not altered, and has or will be executed by processor 208.
In accordance with the foregoing, FIG. 3 shows an exemplary method 300 and steps for performance by a server to protect a designated software executable using an embedded key part and identified key part scheme. Method 300 may be applied to a wide range of different types of executable data and files to provide a more secure product for public distribution and to enable independent control of access to software functions for the distributed software. Once the server has received a completed executable, the code portion making up the designated software protection functions should be defined 302. These are the functions that are to be protected from alteration, and that are not part of the core product functions as are normally used at the client nodes. If source code is supplied to the server, the software protection portion may be defined by reading and classifying the source code. If only compiled code is provided, it should be provided with data addresses that define and delimit the extent of the software protection functions.
At 304, the server may similarly define protected functions that are not included in the software protection functions, and are to be separately protected using a combination key scheme. One or more of protected functions may be defined. At 306, the server may define the combination key functions, meaning those functions that define the combination key protection scheme, e.g., as defined by code portion 122 discussed above. As noted above, combination key functions may, in the alternative, be added by the server to the resulting protected executable 328 according to a protection scheme defined at the server. Together, steps 302, 304, and 306 describe a process of generating or receiving source code, and classifying the functions defined by the received source code into mutually exclusive categories. A category of unprotected code (not shown) may also exist.
At 308, the server may compile the source code 308 to produce one or more executable files. The server may then be used to identify 310 the limits of the compiled protection functions and other functions in the compiled code, through the use of data mapping and/or markers. At 312, the server extracts key data from the compiled protection function according to its identified limits. At 314, the server defines one or more second key parts and a corresponding identifier for each key part as one or more key/identifier data pairs. The server may generate each data pair for use in encrypting different code segments to enable independent access control for different features or functions of the software.
The server may save 316 each data pair in a database or data table. The server by obfuscate and/or encrypt the data table and package it with the software to be protected. In the alternative, or in addition, the server may store each key pair in a secure database for access by remote clients at run time. At 318, the server may combine the first key part and, for each independently protected code segment, a respective one of the second key parts, such as by conjugating each part together to form a unitary data object. The server may generate a cryptographic signature of the unitary data object using any suitable defined process to obtain a cryptographic key. In addition, the server may save each identifier in a format accessible to each client that will be operating the target software. For example, the server may compile 320 one or more identifiers as part of the distributed code. The identifiers should be saved with information indicating which of the separately protected functions will be encrypted or decrypted using a key obtained in part using the identifier. Such information will be necessary for the client to select the correct identifier needed to decrypt different parts of the distributed code.
Using the cryptographic keys derived from the combination of the first key part and each respective second key part, the server may encrypt 322 each separate portion of the executable data that is designated for encryption with a corresponding one of the keys. The server may discard (not preserve in any memory) the keys used for encryption. However, the server may write the combination key functions, including the limits of the first key part, the identifier needed to obtain the second key part, and the cryptographic signature algorithm used to compute the data signature, or an identifier of the algorithm, to data associated with or incorporated in the executable program.
At 324, the server removes the unencrypted part of the executable program that is designated for protection, and adds the data encrypted at step 322. The server may also include executable modules incorporating the combination key instructions intended for use when operating the protected program. The completed protected program may include the compiled software protection functions, the combination key functions, an encrypted portion, and optionally, functions that are not included in any of the foregoing, such as auxiliary functions that do not require a high degree of protection.
At 326, the server may apply a conventional encryption process to the assembled executable. This step merely adds a conventional layer of additional protection to the resulting executable 328. The resulting executable 328 may be encoded on any suitable computer-readable medium for later distribution to one or more clients.
FIG. 4 shows a method 400 that may be performed by a client receiving the protected executable 328. If conventional encryption (e.g., PKI or other scheme) was used to encrypt the executable, the client may decrypt 402 the entire executable prior to further processing. However, decryption step 402 will not result in decryption of the specially encrypted executable portions encrypted at step 322 of FIG. 3.
At 404, the client may execute the protected software protection functions in which at least the first key part, and optionally identifiers for one or more second key parts, is embedded as data. These functions should be performed by the client in response to the conditions specified for them, at initial installation and/or at other times. These may include both existing functions known in the art, and protection functions to be developed in the future. The client may require successful completion of the protection functions before proceeding with method 400. For example, the client may require that the client device is authorized to install and/or operate the protected executable or that the client is in use by a person with authority to use the protected executable, as determined by the protection functions, before proceeding with subsequent steps.
Steps 406-418 together provide examples of actions that may be referred to as combination key functions. It is necessary that the client be provided with instructions for performing the combination key functions. These instructions may be provided with or as part of the protected executable 328 as described above. In the alternative, the combination key functions may be separately transmitted, for example from a server to the client at run time in response to some event triggered by the software protection functions, or by some other method.
At 406, the client locates the key data in the protected executable, using a map or algorithm supplied by the combination key functions. The client read and loads the key data into processor memory as a first step in obtaining a combination key. Next, the client locates 410 encrypted data in the protected executable corresponding to one of the protected features that is to be accessed. The protection functions should operate to ensure that the client is authorized to access the protected feature some time prior to actual decryption or use of the feature. The client may locate 410 the encrypted data using a second map or algorithm supplied by the combination key functions. In the same process, or in a corresponding similar process, the client locates a key identifier compiled into the executable 328 for the feature to be accessed.
Then, at 414, the client may query a remote or local data table using the key identifier to obtain a second key part. The client combines 416 the first key part and the second key part to generate a combination key. The client may perform a cryptographic hash or other one-way function using the combination of the first and second key parts to obtain a decryption key. The client may combine the first key part with different second key parts, and hash the resulting combinations, to obtain different decryption keys for different parts of the protected executable 328. The client may independently decrypt 418 each of the encrypted data portions using a corresponding one of the decryption keys generated at 416.
If each decryption key is valid and the software executable has not been corrupted, the resulting decrypted code will comprise part of the original executable that performs valuable functions on the client. The client may load each decrypted code portion 420 into processor memory and/or a protected memory buffer, for execution whenever called for. If the decrypted functions operate normally when called 422, then operation of the software protection functions is indirectly confirmed 424. Conversely, if the decrypted functions do not operate normally, then this indicates that the software protection functions have been tampered with or corrupted 426. Thus, the technology disclosed herein discourages and prevents tampering with software protection features of distributed executable software, without requiring additional any additional hardware.
Having thus described a preferred embodiment of securing the integrity of executable code using a combination key, it should be apparent to those skilled in the art that certain advantages of the within system have been achieved. It should also be appreciated that various modifications, adaptations, and alternative embodiments thereof may be made without departing from the scope and spirit of the present technology. The following claims define the scope of what is claimed.
1. A method for protecting software from tampering, comprising:
processing, using a computer, first compiled software stored in a computer memory to generate a first key part, the first compiled software configured to perform software protection functions and defined second functions distinct from the software protection functions when executed by a computer processor, and the first key part consisting of a first portion of the first compiled software comprising executable code compiled from the software protection functions;
generating an identifier and a second key part for each of the defined second functions;
generating a cryptographic key determined from the first key part and the second key part;
encrypting a second portion of the first compiled software using the cryptographic key, to produce second compiled software comprising the first portion in unencrypted form and the second portion encrypted with the cryptographic key, wherein the second portion comprises executable code compiled from the defined second functions; and
storing the second compiled software in a computer memory for distribution to a client device.
2. The method of claim 1, further comprising compiling an algorithm to provide an executable object configured for extracting the cryptographic key from the second compiled software.
3. The method of claim 2, further comprising including the executable object in the second compiled software.
4. The method of claim 2, further comprising storing the executable object at a network node and not in the second compiled object.
5. The method of claim 1, further comprising configuring the second compiled software with code for recognizing the identifier and the encrypted second portion in the second compiled software.
6. The method of claim 1, further comprising generating a data table storing the identifier in association with the second key part.
7. The method of claim 6, further comprising serving the data table from a server to a client operating the second compiled software.
8. The method of claim 1, further comprising configuring the second compiled software with code for generating the combination key from the first key portion and the second key portion.
9. The method of claim 8, further comprising including the code for generating the combination key in the second compiled software.
10. A method for executing software at a client device, comprising:
executing a first portion of executable software using a computer processor, to extract a first key part and a key identifier from a second portion of the executable software stored in a computer memory;
querying a data table using the identifier to obtain a second key part;
combining the first key part and the second key part to generate a decryption key;
decrypting a third portion of the executable software using the decryption key to provide an executable third portion that is distinct from the first and second portions of the executable software; and
executing the executable third portion using the computer processor to perform a processing function.
11. The method of claim 10, further comprising executing the second portion of the executable software to perform a function that protects the executable software from unauthorized use.
12. The method of claim 11, wherein the function that protects the executable software from unauthorized use determines whether the executable software is installed on an authorized client device before decrypting the third portion of the executable software.
13. The method of claim 11, wherein the function that protects the executable software from unauthorized use determines whether the client device is in use by an authorized user before decrypting the third portion of the executable software.
14. The method of claim 10, wherein the first key part is extracted from non-contiguous data segments of the executable software by the computer processor.
15. The method of claim 14, wherein the first portion of executable software includes an algorithm for locating the non-contiguous data segments.
16. The method of claim 10, further comprising selecting the key identifier from at least two different key identifiers included in the second portion of the executable software.
17. The method of claim 16, wherein the key identifier is selected using an indicated association with the third portion of the software.
18. A computer-readable medium encoded with instructions configured to cause a computer to:
execute a first portion of the instructions to extract a first key part from a second portion of the instructions;
determine an identifier for a third portion of the instructions;
obtain a second key part using the identifier;
determine a decryption key using the first key part and second key part;
decrypt the third portion of the instructions using the decryption key to provide an executable third portion that is distinct from the first and second portions of the instructions; and
execute the executable third portion to perform a processing function.
19. The computer-readable medium of claim 18, wherein the second portion of the instructions is configured to perform a function that protects the instructions from unauthorized use.
20. The computer-readable medium of claim 19, wherein the second portion of the instructions is configured to protect the executable software from unauthorized use by determining whether the instructions are installed on an authorized client device before decrypting the third portion of the instructions.
US12/792,206 2009-06-19 2010-06-02 Feature-Specific Keys for Executable Code Abandoned US20100325431A1 (en)
US21860209P true 2009-06-19 2009-06-19
US12/792,206 US20100325431A1 (en) 2009-06-19 2010-06-02 Feature-Specific Keys for Executable Code
US20100325431A1 true US20100325431A1 (en) 2010-12-23
ID=42734822
US12/792,206 Abandoned US20100325431A1 (en) 2009-06-19 2010-06-02 Feature-Specific Keys for Executable Code
US (1) US20100325431A1 (en)
EP (1) EP2264640B1 (en)
2010-06-02 US US12/792,206 patent/US20100325431A1/en not_active Abandoned
2010-06-08 EP EP10165197.4A patent/EP2264640B1/en active Active
US10061907B2 (en) * 2015-07-27 2018-08-28 International Business Machines Corporation File origin determination
EP2264640B1 (en) 2018-07-25
EP2264640A3 (en) 2015-02-25
EP2264640A2 (en) 2010-12-22
DE60130172T2 (en) 2008-05-21 A secure and open computer platform