Differentiated Installable Packages

• US 20070261047A1
• Filed: 09/06/2006
• Published: 11/08/2007
• Est. Priority Date: 05/03/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sah, Maneesh, Nell, Garett Richard
• Granted Patent: US 8,578,363 B2
• Time in Patent Office: Days
• US Class Current: 717/168
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A code fix is communicated using an automatically executable code patch that has an additional code element that allows the code to perform the functions of registration, detection, setup, reporting, tracking, policy verification or clean up.

Claims

1. A method of distributing fixes to a software application comprising

creating a source code change to fix the software application;

compiling the source code change into a patch file to be communicated;

creating a specialized mechanism that includes additional executable code that is not a component of an installer or a binary payload containing the source code change;

creating a signed “

for testing”

package to be distributed where the package comprises;

executable installer code that is automatically deployed;

the patch file; and

the specialized mechanism.

2. The method according to claim 1, wherein the specialized mechanism performs at least one selected from a group comprising:

registering the patch file;

detecting whether a receiving computer can accept the package by;

reviewing the receiving computer on which it is to be installed,

determining whether changes need to be made to the receiving computer such that the executable installer code will operate properly or

asks the computer for permission to run the executable installer code;

setting up by assisting in setting up the receiving computer or with installing the patch file;

reporting by communicating reports back to one selected from a group comprising;

a remote computer,

the patch creator, or

a local user on the receiving computer

data about one selected from a group comprising;

state changes,

uninstallation requirements, or

patch installation success or failure;

tracking by communicating tracking data on at least one of;

size of the patch file,

content of the patch file,

patch file deployment time,

subcomponents of the patch file deployment time,

whether a system restart was required,

user credential used when the patch file was installed,

a change in a number of software applications or services on the computer,

system hardware or capabilities now able to be detected after patch payload deployed,

changes in system condition,

a number of patch file installations, and

any problems with the patch files;

verifying policy by ensuring that the patch file conforms to system or administrative policies or

cleaning up by assisting with returning the receiving computer to a functional state.

3. The method according to claim 2, wherein the system or administrative policies comprise:

the patch file is digitally signed and not a malicious patch,

the receiving system is permitted to install the patch file, and

a user is not authenticated to deploy patches or this particular patch.

4. The method according to claim 2, further comprising using the specialized mechanism to check with a host to confirm whether or not installation of the patch file is permitted.

5. The method according to claim 2, further comprising using the specialized mechanism to report that the patch file has been installed to another host on a network.

6. The method of claim 2, further comprising displaying at the receiving computer an indication that the source code change is a testing package.

7. The method of claim 6, wherein the indication comprises one of:

a visual indication on a display;

an audible alert;

or

an visible indication on a keyboard or mouse when associated with the computer.

8. The method according to claim 1, whereby the specialized mechanism is added to existing patches.

9. The method according to claim 1, whereby specialized mechanisms are treated as trusted operations by the operating system without compromising machine security.

10. The method according to claim 1, whereby the patch file can be designated as one of “

for testing”

or “

for evaluation” and

a level of trust is different for patch files designated “

for testing” and

patch files designated “

for evaluation.”

11. The method of claim 1, further comprising the specialized mechanism looking to other computers for sufficient permission to run the installer.

12. A self extracting computer executable file for providing a fix to a computer application comprising:

a package installer;

a wrapper to the package installer;

a certificate management utility;

a detection algorithm for finding patch content with the appropriate title;

a signing mechanism that can assign authority different from official patches;

a “

do not remove”

key;

a mechanism for enforcing a limited installation window; and

a name to differentiate the package from other fixes and indicate a level of trust.

13. The file of claim 12, wherein the certificate management utility performs at least one function selected from the group comprising:

registration of the patch content,

detection, wherein detection further comprises reviewing a receiving computer on which it is to be installed, determining whether changes need to be made to the receiving computer such that the installer will operate properly or asks the receiving computer for permission to run the installer;

setup, wherein setup further comprises assisting in setting up the receiving computer or with installing the patch content;

reporting, wherein reporting reports back to one selected from a group comprising;

a remote computer,

a patch creator, or

a local user on the receiving computer

on one selected from a group comprising;

the patch content installation,

state change required,

uninstallation required or

whether patch content was installed successfully;

tracking, wherein tracking may report back tracking data on at least one of;

the size of the patch content,

the content of the patch,

the patch content deployment time,

subcomponents of the patch content deployment time,

whether a system restart was required,

a user credential used when the patch content was installed,

a change in the number of software applications or services on the receiving computer,

changes in system condition,

a number of patch file installations,

the number of patch content installations, and

any problems with the patch content;

policy verification wherein policy verification further comprises ensuring that the patch content conforms to system or administrative policies, or

clean up, wherein clean up assists with returning the receiving computer to a functional state.

14. The file of claim 13, wherein the system or administrative policies comprise:

the patch content is digitally signed and not malicious patch content,

the receiving system is permitted to install a patch, and

the user at the receiving system is not authenticated to deploy patch content or this particular patch content.

15. The file of claim 12, wherein the do not remove key ensures that the removal of one fix does not disable other fixes.

16. The file of claim 12, wherein the name allows the file to be located by the detection algorithm.

17. The file of claim 12, wherein the certificate management utility reports that a patch/fix has been installed to another host on a network.

18. The file of claim 12, wherein the certificate management utility displays at the receiving station an indication that the source code change is a testing package.

19. The file of claim 12, wherein the indication comprises one of:

a visual indication on a display;

an audible alert;

or

a visible indication on the keyboard or mouse when associated with the receiving computer.

20. A tangible computer readable medium comprising computer executable code for distributing fixes to a software application comprising:

creating a source code change to fix the software application;

compiling the source code into a patch file to be communicated;

creating a specialized mechanism that includes additional executable code that is not a component of an installer or the binary payload containing the source code fix;

creating a signed “

for testing”

package to be distributed where the package comprises;

executable installer code that is automatically deployed;

the patch file; and

the specialized mechanism.