CN105656889A - WebApp issuing method, server and client - Google Patents
WebApp issuing method, server and client Download PDFInfo
- Publication number
- CN105656889A CN105656889A CN201511024381.8A CN201511024381A CN105656889A CN 105656889 A CN105656889 A CN 105656889A CN 201511024381 A CN201511024381 A CN 201511024381A CN 105656889 A CN105656889 A CN 105656889A
- Authority
- CN
- China
- Prior art keywords
- file
- webapp
- binary
- encrypted file
- subfile
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1441—Countermeasures against malicious traffic
- H04L63/1466—Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Storage Device Security (AREA)
Abstract
The invention provides a WebApp issuing method. The WebApp issuing method comprises the steps: by a WebApp provider, loading a WebApp source file including multiple sub files; packaging a file header for each of the multiple sub files, and generating index information according to the multiple file headers; packing the multiple sub files, the multiple file headers and the index information to form a binary file; encrypting the binary file, thereby obtaining an encrypted binary file; issuing the final encrypted binary file. According to the WebApp issuing method provided by the invention, the security of an issued WebApp can be improved, and the issued WebApp is prevented from being falsified and faked; furthermore, after a client obtains the WebApp file packet, no security deployment is needed, so that the WebApp file packet is more convenient in use. The invention further provides a server and a client.
Description
Technical field
The present invention relates to Computer Applied Technology field, particularly to the dissemination method of a kind of WebApp, server and client.
Background technology
WebApp refers to system and the application of sing on web, and its effect is to issue a complex set of content and function to vast end user. From a simple webpage helping consumer to calculate car lease expense, to large complicated network (Web) website providing a complete set of tourist service for commercial staff and holiday maker, it is all WebApp. It includes the Web site that some are complete, and the dedicated functions of Web site and the information processing on Internet, Intranet or ExtraNet are applied.
Common WebApp is usually and is packaged into such as the installation kit of APK form, is installed in Android system, or in iOS system. Also a small amount of WebApp is had to operate in the system of pure Web mode, chromeOS such as Google, but these App (application program) are that needs are preassembled, thus causing that the method for operation of WebApp had both lacked safety, affect again execution efficiency and operation complexity.
Summary of the invention
It is contemplated that at least solve one of above-mentioned technical problem.
For this, it is an object of the present invention to propose the dissemination method of a kind of WebApp. The method can promote safety after WebApp issues, it is to avoid is tampered and forges, it addition, after client obtains WebApp file bag, it is not necessary to carry out security deployment, make WebApp file bag more convenient to use.
Further object is that a kind of server of proposition.
Another object of the present invention is in that to propose a kind of client.
To achieve these goals, the embodiment of a first aspect of the present invention discloses the dissemination method of a kind of WebApp, comprises the following steps: server loads WebApp source file, and wherein, described WebApp source file includes multiple subfile; Encapsulate a file header for each subfile in the plurality of subfile, and generate index information according to multiple file headers; The plurality of subfile, multiple file header and described index information are packaged as binary file; It is encrypted to obtain binary encrypted file to described binary file; Add authentication of message code to described binary encrypted file, and described binary encrypted file is digitally signed, obtain final binary encrypted file; Issue described final binary encrypted file.
The dissemination method of WebApp according to embodiments of the present invention, it is possible to promote safety after WebApp issues, it is to avoid be tampered and forge, additionally, after client obtains WebApp file bag, it is not necessary to carry out security deployment, make WebApp file bag more convenient to use.
It addition, the dissemination method of WebApp according to the above embodiment of the present invention can also have following additional technical characteristic:
In some instances, described file header includes the sequence number of subfile, type and size, and described index information includes file header content and relative address.
In some instances, described it is encrypted to obtain binary encrypted file to binary file, including: obtain the PKI of client; Described binary file is encrypted to obtain binary encrypted file by the PKI according to described client.
In some instances, also include: described client loads the described final binary encrypted file that described WebApp provider issues; According to described authentication of message code and described digital signature, described final binary encrypted file is verified; If the verification passes, then according to the private key of described client, described final binary encrypted file is decrypted, obtains described binary file; The file header of each subfile in the plurality of subfile is deleted according to described index information; Perform described WebApp.
In some instances, before issuing described final binary encrypted file, also include: described final binary encrypted file is compressed.
In some instances, described according to described authentication of message code and described digital signature, described final binary encrypted file is verified before, also include: described final binary encrypted file is decompressed.
The embodiment of second aspect present invention discloses a kind of server, including: load-on module, it is used for loading WebApp source file, wherein, described WebApp source file includes multiple subfile; File header package module, for encapsulating a file header for each subfile in the plurality of subfile, and generates index information according to multiple file headers; Binary system packetization module, for being packaged as binary file by the plurality of subfile, multiple file header and described index information; Cipher key encryption block, for being encrypted to obtain binary encrypted file to described binary file; Authentication of message and signature blocks, for adding authentication of message code to described binary encrypted file, and be digitally signed described binary encrypted file, obtain final binary encrypted file; WebApp release module, is used for issuing described final binary encrypted file.
Server according to embodiments of the present invention, it is possible to promote safety after WebApp issues, it is to avoid be tampered and forge, it addition, after client obtains WebApp file bag, it is not necessary to carry out security deployment, make WebApp file bag more convenient to use.
It addition, server according to the above embodiment of the present invention can also have following additional technical characteristic:
In some instances, described file header includes the sequence number of subfile, type and size, and described index information includes file header content and relative address.
In some instances, described binary system packetization module is used for: obtain the PKI of client; Described binary file is encrypted to obtain binary encrypted file by the PKI according to described client.
In some instances, also include: secondary encapsulation and compression module, before issuing described final binary encrypted file in described WebApp release module, described final binary encrypted file is compressed.
The embodiment of third aspect present invention discloses a kind of client, including: WebApp introducting interface, for loading the described final binary encrypted file that described WebApp provider issues;Signature verification module, for being verified described final binary encrypted file according to described authentication of message code and described digital signature; File decryption module, for, after described signature verification module verification passes through, being decrypted described final binary encrypted file according to the private key of described client, obtain described binary file; Internal memory load-on module, for deleting the file header of each subfile in the plurality of subfile according to described index information; WebApp runs and management module, is used for performing described WebApp.
Client according to embodiments of the present invention, it is not necessary to WebApp file bag is carried out installation and deployment, makes WebApp file bag more convenient to use.
Further, also include: decompression module, before according to described authentication of message code and described digital signature described final binary encrypted file being verified in described signature verification module, described final binary encrypted file is decompressed.
The additional aspect of the present invention and advantage will part provide in the following description, and part will become apparent from the description below, or is recognized by the practice of the present invention.
Accompanying drawing explanation
Above-mentioned and/or the additional aspect of the present invention and advantage are from conjunction with will be apparent from easy to understand the accompanying drawings below description to embodiment, wherein:
Fig. 1 is the flow chart of the dissemination method of WebApp according to an embodiment of the invention;
Fig. 2 is the flow chart of the dissemination method of WebApp in accordance with another embodiment of the present invention;
Fig. 3 is the structured flowchart of server according to an embodiment of the invention; And
Fig. 4 is the structured flowchart of client according to an embodiment of the invention.
Detailed description of the invention
Being described below in detail embodiments of the invention, the example of described embodiment is shown in the drawings, and wherein same or similar label represents same or similar element or has the element of same or like function from start to finish. The embodiment described below with reference to accompanying drawing is illustrative of, and is only used for explaining the present invention, and is not considered as limiting the invention.
In describing the invention, it will be appreciated that, term " " center ", " longitudinal direction ", " transverse direction ", " on ", D score, " front ", " afterwards ", " left side ", " right side ", " vertically ", " level ", " top ", " end ", " interior ", orientation or the position relationship of the instruction such as " outward " are based on orientation shown in the drawings or position relationship, it is for only for ease of the description present invention and simplifies description, rather than the device of instruction or hint indication or element must have specific orientation, with specific azimuth configuration and operation, therefore it is not considered as limiting the invention. additionally, term " first ", " second " are only for descriptive purposes, and it is not intended that indicate or hint relative importance.
In describing the invention, it is necessary to explanation, unless otherwise clearly defined and limited, term " installation ", " being connected ", " connection " should be interpreted broadly, for instance, it is possible to it is fixing connection, it is also possible to be removably connect, or connect integratedly; Can be mechanically connected, it is also possible to be electrical connection; Can be joined directly together, it is also possible to be indirectly connected to by intermediary, it is possible to be the connection of two element internals. For the ordinary skill in the art, it is possible to concrete condition understands above-mentioned term concrete meaning in the present invention.
Below in conjunction with accompanying drawing, the dissemination method of WebApp according to embodiments of the present invention, server and client are described.
Fig. 1 is the flow chart of the dissemination method of WebApp according to an embodiment of the invention. As it is shown in figure 1, the dissemination method of WebApp according to an embodiment of the invention, comprise the steps:
S101: server loads WebApp source file, and wherein, WebApp source file includes multiple subfile.
After WebApp PHP has write WebApp code according to demand, it would be desirable to each subfile unified be put into below a catalogue, the file under this catalogue is WebApp source file. Multiple subfiles include resource file and code file.
S102: encapsulate a file header for each subfile in multiple subfiles, and generate index information according to multiple file headers. Wherein, file header includes the sequence number of subfile, type and size, and described index information includes file header content and relative address.
Specifically, internal memory is opened up one piece of memory space, load all code files and resource file in internal memory, each subfile is encapsulated a file header by internal memory, in order to information such as the sequence number of descriptor file, type, sizes, for instance: NTLV form, N:number, T: type, L: length, V: data. Initial position at the memory space newly opened up adds index information, including the file header content of each subfile, relative address etc.
S103: multiple subfiles, multiple file header and index information are packaged as binary file.
Such as: with binary form, the content in above-mentioned internal memory is repackaged into a proprietary file (that is: a proprietary binary file), suffix name can be oneself definition, if recognizable, for instance " XXX.wedget ".
S104: be encrypted to obtain binary encrypted file to binary file.
Owing to the final purpose of WebApp is available to client, for client, therefore, it can utilize the PKI of client to be encrypted, do so can make the client being authorized to use WebApp. Such as: first obtain the PKI of client, then it is encrypted to obtain binary encrypted file to binary file according to the PKI of client.
S105: add authentication of message code to binary encrypted file, and binary encrypted file is digitally signed, obtain final binary encrypted file. Wherein, binary encrypted file is added authentication of message code, it is possible to avoid WebApp to be maliciously tampered, binary encrypted file is digitally signed, it is possible to be prevented effectively from WebApp and be forged.
S106: issue final binary encrypted file. Such as: be published on network. Thus supporting that the various ways such as network download, USB, disk import WebApp file bag (that is: final binary encrypted file).
Due to WebApp file bag be likely to relatively larger, therefore, it can before issue to its be compressed process, facilitate user's download etc. Such as: before issuing final binary encrypted file, final binary encrypted file is compressed. Thus reducing the volume of WebApp file bag. File bag after compression just can be undertaken issuing by the form of WebApp, thus facilitating client downloads, importing etc.
The dissemination method of WebApp according to embodiments of the present invention, it is possible to promote safety after WebApp issues, it is to avoid be tampered and forge, additionally, after client obtains WebApp file bag, it is not necessary to carry out security deployment, make WebApp file bag more convenient to use.
In one embodiment of the invention, after client imports WebApp file bag, the dissemination method of WebApp, including:
S201: client loads the final binary encrypted file that WebApp provider issues.
Such as: the forms such as network download, USB, disk that first pass through import WebApp file bag, if WebApp file bag is compressed, then the WebApp file of importing is wrapped in and internal memory carries out decompress (that is: the final binary encrypted file issued being decompressed), revert back the file before compression.
S202: final binary encrypted file is verified according to authentication of message code and digital signature. That is: whether checking authentication of message code is correct, if correct, illustrates that WebApp file bag was not tampered with, and whether checking digital signature is correct, if correct, description WebApp file bag is not forged.
S203: if the verification passes, then be decrypted final binary encrypted file according to the private key of client, obtain binary file. Such as: be decrypted by the private key of client self, wherein, decipherment algorithm can be that existing multiple decipherment algorithm realizes.
S204: delete the file header of each subfile in multiple subfiles according to index information.
Specifically, the file after deciphering is re-write new region of memory, and according to index information, the file header of each resource file and code file is extracted and deletes file header, multiple subfiles are resequenced.
S205: perform WebApp. That is: the WebApp file bag in internal memory is loaded and performs, and the life cycle of WebApp is managed.
The dissemination method of WebApp according to embodiments of the present invention, it is possible to promote safety after WebApp issues, it is to avoid be tampered and forge, additionally, after client obtains WebApp file bag, it is not necessary to carry out security deployment, make WebApp file bag more convenient to use.
Fig. 3 is the structured flowchart of server according to an embodiment of the invention. As it is shown on figure 3, according to one embodiment of the invention server 300, including: load-on module 310, file header package module 320, binary system packetization module 330, cipher key encryption block 340, authentication of message and signature blocks 350 and WebApp release module 360.
Wherein, load-on module 310 is used for loading WebApp source file, and wherein, WebApp source file includes multiple subfile. File header package module 320 is for encapsulating a file header for each subfile in multiple subfiles, and generates index information according to multiple file headers. Binary system packetization module 330 is for being packaged as binary file by multiple subfiles, multiple file header and index information. Cipher key encryption block 340 is for being encrypted to obtain binary encrypted file to binary file. Authentication of message and signature blocks 350 are for adding authentication of message code to binary encrypted file, and binary encrypted file is digitally signed, and obtain final binary encrypted file. WebApp release module 360 is used for issuing final binary encrypted file.
Wherein, file header includes but not limited to the sequence number of subfile, type and size, and described index information includes file header content and relative address.
In one embodiment of the invention, binary system packetization module 330 is used for: obtains the PKI of client, is encrypted to obtain binary encrypted file to binary file according to the PKI of client.
As it is shown on figure 3, this server 300, also including: secondary encapsulation and compression module 370, secondary encapsulation and compression module 370 are for, before WebApp release module 360 issues final binary encrypted file, being compressed final binary encrypted file.
Server according to embodiments of the present invention, it is possible to promote safety after WebApp issues, it is to avoid be tampered and forge, it addition, after client obtains WebApp file bag, it is not necessary to carry out security deployment, make WebApp file bag more convenient to use.
It should be noted that the specific implementation of the server of the embodiment of the present invention is similar with the specific implementation of the dissemination method of the WebApp of the embodiment of the present invention, specifically refer to the description of method part, in order to reduce redundancy, do not repeat herein.
Fig. 4 is the structured flowchart of client according to an embodiment of the invention. As shown in Figure 4, client 400 according to an embodiment of the invention, include: WebApp introducting interface 410, signature verification module 420, file decryption module 430, internal memory load-on module 440 and WebApp run and management module 450.
Wherein, WebApp introducting interface 410 is for loading the described final binary encrypted file that WebApp provider issues. Signature verification module 420 is for being verified described final binary encrypted file according to described authentication of message code and described digital signature. File decryption module 430 is for, after described signature verification module verification passes through, being decrypted described final binary encrypted file according to the private key of described client, obtain described binary file. Internal memory load-on module 440 is for deleting the file header of each subfile in the plurality of subfile according to described index information. WebApp runs and management module 450 is used for performing described WebApp.
As shown in Figure 4, this client 400, also include: decompression module 460, decompression module 460 is for, before described final binary encrypted file being verified according to described authentication of message code and described digital signature in described signature verification module 420, decompressing described final binary encrypted file.
Client according to embodiments of the present invention, it is not necessary to WebApp file bag is carried out installation and deployment, makes WebApp file bag more convenient to use.
It should be noted that the specific implementation of the client of the embodiment of the present invention is similar with the specific implementation of the dissemination method of the WebApp of the embodiment of the present invention, specifically refer to the description of method part, in order to reduce redundancy, do not repeat herein.
In the description of this specification, specific features, structure, material or feature that the description of reference term " embodiment ", " some embodiments ", " example ", " concrete example " or " some examples " etc. means in conjunction with this embodiment or example describe are contained at least one embodiment or the example of the present invention. In this manual, the schematic representation of above-mentioned term is not necessarily referring to identical embodiment or example. And, the specific features of description, structure, material or feature can combine in an appropriate manner in any one or more embodiments or example.
Although an embodiment of the present invention has been shown and described, it will be understood by those skilled in the art that: these embodiments can being carried out multiple change, amendment, replacement and modification when without departing from principles of the invention and objective, the scope of the present invention is by claim and equivalency thereof.
Claims (12)
1. the dissemination method of a WebApp, it is characterised in that comprise the following steps:
Server loads WebApp source file, and wherein, described WebApp source file includes multiple subfile;
Encapsulate a file header for each subfile in the plurality of subfile, and generate index information according to multiple file headers;
The plurality of subfile, multiple file header and described index information are packaged as binary file;
It is encrypted to obtain binary encrypted file to described binary file;
Add authentication of message code to described binary encrypted file, and described binary encrypted file is digitally signed, obtain final binary encrypted file;
Issue described final binary encrypted file.
2. the dissemination method of WebApp according to claim 1, it is characterised in that described file header includes the sequence number of subfile, type and size, and described index information includes file header content and relative address.
3. the dissemination method of WebApp according to claim 1, it is characterised in that described be encrypted to obtain binary encrypted file to binary file, including:
Obtain the PKI of client;
Described binary file is encrypted to obtain binary encrypted file by the PKI according to described client.
4. the dissemination method of WebApp according to claim 3, it is characterised in that also include:
Described client loads the described final binary encrypted file that described WebApp provider issues;
According to described authentication of message code and described digital signature, described final binary encrypted file is verified;
If the verification passes, then according to the private key of described client, described final binary encrypted file is decrypted, obtains described binary file;
The file header of each subfile in the plurality of subfile is deleted according to described index information;
Perform described WebApp.
5. the dissemination method of WebApp according to claim 4, it is characterised in that before issuing described final binary encrypted file, also include: described final binary encrypted file is compressed.
6. the dissemination method of WebApp according to claim 5, it is characterized in that, described according to described authentication of message code and described digital signature, described final binary encrypted file is verified before, also include: described final binary encrypted file is decompressed.
7. a server, it is characterised in that including:
Load-on module, is used for loading WebApp source file, and wherein, described WebApp source file includes multiple subfile;
File header package module, for encapsulating a file header for each subfile in the plurality of subfile, and generates index information according to multiple file headers;
Binary system packetization module, for being packaged as binary file by the plurality of subfile, multiple file header and described index information;
Cipher key encryption block, for being encrypted to obtain binary encrypted file to described binary file;
Authentication of message and signature blocks, for adding authentication of message code to described binary encrypted file, and be digitally signed described binary encrypted file, obtain final binary encrypted file;
WebApp release module, is used for issuing described final binary encrypted file.
8. server according to claim 7, it is characterised in that described file header includes the sequence number of subfile, type and size, and described index information includes file header content and relative address.
9. server according to claim 7, it is characterised in that described binary system packetization module is used for:
Obtain the PKI of client;
Described binary file is encrypted to obtain binary encrypted file by the PKI according to described client.
10. server according to claim 7, it is characterised in that also include:
Secondary encapsulation and compression module, before issuing described final binary encrypted file in described WebApp release module, be compressed described final binary encrypted file.
11. a client, it is characterised in that including:
WebApp introducting interface, for loading the described final binary encrypted file that described WebApp provider issues;
Signature verification module, for being verified described final binary encrypted file according to described authentication of message code and described digital signature;
File decryption module, for, after described signature verification module verification passes through, being decrypted described final binary encrypted file according to the private key of described client, obtain described binary file;
Internal memory load-on module, for deleting the file header of each subfile in the plurality of subfile according to described index information;
WebApp runs and management module, is used for performing described WebApp.
12. client according to claim 11, it is characterised in that also include:
Decompression module, before described final binary encrypted file being verified according to described authentication of message code and described digital signature in described signature verification module, decompresses described final binary encrypted file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511024381.8A CN105656889A (en) | 2015-12-30 | 2015-12-30 | WebApp issuing method, server and client |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511024381.8A CN105656889A (en) | 2015-12-30 | 2015-12-30 | WebApp issuing method, server and client |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105656889A true CN105656889A (en) | 2016-06-08 |
Family
ID=56490900
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201511024381.8A Pending CN105656889A (en) | 2015-12-30 | 2015-12-30 | WebApp issuing method, server and client |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105656889A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106874776A (en) * | 2016-12-30 | 2017-06-20 | 厦门天锐科技股份有限公司 | A kind of decryption method for encrypting file |
| CN107656742A (en) * | 2017-09-27 | 2018-02-02 | 北京奇虎科技有限公司 | A kind of software product dissemination method and device |
| CN108268767A (en) * | 2016-12-30 | 2018-07-10 | 北京国双科技有限公司 | Web application authorization method and device |
| CN108710500A (en) * | 2018-05-23 | 2018-10-26 | 北京五八信息技术有限公司 | Resource issuing method, update method and device |
| CN112600848A (en) * | 2020-12-17 | 2021-04-02 | 上海芯安信息科技有限公司 | Software upgrading package encapsulation method and device and software upgrading package decapsulation method and device |
| CN112822228A (en) * | 2019-11-15 | 2021-05-18 | 北京中电普华信息技术有限公司 | Browser file encryption uploading method and system based on state cryptographic algorithm |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130036313A1 (en) * | 2011-08-05 | 2013-02-07 | Schwenk Joerg | Persistent Encryption with XML Encryption |
| CN103177199A (en) * | 2011-12-22 | 2013-06-26 | 盛乐信息技术（上海）有限公司 | Webpage application code protective method and system, and executive speed-up method and system |
| CN104216715A (en) * | 2014-09-02 | 2014-12-17 | 深圳前海诺德咨询服务有限公司 | Web App development framework and method |
| CN104461632A (en) * | 2014-12-09 | 2015-03-25 | 东软集团股份有限公司 | Web App loading method and device |
-
2015
- 2015-12-30 CN CN201511024381.8A patent/CN105656889A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130036313A1 (en) * | 2011-08-05 | 2013-02-07 | Schwenk Joerg | Persistent Encryption with XML Encryption |
| CN103177199A (en) * | 2011-12-22 | 2013-06-26 | 盛乐信息技术（上海）有限公司 | Webpage application code protective method and system, and executive speed-up method and system |
| CN104216715A (en) * | 2014-09-02 | 2014-12-17 | 深圳前海诺德咨询服务有限公司 | Web App development framework and method |
| CN104461632A (en) * | 2014-12-09 | 2015-03-25 | 东软集团股份有限公司 | Web App loading method and device |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106874776A (en) * | 2016-12-30 | 2017-06-20 | 厦门天锐科技股份有限公司 | A kind of decryption method for encrypting file |
| CN108268767A (en) * | 2016-12-30 | 2018-07-10 | 北京国双科技有限公司 | Web application authorization method and device |
| CN106874776B (en) * | 2016-12-30 | 2020-06-09 | 厦门天锐科技股份有限公司 | Decryption method of encrypted file |
| CN107656742A (en) * | 2017-09-27 | 2018-02-02 | 北京奇虎科技有限公司 | A kind of software product dissemination method and device |
| CN108710500A (en) * | 2018-05-23 | 2018-10-26 | 北京五八信息技术有限公司 | Resource issuing method, update method and device |
| CN112822228A (en) * | 2019-11-15 | 2021-05-18 | 北京中电普华信息技术有限公司 | Browser file encryption uploading method and system based on state cryptographic algorithm |
| CN112822228B (en) * | 2019-11-15 | 2023-05-02 | 北京中电普华信息技术有限公司 | Browser file encryption uploading method and system based on cryptographic algorithm |
| CN112600848A (en) * | 2020-12-17 | 2021-04-02 | 上海芯安信息科技有限公司 | Software upgrading package encapsulation method and device and software upgrading package decapsulation method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105656889A (en) | WebApp issuing method, server and client | |
| CN101436141B (en) | Firmware upgrading and encapsulating method and device based on digital signing | |
| CN103744652B (en) | Hybrid APP development method and device across mobile terminals | |
| RU2357288C2 (en) | Method and device for supporting content exchange between domains with different drm | |
| CN104426658B (en) | The method and device of authentication is carried out to the application on mobile terminal | |
| CN104503745B (en) | A kind of method and apparatus generated using channel packet | |
| CN105391717A (en) | APK signature authentication method and APK signature authentication system | |
| CN109194625B (en) | Client application protection method and device based on cloud server and storage medium | |
| CN110362990A (en) | Using the security processing of installation, apparatus and system | |
| CN104573527A (en) | UEFI system updating method based on updating security mechanism | |
| CN101561762A (en) | Software installation procedure packing system and method | |
| CN111143869A (en) | Application package processing method and device, electronic equipment and storage medium | |
| WO2017066995A1 (en) | Method and device for preventing unauthorized access to server | |
| CN109787768A (en) | A kind of authentication configuration method, device and computer readable storage medium | |
| CN107179925A (en) | Hot update method and device | |
| CN107609394A (en) | Tamper resistant method, storage device and the device of Android installation kits | |
| CN101588376A (en) | Information releasing method, device and system | |
| CN108170461B (en) | Differential upgrade package generation method, differential upgrade method and device | |
| CN113961908B (en) | Data storage method and device, computer equipment and storage medium | |
| CN103297816A (en) | Safety downloading method and digital television receiving terminal | |
| CN103401931B (en) | A kind of method and system for downloading file | |
| CN104077158B (en) | The method and device of plug-in unit is installed | |
| CN111045722A (en) | Intelligent contract packaging method, device, system, computer equipment and storage medium | |
| CN107257282A (en) | A kind of full bag encryption method of code based on RC4 algorithms | |
| CN104317817B (en) | The version compatibility method and device of a kind of configuration file |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160608 |