CN114546420A - Software remote installation protection uninstalling method - Google Patents
Software remote installation protection uninstalling method Download PDFInfo
- Publication number
- CN114546420A CN114546420A CN202111671354.5A CN202111671354A CN114546420A CN 114546420 A CN114546420 A CN 114546420A CN 202111671354 A CN202111671354 A CN 202111671354A CN 114546420 A CN114546420 A CN 114546420A
- Authority
- CN
- China
- Prior art keywords
- software
- daemon
- configuration file
- strategy
- uninstallation
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/62—Uninstallation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a remote software installation, protection and uninstallation method, which comprises a software installation protection process and a software uninstallation process; when each piece of software is stored, a configuration file for recording software daemon information is stored together, and the configuration file comprises a daemon identifier of the software, a software daemon strategy and a monitoring process list; software installation flow: downloading software and a configuration file corresponding to the software, and starting a daemon thread when judging that the software needs to be daemon based on a daemon identification in the configuration file; performing timing check according to the daemon strategy in the configuration file, and recovering the software or process violating the daemon strategy; software unloading process: when the software is determined to be daemon based on the daemon identification in the configuration file after any uninstallation is received, the daemon is removed and the uninstallation of the software is started. The method can prevent the software from being illegally tampered.
Description
Technical Field
The invention belongs to the technical field of computer firmware, and particularly relates to a software remote installation protection uninstalling method.
Background
The prior remote installation and uninstallation technology has the following problems:
1) in the process of installing the software remotely, the server cannot acquire whether the client software is installed successfully.
2) And remote uninstalling is performed, and the protected software cannot be uninstalled or whether the software is successfully uninstalled cannot be acquired.
Disclosure of Invention
The invention provides a software remote installation protection uninstalling method which can prevent software from being illegally tampered.
The technical scheme for realizing the invention is as follows:
a remote software installation protection uninstalling method comprises a software installation protection process and a software uninstalling process; wherein the content of the first and second substances,
when each piece of software is stored, a configuration file for recording software daemon information is stored together, and the configuration file comprises a daemon identifier, a software daemon strategy and a monitoring process list of the software;
software installation protection process: downloading software and a configuration file corresponding to the software, and starting a daemon thread when judging that the software needs to be daemon based on a daemon identification in the configuration file; performing timing check according to the daemon strategy in the configuration file, and recovering the software or process violating the daemon strategy;
software unloading process: when the software is determined to be daemon based on the daemon identification in the configuration file after any uninstallation is received, the daemon is removed and the uninstallation of the software is started.
Further, when the daemon strategy in the configuration file is anti-closing, the daemon process and the restarting mode of the process are recorded.
Further, the configuration file of the present invention includes an installation path, a hash value of the file, and a monitoring process list.
Further, the daemon strategy of the invention is to prevent deletion, tampering and/or closing.
Furthermore, the configuration file is stored in the memory together with the software, and the software daemon information recorded by the configuration file can be remotely configured.
Advantageous effects
By the method, the installation and uninstallation states of the software can be acquired by checking the server, and the installed software can be managed only through the installation process, so that the software is prevented from being illegally uninstalled.
Drawings
FIG. 1 is an installation protection flow diagram;
FIG. 2 is an unloading flow chart;
FIG. 3 is a block diagram of a software remote installation and uninstallation method.
Detailed Description
The invention is described in detail below by way of example with reference to the accompanying drawings.
It should be noted that, in the case of no conflict, the features in the following embodiments and examples may be combined with each other; moreover, all other embodiments that can be derived by one of ordinary skill in the art from the embodiments disclosed herein without making any creative effort fall within the scope of the present disclosure.
It is noted that various aspects of the embodiments are described below within the scope of the appended claims. It should be apparent that the aspects described herein may be embodied in a wide variety of forms and that any specific structure and/or function described herein is merely illustrative. Based on the disclosure, one skilled in the art should appreciate that one aspect described herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented and/or a method practiced using any number of the aspects set forth herein. Additionally, such an apparatus may be implemented and/or such a method may be practiced using other structure and/or functionality in addition to one or more of the aspects set forth herein.
The design concept of the invention is as follows: the reporting function of the software installation and uninstallation state is added, and the interactive information is encrypted, so that the installed software is protected, and the software is prevented from being maliciously uninstalled; meanwhile, the protection strategy of the software is removed before the software is unloaded, so that the software can be normally installed and deleted.
The application provides a remote software installation, protection and uninstallation method, which comprises a software installation protection process and a software uninstallation process;
when each piece of software is stored, a configuration file for recording software daemon information is stored together, and the configuration file comprises a daemon identifier, a software daemon strategy and a monitoring process list of the software;
software installation protection process: downloading software and a configuration file corresponding to the software, and starting a daemon thread when judging that the software needs to be daemon based on a daemon identification in the configuration file; when the daemon strategy in the configuration file is anti-closing, recording the daemon process and the restarting mode of the process;
software unloading process: when the software is determined to be daemon based on the daemon identification in the configuration file after any uninstallation is received, the daemon is removed and the uninstallation of the software is started.
As shown in fig. 1, the following describes the installation protection process of software in detail:
step one, starting an installation process.
And step two, waiting for a server side installation command.
And step three, after receiving the installation task, analyzing the installation information, if the analysis fails, sending analysis failure information to the server side and finishing the installation, and if the analysis succeeds, entering step four.
And step four, after the analysis is successful, downloading the software and recording the configuration file of the software daemon information according to the analyzed software package download address, if the download is successful, entering the step five, and if the download is failed, sending download failure information to the server side, and finishing the installation.
In this embodiment, the configuration file includes whether the software needs a daemon identifier, an installation path of each file in the software, a daemon policy, a hash value of the file, a monitoring process list, and the like. The daemon policy may be to prevent deletion, tampering, and/or shutdown; if the file daemon strategy is used for preventing closing, the name of the process and the restarting mode of the process are required to be recorded.
And step five, after the software and the configuration file are downloaded successfully, executing installation, entering step six if the software is installed successfully, and reporting installation failure information to the server if the software is installed unsuccessfully.
And step six, reading a configuration file for recording the software daemon information.
And seventhly, judging whether the software needs to be guarded according to the daemon identification read from the configuration file, starting a daemon thread if the software needs to be guarded, regularly checking the daemon strategy read from the configuration file, and recovering the software or the process which violates the daemon strategy.
And step eight, reporting the installation information.
And step nine, finishing the installation.
As shown in fig. 2, the following describes the software uninstalling process in detail:
step one, starting an unloading process.
And step two, waiting for the server side to unload the command.
And step three, after receiving the unloading task, analyzing the unloading information.
And step four, if the analysis fails, sending analysis failure information to the server, and if the analysis succeeds, entering step five.
And step five, after the analysis is successful, reading a configuration file for recording the daemon information of the software.
And step six, judging whether the file needs to be guarded or not according to the identification which is read from the configuration file and whether the file needs to be guarded or not, if the file needs to be guarded, removing the guard and starting to unload the software, and if the file does not need to be guarded, directly unloading the software.
And step seven, reporting unloading success or failure information to the server side according to the unloading result.
And step eight, unloading is finished.
As shown in FIG. 3, an implementation framework of the software remote installation protection uninstalling method includes a remote software installation and uninstallation platform and an operating system.
(1) The remote software installation and removal platform comprises a remote installation service, a remote removal service and a software library.
a) The remote installation service is used for setting remote installation parameters of the software and starting policy configuration;
b) the remote uninstalling service is used for setting remote uninstalling parameters and uninstalling strategy configuration of the software;
c) and the software library is used for providing software files needing to be installed.
(2) The operating system comprises an extension agent and specified software.
a) The extension agent is used for realizing the installation and the uninstallation of specified software in the operating system.
b) The installation files for the specified software are from the software library.
The above description is only for the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (5)
1. A remote software installation protection uninstalling method comprises a software installation protection process and a software uninstalling process; it is characterized in that the preparation method is characterized in that,
when each piece of software is stored, a configuration file for recording software daemon information is stored together, and the configuration file comprises a daemon identifier, a software daemon strategy and a monitoring process list of the software;
software installation protection process: downloading software and a configuration file corresponding to the software, and starting a daemon thread when judging that the software needs to be daemon based on a daemon identification in the configuration file; performing timing check according to the daemon strategy in the configuration file, and recovering the software or process violating the daemon strategy;
software uninstalling process: when the software is determined to be daemon based on the daemon identification in the configuration file after any uninstallation is received, the daemon is removed and the uninstallation of the software is started.
2. The method for remotely installing, protecting and uninstalling software according to claim 1, wherein when the daemon strategy in the configuration file is anti-shutdown, the daemon process and the restarting mode of the process are recorded.
3. The method of claim 1, wherein the configuration file comprises an installation path, a hash value of a file, and a list of monitoring processes.
4. The method of claim 1, wherein the daemon strategy is deletion, tamper, and/or shutdown resistant.
5. The method for remote installation protection uninstallation of software according to claim 1 wherein said configuration file is stored in a memory together with the software, and the software daemon information recorded by said configuration file can be remotely configured.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111671354.5A CN114546420A (en) | 2021-12-31 | 2021-12-31 | Software remote installation protection uninstalling method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111671354.5A CN114546420A (en) | 2021-12-31 | 2021-12-31 | Software remote installation protection uninstalling method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114546420A true CN114546420A (en) | 2022-05-27 |
Family
ID=81670503
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111671354.5A Pending CN114546420A (en) | 2021-12-31 | 2021-12-31 | Software remote installation protection uninstalling method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114546420A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116431365A (en) * | 2023-06-07 | 2023-07-14 | 北京集度科技有限公司 | Monitoring system and method based on vehicle-mounted service guide framework and vehicle |
-
2021
- 2021-12-31 CN CN202111671354.5A patent/CN114546420A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116431365A (en) * | 2023-06-07 | 2023-07-14 | 北京集度科技有限公司 | Monitoring system and method based on vehicle-mounted service guide framework and vehicle |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9910743B2 (en) | Method, system and device for validating repair files and repairing corrupt software | |
| CN102736978B (en) | A kind of method and device detecting the installment state of application program | |
| US9652632B2 (en) | Method and system for repairing file at user terminal | |
| CN102262574B (en) | Boot protecting method and device of operating system | |
| CN107783776B (en) | Processing method and device of firmware upgrade package and electronic equipment | |
| US20080148399A1 (en) | Protection against stack buffer overrun exploitation | |
| CN103329093A (en) | Updating software | |
| CN112783537B (en) | Embedded linux operating system upgrading method and system based on MTD storage device | |
| US7845010B2 (en) | Terminal control apparatus and terminal control method | |
| CN113094210B (en) | Window platform process and file daemon method and system | |
| JP2006330864A (en) | Control method for server computer system | |
| CN114417335A (en) | Malicious file detection method and device, electronic equipment and storage medium | |
| CN114676419A (en) | Method, system, equipment and medium for real-time early warning of tampering of application program file | |
| CN114546420A (en) | Software remote installation protection uninstalling method | |
| CN108647516B (en) | Method and device for defending against illegal privilege escalation | |
| JP4643201B2 (en) | Buffer overflow vulnerability analysis method, data processing device, analysis information providing device, analysis information extraction processing program, and analysis information provision processing program | |
| CN103309769A (en) | Operation system starting protection method and device | |
| CN118043808A (en) | Information processing device, control method for information processing device, and program | |
| CN114546717A (en) | Method and device for starting android intelligent terminal, intelligent terminal and storage medium | |
| CN113297628A (en) | Modification behavior auditing method, device, equipment and readable storage medium | |
| US20100306844A1 (en) | Application information tampering monitoring apparatus and method | |
| CN115828246B (en) | Offline malicious program and behavior monitoring method, device, medium and equipment | |
| CN117786666B (en) | Function code starting verification method and device, electronic equipment and storage medium | |
| US20240104219A1 (en) | Information processing apparatus, information processing method, and non-transitory computer readable medium | |
| CN115033424A (en) | Computer software guarding method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 100083 north side, 13th floor, Taiji building, No.6 working area (South), wohuqiao, Haidian District, Beijing Applicant after: Kunlun Taike (Beijing) Technology Co.,Ltd. Address before: 100083 north side, 13th floor, Taiji building, No.6 working area (South), wohuqiao, Haidian District, Beijing Applicant before: CLP Technology (Beijing) Co.,Ltd. |
|
| CB02 | Change of applicant information |