CN112202810A - Dynamic encryption transmission method for web data - Google Patents
Dynamic encryption transmission method for web data Download PDFInfo
- Publication number
- CN112202810A CN112202810A CN202011136031.1A CN202011136031A CN112202810A CN 112202810 A CN112202810 A CN 112202810A CN 202011136031 A CN202011136031 A CN 202011136031A CN 112202810 A CN112202810 A CN 112202810A
- Authority
- CN
- China
- Prior art keywords
- encrypted
- encryption
- data
- client
- server
- 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
Links
Images
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
- H04L63/0457—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 wherein the sending and receiving network entities apply dynamic encryption, e.g. stream encryption
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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
- H04L63/0442—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 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
-
- 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/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
- H04L63/068—Network architectures or network communication protocols for network security for supporting key management in a packet data network using time-dependent keys, e.g. periodically changing keys
-
- 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]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Storage Device Security (AREA)
Abstract
The invention provides a dynamic encryption transmission method of web data, which comprises the following steps: setting a configuration background module, and editing parameter names, asymmetric encryption algorithms, public keys, private keys and encryption version number information which are required to be encrypted and transmitted from a client to a server through the configuration background module; setting a planning task module, and acquiring all edited encrypted version number information at regular time through the planning task module; the method can ensure that each transmission parameter has an own encryption protocol, can also support mixed use of a plurality of encryption protocols in the same time period, adopts an asymmetric encryption protocol, ensures that the client exposes the public key and does not decrypt the data, increases the decryption difficulty of the data of the captured packet, and ensures the safety of the transmission data.
Description
Technical Field
The invention relates to the technical field of computer communication, in particular to a dynamic encryption transmission method for web data.
Background
In the domestic scheme for data transmission at the front end and the back end of the web, the protocols of most encryption schemes are relatively fixed and are easy to crack after being subjected to packet capturing. And most of the prior art uses a fixed encryption, such as DES, BASE64 in the symmetric protocol, which is easy to decrypt the original text after the attacker takes the key and the encryption type. The encrypted data is then cracked for substantially all of the time periods. According to the scheme, the multiple encryption algorithms in the same time period are mixed, and even if one algorithm is cracked, the safety of other encrypted data in the same time period can be guaranteed.
Disclosure of Invention
In order to overcome the problems, the invention aims to provide a dynamic encryption transmission method for web data, which increases the difficulty in cracking the data to be captured and packaged and ensures the safety of the transmitted data.
The invention is realized by adopting the following scheme: a web data dynamic encryption transmission method comprises the following steps:
step 1, setting a configuration background module, and editing parameter names, asymmetric encryption algorithms, public keys, private keys and encryption version number information which are required to be encrypted and transmitted from a client to a server through the configuration background module;
step 2, setting a plan task module, acquiring all edited encrypted version number information at regular time through the plan task module, saving the latest configuration edited by the configuration background module as default configuration, generating an encrypted protocol file for the configuration, and saving the encrypted protocol file at a set position for loading when a client requests a service end station;
step 3, initializing a client web page, and acquiring the encrypted protocol file from the server by the client, and loading the encrypted protocol file for analysis;
step 4, the web page submits the request data to the server, matches the request data with the parameter name in the encryption protocol file, encrypts the request data by using the asymmetric encryption algorithm and the public key corresponding to the parameter after matching the corresponding parameter name, sends the encrypted data to the server,
step 5, the server receives the encrypted data of the client and inquires corresponding encrypted version information according to the encrypted version number in the encrypted protocol file;
step 6, if the encrypted version number does not exist or the encrypted version is unavailable, returning to request failure, simultaneously taking out the latest encrypted version information from the cache and returning the latest encrypted version information to the client, wherein the encrypted version information in the cache is written by the planning task module;
and 7, the server receives the encrypted data, decrypts the data successfully, and returns a processing result of the current service request, wherein when decryption fails, decryption failure information and current default encryption version configuration are returned, the client uses the returned encryption version configuration to perform encryption request again on the original request data, and synchronously asynchronously requests the latest encryption protocol file to update the old version cached by the client.
Further, the step 7 is further specifically: step 71, receiving a response of the server, wherein if the decryption of the server is successful, the server continues to execute the corresponding service logic;
step 72, if the server side responds and returns that the decryption is failed, the client side performs a re-encryption request on the original data according to the configuration of the encrypted version in the information returned by the server side, namely, the request of the step 4 is repeatedly executed once, meanwhile, the latest encrypted protocol file is asynchronously requested, the old version cached by the client side is updated, the latest encrypted protocol file is reloaded by the client side, and the latest encrypted protocol used in the next request is ensured;
and 73, if the request of the step 4 is repeatedly executed once or fails, the request fails.
Further, the asymmetric encryption algorithm is an RSA encryption algorithm, an Elgamal encryption algorithm, a knapsack algorithm, a Rabin encryption algorithm, a D-H encryption algorithm, or an ECC encryption algorithm.
Further, the encryption protocol file comprises a parameter name to be encrypted for transmission, an asymmetric encryption algorithm and a public key corresponding to the parameter, and encryption version number information; and when the client requests data, the client encrypts the request data through the encryption protocol file to form encrypted data, and sends the encrypted data to the server.
Further, in the step 7, the server receives the encrypted data for decryption, matches the encrypted data with the parameter names in the encrypted protocol file during decryption, and decrypts the encrypted data by using the asymmetric encryption algorithm and the private key corresponding to the parameters after matching the corresponding parameter names.
Further, the server side decrypts the encrypted data according to the corresponding asymmetric encryption algorithm and the private key.
Further, step 7 is followed by: step 8, recording parameter related data of decryption failure, wherein the parameter related data comprises: and requesting the parameter name, the encrypted version number and the client ip to provide data support for subsequent optimization and analysis of the malicious attack request.
Furthermore, the plan task module is also provided with a regular execution function, randomly obtains an available configuration, automatically generates a public key and a corresponding private key, replaces the public key and the private key in the configuration one by one, generates a new encryption version number, and stores the new encryption version number in a database and a cache, so that the new encryption version number is periodically added to enlarge an encryption version library, even if data of the encryption version library is leaked at a certain time, a new encryption version is added and randomly used, and the safety is improved.
The invention has the beneficial effects that: 1) the safety of data transmission is improved; 2) the data needing to be encrypted of each version is flexibly controlled, only sensitive data are encrypted, and the decryption pressure of a server side can be reduced; 3) the states and data of the encrypted and decrypted versions are updated regularly, and a plurality of encrypted versions are supported, so that the possibility that the data in the transmission process is cracked is greatly reduced.
Drawings
FIG. 1 is a schematic flow diagram of the process of the present invention.
FIG. 2 is a method flow diagram of an embodiment of the present invention.
Detailed Description
The invention is further described below with reference to the accompanying drawings.
Referring to fig. 1, a dynamic encryption transmission method for web data according to the present invention includes the following steps:
step 1, setting a configuration background module, and editing parameter names, asymmetric encryption algorithms, public keys, private keys and encryption version number information which are required to be encrypted and transmitted from a client to a server through the configuration background module; the asymmetric encryption algorithm is an RSA encryption algorithm, an Elgamal encryption algorithm, a knapsack algorithm, a Rabin encryption algorithm, a D-H encryption algorithm or an ECC encryption algorithm.
Step 2, setting a plan task module, acquiring all edited encrypted version number information at regular time through the plan task module, saving the latest configuration edited by the configuration background module as default configuration, generating an encrypted protocol file for the configuration, and saving the encrypted protocol file at a set position for loading when a client requests a service end station;
step 3, initializing a client web page, and acquiring the encrypted protocol file from the server by the client, and loading the encrypted protocol file for analysis;
step 4, the web page submits the request data to the server, matches the request data with the parameter name in the encryption protocol file, encrypts the request data by using the asymmetric encryption algorithm and the public key corresponding to the parameter after matching the corresponding parameter name, sends the encrypted data to the server,
step 5, the server receives the encrypted data of the client and inquires corresponding encrypted version information according to the encrypted version number in the encrypted protocol file;
step 6, if the encrypted version number does not exist or the encrypted version is unavailable, returning to request failure, simultaneously taking out the latest encrypted version information from the cache and returning the latest encrypted version information to the client, wherein the encrypted version information in the cache is written by the planning task module;
and 7, the server receives the encrypted data, decrypts the data successfully, and returns a processing result of the current service request, wherein when decryption fails, decryption failure information and current default encryption version configuration are returned, the client uses the returned encryption version configuration to perform encryption request again on the original request data, and synchronously asynchronously requests the latest encryption protocol file to update the old version cached by the client.
The invention is further illustrated below with reference to a specific embodiment:
as shown in fig. 2, a dynamic encryption transmission method of web data of the present invention,
1. setting a configuration background module, and editing parameter names, asymmetric encryption algorithms and public keys corresponding to the parameters and encryption version number information which are required to be encrypted and transmitted from a client to a server through the configuration background module; the configuration module is at the beginning of the process, and a server administrator edits the name of the parameter to be encrypted, the asymmetric encryption algorithm and the public key corresponding to the parameter and the information of the encrypted version number through the configuration module. And then saved in the data. The state modification may be made to the specified encrypted version, available or unavailable. The asymmetric encryption algorithm is an RSA encryption algorithm, an Elgamal encryption algorithm, a knapsack algorithm, a Rabin encryption algorithm, a D-H encryption algorithm or an ECC encryption algorithm.
2. Setting a plan task module, acquiring all edited encrypted version number information at regular time through the plan task module, saving the latest configuration edited by the configuration background module as default configuration, generating an encryption protocol file for the configuration, and saving the encryption protocol file at a set position for loading when a client requests a service end station; using static files, rather than obtaining encrypted versions through an interface, may increase response speed and server-side pressure. And simultaneously writing into the cache for the web site to return to the client in a failure response to the client.
The planning task module stores available configuration information in a database into a cache (redis database) by reading the available configuration information, and simultaneously randomly takes an available configuration as a default configuration to generate an encryption protocol file for the configuration and store the encryption protocol file at a specified position. And 4, reading the failure condition in the step 4 by the client, reading by the server and returning to the client. In addition, the encrypted version is randomly used, so that data encryption protocols in different time periods are different, and the risk of data cracking is reduced. Meanwhile, the client of part of users can start the cache function of the browser, and different users at the same time can use encryption protocols with different version numbers.
After the processing of the above 2 links is finished, the server can normally work. Step 1, obtaining the parameter configuration information in the cache (redis) by encrypting the version number to process the subsequent flow.
The configuration module generates a configuration format of
{"Version":"1601371853","ParamsInfo":[{"ParamName":"question","Encryption Type":1,"Publickey":"-----BEGIN PUBLIC KEY-----MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCV0tWuYMoH09Fo6/x76BYam1AC XbbkfbQaLSRQ4U3qFfGoAztZ7oVGbNH57jBYrhTG7ArMj1Duu6mYysImfGbwrZXm nvPIug9GsQVrgJHgcCkAaiMGFmuSo9jlgr19KZv1gjNt2joCLN7Ewq8BV0WEepd8GCWS936Lk+qYXUDtzwIDAQAB-----END PUBLIC KEY-----"},{"ParamName":"answer","EncryptionType":1,"Publickey":"-----BEGIN PUBLIC KEY-----MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCV0tWuYMoH09Fo6/x76BYam1AC XbbkfbQaLSRQ4U3qFfGoAztZ7oVGbNH57jBYrhTG7ArMj1Duu6mYysImfGbwrZXm nvPIug9GsQVrgJHgcCkAaiMGFmuSo9jlgr19KZv1gjNt2joCLN7Ewq8BV0WEepd8GCWS936Lk+qYXUDtzwIDAQAB-----END PUBLIC KEY-----"}]}
Meanwhile, the planning task module adds a periodic execution function (once a day or once a week), randomly obtains an available configuration, automatically generates a public key and a corresponding private key, replaces the public key and the private key in the configuration one by one (the public key and the private key of each parameter are different), then generates a new encrypted version number, and stores the version number in a database and a cache. Therefore, new encrypted version numbers are added regularly to strengthen the encrypted version library, and even if data of the encrypted version library is leaked at a certain time, new encrypted versions are added and randomly used, so that the safety is improved.
The planning task module has a newly added function and also needs to add a periodically deleted version function, and the version which exceeds a certain time (which can be 1 month or half a year) is set as unavailable, so that the encrypted version is always changed and the same version cannot be used for a long time.
3. Initializing a client web page, and acquiring the encrypted protocol file from the server by the client, and loading the encrypted protocol file for analysis;
4: web page submission request phase
4.1 the web page submits the request data to the server, and traverses the request data, matches the request data with the parameter name in the encryption protocol file, and encrypts the parameters contained in the encryption protocol file by using the appointed encryption type after matching the corresponding parameter name;
4.2 replace the original value with the encrypted value (i.e. if the value of the original parameter queue is 123, after actual processing, the value sent to the server is 123 encrypted by using the corresponding public key RAS), and add the current encrypted Version number into the list of the requested data (for example, only one parameter of the queue originally requested to the server is now changed to queue, Version, and a parameter Version is added in the requested data to mark the Version number of the request, which is the Version in the encrypted protocol file)
5: the server receives the client request data, and inquires corresponding encrypted version information according to the encrypted version number in the encrypted protocol file; the encryption protocol file comprises a parameter name needing encryption transmission, an asymmetric encryption algorithm and a public key corresponding to the parameter, and encryption version number information; and when the client requests data, the client encrypts the request data through the encryption protocol file to form encrypted data, and sends the encrypted data to the server.
6: if the encrypted version number does not exist or the encrypted version is unavailable, returning the request failure, and simultaneously taking out the latest encrypted version information from the cache (written by the planning task module) and returning the latest encrypted version information to the client, wherein the encrypted version information in the cache is written by the planning task module;
7: web page acquisition server response phase
7.1 requesting the server, if the server decrypts successfully, the server will continue to execute the corresponding service logic;
7.2 if the server side fails to respond to the returned decryption, the client side performs a re-encryption request (namely, the request of the step 4 is repeated once) on the original data according to the configuration of the encrypted version in the information returned by the server side, and simultaneously asynchronously requests the latest encrypted protocol file (namely, the encrypted parameter name, the asymmetric encryption algorithm and the public key corresponding to the parameter, and the current encrypted version number), updates the old version cached by the client side, reloads the encrypted protocol file (with a random number request, the file can be cached by the browser, and the offline encrypted version is used), and ensures that the latest encrypted protocol is used in the next request. And the server receives and decrypts the encrypted data, wherein the decryption is to decrypt the encrypted data according to a corresponding asymmetric encryption algorithm and a private key.
7.3 if the request fails, the popup prompts that the request fails.
8. And recording parameter related data (request parameter name, encrypted version number, client ip and the like) which are failed in decryption, and providing data support for subsequent optimization and analysis of the malicious attack request.
In a word, each transmission parameter can have an own encryption type protocol, and can also support mixed use of multiple encryption protocols in the same time period, and the client side can not decrypt data even if a public key is exposed by adopting an asymmetric encryption protocol; the difficulty of cracking the data of the captured packet is increased, and the safety of data transmission is ensured.
The above description is only a preferred embodiment of the present invention, and all equivalent changes and modifications made in accordance with the claims of the present invention should be covered by the present invention.
Claims (8)
1. A web data dynamic encryption transmission method is characterized in that: the method comprises the following steps:
step 1, setting a configuration background module, and editing parameter names, asymmetric encryption algorithms, public keys, private keys and encryption version number information which are required to be encrypted and transmitted from a client to a server through the configuration background module;
step 2, setting a plan task module, acquiring all edited encrypted version number information at regular time through the plan task module, saving the latest configuration edited by the configuration background module as default configuration, generating an encrypted protocol file for the configuration, and saving the encrypted protocol file at a set position for loading when a client requests a service end station;
step 3, initializing a client web page, and acquiring the encrypted protocol file from the server by the client, and loading the encrypted protocol file for analysis;
step 4, the web page submits the request data to the server, matches the request data with the parameter name in the encryption protocol file, encrypts the request data by using the asymmetric encryption algorithm and the public key corresponding to the parameter after matching the corresponding parameter name, sends the encrypted data to the server,
step 5, the server receives the encrypted data of the client and inquires corresponding encrypted version information according to the encrypted version number in the encrypted protocol file;
step 6, if the encrypted version number does not exist or the encrypted version is unavailable, returning to request failure, simultaneously taking out the latest encrypted version information from the cache and returning the latest encrypted version information to the client, wherein the encrypted version information in the cache is written by the planning task module;
and 7, the server receives the encrypted data, decrypts the data successfully, and returns a processing result of the current service request, wherein when decryption fails, decryption failure information and current default encryption version configuration are returned, the client uses the returned encryption version configuration to perform encryption request again on the original request data, and synchronously asynchronously requests the latest encryption protocol file to update the old version cached by the client.
2. The dynamic encryption transmission method of web data according to claim 1, characterized in that: the step 7 is further specifically: step 71, receiving a response of the server, wherein if the decryption of the server is successful, the server continues to execute the corresponding service logic;
step 72, if the server side responds and returns that the decryption is failed, the client side performs a re-encryption request on the original data according to the configuration of the encrypted version in the information returned by the server side, namely, the request of the step 4 is repeatedly executed once, meanwhile, the latest encrypted protocol file is asynchronously requested, the old version cached by the client side is updated, the latest encrypted protocol file is reloaded by the client side, and the latest encrypted protocol used in the next request is ensured;
and 73, if the request of the step 4 is repeatedly executed once or fails, the request fails.
3. The dynamic encryption transmission method of web data according to claim 1, characterized in that: the asymmetric encryption algorithm is an RSA encryption algorithm, an Elgamal encryption algorithm, a knapsack algorithm, a Rabin encryption algorithm, a D-H encryption algorithm or an ECC encryption algorithm.
4. The dynamic encryption transmission method of web data according to claim 1, characterized in that: the encryption protocol file comprises a parameter name needing encryption transmission, an asymmetric encryption algorithm and a public key corresponding to the parameter, and encryption version number information; and when the client requests data, the client encrypts the request data through the encryption protocol file to form encrypted data, and sends the encrypted data to the server.
5. The dynamic encryption transmission method of web data according to claim 3, characterized in that: and 7, the server receives the encrypted data for decryption, matches the encrypted data with the parameter names in the encrypted protocol file during decryption, and decrypts the encrypted data by using the asymmetric encryption algorithm and the private key corresponding to the parameters after matching the corresponding parameter names.
6. The dynamic encryption transmission method of web data according to claim 5, characterized in that: and the server side decrypts the encrypted data according to the corresponding asymmetric encryption algorithm and the private key.
7. The dynamic encryption transmission method of web data according to claim 1, characterized in that: the step 7 further comprises the following steps: step 8, recording parameter related data of decryption failure, wherein the parameter related data comprises: and requesting the parameter name, the encrypted version number and the client ip to provide data support for subsequent optimization and analysis of the malicious attack request.
8. The method for dynamically encrypting and decrypting the web data based on the server side as claimed in claim 1, wherein: the plan task module is also provided with a regular execution function, randomly obtains an available configuration, automatically generates a public key and a corresponding private key, replaces the public key and the private key in the configuration one by one, generates a new encryption version number, and stores the new encryption version number in a database and a cache, so that the new encryption version number can be periodically added to strengthen the encryption version library, and even if data of the encryption version library is leaked at a certain time, a new encryption version is added and randomly used, and the safety is improved.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011136031.1A CN112202810B (en) | 2020-10-22 | 2020-10-22 | Dynamic encryption transmission method for web data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011136031.1A CN112202810B (en) | 2020-10-22 | 2020-10-22 | Dynamic encryption transmission method for web data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112202810A true CN112202810A (en) | 2021-01-08 |
| CN112202810B CN112202810B (en) | 2022-11-11 |
Family
ID=74010761
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011136031.1A Active CN112202810B (en) | 2020-10-22 | 2020-10-22 | Dynamic encryption transmission method for web data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112202810B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060129801A1 (en) * | 2003-05-20 | 2006-06-15 | Kang Kyung-Don | Method and device of data encryption |
| CN104486321A (en) * | 2014-12-11 | 2015-04-01 | 上海斐讯数据通信技术有限公司 | Web data interaction method and system and corresponding Web server |
| CN107277007A (en) * | 2017-06-14 | 2017-10-20 | 山东中创软件商用中间件股份有限公司 | A kind of data encryption and transmission method and device |
| CN108011857A (en) * | 2016-11-01 | 2018-05-08 | 北京京东尚科信息技术有限公司 | Data dynamic encryption transmission configuration method and apparatus |
| CN109639706A (en) * | 2018-12-27 | 2019-04-16 | 北京城市网邻信息技术有限公司 | A kind of request processing method, server, user terminal and system |
| US20190132120A1 (en) * | 2017-10-27 | 2019-05-02 | EMC IP Holding Company LLC | Data Encrypting System with Encryption Service Module and Supporting Infrastructure for Transparently Providing Encryption Services to Encryption Service Consumer Processes Across Encryption Service State Changes |
-
2020
- 2020-10-22 CN CN202011136031.1A patent/CN112202810B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060129801A1 (en) * | 2003-05-20 | 2006-06-15 | Kang Kyung-Don | Method and device of data encryption |
| CN104486321A (en) * | 2014-12-11 | 2015-04-01 | 上海斐讯数据通信技术有限公司 | Web data interaction method and system and corresponding Web server |
| CN108011857A (en) * | 2016-11-01 | 2018-05-08 | 北京京东尚科信息技术有限公司 | Data dynamic encryption transmission configuration method and apparatus |
| CN107277007A (en) * | 2017-06-14 | 2017-10-20 | 山东中创软件商用中间件股份有限公司 | A kind of data encryption and transmission method and device |
| US20190132120A1 (en) * | 2017-10-27 | 2019-05-02 | EMC IP Holding Company LLC | Data Encrypting System with Encryption Service Module and Supporting Infrastructure for Transparently Providing Encryption Services to Encryption Service Consumer Processes Across Encryption Service State Changes |
| CN109639706A (en) * | 2018-12-27 | 2019-04-16 | 北京城市网邻信息技术有限公司 | A kind of request processing method, server, user terminal and system |
Non-Patent Citations (3)
| Title |
|---|
| WENJUN LUO: "Public key encryption with keyword search based on factoring", 《2012 IEEE 2ND INTERNATIONAL CONFERENCE ON CLOUD COMPUTING AND INTELLIGENCE SYSTEMS》 * |
| 张红岩等: "基于动态加密算法的云端安全存储***", 《科技创新与应用》 * |
| 张鹤高等: "Web服务身份验证与数据加密传输协议的设计与实现", 《电脑与信息技术》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112202810B (en) | 2022-11-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112929172B (en) | System, method and device for dynamically encrypting data based on key bank | |
| US7890643B2 (en) | System and method for providing program credentials | |
| US6601170B1 (en) | Secure internet user state creation method and system with user supplied key and seeding | |
| EP1705871B1 (en) | Method and apparatus for distributed information management | |
| KR100455566B1 (en) | Device and method for updating code | |
| US7454021B2 (en) | Off-loading data re-encryption in encrypted data management systems | |
| US6920560B2 (en) | Secure network user states | |
| US6732277B1 (en) | Method and apparatus for dynamically accessing security credentials and related information | |
| US7496607B2 (en) | Method and system for maintaining synchronization between a local data cache and a data store | |
| US6317829B1 (en) | Public key cryptography based security system to facilitate secure roaming of users | |
| US8082316B2 (en) | Resolving conflicts while synchronizing configuration information among multiple clients | |
| US8271788B2 (en) | Software registration system | |
| JP2013511771A (en) | Method and apparatus for document sharing | |
| US20210306150A1 (en) | Computer implemented methods and systems for managing a cryptographic service | |
| CN111970109B (en) | Data transmission method and system | |
| US11321471B2 (en) | Encrypted storage of data | |
| CN112199704B (en) | Method for dynamically encrypting and decrypting web data based on server | |
| CN110830239B (en) | Key updating method, device and system | |
| CN111010408B (en) | Distributed encryption and decryption method and system | |
| CN112199703B (en) | Web data dynamic encryption transmission method and system based on client | |
| CN112202810B (en) | Dynamic encryption transmission method for web data | |
| CN111177736A (en) | System, method and device for data storage and access | |
| CN111679854B (en) | Version control method, device and system of software product | |
| CN116436647A (en) | Information encryption method and terminal | |
| CN115529139A (en) | Object serialization-based online software encryption authorization system and method |
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 |