Software publisher or distributor configurable software security mechanism

• US 6,044,469 A
• Filed: 08/29/1997
• Issued: 03/28/2000
• Est. Priority Date: 08/29/1997
• Status: Expired due to Term

• Current Assignee: SafeNet Data Security (Israel) Ltd.
• Original Assignee: Preview Software, Inc.
• Inventors: Horstmann, Cay S.
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): BADERMAN, SCOTT T
• Application Number:
  US08/921,272
• Time in Patent Office: 942 Days
• Field of Search: 395/186, 395/187.01, 395/188.01, 395/200.59, 380/4, 705/51, 705/54, 705/57, 705/58, 705/59
• US Class Current: 726/29
• CPC Class Codes: G06Q 99/00 Subject matter not provided for in other groups of this subclass

Abstract

The present invention, generally speaking, provides a software protection mechanism that may be conveniently configured by a software publisher and applied to a software product. Various predefined software protection measures are presented to the software publisher, who selects which protection measures, if any, the software publisher wishes to apply to a software product. The software publisher may select all of the software protection measures, none of the software protection measures, or any logically consistent combination thereof. An option is also provided for the software publisher to provide code implementing a custom software protection mechanism. The software publisher'"'"'s selections are saved in a license file that is attached to the software product. A Protector Module is also attached to the software product. The Protector Module includes code for each predefined software protection option. When an attempt is made to run the software product, the Protector Module reads the license file and executes code for each software protection option that has been selected. If the software-publisher-defined option is selected, the Protector Module causes publisher-provided software protection code to be executed. The publisher-provided code may be added as part of the license file, for example, or as a separate dynamically loadable code module. The resulting software protection mechanism provides the software publisher complete control over the trade-off between security and user convenience.

Claims

1. A method of protecting against unauthorized use of a software product, comprising the steps of:

a software publisher or distributor, using a software wrapping tool, adding Protector code to the software product and selecting from among a plurality of protection options whereby selection is made from among varying machine-determinable conditions under which the Protector code allows the software product to be used, the Protector code including code for implementing a plurality of predefined protection options;

recording protection options selections of the software publisher or distributor and attaching a resulting record to the software product in a tamper-resistant way;

distributing the software product with the Protector code added; and

when an attempt to access the software product is made, the Protector code reading recorded selections of the software publisher or distributor and executing code corresponding to selected protection options, if any.

2. The method of claim 1, comprising the further step of providing license information, including license conditions, accessible to the Protector code, the Protector code measuring a program user'"'"'s conformance to the license conditions and recording conformance data.

3. The method of claim 2, wherein in accordance with one of said predefined protection options information related to said conformance data is stored obscurely on a user'"'"'s machine to effect a binding.

4. The method of claim 2, wherein in accordance with one of said predefined protection options an executable portion of said software product is marked, binding it to said conformance data.

5. The method of claim 2, wherein in accordance with one of said predefined protection options information describing a computer hardware environment is recorded along with said conformance data.

6. The method of claim 5, wherein an attempt to access the software product causes code to be executed that checks correspondence of a current computer hardware environment and said information describing said computer hardware environment.

7. The method of claim 6, wherein only substantial correspondence, not exact correspondence, is required in order for access to the software product to be allowed.

8. The method of claim 1, wherein in accordance with a particular protection option the software publisher or distributor supplies code to be executed by the Protector code, in addition to any other predefined protection options selected by the software publisher or distributor.

9. The method of claim 1, wherein the software publisher or distributor specifies different protection options selections for different geographic locales and, when an attempt to access the software product is made, the Protector code ascertains locality information and executes code corresponding to selected protection options, if any, for the current geographic locale.