Post-production preparation of an unprotected installation image for downloading as a protected software product

• US 8,671,060 B2
• Filed: 10/07/2011
• Issued: 03/11/2014
• Est. Priority Date: 09/20/2007
• Status: Active Grant

• Current Assignee: Uniloc 2017 LLC (SoftBank Group Corp.)
• Original Assignee: Uniloc Luxembourg S.à r.l. (f/k/a Uniloc Luxembourg S.A.) (Uniloc Corporation Pty. Limited)
• Inventors: Richardson, Ric B.
• Primary Examiner(s): Reagan, James A
• Application Number:
  US13/269,415
• Publication Number:
  US 20120030668A1
• Time in Patent Office: 886 Days
• Field of Search: 705/51
• US Class Current: 705/51
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]

Abstract

An installation image for installing an unprotected software product is used to install a protected version of the same product. A protected version of the executable file is embedded in a new installation image with the original installation image, in which the unprotected version of the executable file is damaged so as to be unusable and unreadable. The new installation image causes the original installation image to operate, installing the damaged installation file and other data files. The new installation image then replaces the damaged installation file with the protected installation file.

Claims

1. A method for altering an unprotected software installation image to install a protected version of an unprotected executable file included in the installation image, instead of installing the unprotected executable file, the method involving assembling a master installation image at a server, the master installation image for download from a server to a target computer, wherein the master installation image is assembled by:

receiving, by the server, a first executable file comprising the unprotected software installation image configured for installing the unprotected executable file in the target computer;

receiving, a second executable file comprising the protected version of the unprotected executable file that is identical in function to the unprotected executable file except for incorporating additional code configured to protect the unprotected executable file from unauthorized use;

receiving a third executable file configured with instructions for replacing the unprotected executable file with the protected version of the unprotected executable file in a computer-readable medium, in response to completion of installation of the unprotected executable file in the computer-readable medium; and

integrating, at the server, the unprotected installation image, the protected version of the unprotected executable file, and the third executable file to produce the master installation image configured for installing the protected version of the unprotected executable file instead of the unprotected executable file.

2. The method of claim 1, further comprising receiving a fourth executable file configured for initiating operation of the unprotected installation image on the target computer.

3. The method of claim 2, further comprising integrating the fourth executable file into the master installation image.

4. The method of claim 1, further comprising disabling the unprotected executable file included in the master installation image to render the unprotected executable file inoperable.

5. The method of claim 4, further comprising irreversibly altering information in the unprotected executable file to disable the unprotected executable file.

6. The method of claim 4, further comprising randomly altering information in the unprotected executable file to disable the unprotected executable file.

7. The method of claim 1, further comprising transmitting the master installation image to the target computer.

8. The method of claim 1, further comprising writing the master installation image to a computer-readable medium.

9. The method of claim 1, wherein the third executable file is further configured with instructions to deliberately and irreversibly corrupt the unprotected executable file so that it will not run and cannot be decompiled.