N-tier license distribution

• US 20070043679A1
• Filed: 12/01/2005
• Published: 02/22/2007
• Est. Priority Date: 08/22/2005
• Status: Abandoned Application

• Current Assignee: SafeNet Incorporated (Thales SA)
• Original Assignee: SafeNet Incorporated (Thales SA)
• Inventors: Snyder, Derick, Le, Tu
• Application Number:
  US11/290,463
• Publication Number:
  US 20070043679A1
• Time in Patent Office: Days
• US Class Current: 705/59
• 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

A system and method for the issuance of software licenses through a tiered structure, whereby a software license is issued from a software developer to an end user through one or more intermediate layers of distribution. The system and method for doing so enforces a predefined security policy. In an embodiment of the invention, the security policy is defined by the security developer. The security policy may, for example, address who may use the software package, how many users there may be, an expiration date for use of the software, and/or specific features that may or may not be used by a particular user. The software developer first issues a license template to the next intermediate layer of distribution. This may be a software distributor, who then specifies one or more restrictions on the use of the software. This is done be articulating these restrictions in the license template, effectively “filling in” some or all of the template. Any such embellishment of the software license template must be in accordance with the security policy. In the final transaction, a final distributor transmits a completed software license to a user. At no time can an intermediate distributor issue a license or template that is less restrictive than what is dictated by the security policy, or less restrictive than the template given to the distributor.

Claims

1. A license server, comprising:

means for acquiring a license template from a higher level license server;

means for adding constraint information to said license template in accordance with a security policy, to create a modified license template; and

means for outputting said modified license template.

2. The license server of claim 1, further comprising:

means for receiving a request for a license from a user.

3. The license server of claim 1, wherein said modified license template comprises a license.

4. The license server of claim 3, wherein said means for outputting said modified license template comprises means for sending said license to a user.

5. The license server of claim 1, further comprising means for authenticating said modified license template.

6. The license server of claim 5, wherein said means for authenticating comprises a hashing function.

7. The license server of claim 6, wherein said hashing function comprises a secure hashing function.

8. The license server of claim 6, wherein said hashing function receives a hash input comprising a license and a computer fingerprint of a recipient, and produces a corresponding hash output.

9. The license server of claim 6, wherein said hashing function receives a hash input comprising said license template and a computer fingerprint of a recipient, and produces a corresponding hash output.

10. The license server of claim 6, wherein said means for authenticating further comprises a signature function, which signs an output of said hash function and produces a signature.

11. The license server of claim 1, wherein said means for acquiring a license template comprises means for authenticating said license template.

12. The license server of claim 11, wherein said means for authenticating said license template comprises an unsigning function which unsigns a signature that accompanies said license template.

13. The license server of claim 12, wherein said means for authenticating said license template further comprises a hashing function which hashes said license template and a computer fingerprint, and which produces a hash output for comparison with an output of said unsigning function.

14. The license server of claim 13, wherein said hashing function comprises a secure hashing function.

15. A method of conveying an acquired license template to a recipient, comprising the steps of:

(a) verifying authenticity of the acquired license template;

(b) combining the acquired license template with a computer fingerprint (CFP) of the recipient;

(c) hashing the combination resulting from said step (b) to form a hash output;

(d) signing the hash output to form a signature;

(e) appending the signature with the combination of step (b); and

(f) sending the signature and the combination of step (b) to the recipient.

16. The method of claim 15, wherein said step (a) comprises:

(i) unsigning a signature received with the acquired license template;

(ii) hashing the acquired license template; and

(iii) comparing an output of step (i) with an output of step (ii).

17. The method of claim 15, further comprising:

(g) modifying existing constraint information in the acquired license template,

performed after step (a) and before step (b).

18. The method of claim 15, further comprising:

(g) adding constraint information to the acquired license template, performed after step (a) and before step (b).

19. The method of claim 18, wherein

said step (g) comprises adding sufficient constraint information to the acquired license template, so that the acquired license template becomes a license;

and

said step (f) represents sending the signature and the combination of the license and the CFP to the recipient.

20. The method of claim 15, wherein said step (c) comprises securely hashing the combination resulting from said step (b).