Software distribution system

• US 20020174422A1
• Filed: 09/26/2001
• Published: 11/21/2002
• Est. Priority Date: 09/28/2000
• Status: Abandoned Application

• Current Assignee: Regents of the University of California (University of California)
• Original Assignee: Regents of the University of California (University of California)
• Inventors: Elko, Scott D., Dobbs, Lauri A., Kelley, Marcey L., Bartoletti, Tony
• Application Number:
  US09/964,029
• Publication Number:
  US 20020174422A1
• Time in Patent Office: Days
• US Class Current: 717/178
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A system to securely install software upgrades and patches includes determining which software upgrades and patches should be applied, collecting the software upgrades and patches from vendors by downloading them from the vendor'"'"'s ftp sites, and installing the software upgrades and patches. Embodiments of the system include interpreting how much memory and disk space is needed to install the software upgrades; interpreting the operating system type, version and architecture the software upgrades apply to; interpreting dependencies on other layered products; interpreting dependencies on other upgrades or patches, interpreting which files and directories will be affected by the installation of the software upgrades; backing out software upgrades and patches.

Claims

1. A computer-implemented method of secure installation of vendor'"'"'s software patches on client'"'"'s systems, comprising the steps of:

determining which of said software patches should be applied to said client'"'"'s systems

collecting said software patches from said vendors by downloading them from said vendor'"'"'s ftp sites

distributing said software patches to said client'"'"'s systems

installing said software patches

2. The computer-implemented method of secure installation of vendor'"'"'s software patches on client'"'"'s systems of claim 1, include steps of:

determining which software patches should be applied to said client'"'"'s systems

collecting said software patches from said vendors by downloading them from said vendor'"'"'s ftp sites

distributing said software patches to said client'"'"'s systems

Interpreting which files will be affected by the installation of said software patches

interpreting which directories will be affected by the installation of said software patches

installing said software patches

3. The computer-implemented method of secure installation of vendor'"'"'s software patches on client'"'"'s systems of claim 1, include steps of:

determining which software patches should be applied to said client'"'"'s systems

collecting said software patches from said vendors by downloading them from said vendor'"'"'s ftp site

distributing said software patches to said client'"'"'s systems

interpreting which files and directories will be affected by the installation of said software patches

interpreting how much memory and disk space is needed to install software upgrades and installing said software patches

4. The computer-implemented method of secure installation of vendor'"'"'s software patches on client'"'"'s systems of claim 1, include steps of:

determining which software patches should be applied to said client'"'"'s systems

collecting said software patches from said vendors by downloading them from said vendor'"'"'s ftp sites

distributing said software patches to paid client'"'"'s systems

interpreting the operating system type, version and architecture said software patches apply to

interpreting which files and directories will be affected by the installation of said software patches

interpreting how much memory and disk space is needed to install said software patches

interpreting dependencies on other layered products

installing said software patches

5. The computer-implemented method of secure installation of vendor'"'"'s software patches on client'"'"'s systems of claim 1, include steps of:

determining which software patches should be or should have been applied to said client'"'"'s systems

collecting said software patches from said vendors by downloading them from said vendor'"'"'s ftp sites

distributing said software patches to said client'"'"'s systems

interpreting the operating system type, version and architecture said software patches apply to

interpreting which files and directories are affected by the installation of said software patches

interpreting how much memory and disk space is needed to install said software patches

interpreting dependencies on other layered products

installing said software patches

backing-out said software patches that have been applied to said client'"'"'s systems

6. A computer-implemented method of secure distribution of vendor'"'"'s upgrades and patches to client'"'"'s systems, comprising:

determining which of vendor'"'"'s upgrades and patches have been applied to client'"'"'s systems

determining which said software upgrades and patches should be or should have been applied to said clients systems

7. The computer-implemented method of secure distribution of vendor'"'"'s upgrades and patches of claim 6, include:

collection of said patches and upgrades from said vendor'"'"'s and downloading said patches and upgrades to client systems

8. The computer-implemented method of secure distribution of vendor'"'"'s upgrades and patches of claim 7, include the step of:

interpreting the operating system type

9. The computer-implemented method of secure distribution of vendor'"'"'s upgrades and patches of claim 7, include the step of:

interpreting the operating system version

10. The computer-implemented method of secure distribution of vendor'"'"'s upgrades and patches of claim 7, include the step of:

interpreting the operating system architecture the patch applies to

11. The computer-implemented method of secure distribution of vendor'"'"'s upgrades and patches of claim 7, include the step of:

determining how much memory is needed to install said patch and upgrades

12. The computer-implemented method of secure distribution of vendor'"'"'s upgrades and patches of claim 7, include the step of:

determining how dependencies on other layered products affect the installation of said patches and upgrades

13. The computer-implemented method of secure distribution of vendor'"'"'s upgrades and patches of claim 7, include the step of:

determining how dependencies on other patches, or software upgrades affect the installation of a patch

14. The computer-implemented method of secure distribution of vendor'"'"'s upgrades and patches of claim 7, include the step of:

determining how dependencies on other software upgrades affect the installation of a patch

15. The computer-implemented method of secure distribution of vendor'"'"'s upgrades and patches of claim 7, include the step of:

determining which files will be affected by the installation of a patch

16. The computer-implemented method of secure distribution of vendor'"'"'s upgrades and patches of claim 7, include the step of:

determining which directories will be affected by the installation of a patch

17. The computer-implemented method of secure distribution of vendor'"'"'s upgrades and patches of claim 7, include the step of:

Checking the permissions and ownership of the files referenced in the patch and ensuring that the system software is authentic