CN111049909A - Software release method - Google Patents

Software release method Download PDF

Info

Publication number
CN111049909A
CN111049909A CN201911297939.8A CN201911297939A CN111049909A CN 111049909 A CN111049909 A CN 111049909A CN 201911297939 A CN201911297939 A CN 201911297939A CN 111049909 A CN111049909 A CN 111049909A
Authority
CN
China
Prior art keywords
file
client
server
software
information
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.)
Granted
Application number
CN201911297939.8A
Other languages
Chinese (zh)
Other versions
CN111049909B (en
Inventor
吴波
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kunshan Huadong Information Technology Co Ltd
Original Assignee
Kunshan Huadong Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Kunshan Huadong Information Technology Co Ltd filed Critical Kunshan Huadong Information Technology Co Ltd
Priority to CN201911297939.8A priority Critical patent/CN111049909B/en
Publication of CN111049909A publication Critical patent/CN111049909A/en
Application granted granted Critical
Publication of CN111049909B publication Critical patent/CN111049909B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/34Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/12Protecting executable software
    • G06F21/121Restricting unauthorised execution of programs
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/12Protecting executable software
    • G06F21/121Restricting unauthorised execution of programs
    • G06F21/128Restricting unauthorised execution of programs involving web programs, i.e. using technology especially used in internet, generally interacting with a web browser, e.g. hypertext markup language [HTML], applets, java
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44Program or device authentication
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/51Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0442Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/141Setup of application sessions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/568Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5683Storage of data provided by user terminals, i.e. reverse caching
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H04L69/162Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms

Abstract

The invention relates to the technical field of automatic software installation, deployment and release, in particular to an automatic software release method. The method comprises the following steps: the client initiates a connection issuing request to the server; the server receives a connection request of the client and performs security authentication; the client initiates a request for acquiring the version information of the server file after the security authentication is passed; the server receives a client request instruction and transmits all file version information in the target folder to the client; the client receives the version information transmitted by the server and compares the version information with the file information; and updating the published file information at the server according to the comparison result. By adopting the invention, the safety problem of file information transmission is solved, and the automatic backup of software release can be solved.

Description

Software release method
Technical Field
The invention relates to a method for automatically installing, deploying and releasing software, and belongs to the technical field of automatic upgrading of software versions.
Background
Software installation and deployment of a small-scale software company are released manually, the software is developed to a certain scale, and the timeliness and the correctness of system release updating cannot be met by pure manual operation. Software installation deployment is gradually moving towards automation. The manual labor mode is replaced by the automatic tool, and the working efficiency is improved.
At present, relative to automatic release software, a network file sharing 445 port is generally opened, which files are changed are determined by a file comparison method, and then file synchronization is performed. The requirement for the network port is special, and the 445 port must be opened. 445 port is not generally recommended by enterprises to be opened, the extant lemonavirus is file infection in a local area network through the 445 port, and the worm virus can be spread through the 445 port of the network file sharing. Introducing risk to the corporate network security.
Disclosure of Invention
The invention aims to provide a software release method, which realizes the safety management of the intelligent software release process in a network environment through the Windows Socket communication technology + the RSA encryption technology, not only solves the transmission problem, but also can solve the automatic backup of software release. .
In order to achieve the above object, the present invention provides a software distribution method, including the steps of:
(1) a user clicks to issue, and a client initiates an issuing connection request to a server;
(2) the server receives a connection request of the client and performs security authentication;
(3) the client initiates a request for acquiring the version information of the server file after the security authentication is passed;
(4) the server receives a client request instruction and transmits all file version information in the target folder to the client;
(5) the client receives the version information transmitted by the server, compares the file information in the source folder with the file information in the target file one by one according to a preset rule, and determines whether to update the version of the release file or not according to the comparison result;
(6) if the updating and releasing are needed, the client side initiates a file package transmission request;
(7) the server receives the file publishing packet transmitted by the client and publishes the content of the publishing packet to a target folder;
(8) the server side feeds back the issuing result to the client side, and the client side submits the issuing record to the uniform issuing platform.
The invention is further perfected by the following operations before the user clicks and releases: a user logs in a client, the client displays all online server lists, and the user selects a target server of the secondary release software from the client; and configuring and storing software file information in a source folder and a target folder issued by software.
The invention is further perfected that the preset rule of the file information comparison can adopt any one of the following two modes:
comparing the last modification date of the file, if the last modification date of the server side file information is different from that of the client side file information, determining that the file is different, and updating and releasing the file;
and a second mode of comparing the file contents by calculating the HASH value of the file contents. And if the HASH values of the client file and the server file are different, the files are considered to be different, and updating and releasing are needed.
The invention further perfects that the file information comparison process is cached in the client.
The invention further perfects that the information interaction is carried out between the client and the server in a Socket mode.
The invention further perfects that the safety certification account number and the password are transmitted through RAS asymmetric encryption.
According to the invention, the server program receives the instruction of the client, and the server program automatically executes file version comparison, file backup and file release operations, so that management personnel can realize remote installation and deployment without logging in a remote server, and the efficiency and safety of problem processing are improved. Each releasing process is automatically recorded to the platform, so that the releasing process can be tracked, and the manageability is improved. The security of the software release process is improved through the encryption of the communication between the client and the server.
Drawings
The above and other features, properties and advantages of the present invention will become more apparent from the following description of the embodiments with reference to the accompanying drawings in which like reference numerals denote like features throughout the several views, wherein:
fig. 1 is a flowchart of a method for automatically releasing software according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The invention aims to overcome the defects in the prior art and provide an automatic application software release system and an automatic application software release method, which not only can realize the safety management of the intelligent software release process, but also can solve the problem of automatic backup of software release.
According to the scheme provided by the invention, the software publishing method comprises the following steps:
(1) a user clicks to issue, and a client initiates an issuing connection request to a server;
(2) the server receives a connection request of the client and performs security authentication;
(3) the client initiates a request for acquiring the version information of the server file after the security authentication is passed;
(4) after the server receives the instruction of the client for requesting to acquire the version information of the server file, the server traverses the target
All files in the folder return the version information of the files, and the version information in the target folder is transmitted to the client;
(5) after receiving the version information transmitted by the server, the client compares the file information in the source folder with the file information in the target file one by one according to a preset rule, and determines whether to update the version of the release file or not according to a comparison result;
(6) if the update and the release are needed, the client-side performs zip compression on the release packet, reduces the network flow through the compression and initiates a file transfer request;
(7) the server receives the publishing packet, zip decompression processing is carried out, the server carries out unified backup processing on files of the target folder according to a file list in the publishing packet, and after the backup is finished, the content of the publishing packet is published to the target folder;
(8) the server side feeds back the issuing result to the client side, the client side submits the issuing record to the uniform issuing platform, and all issuing records are managed through the uniform issuing platform.
(9) The client ends the publication.
Further, the security authentication account number and the password are transmitted through RAS asymmetric encryption to ensure that transmission contents cannot be leaked;
further, before the user clicks the release, the following operations are also performed: a user logs in a client, the client displays all online server lists, and the user selects a target server of the secondary release software from the client; configuring software file information in a source folder and a target folder issued by software, and storing the software file information; and then software release is carried out.
Further, the file information comparison mode adopts two modes:
comparing the last modification date of the file, if the last modification date of the server side file is different from that of the client side file, determining that the files are different, and updating and releasing the files;
and a second mode of comparing the file contents by calculating the HASH value of the file contents. If it is not
And if the HASH values of the client file and the server file are different, the files are considered to be different, and updating and releasing are needed.
Furthermore, in order to accelerate the comparison process, the comparison process is designed to be cached in the client, and the file version information of the server can be directly obtained from the local cache in the next comparison period, so that the situation that the version information is obtained from the remote server every time is avoided.
Further, a Socket mode is adopted between the client and the server for information interaction.
The target server is provided with server software, the server software is used for receiving a published file of the client, the client is provided with client software, and the client software is used for publishing the file on the local computer of the client to the remote server.
According to the invention, the server program receives the instruction of the client, and the server program automatically executes file version comparison, file backup and file release operations, so that management personnel can realize remote installation and deployment without logging in a remote server, and the efficiency and safety of problem processing are improved. Each releasing process is automatically recorded to the platform, so that the releasing process can be tracked, and the manageability is improved. The security of the software release process is improved through the encryption of the communication between the client and the server.
The embodiments described above are provided to enable persons skilled in the art to make or use the invention and that modifications or variations can be made to the embodiments described above by persons skilled in the art without departing from the inventive concept of the present invention, so that the scope of protection of the present invention is not limited by the embodiments described above but should be accorded the widest scope consistent with the innovative features set forth in the claims.

Claims (6)

1. A method for software release, the method comprising the steps of:
(1) a user clicks to issue, and a client initiates an issuing connection request to a server;
(2) the server receives a connection request of the client and performs security authentication;
(3) the client initiates a request for acquiring the version information of the server file after the security authentication is passed;
(4) the server receives a client request instruction and transmits all file version information in the target folder to the client;
(5) the client receives the version information transmitted by the server, compares the file information in the source folder with the file information in the target file one by one according to a preset rule, and determines whether to update the version of the release file or not according to the comparison result;
(6) if the updating and releasing are needed, the client side initiates a file package transmission request;
(7) the server receives the file publishing packet transmitted by the client and publishes the content of the publishing packet to a target folder;
(8) the server side feeds back the issuing result to the client side, and the client side submits the issuing record to the uniform issuing platform.
2. The software publishing method of claim 1, wherein before the user clicks publishing, the following operations are further performed: a user logs in a client, the client displays all online server lists, and the user selects a target server of the secondary release software from the client; and configuring and storing software file information in a source folder and a target folder issued by software.
3. The software distribution method according to any one of claims 1 or 2, wherein the predetermined rule for comparing the file information can adopt any one of the following two modes:
comparing the last modification date of the file, if the last modification date of the server side file information is different from that of the client side file information, determining that the file is different, and updating and releasing the file;
and a second mode of comparing the file contents by calculating the HASH value of the file contents. And if the HASH values of the client file and the server file are different, the files are considered to be different, and updating and releasing are needed.
4. The software publishing method according to claim 3, wherein the file information comparison process is cached at the client.
5. The software release method of claim 1, wherein the client and the server perform information interaction in a Socket manner.
6. The software release method according to claim 1, wherein the security authentication account and the password are transmitted through RAS asymmetric encryption.
CN201911297939.8A 2019-12-17 2019-12-17 Software release method Active CN111049909B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911297939.8A CN111049909B (en) 2019-12-17 2019-12-17 Software release method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911297939.8A CN111049909B (en) 2019-12-17 2019-12-17 Software release method

Publications (2)

Publication Number Publication Date
CN111049909A true CN111049909A (en) 2020-04-21
CN111049909B CN111049909B (en) 2024-04-02

Family

ID=70236942

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911297939.8A Active CN111049909B (en) 2019-12-17 2019-12-17 Software release method

Country Status (1)

Country Link
CN (1) CN111049909B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7076496B1 (en) * 2001-02-23 2006-07-11 3Com Corporation Method and system for server based software product release version tracking
CN101944170A (en) * 2010-09-20 2011-01-12 中兴通讯股份有限公司 Method, system and device for issuing software version
CN108874409A (en) * 2017-05-09 2018-11-23 腾讯科技(深圳)有限公司 A kind of information updating method, device, server and system
CN109040069A (en) * 2018-08-06 2018-12-18 江苏易安联网络技术有限公司 A kind of dissemination method, delivery system and the access method of cloud application program
CN109617694A (en) * 2018-12-21 2019-04-12 网易(杭州)网络有限公司 A kind of application issued method and apparatus
CN110336695A (en) * 2019-06-21 2019-10-15 威富通科技有限公司 A kind of method and server of deployment and maintenance application

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7076496B1 (en) * 2001-02-23 2006-07-11 3Com Corporation Method and system for server based software product release version tracking
CN101944170A (en) * 2010-09-20 2011-01-12 中兴通讯股份有限公司 Method, system and device for issuing software version
CN108874409A (en) * 2017-05-09 2018-11-23 腾讯科技(深圳)有限公司 A kind of information updating method, device, server and system
CN109040069A (en) * 2018-08-06 2018-12-18 江苏易安联网络技术有限公司 A kind of dissemination method, delivery system and the access method of cloud application program
CN109617694A (en) * 2018-12-21 2019-04-12 网易(杭州)网络有限公司 A kind of application issued method and apparatus
CN110336695A (en) * 2019-06-21 2019-10-15 威富通科技有限公司 A kind of method and server of deployment and maintenance application

Also Published As

Publication number Publication date
CN111049909B (en) 2024-04-02

Similar Documents

Publication Publication Date Title
CN110727712B (en) Data processing method and device based on block chain network, electronic equipment and storage medium
US9519474B2 (en) Modular system including management and deployment of software updates and revisions
WO2017050141A1 (en) Distributed storage-based file delivery system and method
US8495182B1 (en) Scalable systems management abstraction framework
EP2675127B1 (en) Method and device for automatically migrating system configuration item
CN112270550B (en) New energy power tracing method and system based on blockchain
CN105072183B (en) The management method and managing device in cloud O/S software warehouse
US20050278384A1 (en) External authentication against a third-party directory
CN110598434B (en) House information processing method and device based on blockchain network, electronic equipment and storage medium
CN102710630A (en) Cloud upload and download method and system of multi-threaded slice
CN103067363B (en) Index conversion method for public data integrity checking
CN112835977B (en) Database management method and system based on block chain
CN101753547A (en) Method and system for updating applications and parameters of multi-model POS terminal device
CN105808273B (en) Method for upgrading software and software updating apparatus
JP7280260B2 (en) Propagation of information by network nodes
CN105453127A (en) Method and system for document synchronization in a distributed server-client environment
CN104268156A (en) Website management system and method
CN104298761A (en) Implementation method for master data matching between heterogeneous software systems
CN113271366B (en) Data sharing system based on block chain and safety calculation
CN111176677A (en) Server system reinforcement updating method and device
CN111510428B (en) Security resource operation and maintenance platform system and control method
US11165759B2 (en) Data encryption and decryption processing method in cloud network environment
CN111049909A (en) Software release method
CN111914019A (en) Stable control data management system and method based on block chain technology
CN109344620B (en) Detection method based on hadoop security configuration

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
GR01 Patent grant
GR01 Patent grant