CN102156651B - Method and device for realizing installation of patches - Google Patents
Method and device for realizing installation of patches Download PDFInfo
- Publication number
- CN102156651B CN102156651B CN201110050562.3A CN201110050562A CN102156651B CN 102156651 B CN102156651 B CN 102156651B CN 201110050562 A CN201110050562 A CN 201110050562A CN 102156651 B CN102156651 B CN 102156651B
- Authority
- CN
- China
- Prior art keywords
- patch
- file
- installation kit
- installation
- assembly
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 238000009434 installation Methods 0.000 title claims abstract description 151
- 238000000034 method Methods 0.000 title claims abstract description 30
- 238000012360 testing method Methods 0.000 claims description 48
- 230000008439 repair process Effects 0.000 claims description 7
- 239000013589 supplement Substances 0.000 claims description 6
- 230000001502 supplementing effect Effects 0.000 claims description 4
- 238000005516 engineering process Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 238000012217 deletion Methods 0.000 description 4
- 230000037430 deletion Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000001514 detection method Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000000052 comparative effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000011900 installation process Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
Abstract
The embodiment of the invention discloses a method and a device for realizing installation of patches, wherein the method comprises the following steps of analyzing a patch file from a first patch installation package; utilizing the patch file and the prearranged installation strategy to generate a second patch installation package; and utilizing the prearranged installation strategy to install the second patch installation package after the first patch installation package fails to install. By adopting the method and the device, the success rate of installation of patches can be improved, and the safety and stability of the system of a user can be further ensured effectively.
Description
Technical field
The application relates to field of computer technology, particularly relates to a kind of method and the device that realize patch installation.
Background technology
In the various application processes of current computing machine; usually can find existing problems or the leaks such as various operating system, application software; also can be described as BUG; and these leaks can make user occur interference when using operating system or software; or cause the security performance of software to reduce; therefore by writing out the program language that some can insert source program, can repair these leaks, the above-mentioned program language for patching bugs is just called patch.
Usually, the special website of certain operations system or application software can regularly publish patch, to carry out leak reparation for these operating systems or application software; And as shown in Figure 1, patch installation of the prior art generally comprises following steps:
Step 110: obtain patch installation kit; Step 120: parse patch file and patch installation detection file from described patch installation kit; Step 130: utilize described patch installation detection file to detect active client in patch file installation process and whether meet patch mounting condition, if do not met, show that current patch is installed unsuccessfully; Wherein, described patch install detect file in order to detect described patch for object whether meet patch mounting condition, include but not limited to: the version after whether the version detecting described object upgrades lower than described patch, detect described object whether existed in registration table described patch install after key assignments information etc.But, inventor finds in the research process of prior art, due to client because some technical reason causes the requirement that cannot meet described patch mounting condition, patch can be caused to install, thus cause the reduction that patch is mounted to power, make user cannot carry out the installation of patch in time for leak, and then then very possible serious threat is formed to computer system or application program.
Summary of the invention
The embodiment of the present application provides a kind of method and the device that realize patch installation, is mounted to low the caused problem of power to solve existing patch.
In order to solve the problems of the technologies described above, the embodiment of the present application discloses following technical scheme:
Realize the method that patch is installed, comprising:
Patch file is parsed from the first patch installation kit;
Described patch file is utilized to generate the second patch installation kit with the mounting strategy preset;
When the first patch installation kit is installed unsuccessfully, utilize described default mounting strategy that the second patch installation kit is installed.
Preferably, the method also comprises and obtains the first patch installation kit in the following manner:
Refresh patch and issue the page;
When the described patch issue page exists lastest imformation, obtain the patch information in described lastest imformation;
Link and access patch downloading page and download the first patch installation kit.
Preferably, described default mounting strategy comprises one of following condition or its combination in any:
When the version of program or assembly and/or relevant program or assembly do not have the patch comprised in the first patch installation kit install institute in testing conditions for the version of object new time, judge that described patch file is suitable for installation;
When finding that the program of leak or assembly and/or relevant program or assembly exist the danger dangerous or unstable to system cloud gray model, and patch file can eliminate described dangerous time, judge that described patch file is suitable for installing;
When finding that the program of leak or assembly and/or relevant program or assembly are to system cloud gray model safety or stable irrelevant, and described patch file is not installed does not affect other patch files when installing, judge that described patch file is unsuitable for installing;
When finding that the version after the program of leak or the version of assembly and/or relevant program or assembly are installed with described second patch installation kit is identical, but when still there is the recoverable leak of patch file, judge that described patch file is suitable for installation.
Preferably, the program of described discovery leak or the version of assembly and/or relevant program or assembly are determined in the following manner:
Check the version information in version number, filename and/or registration table.
Preferably, the generating mode of described default mounting strategy at least comprises any one in several mode:
Testing conditions is installed to described patch and carries out all or part of amendment;
To described patch, testing conditions is installed to supplement, upgrade;
Testing conditions is installed to described patch and carries out part deletion.
Preferably, testing conditions is installed to described patch and carries out all or part of amendment and comprise: patch is installed institute in testing conditions for the most highest version of reparation object as comparison other, the version lower than comparison other is suitable for installation patch file;
Install testing conditions to described patch to supplement, upgrade and comprise: available patch file is carried out leak reparation and patch is installed not for the reparation object that the object repaired increases in described predetermined policy in testing conditions, the reparation object of described increase is suitable for installing patch file;
To described patch, testing conditions is installed to carry out part and delete and comprise: patch is installed in testing conditions and limit that patch file is installed and condition that patch file can repair corresponding leak is deleted.
Preferably, part or all of described patch file is utilized to generate the second patch installation kit with the mounting strategy preset.
Preferably, in the following way at least one judge described first patch installation kit whether successful installation:
The key assignments information in registration table is utilized to judge described first patch installation kit whether successful installation;
The patch information obtained is utilized to judge described first patch installation kit whether successful installation.
Realize the device that patch is installed, comprising:
Resolution unit, for parsing patch file from the first patch installation kit;
Generation unit, the patch file parsed for utilizing described resolution unit generates the second patch installation kit with the mounting strategy preset;
Installation unit, for installing unsuccessfully at described first patch installation kit, utilizes described default mounting strategy to install the second patch installation kit.
Preferably, described resolution unit comprises:
Refresh the refresh module of the patch issue page, obtain the acquisition module of the patch information in described lastest imformation when the described patch issue page exists lastest imformation and link and access the download module that patch downloading page downloads the first patch installation kit.
Preferably, this device also comprises: setting unit, for default mounting strategy; Wherein, described default mounting strategy comprises one of following condition or its combination in any:
When the version of program or assembly and/or relevant program or assembly do not have the patch comprised in the first patch installation kit install institute in testing conditions for the version of object new time, judge that described patch file is suitable for installation;
When finding that the program of leak or assembly and/or relevant program or assembly exist the danger dangerous or unstable to system cloud gray model, and patch file can eliminate described dangerous time, judge that described patch file is suitable for installing;
When finding that the program of leak or assembly and/or relevant program or assembly are to system cloud gray model safety or stable irrelevant, and described patch file is not installed does not affect other patch files when installing, judge that described patch file is unsuitable for installing;
When finding that the version after the program of leak or the version of assembly and/or relevant program or assembly are installed with described second patch installation kit is identical, but when still there is the recoverable leak of patch file, judge that described patch file is suitable for installation.
Preferably, described setting unit comprises:
The first processing module that testing conditions carries out all or part of amendment is installed to described patch; And/or, to the second processing module that described patch installation testing conditions supplements, upgrades; And/or, the 3rd processing module that testing conditions carries out part deletion is installed to described patch.
As can be seen from the above-described embodiment, in the embodiment of the present application, by obtaining patch mounting condition from former patch installation kit, described patch file is utilized to form new patch installation kit with the patch mounting strategy preset, when former patch is installed unsuccessfully, utilize described new patch installation kit to carry out the installation of patch, improve the success ratio that patch is installed, and then effectively ensure that the security of system of user and stablize.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present application or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, for those of ordinary skills, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
Fig. 1 is the schematic flow sheet that in prior art, patch is installed;
Fig. 2 is the first embodiment schematic flow sheet that the application realizes the method that patch is installed;
Fig. 3 is the schematic flow sheet obtaining the first patch installation kit in the application first embodiment;
Fig. 4 is the embodiment block diagram that the application realizes the device that patch is installed.
Embodiment
Basic thought of the present invention is to obtain patch mounting condition from former patch installation kit, described patch file is utilized to form new patch installation kit with the patch mounting strategy preset, when former patch is installed unsuccessfully, described new patch installation kit is utilized to carry out the installation of patch, improve the success ratio that patch is installed, and then effectively ensure that the security of system of user and stablize.
The following embodiment of the present invention provides a kind of method and the device that realize patch installation.
Technical scheme in the embodiment of the present invention is understood better in order to make those skilled in the art person, and enable the above-mentioned purpose of the embodiment of the present invention, feature and advantage become apparent more, below in conjunction with accompanying drawing, technical scheme in the embodiment of the present invention is described in further detail.
See Fig. 2, for the application realizes the first embodiment process flow diagram of the method that patch is installed:
Step 210: parse patch file from the first patch installation kit;
Wherein, the the first patch installation kit mentioned in the present embodiment is that unartificial mode obtains, but manual type is collected patch installation kit or third party and collected patch installation kit and also can realize the present invention, and the present embodiment specifically can adopt following steps to realize, as shown in Figure 3, but be not limited thereto:
S211: refresh patch and issue the page; Adopt third party software/instrument to refresh the technology comparative maturity of fixing Webpage in prior art, and this step also can adopt prior art to realize in the present embodiment, such as, the patch adopting brush screen software program regularly to refresh the company's sites such as Microsoft issues the page; Specifically repeat no more herein;
S212: when the described patch issue page exists lastest imformation, obtain the patch information in described lastest imformation; Concrete acquisition process adopts the acquiring technology of page key word in prior art to realize, but be not limited thereto: the source code information such as analyzing current page, if wherein contain the information such as trasaction key, namely show that current page upgrades, therefrom obtain associated patch information again; Particular content repeats no more herein;
S213: link and access patch downloading page download patches installation kit;
Concrete, after described patch is issued and be there is updating message in the page, in described updating message, contain the download URL of patch installation kit, then AutoLink access the page corresponding to this URL, therefrom download described patch installation kit.
Step 220: utilize described patch file to generate the second patch installation kit with the mounting strategy preset;
Concrete, described default mounting strategy comprises one of following condition or its combination in any:
A, when the version of program or assembly and/or relevant program or assembly do not have patch to install in testing conditions for the version of object new time, judge that patch file is suitable for installing, such as, if a program version is the version on January 1st, 2011, corresponding version number is v1.1, it does not have the version of the patch mounting object of patch installation defined in testing conditions new, then think that this patch file is suitable for installing, this version new and old for date issued, if version number's order and date correspondence, also can judge the new and old of each version with version number;
B, when finding that the program of leak or assembly and/or relevant program or assembly exist the danger dangerous or unstable to system cloud gray model, and patch file is when can eliminate danger, judge that patch file is suitable for installing, such as, patch file can repair some up-to-date leaks that may cause system cloud gray model risk, and version corresponding to these leaks is installed in testing conditions at original patch and shown, now still judge that this patch file is suitable for installing;
C, when finding that the program of leak or assembly and/or relevant program or assembly are to system cloud gray model safety or stable irrelevant, and do not install patch file do not affect other patch files install time, judge that patch file is unsuitable for installing, such as, to the patch that office helps, do not affect safety and stability, so can not install, certainly, " being unsuitable for installing " of mentioning in the present embodiment considers from the angle economized on resources, be defined as to install, if user needs, completely can the patch that helps as elucidated before of installation example;
D, version after the discovery program of leak or the version of assembly and/or relevant program or assembly are installed with the second patch installation kit is identical, but when still there is the recoverable leak of patch file, judge that patch file is suitable for installing, such as, if a program finds leak, even if its version install with the second patch installation kit after version identical, also still can judge that this patch file is suitable for installing, this patch file mainly installed for (but being not limited to) go to pot or after repairing because other problem produces the situation that identical leak needs to reinstall again.
Wherein, find in the present embodiment that the program of leak or the version of assembly and/or relevant program or assembly can be determined in the following manner, but be not limited to this: check the version information in version number, filename and/or registration table; Such as, give out information Microsoft's patch registration, forms registration form, and registration form is kept at client this locality or server, then new and old by checking the mode comparison version of registration record.
It should be noted that the generating mode utilizing described patch file and the mounting strategy preset to generate the second patch installation kit includes but not limited to: utilizes the mounting strategy preset to the patch comprised in described first patch installation kit install testing conditions carry out all or part of amendment, supplementary, upgrade and/or deletion etc.;
Wherein, testing conditions is installed to patch and carries out all or part of amendment and can comprise: patch is installed institute in testing conditions for the latest edition of reparation object as comparison other, the version early than comparison other is suitable for installation patch file;
Install testing conditions to patch to carry out supplementing or upgrading and can comprise: available patch file is carried out leak reparation and patch is installed not for the reparation object that the object of reparation increases in predetermined policy in testing conditions, the reparation object of increase is suitable for installation patch file; Such as, second patch installation kit for object only may be date of issue before existing, but the leak again occurring that available patch file is repaired may be there is after patch date of issue, now this patch file being also suitable for installation for this object and being set to mounting strategy, supplementing for carrying out renewal to the patch installation testing conditions in the first patch installation kit.
To patch mounting condition carry out part delete comprise: patch is installed in testing conditions limit patch file install and patch file can repair corresponding leak condition delete; Such as, in patch mounting condition must there is some function (such as helping) in limiting program software, or there is not some function, and these functions do not affect patch file to the reparation of repairing object, now this condition can be deleted, form described mounting strategy.
Those of ordinary skill in the art should readily understand, default mounting strategy in the present embodiment be can improve patch in order to user be mounted to power, therefore in actual applications, power is mounted in order to improve patch further, completely can not testing conditions be set, namely directly can carry out the installation of patch without the need to any testing conditions or mounting strategy, thus make any use in time, effectively can complete patch installation per family.
In addition, all or part of patch file and predetermined policy can be combined in the present embodiment, to generate the second patch installation kit.Wherein, all or part of combination can be understood as: it is identical with the problem that original patch installation kit solves that whole patch files and default mounting strategy generate the second patch installation kit, testing conditions is just installed and has had change, namely, by original installation testing conditions is changed to default mounting strategy, this second patch installation kit can be made to complete and to repair identical leak or identical upgrading with the first patch installation kit; It is because under specific circumstances that part patch file and default mounting strategy combine, part patch file just can complete the identical task of original patch installation kit, in yet some other cases, part patch file combination in different patch installation kit, the task different from single patch installation kit can be completed, the mode that such part patch file and default mounting strategy combine can reduce the data volume of user's download patches installation kit, also makes the second patch installation kit generate more flexible.
Step 230: when the first patch installation kit is installed unsuccessfully, utilizes described default mounting strategy to install the second patch installation kit;
In actual applications, concrete first service packs install that failed judgment mode can adopt in the following two kinds mode any one, but be not limited to this:
A: utilize the key assignments information in registration table to judge described first patch installation kit whether successful installation;
Such as to judge patch KB979099 whether successful installation, first in the following items of registration table, inquire about the key assignments whether having and comprise KB979099: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows Current Version Component Based Servicing Packages, if installed described patch, the register button certainly existing similar Package_for_KB979099_RTM ~ 31bf3856ad364e35 ~ x86 ~ ~ 6.1.1.0 in the project of then above-mentioned registration table exists, and is the mount message of described patch in this key; Described first patch installation kit whether successful installation can be judged with this.
B: utilize the patch information obtained to judge described first patch installation kit whether successful installation;
Concrete, the fileversion number in described patch information or filename etc. can be utilized to judge, but be not limited to this: such as described patch is for upgrading patch, and its effect makes the application program update of its correspondence to version be 10.1.102.64; Whether to judge this patch successful installation, namely needing to inquire about version under this application program place drive catalogue is whether the file of 10.1.102.64 exists, if file exists, then can confirm described first patch installation kit successful installation.
Can find out, adopt the method for the above embodiment of the present invention, by obtaining patch mounting condition from former patch installation kit, described patch file is utilized to form new patch installation kit with the patch mounting strategy preset, when former patch is installed unsuccessfully, utilize described new patch installation kit to carry out the installation of patch, improve the success ratio that patch is installed, and then effectively ensure that the security of system of user and stablize.
Corresponding with the embodiment that the application realizes the method that patch is installed, present invention also provides the embodiment of the device realizing the method.
The device embodiment block diagram of patch installation is realized see the application described in Fig. 4:
This device 400 comprises: 410 resolution unit, for parsing patch file from the first patch installation kit; Generation unit 420, the patch file parsed for utilizing described resolution unit 410 generates the second patch installation kit with the mounting strategy preset; Installation unit 430, for installing unsuccessfully at described first patch installation kit, utilizes described default mounting strategy to install the second patch installation kit.
Wherein, described resolution unit 410 comprises (not shown in Fig. 4): refresh the refresh module of the patch issue page, obtain the acquisition module of the patch information in described lastest imformation when the described patch issue page exists lastest imformation and link and access the download module that patch downloading page downloads the first patch installation kit.
In addition, this device also comprises: setting unit (not shown in Fig. 4), for default mounting strategy; Wherein, described default mounting strategy comprises one of following condition or its combination in any: when the version of program or assembly and/or relevant program or assembly do not have the patch comprised in the first patch installation kit install institute in testing conditions for the version of object new time, judge that described patch file is suitable for installation; When finding that the program of leak or assembly and/or relevant program or assembly exist the danger dangerous or unstable to system cloud gray model, and patch file can eliminate described dangerous time, judge that described patch file is suitable for installing; When finding that the program of leak or assembly and/or relevant program or assembly are to system cloud gray model safety or stable irrelevant, and described patch file is not installed does not affect other patch files when installing, judge that described patch file is unsuitable for installing; When finding that the version after the program of leak or the version of assembly and/or relevant program or assembly are installed with described second patch installation kit is identical, but when still there is the recoverable leak of patch file, judge that described patch file is suitable for installation.
Wherein, described setting unit also can comprise (not shown in Fig. 4): install to described patch the first processing module that testing conditions carries out all or part of amendment; And/or, to the second processing module that described patch installation testing conditions supplements, upgrades; And/or, the 3rd processing module that testing conditions carries out part deletion is installed to described patch.
Those skilled in the art can be well understood to the mode that technology in the embodiment of the present invention can add required general hardware platform by software and realize.Based on such understanding, technical scheme in the embodiment of the present invention can embody with the form of software product the part that prior art contributes in essence in other words, this computer software product can be stored in storage medium, as ROM/RAM, magnetic disc, CD etc., comprising some instructions in order to make a computer equipment (can be personal computer, server, or the network equipment etc.) perform the method described in some part of each embodiment of the present invention or embodiment.
Each embodiment in this instructions all adopts the mode of going forward one by one to describe, between each embodiment identical similar part mutually see, what each embodiment stressed is the difference with other embodiments.Especially, for system embodiment, because it is substantially similar to embodiment of the method, so description is fairly simple, relevant part illustrates see the part of embodiment of the method.
Above-described embodiment of the present invention, does not form limiting the scope of the present invention.Any amendment done within the spirit and principles in the present invention, equivalent replacement and improvement etc., all should be included within protection scope of the present invention.
Claims (9)
1. realize the method that patch is installed, it is characterized in that, comprising:
Patch file is parsed from the first patch installation kit;
Utilize described patch file to generate the second patch installation kit with the mounting strategy preset, specifically comprise:
Utilize the mounting strategy preset, to the patch comprised in described first patch installation kit, testing conditions is installed to carry out all or part of amendment, supplement, upgrade and/or delete;
To patch, testing conditions is installed to carry out all or part of amendment and comprise: patch is installed institute in testing conditions for the latest edition of reparation object as comparison other, the version early than comparison other is suitable for installation patch file;
Install testing conditions to patch to carry out supplementing or upgrading comprising: available patch file is carried out leak reparation and patch is installed not for the reparation object that the object of reparation increases in predetermined policy in testing conditions, the reparation object of increase is suitable for installation patch file;
To patch install testing conditions carry out part delete comprise: patch is installed in testing conditions limit patch file install and patch file can repair corresponding leak condition delete;
Directly utilize described patch file to carry out installing or work as the first patch installation kit to install unsuccessfully, utilize described default mounting strategy that the second patch installation kit is installed.
2. method according to claim 1, is characterized in that, the method also comprises and obtains the first patch installation kit in the following manner:
Refresh patch and issue the page;
When the described patch issue page exists lastest imformation, obtain the patch information in described lastest imformation;
Link and access patch downloading page and download the first patch installation kit.
3. method according to claim 1, is characterized in that, described default mounting strategy comprises one of following condition or its combination in any:
When the version of program or assembly and/or relevant program or assembly do not have the patch comprised in the first patch installation kit install institute in testing conditions for the version of object new time, judge that described patch file is suitable for installation;
When finding that the program of leak or assembly and/or relevant program or assembly exist the danger dangerous or unstable to system cloud gray model, and patch file can eliminate described dangerous time, judge that described patch file is suitable for installing;
When finding that the program of leak or assembly and/or relevant program or assembly are to system cloud gray model safety or stable irrelevant, and described patch file is not installed does not affect other patch files when installing, judge that described patch file is unsuitable for installing;
When finding that the version after the program of leak or the version of assembly and/or relevant program or assembly are installed with described second patch installation kit is identical, but when still there is the recoverable leak of patch file, judge that described patch file is suitable for installation.
4. method according to claim 3, is characterized in that, the program of described discovery leak or the version of assembly and/or relevant program or assembly are determined in the following manner:
Check the version information in version number, filename and/or registration table.
5. method according to claim 1, is characterized in that, the method also comprises: utilize part or all of described patch file to generate the second patch installation kit with the mounting strategy preset.
6. method according to claim 1, is characterized in that, at least one in the following way judges described first patch installation kit whether successful installation:
The key assignments information in registration table is utilized to judge described first patch installation kit whether successful installation;
The patch information obtained is utilized to judge described first patch installation kit whether successful installation.
7. realize the device that patch is installed, it is characterized in that, comprising:
Resolution unit, for parsing patch file from the first patch installation kit;
Generation unit, the patch file parsed for utilizing described resolution unit generates the second patch installation kit with the mounting strategy preset, and specifically comprises:
Utilize the mounting strategy preset, to the patch comprised in described first patch installation kit, testing conditions is installed to carry out all or part of amendment, supplement, upgrade and/or delete;
To patch, testing conditions is installed to carry out all or part of amendment and comprise: patch is installed institute in testing conditions for the latest edition of reparation object as comparison other, the version early than comparison other is suitable for installation patch file;
Install testing conditions to patch to carry out supplementing or upgrading comprising: available patch file is carried out leak reparation and patch is installed not for the reparation object that the object of reparation increases in predetermined policy in testing conditions, the reparation object of increase is suitable for installation patch file;
To patch install testing conditions carry out part delete comprise: patch is installed in testing conditions limit patch file install and patch file can repair corresponding leak condition delete;
Installation unit, carrying out for directly utilizing described patch file installing or installing unsuccessfully at described first patch installation kit, utilizing described default mounting strategy to install the second patch installation kit.
8. device according to claim 7, is characterized in that, described resolution unit comprises:
Refresh the refresh module of the patch issue page, obtain the acquisition module of the patch information in described lastest imformation when the described patch issue page exists lastest imformation and link and access the download module that patch downloading page downloads the first patch installation kit.
9. device according to claim 7, is characterized in that, this device also comprises: setting unit, for default mounting strategy; Wherein, described default mounting strategy comprises one of following condition or its combination in any:
When the version of program or assembly and/or relevant program or assembly do not have the patch comprised in the first patch installation kit install institute in testing conditions for the version of object new time, judge that described patch file is suitable for installation;
When finding that the program of leak or assembly and/or relevant program or assembly exist the danger dangerous or unstable to system cloud gray model, and patch file can eliminate described dangerous time, judge that described patch file is suitable for installing;
When finding that the program of leak or assembly and/or relevant program or assembly are to system cloud gray model safety or stable irrelevant, and described patch file is not installed does not affect other patch files when installing, judge that described patch file is unsuitable for installing;
When finding that the version after the program of leak or the version of assembly and/or relevant program or assembly are installed with described second patch installation kit is identical, but when still there is the recoverable leak of patch file, judge that described patch file is suitable for installation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110050562.3A CN102156651B (en) | 2011-03-02 | 2011-03-02 | Method and device for realizing installation of patches |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110050562.3A CN102156651B (en) | 2011-03-02 | 2011-03-02 | Method and device for realizing installation of patches |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102156651A CN102156651A (en) | 2011-08-17 |
| CN102156651B true CN102156651B (en) | 2015-05-06 |
Family
ID=44438159
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110050562.3A Expired - Fee Related CN102156651B (en) | 2011-03-02 | 2011-03-02 | Method and device for realizing installation of patches |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102156651B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107423033A (en) * | 2016-05-23 | 2017-12-01 | 中兴通讯股份有限公司 | Plant maintenance method and device |
| CN109800126A (en) * | 2018-12-27 | 2019-05-24 | 北京奇安信科技有限公司 | The analysis method and device of patch install failure |
| CN110443046B (en) * | 2019-08-14 | 2021-10-29 | 中国电子信息产业集团有限公司第六研究所 | Vulnerability repairing method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6161218A (en) * | 1996-01-16 | 2000-12-12 | Sun Microsystems Inc. | Software patch architecture |
| CN101661400A (en) * | 2009-09-16 | 2010-03-03 | 中兴通讯股份有限公司 | Method and device for managing software patches |
| CN102156649A (en) * | 2011-03-01 | 2011-08-17 | 奇智软件（北京）有限公司 | Patch installation method and device thereof |
-
2011
- 2011-03-02 CN CN201110050562.3A patent/CN102156651B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6161218A (en) * | 1996-01-16 | 2000-12-12 | Sun Microsystems Inc. | Software patch architecture |
| CN101661400A (en) * | 2009-09-16 | 2010-03-03 | 中兴通讯股份有限公司 | Method and device for managing software patches |
| CN102156649A (en) * | 2011-03-01 | 2011-08-17 | 奇智软件（北京）有限公司 | Patch installation method and device thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102156651A (en) | 2011-08-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2005201434B2 (en) | Efficient patching | |
| CN101110788B (en) | Method and system for updating client software | |
| CN104346167B (en) | The method and device of channel bag is applied in generation | |
| EP3488337B1 (en) | Shared software libraries for computing devices | |
| US7735079B1 (en) | Securely hooking installations for compatibility with other applications | |
| CN105786538B (en) | software upgrading method and device based on android system | |
| CN102262549B (en) | Method and system for installing patches | |
| US20050256664A1 (en) | Efficient patching | |
| CN103530148A (en) | Distribution method for large-scale Linux software package | |
| WO2013078951A1 (en) | Method and system for upgrading software | |
| CN102195804A (en) | Automatic updating method of software and system thereof | |
| US8954949B2 (en) | Smart patch delivery system | |
| US8490078B2 (en) | System and method for application management | |
| US7627866B2 (en) | Systems and methods for dynamic application patching | |
| CA2860657C (en) | Installation engine and package format for parallelizable, reliable installations | |
| CN105608382A (en) | Software maintenance method, software problem judgment method and corresponding apparatuses | |
| CN102156650B (en) | Method and device capable of implementing automatic analysis of patch | |
| CN102156651B (en) | Method and device for realizing installation of patches | |
| CN110297655B (en) | Method, device, equipment and storage medium for generating patch package | |
| CN101963911A (en) | Patch generating method and device | |
| CN108121552B (en) | Automatic patching method based on XenServer | |
| US20060161415A1 (en) | Driver handler object framework | |
| US20060015867A1 (en) | Business productivity pack | |
| US20080209408A1 (en) | Seeding product information | |
| CN102110212B (en) | Method and device for realizing patch amendment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20151022 Address after: 100088 Beijing city Xicheng District xinjiekouwai Street 28, block D room 112 (Desheng Park) Patentee after: BEIJING QIHOO TECHNOLOGY Co.,Ltd. Patentee after: Qizhi software (Beijing) Co.,Ltd. Address before: The 4 layer 100025 unit of Beijing city Chaoyang District Jiuxianqiao Road No. 14 Building C Patentee before: Qizhi software (Beijing) Co.,Ltd. |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20220721 Address after: Room 801, 8th floor, No. 104, floors 1-19, building 2, yard 6, Jiuxianqiao Road, Chaoyang District, Beijing 100015 Patentee after: BEIJING QIHOO TECHNOLOGY Co.,Ltd. Address before: 100088 room 112, block D, 28 new street, new street, Xicheng District, Beijing (Desheng Park) Patentee before: BEIJING QIHOO TECHNOLOGY Co.,Ltd. Patentee before: Qizhi software (Beijing) Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20150506 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |