Account management in a system and method for providing code signing services

• US 20070074033A1
• Filed: 09/29/2005
• Published: 03/29/2007
• Est. Priority Date: 09/29/2005
• Status: Abandoned Application

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Adams, Neil, Little, Herbert, Tapuska, David, Kirkup, Michael, Rybak, Michael
• Application Number:
  US11/237,726
• Publication Number:
  US 20070074033A1
• Time in Patent Office: Days
• US Class Current: 713/176
• CPC Class Codes: G06F 21/629 to features or functions of an application
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/80 Wireless network architectures or network communication protocols for wireless network security H04W12/00
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

A system and method for providing code signing services to software application developers or to other individuals or entities that wish to have applications digitally signed. Signing of the applications may be required in order to enable the applications to access sensitive APIs and associated resources of a computing device when the applications are executed on the computing device. In one embodiment, a method of providing code signing services will comprise at least some steps relating to registering the entities that seek access to sensitive APIs as controlled by the code signing authority, and managing the accounts of the registered entities.

Claims

1. A method for providing code signing services, the method comprising the steps of:

a) creating at least one public key and at least one corresponding private key;

b) deploying each public key to protect at least one sensitive API and storing each corresponding private key;

c) registering at least one entity for code signing services, wherein the identity of each entity is authenticated, and wherein an account record for each registered entity is created;

d) receiving a code signing request from a requester, said requestor being an entity registered at the registering step, wherein the code signing request comprises an object that the requester is requesting to have signed with a select private key of said at least one private key created;

e) digitally signing the object, wherein a digital signature is generated using said select private key; and

f) transmitting said digital signature to said requestor;

wherein the method further comprises the step of providing a user interface, wherein said user interface is adapted to receive input from a user, wherein said input is used to populate the account record of one or more registered entities.

2. The method of claim 1, wherein the input includes e-mail notification settings, and wherein the method further comprises the step of sending an e-mail notification when said registering step is performed, if required by said e-mail notification settings.

3. The method of claim 1, wherein the input includes e-mail notification settings, and wherein the method further comprises the step of sending an e-mail notification when said code signing request is received, if required by said e-mail notification settings.

4. The method of claim 1, wherein the input includes e-mail notification settings, and wherein the method further comprises the step of sending an e-mail notification upon the occurrence of at least one of an error and irregular behavior, if required by said e-mail notification settings.

5. The method of claim 1, wherein the input includes an expiry date, and wherein the object is digitally signed at the signing step only if the expiry date has not passed.

6. The method of claim 1, wherein the input includes a number of allowable signing requests, wherein the object is digitally signed at the signing step only if the number of allowable signing requests indicates that there are allowable signing requests remaining, and wherein the method further comprises the step of updating the number of allowable signing requests after the signing step is performed.

7. The method of claim 1, wherein each of said at least one entity is a software application developer.

8. The method of claim 7, wherein the object is a software application.

9. The method of claim 7, wherein the object is a hash of a software application, said hash generated by the requestor using a hashing algorithm.

10. The method of claim 1, wherein the registering step comprises validating credit card information associated with each entity to authenticate the identity of the respective entity.

11. The method of claim 1, wherein the code signing request received from the requestor further comprises a second digital signature, the second digital signature associated with the requestor, and wherein the method further comprises a step of verifying the second digital signature before the signing and transmitting steps are performed.

12. The method of claim 1, wherein a random data service provides random data used to create the at least one public key and the at least one corresponding private key at the creating step, and wherein the method comprises the steps of determining the randomness quality of the random data, and displaying an indicator of the randomness quality to a user prior to completion of the creating step.

13. The method of claim 1, further comprising the step of tracking registration attempts made against an account associated with the account record, and disabling the account if the registration attempts exceed a pre-defined number.

14. A computer-readable medium comprising instructions for performing the steps of the method as claimed in claim 1, wherein said instructions are executable on a computing device.

15. A system for providing code signing services, comprising a private key store for storing a plurality of private keys, a client information database for storing a plurality of account records, and a code signing authority application which, when executed on a computing device, performs the steps of the method as claimed in claim 1.

16. The system of claim 15, further comprising a user interface for receiving input from a user to facilitate management of said account records.