TECHNIQUES FOR DELIVERING THIRD PARTY UPDATES

• US 20090288071A1
• Filed: 05/13/2008
• Published: 11/19/2009
• Est. Priority Date: 05/13/2008
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Ekeji, Chika P., Walsh, Michael E. JR., Seidman, David L.
• Application Number:
  US12/119,501
• Publication Number:
  US 20090288071A1
• Time in Patent Office: Days
• US Class Current: 717/126
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

Various technologies and techniques are disclosed for receiving and distributing updates for third party customers to end users. Input is received from a customer to login to a software update system. A software update is received from the customer. Metadata describing the software update is received from the customer. The software update is optionally validated to confirm that the software update can be trusted by end users who have a software program that could be updated with the software update. The software update is made available to update systems running on computers of end users after receiving the customer consent to the release of the software update.

Claims

1. A method for receiving and validating updates from third party customers for later distribution to end users comprising the steps of:

receiving input from a customer to login to a software update system;

receiving a software update from the customer;

receiving metadata describing the software update from the customer; and

validating the software update to confirm that the software update can be trusted by end users who have a software program that could be updated with the software update.

2. The method of claim 1, further comprising the steps of:

receiving detection information from the customer that specifies how to determine if the software update applies to a given end user.

3. The method of claim 1, further comprising the steps of:

storing the software update in the software update system for access by an update system that runs on respective computers of the end users.

4. The method of claim 1, wherein the validating step comprises the steps of:

performing virus scanning on the software update to ensure that the software update does not contain a virus.

5. The method of claim 1, wherein the validating step comprises the steps of:

performing digital signature verification on the software update to ensure that an entity represented by the customer who is uploading the software update matches an entity assigned to a digital signature present on the software update.

6. The method of claim 1, wherein the validating step comprises the steps of:

performing metadata verification to confirm that metadata contained in the software update matches metadata entered by the customer into the software update system.

7. The method of claim 1, wherein the validating step comprises the steps of:

performing a basic detection validation that comprises the steps of;

installing the software program;

verifying that the software update is offered and installs; and

verifying that the software update is no longer offered.

8. The method of claim 7, wherein the basic detection validation step further comprises the steps of:

if an uninstall option is available, uninstalling the software update and verifying that the software update is offered again.

9. The method of claim 1, wherein the validating step comprises the steps of:

determining if the software update affects a correct set of files as indicated by the metadata entered by the customer into the software update system.

10. The method of claim 1, wherein the validating step comprises the steps of:

determining if the software program loads after the software update is installed.

11. The method of claim 1, wherein the validating step comprises the steps of:

performing virus scanning on the software update to ensure that the software update does not contain a virus;

performing digital signature verification on the software update to ensure that an entity represented by the customer who is uploading the software update matches an entity assigned to a digital signature present on the software update; and

performing metadata verification to confirm that metadata contained in the software update matches metadata entered by the customer into the software update system.

12. The method of claim 1, further comprising the steps of:

providing a test system to enable the customer to test and approve the software update before the software update is made available to end users.

13. A method for enabling customer verification of software updates before the software updates are made available to end users comprising the steps of:

enabling a customer to access a test system for testing a software update that was previously submitted by the customer for distribution to end user computers through a centralized update system;

if the customer approves the software update after testing the software update, receiving consent from the customer to publish the software update to make the software update available to an update system that runs on the end user computers; and

if the customer does not approve the software update after testing the software update, then not making the software update available to an update system that runs on the end user computers.

14. The method of claim 13, wherein the testing system contains software updates from a plurality of different customers.

15. The method of claim 14, wherein the testing system only allows the customer to view software updates that were submitted by the customer, and to not allow the customer to view software updates that were submitted by other customers.

16. The method of claim 13, wherein the testing system contains software updates that were submitted by the customer, but not software updates that were submitted by other customers.

17. The method of claim 16, wherein a separate testing system is created for software updates that were submitted by other customers.

18. A computer-readable medium having computer-executable instructions for causing a computer to perform steps comprising:

receiving input from a customer to login to a software update system;

receiving a software update from the customer;

receiving metadata describing the software update from the customer; and

making the software update available to update systems running on computers of end users after receiving verification that the customer has consented to the release of the software update.

19. The computer-readable medium of claim 18, further having computer-executable instructions for causing a computer to perform steps comprising:

prior to making the software update available to update systems running on computers of end users, first validating the software update to confirm that the software update can be trusted by end users who have a software program that could be updated with the software update; and

receiving verification that the customer has consented to the release by publishing the software update to a test system to enable the customer to test the software update and provide consent to the release before distribution to end users.

20. The computer-readable medium of claim 19, wherein the validating step is operable to perform steps comprising:

performing digital signature verification on the software update to ensure that an entity represented by the customer who is uploading the software update matches an entity assigned to a digital signature present on the software update;

performing virus scanning on the software update to ensure that the software update does not contain a virus; and

performing metadata verification to confirm that metadata contained in the software update matches metadata entered by the customer into the software update system.