Method for prompting a user to install and execute an unauthenticated computer application

Abstract

The present invention prompts a user to accept, install and execute unauthenticated computer applications. When the user accepts the application, information relating to the application files may be added to a prompt exclusion list (PEL). In this way, further downloads or execution of the same applications may be performed without prompting the user. The integrity of the application is checked before it is run. If the integrity does not match the stored integrity, the application is terminated. A revocation list is maintained that denies any applications on the revocation list from executing even if they contain signed certificates and are from trusted sources.

Description

FIELD OF THE INVENTION

[0002] The present invention relates generally to software, and more particularly authentication of software.

BACKGROUND OF THE INVENTION

[0003] In today's computing age, mobile devices are achieving widespread use and great sophistication. In many instances, mobile devices can install and execute software applications that are much more advanced than in even recent years past. Many times, those software applications are installed while the mobile device is connected to a land-line network. However, today's technology even allows software applications to be downloaded over-the-air to some wireless mobile devices.

[0004] Wireless transmissions are at a higher risk of being intercepted or otherwise interfered with than their land-line counterparts. Accordingly, the industry is evolving ways to ensure the integrity of downloaded applications to prevent malicious code from being interjected into the transmission. One way in which to ensure the integrity of a download is by using digital certificates and signatures. These mechanisms enable a mobile device to determine that a package downloaded over-the-air (or otherwise) is actually the same package that was created by a trusted source. The digital certificates authenticate that the sender is a trusted source, and the digital signatures authenticate that the package has not been tampered with since being transmitted. Both are commonly used in security schemes.

[0005] Users often take advantage of the security provided by digital certificates and signatures. In many cases, however, these mechanisms are either not available or not necessary. Enforcing digital certificates and/or signatures helps to ensure security but at the sacrifice of not being able to install some applications. Not enforcing digital certificates and/or signatures enables the user to install applications, but at the risk of potentially malicious applications being loaded. An adequate solution to this dilemma has eluded those skilled in the art.

SUMMARY OF THE INVENTION

[0006] The present invention is directed at prompting a user to accept, install and execute unauthenticated computer applications. Briefly stated, before the application is installed or executed, the user is prompted with a dialog to the effect of: “The application is not signed, are you sure you want to run it?” If the user chooses “Yes” the application is run despite the fact that the file is unsigned.

[0007] According to one aspect of the invention, when the user accepts the file, information relating to the file may be added to a prompt exclusion list (PEL). In this way, further downloads or execution of the same files may be performed without prompting the user.

[0008] According to another aspect of the invention, the application is hashed to create a unique representation of the application.

[0009] According to yet another aspect of the invention, a revocation list is maintained that denies any files listed on the revocation list from executing even if they contain digital signatures.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG. 1 illustrates an exemplary mobile computing device;

[0011] FIG. 2 is a functional block diagram generally illustrating an authentication system;

[0012] FIG. 3 is a flow chart that generally illustrates a process for installing an application from a received package file; and

[0013] FIG. 4 is a flow chart that generally illustrates a process for executing an installed file of application, in accordance with aspects of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0014] The present invention is directed at prompting a user to accept, install and execute unauthenticated computer applications. Briefly stated, before the application is installed or executed, the user is prompted with a dialog to the effect of: “The application is not signed, are you sure you want to run it?” If the user chooses “Yes” the application is run despite the fact that the file is unsigned. When the user accepts the file, information relating to the file may be added to a prompt exclusion list (PEL). In this way, further downloads or execution of the same files may be performed without prompting the user. A revocation list may also be maintained that denies any files listed on the revocation list from executing even if they contain signed certificates.

[0015] FIG. 1 illustrates a mobile computing device that may be used in one exemplary embodiment of the present invention. Mobile computing device 100 includes processor 160, memory 162, display 128, keypad 13, audio interface 174, wireless interface 172, and power supply 170. Memory 162 generally includes both volatile memory (e.g., RAM) and non-volatile memory (e.g., ROM, Flash Memory, or the like). As illustrated, mobile computing device 100 includes operating system 164, such as the Windows CE operating system from Microsoft Corporation or other operating system, which is resident in memory 162 and executes on processor 160. Keypad 132 may be a push button numeric dialing pad (such as on a typical telephone), a multi-key keyboard (such as a conventional keyboard), or some other input device. Display 128 may be a liquid crystal display, or any other type of display commonly used in mobile computing devices. Display 128 may be touch-sensitive, and would then also act as an input device.

[0016] One or more application programs 166 are loaded into memory 162 and run on operating system 164. Examples of application programs include phone dialer programs, email programs, scheduling programs, PIM (personal information management) programs, word processing programs, spreadsheet programs, Internet browser programs, and so forth. Mobile computing device 100 also includes non-volatile storage 168 within memory 162. Non-volatile storage 168 may be used to store persistent information which should not be lost if mobile computing device 100 is powered down. Applications 166 may use and store information in storage 168, such as e-mail or other messages used by an e-mail application, contact information used by a PIM, appointment information used by a scheduling program, documents used by a word processing application, and the like. An authentication application also resides on mobile computing device 100 and is programmed for authentication of applications that may be signed or unsigned.

[0017] Mobile computing device 100 includes power supply 170, which may be implemented as one or more batteries. Power supply 170 might further include an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the batteries.

[0018] Mobile computing device 100 is shown with audio interface 174 that may be directly coupled to power supply 170 so that when activated, it remains on for a duration dictated by the notification mechanism even though processor 160 and other components might shut down to conserve battery power. Audio interface 174 is used to provide audible signals to and receive audible signals from the user. For example, audio interface 174 may be coupled to a speaker for providing audible output and to a microphone for receiving audible input, such as to facilitate a telephone conversation.

[0019] Mobile computing device 100 also includes wireless interface 172 that performs the function of transmitting and receiving communications, such as radio frequency communications. Wireless interface layer 172 facilitates wireless connectivity between mobile computing device 100 and other nodes, via a communications carrier or service provider. Transmissions to and from wireless interface layer 172 may be conducted under control of operating system 164. In other words, communications received by wireless interface 172 may be disseminated to application programs 166 via operating system 164, and vice versa.

[0020] FIG. 2 is a functional block diagram generally illustrating an authentication system, in accordance with aspects of the present invention. Authentication system 200 is configured to determine when to install or execute files (applications) on a mobile device. In the embodiment illustrated, authentication system 200 is resident on a mobile device, such as mobile device 100 illustrated in FIG. 1.

[0021] A general description of authentication system will now be provided. Generally, when an action (installing the application or executing the application) associated with an application is requested, the authentication system determines if the action should be executed. Determining when to execute the action depends on many different items. For example, a Security Policy may be used to determine which of the authentication actions are taken and/or required. According to one embodiment of the invention, when the application is stored on revocation list 245, the action requested is not allowed and the application is terminated.

[0022] When the application is not on file revocation list 245, the certificates associated with the application are inspected. If the certificate associated with the application is in certificate store 275 then the file is executed without prompting the user. If the certificate hash is on the revoked list, execution of the file fails. According to one embodiment, the chain of certificates is walked completely. If any one of the certificates is revoked, execution fails.

[0023] The chain of certificates in the signature may also be checked against the Privileged Store and the Unprivileged Store. If a match is found in Privileged Store, the Secure Loader executes the application in Privileged Mode. If a match is not encountered in the Privileged Store, the signature is compared against the Unprivileged Store. (See FIG. 4 and related discussion).

[0024] If a match is found in Unprivileged Store, the Secure Loader executes the application in Unprivileged Mode. If the Unprivileged Store is empty or a match is not encountered, the application is treated as unsigned, and the user may be prompted.

[0025] When the certificate is not in certificate store 275, a prompt exclusion list (PEL) is checked to determine if the application has previously been approved. If so, the application is executed and no prompt is given to the user. If the application has not already been approved, the authentication system prompts the user to determine if the unauthenticated application should be executed. When the response to the prompt is “yes” then the application is executed (i.e. the application is installed or run). When the application is executed, the application is added to the PEL such that later action requests involving the application that have already been approved do not invoke a prompt.

[0026] According to one embodiment of the invention, the PEL is an ordered list of hashes of CABs and executables that is stored in the registry of the mobile device. The PEL is referenced each time an unsigned CAB or application is run when the appropriate security policies are enabled. The appropriate security policies may consist of turning on or off flags relating to the authentication system. If a hash of the CAB or executable already exists in the PEL, the user is not prompted. According to one embodiment, the hashes are computed with the SHA1 algorithm.

[0027] Given the relatively small lifetime size of this list of hashes, it is not necessary that the PEL is automatically trimmed or cleared at some particular time. Instead, the PEL may be maintained for the lifetime of the device. According to one embodiment, each application has one hash for the CAB plus one hash for each executable. Assume a maximum of average of five (5) total hashes per CAB. Each hash consumes 20 bytes meaning each application only uses 100 bytes. If space is needed, however, the PEL may be cleared or trimmed accordingly.

[0028] Examples relating to the installation or execution of application 1 (205), application 2 (225), and application 3 (235) will now be provided. The discussion will first look at exemplary application 1 (205). As illustrated, application 1 includes Certificate A (210) that references parent certificate C (215). As certificate C (215) is included in certificate store 275, and is not included in revocation list 245 (i.e. a trusted application), application 1 is allowed to run (install or execute) without first prompting the user to determine if the application should be trusted.

[0029] Turning now to application 2 it can be seen that application 2 includes certificate B. Application 2, however, is listed in revocation list 245 indicating that the application is not to be trusted. According to one embodiment, even if certificate B was included in certificate store 275, application 2 would not be allowed to run. As discussed above, applications listed in the revocation list are applications that can not be trusted.

[0030] Application 3 does not include a signed certificate, is not on the revocation list, and is not included in the PEL. As such, a prompt is provided to the user asking whether application 3 should be trusted (“accepted”). If the user responds no, the application is not executed. According to one embodiment, application 3 may also be added to the revocation list. If the user responds yes, the application is run and the application is added to the PEL such that the user will not be prompted in the future regarding running this application. Application 3, although unsigned, becomes a trusted application on the device.

[0031] Assume that application 4 is a CAB file that is signed, but some of its contents are not, then the user has not been prompted to accept the unsigned material, since the CAB itself was signed. For example, an unsigned DLL or EXE is referenced by application 4. When this situation is detected, authentication application 200 stops and prompts the user to determine whether or not to continue with application 4. If the user accepts the application, the application continues and the previously unaccepted material becomes accepted and part of the PEL. If the user rejects the application, the installation is canceled and all changes are rolled back. In the case where the CAB is not signed and the contents are not signed then the user is prompted once for the CAB. When the CAB is accepted the contents are also accepted. This saves the user from encountering two different prompts regarding the CAB and the contents.

[0032] As illustrated, application 5 is signed with a certificate (Certificate E), but Certificate E is not in the certificate store. In this case, application 5 is treated as unsigned and the user gets a prompt as to whether to accept or not.

[0033] FIGU RE 3 is a flow chart that generally illustrates a process for installing an application from a received package file, in accordance with aspects of the invention.

[0034] At step 302, a request is made to install a received package file, such as a cab file, or the like. At decision block 305, a hash of the file (signed or unsigned) is checked against a revocation list. If the hash of the file is on the revocation list the installation fails and moves to an end block and terminates. If the hash is not in the revocation list, the process flows to decision block 315 where a determination is made as to whether the file is signed with a certificate that is recognized by the device as valid, such as by digital signature and/or certificate. If not, the process continues to decision block 320. If the file is self-authenticating, the process continues to decision block 360.

[0035] At decision block 320, a determination is made whether unsigned files are allowed to run on the device. If not, installation fails and moves to an end block where the process terminates. If unsigned files are allowed, the process continues to decision block 325.

[0036] At decision block 325, a determination is made as to whether the user should be prompted to accept file installation despite the fact that the file is not self-authenticated. According to one embodiment, this determination may be made by checking a security setting indicating whether or not to prompt. If prompting is disabled, the file is installed at block 330 in accordance with local policy. If user prompting is enabled, however the process continues decision block 335.

[0037] At decision block 335, a determination is made whether the hash of the file is on a Prompt Exclusion List (PEL). If the file is on the PEL then the user has previously accepted the file and the file is installed at block 330 without prompting the user. If the file is not on the PEL, then, at block 340, the user is prompted to accept the unsigned file. At decision block 345, a determination is made whether the user accepted the unsigned file. If the user rejects the unsigned file, installation fails and moves to an end block. If the user accepts the unsigned file, the hash of the file and any unsigned executables associated with the application are added to the PEL at block 355. The process then moves to block 330 where the file is installed.

[0038] Returning to decision block 315, if the file is self-authenticating, the process continues to decision block 360 where the validity of the signature is verified. If the signature is not valid, installation fails and moves to an end block. If the signature is valid, the process moves to decision block 365 where the file's integrity is checked. According to one embodiment, the file integrity is checked in the following manner. The hash of the file is computed, and the hash of the file signed by the private key of the publishing certificate authority is extracted from the signature. The signed hash is decrypted using the public key of the certificate used to sign the file. The two hashes are compared to determine if they are identical. If the hashes are not identical, the file has been tampered with and the process moves to an end block where the installation fails. If the hashes are identical, the file remains intact and the process continues to decision block 370.

[0039] At decision block 370, a determination is made whether the certificate hash is on the security revocation list. If the certificate has been revoked, installation moves to an end block and fails. If the certificate has not been revoked, decision block 375 checks the chain of certificates in the signature against the SPC store. If a match is found, the file is installed at block 330 in accordance with policy. If a match is not found, the process continues to decision block 320, at which the process continues as described above.

[0040] FIG. 4 is a flow chart that generally illustrates a process for executing an installed file of application, in accordance with aspects of the invention. At step 402, a request is made to run an executable file. At decision block 405, a hash of the file (signed or unsigned) is checked against a revocation list. If the hash of the file is on the revocation list, execution fails and moves to an end block. If the hash is not in the revocation list, decision block 415 determines if the file is self-authenticating, such as by digital signature and/or certificate. If not, the process continues to decision block 420. If the file is self-authenticating, the processes continue to decision block 460.

[0041] At decision block 420, a determination is made whether unsigned files are allowed. If not, the execution fails and the process moves to an end block. If unsigned files are allowed, the process continues to decision block 425.

[0042] At decision block 425, a determination is made whether the user should be prompted to accept the execution despite the fact that the file is not authenticated. This determination may be made by checking a setting or the like. If prompting is disabled, the file is executed in unprivileged mode at block 430. However, if user prompting is enabled, the process continues to decision block 435.

[0043] At decision block 435, a determination is made whether the hash of the file is on the PEL. If the hash is on the PEL, the user has previously accepted the file an no prompting is required. Thus, the file is executed in unprivileged mode at block 430 without prompting the user. If the hash is not on the PEL, then, at block 440, the user is prompted to accept the unsigned file. If the user rejects the unsigned file, execution fails and moves to an end block. If the user accepts the unsigned file, the hash of the file is added to the PEL at block 255. The file is then executed in unprivileged mode at block 430.

[0044] Returning to decision block 415, if the file is self-authenticating, the process continues to decision block 460 where the signature's validity is verified. If the signature is not valid, execution fails and moves to an end block. If the signature is valid, the file's integrity is checked at block 465 as described above. If the hashes are different, the file has been tampered with and execution fails and moves to an end block. If the hashes are identical, the file remains intact and the process continues to decision block 470.

[0045] At decision block 470, a determination is made whether the certificate hash is on the security revocation list. If the certificate has been revoked, execution fails and moves to an end block. If the certificate has not been revoked, decision block 475 checks the chain of certificates in the signature against the unprivileged store. If a match is found, the file is executed in unprivileged mode at block 430. If a match is not found in the unprivileged store, then decision block 480 checks if a valid certificate is in the privileged store. If a match of the certificate is found, the file is executed in privileged mode at block 485. If the privileged store is empty or a match is not encountered, the file is treated as an unsigned file and the process returns to decision block 420, at which the process continues as described above.

[0046] The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.

Claims

1. A method for running a file on a mobile device that may be authenticated or unauthenticated, comprising: determining when the file is unauthenticated, and when: determining when to prompt a user to aid in determining when to accept the file; and determining whether the application is accepted; and when: running the file.

2. The method of claim 1, further comprising determining when the file is on a revocation list, and when the file is on the revocation list terminating the file.

3. The method of claim 2, further comprising determining when the file is self-authenticating.

4. The method of claim 2, wherein determining when to prompt the user further comprises checking a prompt exclusion list (PEL).

5. The method of claim 4, wherein the user is prompted when the unauthenticated file is not included in the PEL.

6. The method of claim 4, wherein the PEL includes information relating to unauthenticated files that have been accepted by a user.

7. The method of claim 5, further comprising determining when the user has accepted the file based on the prompt and adding the file to the PEL.

8. The method of claim 7, wherein adding the file to the PEL, further comprises creating a hash of the file.

9. The method of claim 2, further comprising checking an integrity of the file.

10. The method of claim 9, wherein checking the integrity of the file further comprises comparing a hash of the file with a stored hash.

11. A computer readable medium for performing an action associated with a file on a mobile device, comprising: determining when to prompt a user to aid in determining when to accept the file; and when determined: prompting a user to accept the file; determining a response to the prompt: and determining whether the application is accepted; and when: performing the action, otherwise terminating the action.

12. The computer readable medium of claim 11, further comprising determining when the file is on a revocation list, and when the file is on the revocation list terminating the action.

13. The computer readable medium of claim 12, wherein determining when to prompt the user further comprises checking a prompt exclusion list (PEL).

14. The computer readable medium of claim 13, wherein the PEL includes files that have been accepted by the user

15. The computer readable medium of claim 13, wherein the file is hashed and added to the PEL when accepted.

16. The computer readable medium of claim 11, further comprising checking an integrity of the file.

17. The computer readable medium of claim 16, wherein checking the integrity of the file further comprises comparing a hash of the file with a stored hash.

18. An apparatus for performing an action associated with a file, comprising: a processor and a computer-readable medium; an operating environment stored on the computer-readable medium and executing on the processor; a wireless interface layer operating under the control of the operating environment and configured to connect with another device; and an authentication device operating under the control of the operating environment and operative to perform actions, including: determining when to prompt a user to aid in determining when to accept the file; and when determined: prompting a user to accept the file; determining a response to the prompt: and determining whether the application is accepted based on the response; and when the prompt indicates to accept the file: performing the action, otherwise terminating the action.

19. The apparatus of claim 18, further comprising determining when the file is on a revocation list, and when the file is on the revocation list terminating the action.

20. The apparatus of claim 19, wherein determining when to prompt the user further comprises checking a prompt exclusion list (PEL).

21. The apparatus of claim 20, wherein the PEL includes files that have been accepted by the user

22. The apparatus of claim 20, wherein the file is hashed and added to the PEL when accepted.

23. The apparatus of claim 21, further comprising checking an integrity of the file.

24. The apparatus of claim 23, wherein checking the integrity of the file further comprises comparing a hash of the file with a stored hash.