US20020091644A1 - Electronic software license with software product installer identifier - Google Patents
Electronic software license with software product installer identifier Download PDFInfo
- Publication number
- US20020091644A1 US20020091644A1 US09/755,433 US75543301A US2002091644A1 US 20020091644 A1 US20020091644 A1 US 20020091644A1 US 75543301 A US75543301 A US 75543301A US 2002091644 A1 US2002091644 A1 US 2002091644A1
- Authority
- US
- United States
- Prior art keywords
- software product
- stored
- license
- file
- software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000009434 installation Methods 0.000 claims abstract description 46
- 238000000034 method Methods 0.000 claims description 49
- 230000004044 response Effects 0.000 claims description 14
- 230000003287 optical effect Effects 0.000 description 7
- 238000013459 approach Methods 0.000 description 5
- 238000012546 transfer Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000005055 memory storage Effects 0.000 description 3
- 230000006855 networking Effects 0.000 description 3
- 230000008439 repair process Effects 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000012552 review Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
- G06F21/73—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information by creating or determining hardware identification, e.g. serial numbers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/12—Protecting executable software
- G06F21/121—Restricting unauthorised execution of programs
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99939—Privileged access
Definitions
- the present invention generally relates to providing tools to reduce software piracy. More particularly, the present invention relates to an electronic software license having an installer identifier that restricts the use of the software license to a particular software product.
- Another attempt to limit the ability of a user to duplicate a software product involves verifying the presence of an electronic software license, prior to enabling the execution of the software product.
- an electronic license is generated and stored on the user's computer (e.g., hard drive) when the user attempts an installation of the software product. Subsequently, when the user attempts to run (i.e., execute) the software product, the software product will not execute if the electronic license is not present.
- this approach also has a shortcoming: the license can be copied and used with another software product that uses a similar licensing system. That is, a software pirate could purchase and install one software product and then copy the license from his hard drive to be used with other software products. Thus, the installed license could be misused to pirate other software products.
- the present invention meets the above-described needs by providing an anti-piracy software licensing system that associates a license file with a particular software product, so that the license file cannot be used with a separate product.
- the present invention associates the license with one and only one product by adding an Installer Identifier (IID) to the license file.
- IID is an identification number that is used to identify a software product by characterizing the media on which the software product originally resides.
- the IID may be generated by “hashing” the files on the media containing a particular software product or by any other means for associating the IID with the particular, licensed software product.
- a set-up or installation program can be executed to install the software product.
- the set-up program requires that a user enters a product key associated with the software media (e.g., printed on a label on the media). Once the user has entered the correct product key, the set-up program will transfer the required run-time files and the license file on the media from the software media to the user's hard drive. The set-up program will then generate the IID based on a characteristic of the media and will check the generated IID against the IID stored in the license file on the same media.
- a match will verify that the license file on the media (i.e., the media license file) was not tampered with prior to installation and that the license file was intended to be used with the software product on the media. If there is a match, the media license file and a hardware identifier (HWID), identifying the computer on which the software is being installed, are stored in a hardware signature file. However, if there is not a match, then the installation will be halted and the user will be informed of the inability to install the software.
- HWID hardware identifier
- the locally stored license file i.e., local license file
- the HWID of the local machine is computed and compared with the license in the hardware signature file. This is done to verify that local license file was not tampered with after installation has been completed. If there is a match it is assumed that the local license file is properly associated with the installed software product and execution of the software product is enabled. If there is not a match, the user will be prompted to repair the software.
- a method for restricting the installation of a software product.
- An installer identifier is generated and compared to a previously stored installer identifier. If the generated installer identifier and the stored installer identifier match, a license file is stored and a complete installation of the software product is enabled. The license file can be subsequently accessed to enable the execution of the completely installed software product.
- a method for restricting the installation and execution of a software product.
- An installer identifier is generated and compared to a previously stored installer identifier. If the generated installer identifier and the stored installer identifier match, a license file is stored and a complete installation of the software product is enabled. In addition, execution of the software product is enabled, in response to a determination that a proper license file has been stored.
- a system for restricting the installation of a software product.
- a set-up program generates an installer identifier representing a characteristic of the software product media containing the software product.
- the set-up program also compares the generated installer identifier to a stored installer identifier and enables the installation of the software product's run-time files in response to a determination that the generated installer identifier matches the stored installer identifier.
- FIG. 1 is a block diagram illustrating an exemplary operating environment for implementing of the present invention.
- FIG. 2 depicts an exemplary installation transaction between a computer and a software product media.
- FIG. 3 depicts an installation transaction performed by an exemplary embodiment of the present invention.
- FIG. 4 depicts an exemplary software product media containing a software product that can be protected by an exemplary embodiment of the present invention.
- FIG. 5 is a flow chart depicting an exemplary method for installing a software product that is protected by a software license and an installer identifier.
- FIG. 6 is a flow chart depicting an exemplary method for enabling and disabling the execution of a software product that is protected by a software license and an installer identifier.
- an antipiracy software licensing system that associates a license file to a particular software product, so that the license file cannot be used with a separate product.
- This embodiment of the present invention associates the license with one and only one product by adding an Installer Identifier (IID) to the license file.
- IID is an identification number that is used to identify a software product by characterizing the media on which the software product originally resides.
- the IID may be generated by “hashing” the files on the media containing a particular software product or by any other means for associating the IID with the particular, licensed software product.
- a user can insert the software media and run a set-up program.
- the set-up program will usually require that the user enters a product key associated with the software media (e.g., printed on a label on the media).
- the set-up program will transfer the required run-time files and the license file on the media (media license file) from the software media to the user's hard drive.
- the set-up program will then generate the IID based on a characteristic of the media and will check the generated IID against the IID stored in the license file on the same media. A match will verify that the media license file was not tampered with prior to installation and that the license file is intended to be used with the software product on the media.
- the media license file and a hardware identifier (HWID), identifying the computer on which the software is being installed, are stored in a hardware signature file. However, if there is not a match, then the installation will be halted and the user will be informed of the inability to install the software.
- HWID hardware identifier
- the locally stored license file i.e., local license file
- the HWID of the local machine is computed and compared against the license in the hardware signature file. This is done to verify that local license file was not tampered with after installation has been completed. If there is a match it is assumed that the local license file is properly associated with the installed software product and execution of the software product is enabled. If there is not a match, the user will be prompted to repair the software.
- FIG. 1 illustrates an exemplary operating environment for implementation of the present invention.
- the exemplary operating environment includes a general-purpose computing device in the form of a conventional personal computer 20 .
- a personal computer 20 includes a processing unit 21 , a system memory 22 , and a system bus 23 that couples various system components including the system memory 22 to processing unit 21 .
- System bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
- the system memory includes a read only memory (ROM) 24 and random access memory (RAM) 25 .
- a basic input/output system (BIOS) 26 containing the basic routines that help to transfer information between elements within personal computer 20 , such as during start-up, is stored in ROM 24 .
- BIOS basic input/output system
- Personal computer 20 further includes a hard disk drive 27 for reading from and writing to a hard disk, not shown, a magnetic disk drive 28 for reading from or writing to a removable magnetic disk 29 , and an optical disk drive 30 for reading from or writing to a removable optical disk 31 such as a CD-ROM or other optical media.
- Hard disk drive 27 , magnetic disk drive 28 , and optical disk drive 30 are connected to system bus 23 by a hard disk drive interface 32 , a magnetic disk drive interface 33 , and an optical disk drive interface 34 , respectively.
- a number of program modules may be stored on hard disk 27 , magnetic disk 29 , optical disk 31 , ROM 24 , or RAM 25 , including an operating system 35 , a set-up program 36 , a local license file 38 , and a hardware signature file 39 .
- Program modules include routines, sub-routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types.
- aspects of the present invention may be implemented in the form of a set-up program 36 that can be incorporated into or otherwise in communication with a local license file 38 .
- the set-up program 36 generally comprises computer-executable instructions for setting-up and installing a software product.
- the local license file 38 generally comprises computer-executable instructions and/or data enabling the installation and/or execution of a software product associated with the license file.
- the local license file 38 is generally accessible to the set-up program 36 , but can also be implemented as an integral part of the set-up program.
- a user may enter commands and information into personal computer 20 through input devices, such as a keyboard 40 and a pointing device 42 .
- Other input devices may include a microphone, joystick, game pad, satellite dish, scanner, or the like.
- processing unit 22 may be connected by a serial port interface 46 that is coupled to the system bus 23 , but may be connected by other interfaces, such as a parallel port, game port, a universal serial bus (USB), or the like.
- a display device 47 may also be connected to system bus 23 via an interface, such as a video adapter 48 .
- personal computers typically include other peripheral output devices (not shown), such as speakers and printers.
- the personal computer 20 may operate in a networked environment using logical connections to one or more remote computers 49 .
- Remote computer 49 may be another personal computer, a server, a client, a router, a network PC, a peer device, or other common network node. While a remote computer 49 typically includes many or all of the elements described above relative to the personal computer 20 , only a memory storage device 50 has been illustrated in the figure.
- the logical connections depicted in the figure include a local area network (LAN) 51 and a wide area network (WAN) 52 .
- LAN local area network
- WAN wide area network
- the personal computer 20 When used in a LAN networking environment, the personal computer 20 is often connected to the local area network 51 through a network interface or adapter 53 .
- the personal computer 20 When used in a WAN networking environment, the personal computer 20 typically includes a modem 54 or other means for establishing communications over WAN 52 , such as the Internet.
- Modem 54 which may be internal or external, is connected to system bus 23 via serial port interface 46 .
- program modules depicted relative to personal computer 20 may be stored in the remote memory storage device 50 . It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
- the present invention may be implemented in other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor based or programmable consumer electronics, network person computers, minicomputers, mainframe computers, and the like.
- the invention may also be practiced in distributed computing environments, where tasks are performed by remote processing devices that are linked through a communications network.
- program modules may be located in both local and remote memory storage devices.
- FIG. 2 depicts an exemplary installation transaction between a computer and a software product media.
- a hard drive 200 transmits an installation request to a software product 202 .
- an installation request will constitute an instruction to install the software product 202 on the hard drive 200 .
- this is done by executing a set-up program that is located on the software product 202 .
- a set-up program that is located on the software product 202 .
- the software product 202 can transmit a software license to the hard drive 200 .
- the software license is a security file that can be used to verify that the user is attempting to install an authorized copy of the software product.
- execution of the installed software product is subsequently attempted, the presence of the software license on the hard drive can be verified prior to enabling execution.
- Execution of the installed software product can be disabled in the absence of an acceptable software license file. Execution of the installed software product will be enabled, when the presence of an acceptable software license is determined.
- the installation transaction may require the entry of a software product key.
- the software product key is a password associated with the software product. Installation and/or subsequent execution of the software product may be disabled, in response to the entry of an incorrect software product key.
- a software product key is often physically associated with the software product, such as by a label affixed to the software product media containing the software product.
- the installation transaction depicted in FIG. 2 can reduce the use of illicit copies of software products by disabling those products.
- a software anti-piracy system utilizing this transaction is susceptible to circumvention.
- the software license is provided as a license file
- the file can be duplicated and used to enable the execution and/or installation of illicitly duplicated software products.
- execution may be inadvertently enabled by the recognized presence of an illicitly duplicated license file.
- the license file for one software product may be duplicated and used to enable the execution of an illicitly installed copy of a second software product.
- an anti-piracy system utilizing the installation transaction depicted in FIG. 2 can be improved by limiting the use of a license file to enabling the execution of only one software product.
- Embodiments of the present invention so limit the use of a license file, by associating the license file with at least one characteristic of the software product.
- FIG. 3 depicts an installation transaction performed by an exemplary embodiment of the present invention.
- the installation transaction depicted in FIG. 3 includes the transfer of a software license from a software product 302 to a hard drive 300 in response to an installation request.
- the installation transaction of FIG. 3 also involves the transfer of an installer identifier (IID).
- the IID provides a connection between the transferred license file and the software product 302 .
- the IID is an identifying characteristic of the software product 302 .
- the IID may be a “hash” value representing all of the files on the media containing the software product 302 (e.g., a compact disc).
- a hash value is a well-known means for adding or summarizing data to generate a number characterizing the data.
- a hash value can be used, for example, for error checking the underlying data. It will be appreciated by those skilled in the art that various other identifying characteristics of the software product 302 could be used in accordance with embodiments of the present invention.
- FIG. 4 depicts an exemplary software product media 400 containing a software product that can be protected by an exemplary embodiment of the present invention.
- the software product media 400 contains all of the necessary files to execute a software product.
- the software product media 400 also contains a license file 404 .
- the license file 404 can be transferred to a computer to limit the execution of the software product.
- the software product media 400 can also include a file list 402 containing a list or a summary of all of the files contained by the software product media 400 .
- the file list 402 could be generated by scanning the software product media 400 and compiling a list of the files found thereon.
- the contents of the file list 402 could be processed by a hashing algorithm to generate a hash value.
- the hash value could be transferred as an IID along with the license file 404 , in order to limit the execution of the associated software product to a computer having a copy of the license file as well as an accurate record of an IID that matches the hash value of the software product media 400 .
- an embodiment of the present invention can be used to disable the execution of a software product where the license file and/or the IID do not conform to the applicable characteristics of software product media 400 . Accordingly, illicit copies of the software product media can be disabled. Execution of a software product can be disabled when it is recognized that a license file associated with one software product is being used to attempt the execution of a separate software product.
- FIG. 5 is a flow chart depicting an exemplary method for installing a software product that is protected by a software license and an installer identifier.
- the method of FIG. 5 starts at block 500 and proceeds to step 502 .
- a set-up program is executed.
- the first step of the installation of a software product is the execution of a set-up program.
- Set-up programs are commonly stored on a software product media and are usually executed directly from the software product media.
- the method of FIG. 5 proceeds from step 502 to step 504 .
- a prompt for a software product key is generated.
- the software product key is typically physically associated with a software product media.
- the software product key may be printed on a label that is affixed to a case holding the software product media.
- step 506 a determination is made as to whether the proper product key was received. If the proper product key was not received, the method proceeds to step 510 and ends. Alternatively, the method could at this point prompt the re-entry of the product key or could generate a dialog box with an explanation that the installation had been stopped in response to an incorrect product key. In any case, the method can terminate installation at step 510 when an incorrect product key has been entered. On the other hand, if a determination is made at decision block 506 that the proper product key has been received, then the method proceeds to step 508 .
- run-time files can be transferred from the software product media to a hard drive.
- run-time files are simply those files needed to execute the software product on the computer associated with the hard drive.
- the method proceeds from step 508 to step 512 .
- the license file is transferred from the software product media to the hard drive and is stored as the local license file.
- step 514 an installer identifier (IID) is generated.
- the IID in this embodiment is generated based on one or more characteristics of the software product. For example, as described in connection with FIG. 4, the IID can be a hash value corresponding to a file list that is associated with the soft product media.
- decision block 516 a determination is made as to whether the generated IID matches a stored IID.
- the stored IID can be stored within the license file that is stored on the software product media.
- the stored license file corresponds to the software product contained on the software product media from which the generated IID was produced. That is, the match verifies that the proper license file is being used to install the software product from the software product media.
- step 520 If a determination is made at decision block 516 that the generated IID does not match the stored IID, the method branches to step 520 and ends. Alternatively, the method could generate a dialog box to display an explanation for the terminated installation transaction. If, on the other hand, a determination is made at decision block 516 that the generated IID matches the stored IID, the method branches to step 518 .
- the license and a hardware identifier are stored in a hardware signature file.
- the hardware identifier can be used to identify the computer that is the host of the hard drive on which the software product has been installed. Once the license and hardware identifier have been stored, the method proceeds to step 520 and ends.
- the method of FIG. 5 either successfully enables or disables the installation of the software product.
- the license stored in the hardware signature file can be used to enable and disable the execution of the installed software product.
- FIG. 6 is a flow chart depicting an exemplary method for enabling and disabling the execution of a software product that is protected by a software license and an installer identifier.
- the method of FIG. 6 starts at block 600 and proceeds to step 602 .
- step 602 an attempt is made to execute the software product that has been previously installed on a hard drive.
- step 604 the local license file stored on the hard drive is compared with the license stored in the hardware signature file.
- the method then proceeds to decision block 606 .
- the method branches to step 612 . At step 612 , execution of the software product is enabled. The method then proceeds to step 610 and ends.
- an exemplary embodiment of the present invention verifies that the use of the license is restricted to enabling the installation and execution of a particular software product. Additionally, by comparing a local license file with the license stored in the hardware signature file, an exemplary embodiment of the present invention prohibits the execution of illicitly installed software products.
Abstract
Description
- The present invention generally relates to providing tools to reduce software piracy. More particularly, the present invention relates to an electronic software license having an installer identifier that restricts the use of the software license to a particular software product.
- The distribution of software products exposes software manufacturers to an increased risk of software piracy. Because software products are generally distributed on some tangible media, such as a compact disk (CD), a software purchaser must be generally able to duplicate a software product from the media onto the purchaser's hard drive to properly use the software. Usually, a software product purchaser purchases only a license to use the software on a single computer (machine). Unfortunately, it can be difficult to limit the single-computer license purchaser to making only a single copy for the purchaser's single-computer use. Often, the purchaser will duplicate the software for use on other computers. Criminals will even duplicate the software for re-sale to others.
- In an effort to reduce software piracy, various attempts have been made to limit the ability of users to duplicate software. In one approach, software is distributed with a printed password associated with the product packaging (e.g., printed on a CD case). The printed password corresponds to a stored password that is encoded into the software. When a user duplicates the software onto a hard drive, the user is prompted to input the printed password before the duplicated software will run for the first time. The input password is compared to the stored password that is encoded into the software. The software will be enabled only if a match is made. Unfortunately, this approach fails to prevent software pirates from creating illicit duplicates of the software. As long as a software pirate provides a copy of the printed password with each illicit copy of the software, the illicit copies will install and function properly.
- Another attempt to limit the ability of a user to duplicate a software product, involves verifying the presence of an electronic software license, prior to enabling the execution of the software product. In this approach, an electronic license is generated and stored on the user's computer (e.g., hard drive) when the user attempts an installation of the software product. Subsequently, when the user attempts to run (i.e., execute) the software product, the software product will not execute if the electronic license is not present. However, this approach also has a shortcoming: the license can be copied and used with another software product that uses a similar licensing system. That is, a software pirate could purchase and install one software product and then copy the license from his hard drive to be used with other software products. Thus, the installed license could be misused to pirate other software products.
- The anti-piracy approaches described above fail to prevent a user from using the electronic license provided by installing Product A to enable the use of an illicit copy of Product B. Therefore, there is a need in the art for an anti-piracy software license that will require a user to generate an electronic license to use a software product, but will also prohibit the duplication of a license for use with an illicit copy of a separate product.
- The present invention meets the above-described needs by providing an anti-piracy software licensing system that associates a license file with a particular software product, so that the license file cannot be used with a separate product. The present invention associates the license with one and only one product by adding an Installer Identifier (IID) to the license file. The IID is an identification number that is used to identify a software product by characterizing the media on which the software product originally resides. The IID may be generated by “hashing” the files on the media containing a particular software product or by any other means for associating the IID with the particular, licensed software product.
- At set-up, a set-up or installation program can be executed to install the software product. The set-up program requires that a user enters a product key associated with the software media (e.g., printed on a label on the media). Once the user has entered the correct product key, the set-up program will transfer the required run-time files and the license file on the media from the software media to the user's hard drive. The set-up program will then generate the IID based on a characteristic of the media and will check the generated IID against the IID stored in the license file on the same media. A match will verify that the license file on the media (i.e., the media license file) was not tampered with prior to installation and that the license file was intended to be used with the software product on the media. If there is a match, the media license file and a hardware identifier (HWID), identifying the computer on which the software is being installed, are stored in a hardware signature file. However, if there is not a match, then the installation will be halted and the user will be informed of the inability to install the software.
- At run-time the locally stored license file (i.e., local license file) with the HWID of the local machine is computed and compared with the license in the hardware signature file. This is done to verify that local license file was not tampered with after installation has been completed. If there is a match it is assumed that the local license file is properly associated with the installed software product and execution of the software product is enabled. If there is not a match, the user will be prompted to repair the software.
- In one aspect of the invention, a method is provided for restricting the installation of a software product. An installer identifier is generated and compared to a previously stored installer identifier. If the generated installer identifier and the stored installer identifier match, a license file is stored and a complete installation of the software product is enabled. The license file can be subsequently accessed to enable the execution of the completely installed software product.
- In another aspect of the invention, a method is provided for restricting the installation and execution of a software product. An installer identifier is generated and compared to a previously stored installer identifier. If the generated installer identifier and the stored installer identifier match, a license file is stored and a complete installation of the software product is enabled. In addition, execution of the software product is enabled, in response to a determination that a proper license file has been stored.
- In yet another aspect of the invention, a system is provided for restricting the installation of a software product. A set-up program generates an installer identifier representing a characteristic of the software product media containing the software product. The set-up program also compares the generated installer identifier to a stored installer identifier and enables the installation of the software product's run-time files in response to a determination that the generated installer identifier matches the stored installer identifier.
- The various aspects of the present invention may be more clearly understood and appreciated from a review of the following detailed description of the disclosed embodiments and by reference to the drawings and claims.
- FIG. 1 is a block diagram illustrating an exemplary operating environment for implementing of the present invention.
- FIG. 2 depicts an exemplary installation transaction between a computer and a software product media.
- FIG. 3 depicts an installation transaction performed by an exemplary embodiment of the present invention.
- FIG. 4 depicts an exemplary software product media containing a software product that can be protected by an exemplary embodiment of the present invention.
- FIG. 5 is a flow chart depicting an exemplary method for installing a software product that is protected by a software license and an installer identifier.
- FIG. 6 is a flow chart depicting an exemplary method for enabling and disabling the execution of a software product that is protected by a software license and an installer identifier.
- In an exemplary embodiment of the present invention, an antipiracy software licensing system is provided that associates a license file to a particular software product, so that the license file cannot be used with a separate product. This embodiment of the present invention associates the license with one and only one product by adding an Installer Identifier (IID) to the license file. The IID is an identification number that is used to identify a software product by characterizing the media on which the software product originally resides. The IID may be generated by “hashing” the files on the media containing a particular software product or by any other means for associating the IID with the particular, licensed software product.
- At set-up, a user can insert the software media and run a set-up program. The set-up program will usually require that the user enters a product key associated with the software media (e.g., printed on a label on the media). Once the user has entered the correct product key, the set-up program will transfer the required run-time files and the license file on the media (media license file) from the software media to the user's hard drive. The set-up program will then generate the IID based on a characteristic of the media and will check the generated IID against the IID stored in the license file on the same media. A match will verify that the media license file was not tampered with prior to installation and that the license file is intended to be used with the software product on the media. If there is a match, the media license file and a hardware identifier (HWID), identifying the computer on which the software is being installed, are stored in a hardware signature file. However, if there is not a match, then the installation will be halted and the user will be informed of the inability to install the software.
- At run-time the locally stored license file (i.e., local license file) with the HWID of the local machine is computed and compared against the license in the hardware signature file. This is done to verify that local license file was not tampered with after installation has been completed. If there is a match it is assumed that the local license file is properly associated with the installed software product and execution of the software product is enabled. If there is not a match, the user will be prompted to repair the software.
- Exemplary embodiments of the present invention will hereinafter be described with reference to the drawings, in which like numerals represent like elements throughout the several figures. FIG. 1 illustrates an exemplary operating environment for implementation of the present invention. The exemplary operating environment includes a general-purpose computing device in the form of a conventional
personal computer 20. Generally, apersonal computer 20 includes aprocessing unit 21, asystem memory 22, and asystem bus 23 that couples various system components including thesystem memory 22 toprocessing unit 21.System bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. The system memory includes a read only memory (ROM) 24 and random access memory (RAM) 25. A basic input/output system (BIOS) 26, containing the basic routines that help to transfer information between elements withinpersonal computer 20, such as during start-up, is stored inROM 24. -
Personal computer 20 further includes ahard disk drive 27 for reading from and writing to a hard disk, not shown, amagnetic disk drive 28 for reading from or writing to a removablemagnetic disk 29, and anoptical disk drive 30 for reading from or writing to a removableoptical disk 31 such as a CD-ROM or other optical media.Hard disk drive 27,magnetic disk drive 28, andoptical disk drive 30 are connected tosystem bus 23 by a harddisk drive interface 32, a magneticdisk drive interface 33, and an opticaldisk drive interface 34, respectively. Although the exemplary environment described herein employshard disk 27, removablemagnetic disk 29, and removableoptical disk 31, it should be appreciated by those skilled in the art that other types of computer readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, RAMs, ROMs, and the like, may also be used in the exemplary operating environment. The drives and their associated computer readable media provide nonvolatile storage of computer-executable instructions, data structures, program modules, and other data forpersonal computer 20. - A number of program modules may be stored on
hard disk 27,magnetic disk 29,optical disk 31,ROM 24, orRAM 25, including anoperating system 35, a set-upprogram 36, alocal license file 38, and ahardware signature file 39. Program modules include routines, sub-routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. Aspects of the present invention may be implemented in the form of a set-upprogram 36 that can be incorporated into or otherwise in communication with alocal license file 38. The set-upprogram 36 generally comprises computer-executable instructions for setting-up and installing a software product. Thelocal license file 38 generally comprises computer-executable instructions and/or data enabling the installation and/or execution of a software product associated with the license file. Thelocal license file 38 is generally accessible to the set-upprogram 36, but can also be implemented as an integral part of the set-up program. - A user may enter commands and information into
personal computer 20 through input devices, such as akeyboard 40 and apointing device 42. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to processingunit 22 through aserial port interface 46 that is coupled to thesystem bus 23, but may be connected by other interfaces, such as a parallel port, game port, a universal serial bus (USB), or the like. Adisplay device 47 may also be connected tosystem bus 23 via an interface, such as avideo adapter 48. In addition to the monitor, personal computers typically include other peripheral output devices (not shown), such as speakers and printers. - The
personal computer 20 may operate in a networked environment using logical connections to one or moreremote computers 49.Remote computer 49 may be another personal computer, a server, a client, a router, a network PC, a peer device, or other common network node. While aremote computer 49 typically includes many or all of the elements described above relative to thepersonal computer 20, only amemory storage device 50 has been illustrated in the figure. The logical connections depicted in the figure include a local area network (LAN) 51 and a wide area network (WAN) 52. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet. - When used in a LAN networking environment, the
personal computer 20 is often connected to thelocal area network 51 through a network interface oradapter 53. When used in a WAN networking environment, thepersonal computer 20 typically includes amodem 54 or other means for establishing communications overWAN 52, such as the Internet.Modem 54, which may be internal or external, is connected tosystem bus 23 viaserial port interface 46. In a networked environment, program modules depicted relative topersonal computer 20, or portions thereof, may be stored in the remotememory storage device 50. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used. - Moreover, those skilled in the art will appreciate that the present invention may be implemented in other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor based or programmable consumer electronics, network person computers, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments, where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
- FIG. 2 depicts an exemplary installation transaction between a computer and a software product media. In FIG. 2, a
hard drive 200 transmits an installation request to asoftware product 202. Typically, an installation request will constitute an instruction to install thesoftware product 202 on thehard drive 200. Often, this is done by executing a set-up program that is located on thesoftware product 202. Those skilled in the art will appreciate that virtually any means of triggering an installation of asoftware product 202 could be used. - In response to the installation request, the
software product 202 can transmit a software license to thehard drive 200. The software license is a security file that can be used to verify that the user is attempting to install an authorized copy of the software product. When execution of the installed software product is subsequently attempted, the presence of the software license on the hard drive can be verified prior to enabling execution. Execution of the installed software product can be disabled in the absence of an acceptable software license file. Execution of the installed software product will be enabled, when the presence of an acceptable software license is determined. - As an additional anti-piracy step, the installation transaction may require the entry of a software product key. The software product key is a password associated with the software product. Installation and/or subsequent execution of the software product may be disabled, in response to the entry of an incorrect software product key. A software product key is often physically associated with the software product, such as by a label affixed to the software product media containing the software product.
- The installation transaction depicted in FIG. 2 can reduce the use of illicit copies of software products by disabling those products. However, a software anti-piracy system utilizing this transaction is susceptible to circumvention. For example, if the software license is provided as a license file, the file can be duplicated and used to enable the execution and/or installation of illicitly duplicated software products. When an illicitly installed software product on a
hard drive 200 checks for a license file, execution may be inadvertently enabled by the recognized presence of an illicitly duplicated license file. Moreover, the license file for one software product may be duplicated and used to enable the execution of an illicitly installed copy of a second software product. - Therefore, an anti-piracy system utilizing the installation transaction depicted in FIG. 2 can be improved by limiting the use of a license file to enabling the execution of only one software product. Embodiments of the present invention so limit the use of a license file, by associating the license file with at least one characteristic of the software product.
- FIG. 3 depicts an installation transaction performed by an exemplary embodiment of the present invention. As with the installation transaction described in connection with FIG. 2, the installation transaction depicted in FIG. 3 includes the transfer of a software license from a
software product 302 to ahard drive 300 in response to an installation request. However, the installation transaction of FIG. 3 also involves the transfer of an installer identifier (IID). The IID provides a connection between the transferred license file and thesoftware product 302. In an exemplary embodiment of the present invention, the IID is an identifying characteristic of thesoftware product 302. For example, the IID may be a “hash” value representing all of the files on the media containing the software product 302 (e.g., a compact disc). A hash value is a well-known means for adding or summarizing data to generate a number characterizing the data. A hash value can be used, for example, for error checking the underlying data. It will be appreciated by those skilled in the art that various other identifying characteristics of thesoftware product 302 could be used in accordance with embodiments of the present invention. - FIG. 4 depicts an exemplary
software product media 400 containing a software product that can be protected by an exemplary embodiment of the present invention. Thesoftware product media 400 contains all of the necessary files to execute a software product. Thesoftware product media 400 also contains alicense file 404. As described above, thelicense file 404 can be transferred to a computer to limit the execution of the software product. Thesoftware product media 400 can also include afile list 402 containing a list or a summary of all of the files contained by thesoftware product media 400. Alternatively, thefile list 402 could be generated by scanning thesoftware product media 400 and compiling a list of the files found thereon. - In an embodiment of the present invention in which the IID is a hash value, the contents of the
file list 402 could be processed by a hashing algorithm to generate a hash value. The hash value could be transferred as an IID along with thelicense file 404, in order to limit the execution of the associated software product to a computer having a copy of the license file as well as an accurate record of an IID that matches the hash value of thesoftware product media 400. - By using both the
license file 404 and the IID, an embodiment of the present invention can be used to disable the execution of a software product where the license file and/or the IID do not conform to the applicable characteristics ofsoftware product media 400. Accordingly, illicit copies of the software product media can be disabled. Execution of a software product can be disabled when it is recognized that a license file associated with one software product is being used to attempt the execution of a separate software product. - FIG. 5 is a flow chart depicting an exemplary method for installing a software product that is protected by a software license and an installer identifier. The method of FIG. 5 starts at
block 500 and proceeds to step 502. Atstep 502, a set-up program is executed. Typically, the first step of the installation of a software product is the execution of a set-up program. Set-up programs are commonly stored on a software product media and are usually executed directly from the software product media. The method of FIG. 5 proceeds fromstep 502 to step 504. Atstep 504, a prompt for a software product key is generated. As described above in connection with FIG. 2, the software product key is typically physically associated with a software product media. For example, the software product key may be printed on a label that is affixed to a case holding the software product media. - The method proceeds from
step 504 todecision block 506. Atdecision block 506, a determination is made as to whether the proper product key was received. If the proper product key was not received, the method proceeds to step 510 and ends. Alternatively, the method could at this point prompt the re-entry of the product key or could generate a dialog box with an explanation that the installation had been stopped in response to an incorrect product key. In any case, the method can terminate installation atstep 510 when an incorrect product key has been entered. On the other hand, if a determination is made atdecision block 506 that the proper product key has been received, then the method proceeds to step 508. - At
step 508, all run-time files can be transferred from the software product media to a hard drive. For the purposes of the description of this exemplary embodiment, run-time files are simply those files needed to execute the software product on the computer associated with the hard drive. The method proceeds fromstep 508 to step 512. Atstep 512, the license file is transferred from the software product media to the hard drive and is stored as the local license file. - The method proceeds from
step 512 to step 514. Atstep 514, an installer identifier (IID) is generated. The IID in this embodiment is generated based on one or more characteristics of the software product. For example, as described in connection with FIG. 4, the IID can be a hash value corresponding to a file list that is associated with the soft product media. The method proceeds fromstep 514 todecision block 516. Atdecision block 516, a determination is made as to whether the generated IID matches a stored IID. The stored IID can be stored within the license file that is stored on the software product media. Thus, it can be assumed that if the generated IID matches the stored IID, then the stored license file corresponds to the software product contained on the software product media from which the generated IID was produced. That is, the match verifies that the proper license file is being used to install the software product from the software product media. - If a determination is made at
decision block 516 that the generated IID does not match the stored IID, the method branches to step 520 and ends. Alternatively, the method could generate a dialog box to display an explanation for the terminated installation transaction. If, on the other hand, a determination is made atdecision block 516 that the generated IID matches the stored IID, the method branches to step 518. Atstep 518, the license and a hardware identifier are stored in a hardware signature file. The hardware identifier can be used to identify the computer that is the host of the hard drive on which the software product has been installed. Once the license and hardware identifier have been stored, the method proceeds to step 520 and ends. Thus, the method of FIG. 5 either successfully enables or disables the installation of the software product. As is described in more detail in connection with FIG. 6, the license stored in the hardware signature file can be used to enable and disable the execution of the installed software product. - FIG. 6 is a flow chart depicting an exemplary method for enabling and disabling the execution of a software product that is protected by a software license and an installer identifier. The method of FIG. 6 starts at
block 600 and proceeds to step 602. Atstep 602, an attempt is made to execute the software product that has been previously installed on a hard drive. The method proceeds to step 604, wherein the local license file stored on the hard drive is compared with the license stored in the hardware signature file. The method then proceeds todecision block 606. - At
decision block 606, a determination is made as to whether the local license matches the license stored in the hardware signature file. If the local license does not match the license stored in the hardware signature file, the method branches to step 608. Atstep 608, a prompt is generated to re-install the run-time files on the hard drive or to repair the local license file. The method then proceeds to step 610 and ends, thereby disabling execution of the software product. Returning to decision block 606, if a determination is made that the local license file matches the license in the hardware signature file, the method branches to step 612. Atstep 612, execution of the software product is enabled. The method then proceeds to step 610 and ends. - By requiring the matching of a generated IID and a stored IID as a prerequisite to storing a license in a hardware signature file, an exemplary embodiment of the present invention verifies that the use of the license is restricted to enabling the installation and execution of a particular software product. Additionally, by comparing a local license file with the license stored in the hardware signature file, an exemplary embodiment of the present invention prohibits the execution of illicitly installed software products.
- Although the present invention has been described in connection with various exemplary embodiments, those of ordinary skill in the art will understand that many modifications can be made thereto within the scope of the claims that follow. Accordingly, it is not intended that the scope of the invention in any way be limited by the above description, but instead be determined entirely by reference to the claims that follow.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/755,433 US7236958B2 (en) | 2001-01-05 | 2001-01-05 | Electronic software license with software product installer identifier |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/755,433 US7236958B2 (en) | 2001-01-05 | 2001-01-05 | Electronic software license with software product installer identifier |
Publications (2)
Publication Number | Publication Date |
---|---|
US20020091644A1 true US20020091644A1 (en) | 2002-07-11 |
US7236958B2 US7236958B2 (en) | 2007-06-26 |
Family
ID=25039130
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/755,433 Expired - Fee Related US7236958B2 (en) | 2001-01-05 | 2001-01-05 | Electronic software license with software product installer identifier |
Country Status (1)
Country | Link |
---|---|
US (1) | US7236958B2 (en) |
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020147922A1 (en) * | 2000-05-15 | 2002-10-10 | Andreas Hartinger | Software protection mechanism |
US20020176580A1 (en) * | 2001-05-24 | 2002-11-28 | Sanyo Electric Co., Ltd. | Data terminal device providing backup of uniquely existable content data |
US20030126456A1 (en) * | 2001-11-14 | 2003-07-03 | Siemens Aktiengesellschaft | Method for licensing software |
US20040194083A1 (en) * | 2001-07-02 | 2004-09-30 | Ian Hindle | Program installation process |
US20050038751A1 (en) * | 2003-08-15 | 2005-02-17 | Gaetano Arthur Louis | System and method for software site licensing |
US20050038752A1 (en) * | 2003-08-15 | 2005-02-17 | Gaetano Arthur Louis | System and method for software site licensing |
US20050044359A1 (en) * | 2003-05-12 | 2005-02-24 | Thomas Eriksson | Anti-piracy software protection system and method |
US20050076334A1 (en) * | 2003-10-03 | 2005-04-07 | Michael Demeyer | System and method for licensing software |
US6973093B1 (en) | 2000-12-29 | 2005-12-06 | Cisco Technology, Inc. | Switching fabric for interfacing a host processor and a plurality of network modules |
US20060064758A1 (en) * | 2004-09-22 | 2006-03-23 | Joe Petner | Method for preventing piracy of computer software |
US20060106729A1 (en) * | 2004-10-25 | 2006-05-18 | Roberts Henry J Jr | Method and apparatus for restricting use of a computer program |
US20060114762A1 (en) * | 2004-11-30 | 2006-06-01 | Sanyo Electric Co., Ltd. | Contents data structure, contents data recording medium and contents data recorder |
US20070043675A1 (en) * | 2000-05-15 | 2007-02-22 | Siemens Aktiengesellschaft | Software license manager |
US20080189549A1 (en) * | 2007-02-01 | 2008-08-07 | Microsoft Corporation | Secure serial number |
US20080319779A1 (en) * | 2007-06-25 | 2008-12-25 | Microsoft Corporation | Activation system architecture |
US20090328227A1 (en) * | 2008-06-26 | 2009-12-31 | Valve Corporation | Anti-piracy measures for a video game using hidden secrets |
US20100162405A1 (en) * | 2008-12-23 | 2010-06-24 | Valve Corporation | Protecting against polymorphic cheat codes in a video game |
US8666900B1 (en) * | 2005-03-30 | 2014-03-04 | Intuit Inc. | Secure product enablement over channels with narrow bandwidth |
US8954732B1 (en) | 2012-06-27 | 2015-02-10 | Juniper Networks, Inc. | Authenticating third-party programs for platforms |
US9256765B2 (en) | 2012-06-29 | 2016-02-09 | Kip Sign P1 Lp | System and method for identifying software changes |
US20170300696A1 (en) * | 2015-01-07 | 2017-10-19 | Huawei Technologies Co., Ltd. | Software verification method and apparatus |
US20190080080A1 (en) * | 2017-09-11 | 2019-03-14 | Kabushiki Kaisha Toshiba | Information processing apparatus, information processing method, and computer program product |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1374040A1 (en) * | 2001-03-30 | 2004-01-02 | Nokia Corporation | Downloading application software to a mobile terminal |
US7096187B1 (en) | 2002-07-23 | 2006-08-22 | Harris Scott C | Compressed audio information |
JP4217455B2 (en) * | 2002-10-15 | 2009-02-04 | キヤノン株式会社 | Peripheral device, information processing method, and control program |
EP1741045A2 (en) * | 2004-04-14 | 2007-01-10 | Ipass Inc. | Dynamic executable |
US7860239B2 (en) * | 2004-07-07 | 2010-12-28 | International Business Machines Corporation | Method and apparatus for metering usage of software products using multiple signatures |
US20060136733A1 (en) * | 2004-12-16 | 2006-06-22 | Ogram Mark E | Anti-pirating system |
JP4868801B2 (en) * | 2005-09-13 | 2012-02-01 | キヤノン株式会社 | License authentication device |
US8010947B2 (en) * | 2006-05-23 | 2011-08-30 | International Business Machines Corporation | Discovering multi-component software products based on weighted scores |
US20090171747A1 (en) * | 2007-12-26 | 2009-07-02 | Microsoft Corporation | Product activation/registration and offer eligibility |
JP7187351B2 (en) * | 2019-02-27 | 2022-12-12 | キヤノン株式会社 | DEVICE MANAGEMENT SERVER, ITS CONTROL METHOD AND PROGRAM |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5933498A (en) * | 1996-01-11 | 1999-08-03 | Mrj, Inc. | System for controlling access and distribution of digital property |
US6044469A (en) * | 1997-08-29 | 2000-03-28 | Preview Software | Software publisher or distributor configurable software security mechanism |
US6049671A (en) * | 1996-04-18 | 2000-04-11 | Microsoft Corporation | Method for identifying and obtaining computer software from a network computer |
US6134593A (en) * | 1997-09-30 | 2000-10-17 | Cccomplete, Inc. | Automated method for electronic software distribution |
US6567793B1 (en) * | 1997-12-22 | 2003-05-20 | Christian Bielefeldt Hicks | Remote authorization for unlocking electronic data system and method |
US6816842B1 (en) * | 1999-12-31 | 2004-11-09 | Ge Medical Technology Services, Inc. | Method and apparatus for automatically processing business contract information into licensed end-user application |
US6948168B1 (en) * | 2000-03-30 | 2005-09-20 | International Business Machines Corporation | Licensed application installer |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0463251A1 (en) * | 1990-06-28 | 1992-01-02 | International Business Machines Corporation | Software installation |
US6044471A (en) | 1998-06-04 | 2000-03-28 | Z4 Technologies, Inc. | Method and apparatus for securing software to reduce unauthorized use |
-
2001
- 2001-01-05 US US09/755,433 patent/US7236958B2/en not_active Expired - Fee Related
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5933498A (en) * | 1996-01-11 | 1999-08-03 | Mrj, Inc. | System for controlling access and distribution of digital property |
US6049671A (en) * | 1996-04-18 | 2000-04-11 | Microsoft Corporation | Method for identifying and obtaining computer software from a network computer |
US6044469A (en) * | 1997-08-29 | 2000-03-28 | Preview Software | Software publisher or distributor configurable software security mechanism |
US6134593A (en) * | 1997-09-30 | 2000-10-17 | Cccomplete, Inc. | Automated method for electronic software distribution |
US6567793B1 (en) * | 1997-12-22 | 2003-05-20 | Christian Bielefeldt Hicks | Remote authorization for unlocking electronic data system and method |
US6816842B1 (en) * | 1999-12-31 | 2004-11-09 | Ge Medical Technology Services, Inc. | Method and apparatus for automatically processing business contract information into licensed end-user application |
US6948168B1 (en) * | 2000-03-30 | 2005-09-20 | International Business Machines Corporation | Licensed application installer |
Cited By (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020147922A1 (en) * | 2000-05-15 | 2002-10-10 | Andreas Hartinger | Software protection mechanism |
US20070043675A1 (en) * | 2000-05-15 | 2007-02-22 | Siemens Aktiengesellschaft | Software license manager |
US6973093B1 (en) | 2000-12-29 | 2005-12-06 | Cisco Technology, Inc. | Switching fabric for interfacing a host processor and a plurality of network modules |
US7134026B2 (en) * | 2001-05-24 | 2006-11-07 | Sanyo Electric Co. Ltd. | Data terminal device providing backup of uniquely existable content data |
US20020176580A1 (en) * | 2001-05-24 | 2002-11-28 | Sanyo Electric Co., Ltd. | Data terminal device providing backup of uniquely existable content data |
US20040194083A1 (en) * | 2001-07-02 | 2004-09-30 | Ian Hindle | Program installation process |
US20030126456A1 (en) * | 2001-11-14 | 2003-07-03 | Siemens Aktiengesellschaft | Method for licensing software |
US20050044359A1 (en) * | 2003-05-12 | 2005-02-24 | Thomas Eriksson | Anti-piracy software protection system and method |
US7716474B2 (en) | 2003-05-12 | 2010-05-11 | Byteblaze, Inc. | Anti-piracy software protection system and method |
US20050038752A1 (en) * | 2003-08-15 | 2005-02-17 | Gaetano Arthur Louis | System and method for software site licensing |
US20050038751A1 (en) * | 2003-08-15 | 2005-02-17 | Gaetano Arthur Louis | System and method for software site licensing |
US8738535B2 (en) | 2003-08-15 | 2014-05-27 | Inter-Tel (DE) Inc | System and method for software site licensing |
US20050076334A1 (en) * | 2003-10-03 | 2005-04-07 | Michael Demeyer | System and method for licensing software |
US9015696B2 (en) | 2003-10-03 | 2015-04-21 | Cyberlink Corp. | System and method for licensing software |
US8898657B2 (en) | 2003-10-03 | 2014-11-25 | Cyberlink Corp. | System and method for licensing software |
US20060064758A1 (en) * | 2004-09-22 | 2006-03-23 | Joe Petner | Method for preventing piracy of computer software |
US20060106729A1 (en) * | 2004-10-25 | 2006-05-18 | Roberts Henry J Jr | Method and apparatus for restricting use of a computer program |
US20060114762A1 (en) * | 2004-11-30 | 2006-06-01 | Sanyo Electric Co., Ltd. | Contents data structure, contents data recording medium and contents data recorder |
US8666900B1 (en) * | 2005-03-30 | 2014-03-04 | Intuit Inc. | Secure product enablement over channels with narrow bandwidth |
US20080189549A1 (en) * | 2007-02-01 | 2008-08-07 | Microsoft Corporation | Secure serial number |
US20110296532A1 (en) * | 2007-02-01 | 2011-12-01 | Microsoft Corporation | Secure serial number |
US8001383B2 (en) * | 2007-02-01 | 2011-08-16 | Microsoft Corporation | Secure serial number |
US8732844B2 (en) * | 2007-02-01 | 2014-05-20 | Microsoft Corporation | Secure serial number |
US9292665B2 (en) | 2007-02-01 | 2016-03-22 | Microsoft Technology Licensing, Llc | Secure serial number |
US8620818B2 (en) * | 2007-06-25 | 2013-12-31 | Microsoft Corporation | Activation system architecture |
US20080319779A1 (en) * | 2007-06-25 | 2008-12-25 | Microsoft Corporation | Activation system architecture |
US9881348B2 (en) | 2007-06-25 | 2018-01-30 | Microsoft Technology Licensing, Llc | Activation system architecture |
US8578510B2 (en) | 2008-06-26 | 2013-11-05 | Valve Corporation | Anti-piracy measures for a video game using hidden secrets |
US20090328227A1 (en) * | 2008-06-26 | 2009-12-31 | Valve Corporation | Anti-piracy measures for a video game using hidden secrets |
US20100162405A1 (en) * | 2008-12-23 | 2010-06-24 | Valve Corporation | Protecting against polymorphic cheat codes in a video game |
US9317684B2 (en) | 2008-12-23 | 2016-04-19 | Valve Corporation | Protecting against polymorphic cheat codes in a video game |
US10668385B2 (en) | 2008-12-23 | 2020-06-02 | Valve Corporation | Protecting against polymorphic cheat codes in a video game |
US8954732B1 (en) | 2012-06-27 | 2015-02-10 | Juniper Networks, Inc. | Authenticating third-party programs for platforms |
US9256765B2 (en) | 2012-06-29 | 2016-02-09 | Kip Sign P1 Lp | System and method for identifying software changes |
US20170300696A1 (en) * | 2015-01-07 | 2017-10-19 | Huawei Technologies Co., Ltd. | Software verification method and apparatus |
US10796001B2 (en) * | 2015-01-07 | 2020-10-06 | Huawei Technologies Co., Ltd. | Software verification method and apparatus |
US20190080080A1 (en) * | 2017-09-11 | 2019-03-14 | Kabushiki Kaisha Toshiba | Information processing apparatus, information processing method, and computer program product |
US10846394B2 (en) * | 2017-09-11 | 2020-11-24 | Kabushiki Kaisha Toshiba | Information processing apparatus, information processing method, and computer program product |
Also Published As
Publication number | Publication date |
---|---|
US7236958B2 (en) | 2007-06-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7236958B2 (en) | Electronic software license with software product installer identifier | |
EP1469369B1 (en) | Verbose hardware identification for binding a software package to a computer system having tolerance for hardware changes | |
EP1443381B1 (en) | System and method for secure software activation with volume licenses | |
EP1591865B1 (en) | Method and system for limiting software updates | |
EP1455258B1 (en) | Compact hardware identification for binding a software package to a computer system having tolerance for hardware changes | |
CA1292791C (en) | Hardware assist for protecting pc software | |
US7490245B2 (en) | System and method for data processing system planar authentication | |
US6226747B1 (en) | Method for preventing software piracy during installation from a read only storage medium | |
US7644442B2 (en) | Systems and methods for using machine attributes to deter software piracy in an enterprise environment | |
US6243468B1 (en) | Software anti-piracy system that adapts to hardware upgrades | |
US7503072B2 (en) | Hardware ID to prevent software piracy | |
US6067640A (en) | System for management of software employing memory for processing unit with regulatory information, for limiting amount of use and number of backup copies of software | |
MX2007011377A (en) | Secure boot. | |
US20060020810A1 (en) | System and method for software load authentication | |
US7080249B1 (en) | Code integrity verification that includes one or more cycles | |
KR20010044823A (en) | Method and System for Protecting Data Requiring User's Authentication at Computer | |
US20060136746A1 (en) | Security system for preventing unauthorized copying of digital data | |
JP3289656B2 (en) | Program execution control method | |
JP2000207197A (en) | System and method for protecting computer software |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WONG, ERIC;NISHANOVA, ANZHELIKA Y.;REEL/FRAME:011438/0586 Effective date: 20010103 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034541/0001 Effective date: 20141014 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20190626 |