CN112152799B - Secret source normalization mechanism for multimode executive encryption application - Google Patents
Secret source normalization mechanism for multimode executive encryption application Download PDFInfo
- Publication number
- CN112152799B CN112152799B CN202010899528.2A CN202010899528A CN112152799B CN 112152799 B CN112152799 B CN 112152799B CN 202010899528 A CN202010899528 A CN 202010899528A CN 112152799 B CN112152799 B CN 112152799B
- Authority
- CN
- China
- Prior art keywords
- random value
- scheduler
- encryption key
- number information
- secret source
- 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.)
- Active
Links
Images
Classifications
-
- 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/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
-
- 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/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
- H04L9/0869—Generation of secret information including derivation or calculation of cryptographic keys or passwords involving random numbers or seeds
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Storage Device Security (AREA)
Abstract
The invention provides a secret source normalization mechanism for multimode executor encryption application. The dense source normalization mechanism includes: the method comprises the steps that a scheduler receives requests for applying for a secret source sent by each executive body, wherein the secret source refers to parameter information influencing encryption; and the scheduler returns the same secret source to different executors according to the secret source type of the request and the secret source synchronous flow corresponding to each secret source type so as to ensure that the encrypted cryptographs of the executors are consistent. The invention designs a secret source normalization mechanism by analyzing the reason of causing the inconsistent encryption application performance of the multimode executive body, so that the multimode executive body uniformly applies secret source information such as random values, encryption keys, byte numbers and the like to the scheduler, and normalizes the secret sources, thereby ensuring that the cryptographs generated by different executive bodies are consistent in performance, solving the problem of inconsistent encryption application performance in the multimode executive body and being beneficial to the arbitration judgment of the scheduler.
Description
Technical Field
The invention relates to the technical field of network security, in particular to a secret source normalizing mechanism for multimode executor encryption application.
Background
How to construct a safe and reliable system according to toxic and bacteria-carrying devices, wujiang xing and the like propose a mimicry defense idea, a dynamic heterogeneous redundancy idea is adopted to break the similarity determination static execution environment which is commonly relied on by vulnerability utilization, a specific model is shown in figure 1, external input is distributed to heterogeneous executors through an input agent, the heterogeneous executors execute the same task and send the result to a scheduler, the scheduler adopts a large number of strategies such as arbitration to arbitrate the execution result, and finally an output result which is considered to be correct is generated, the scheduler can perform corresponding feedback control according to the performance of each executor, if a certain executor generates errors, the executor is cleaned, and is added into a work queue after the cleaner is cleaned, and arbitration related parameters and system operation state information can be controlled and checked through a feedback controller.
Although a mimicry system can effectively defend against known or unknown bugs/backdoor attacks, some encryption protocols (such as SSH and the like) can generate different encryption results on different executors, even if the same processor and the same operating system are used, the same encryption protocol is run, and the encrypted ciphertexts are completely different by using the same plaintext, so that the scheduler can fail to judge, and an effective method for solving the problem is not available at present.
Disclosure of Invention
Aiming at the problem that different encryption results can be generated by different executors in some encryption protocols so as to cause the judgment failure of a scheduler, the invention provides a secret source normalization mechanism for multimode executor encryption application.
The invention provides a secret source normalizing mechanism for multimode executor encryption application, which comprises the following steps:
the method comprises the steps that a scheduler receives requests for applying for a secret source sent by each executive body, wherein the secret source refers to parameter information influencing encryption;
and the scheduler returns the same secret source to different executors according to the secret source type of the request and the secret source synchronous flow corresponding to each secret source type so as to ensure that the encrypted cryptographs of the executors are consistent.
Further, the secret source includes: random value, encryption key parameter and byte number of return message; correspondingly, the dense source synchronization process includes: a random value synchronization process, an encryption key parameter synchronization process and a byte number synchronization process.
Further, at the executive body end, the random value synchronization process includes:
step A1.1: when a random value is required to be used in a protocol, sending a random value application request to a scheduler, wherein the random value application request carries executive body number information, process number information, protocol number information and session number information;
step A1.2: and receiving the random value sent by the scheduler, and continuously operating the corresponding protocol process according to the random value.
Further, at the scheduler end, the random value synchronization procedure includes:
step B1.1: waiting for receiving a random value application request of an executive body, wherein the random value application request carries executive body number information, process number information, protocol number information and conversation number information;
step B1.2: after receiving the random value application request, judging whether random value information which is the same as the process number information, the protocol number information and the session number information carried by the current random value application request is stored, if so, executing the step B1.3; if not, executing the step B1.4;
step B1.3: sending the random value corresponding to the stored random value information to the corresponding executive body, and continuing to execute the step B1.5;
step B1.4: generating and managing random value information, generating a random value corresponding to the random value information at the same time, sending the random value to a corresponding execution body, storing the random value, and continuing to execute the step B1.5;
step B1.5: judging whether random value application requests of all executors are received or not, and if so, deleting the stored random value information; if not, returning to the step B1.1.
Further, at the executive body end, the encryption key parameter synchronization process includes:
step A2.1: when a key is generated in a protocol, sending an encryption key parameter application request to a scheduler, wherein the encryption key parameter application request carries execution body number information, process number information, protocol number information, session number information and encryption key parameters;
step A2.2: and receiving the encryption key parameters sent by the scheduler, and continuing to operate the corresponding protocol process according to the encryption key parameters.
Further, at the scheduler, the encryption key parameter synchronization process includes:
step B2.1: waiting for receiving an encryption key parameter application request of an executive, wherein the encryption key parameter application request carries executive number information, process number information, protocol number information, session number information and encryption key parameters;
step B2.2: after receiving the encryption key parameter application request, judging whether the encryption key parameter application request is received for the first time, if so, executing a step B2.3; if not, executing the step B2.4;
step B2.3: storing the number information of the executive body and the encryption key parameter, sending the encryption key parameter to the corresponding executive body, and continuing to execute the step B2.5;
step B2.4: sending the stored encryption key parameters to the corresponding executive body, and continuing to execute the step B2.5;
step B2.5: judging whether encryption key application requests of all executives are received or not, and if so, deleting the stored encryption key parameters; if not, returning to the step B2.1.
Further, at the execution body end, the byte number synchronization flow includes:
step A3.1: before the byte number of the returned message, sending a byte number application request to a scheduler, wherein the byte number application request carries execution body number information, process number information, protocol number information, session number information and byte number;
step A3.2: receiving the byte number sent by the scheduler, and continuing to operate the corresponding protocol process according to the byte number.
Further, at the scheduler end, the byte number synchronization process includes:
step B3.1: waiting for receiving a byte number application request of an execution body, wherein the byte number application request carries execution body number information, process number information, protocol number information, session number information and byte number;
step B3.2: recording the number information and the number of bytes of the execution after receiving the byte number application request;
step B3.3: judging whether byte number application requests of all executive bodies under the corresponding process number, the corresponding protocol number and the corresponding conversation number are received or not, if so, executing a step B3.4; if not, returning to the step B3.1;
step B3.4: comparing the byte numbers of all the execution bodies, determining the minimum value of the byte numbers, modifying the byte number of the execution body of which the byte number is not the minimum value to be the minimum value, and managing the remaining byte number to be sent; the minimum number of bytes is then sent to all executors.
The invention has the beneficial effects that:
according to the invention, through analyzing the reason of causing the inconsistent encryption application performance of the multi-mode executive body, a secret source normalization mechanism is designed, so that the multi-mode executive body uniformly applies secret source information such as a random value, an encryption key, byte number and the like to a scheduler, and the secret sources are normalized, so that the cryptographs generated by different executive bodies are consistent in performance, the problem of inconsistent encryption application performance in the multi-mode executive body is solved, and the arbitration judgment by the scheduler is facilitated.
Drawings
FIG. 1 is a schematic diagram of a proposed defense system provided in the prior art;
fig. 2 is a schematic flowchart of a secret source normalization mechanism for a multi-mode executable encryption application according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a process of synchronizing random values of an executive body according to an embodiment of the present invention;
fig. 4 is a schematic diagram illustrating a random value synchronization process at a scheduler according to an embodiment of the present invention;
fig. 5 is a schematic diagram illustrating a parameter synchronization process of an encryption key of an executive end according to an embodiment of the present invention;
fig. 6 is a schematic diagram illustrating an encryption key parameter synchronization process at a scheduler according to an embodiment of the present invention;
FIG. 7 is a schematic diagram illustrating a byte number synchronization process of an execution body end according to an embodiment of the present invention;
fig. 8 is a schematic diagram illustrating a byte number synchronization process at a scheduler according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1
As shown in fig. 2, an embodiment of the present invention provides a secret source normalizing mechanism for a multimode executable encryption application, including the following steps:
s201: the method comprises the steps that a scheduler receives requests for applying for a secret source sent by each executive body, wherein the secret source refers to parameter information influencing encryption;
specifically, in this embodiment, the secret source includes: random value, encryption key parameter and byte number of return message;
s202: and the scheduler returns the same secret source to different executors according to the secret source type of the request and the secret source synchronous flow corresponding to each secret source type so as to ensure that the encrypted cryptographs of the executors are consistent.
Specifically, the reason that the encryption ciphertext of each execution body is usually inconsistent is that the encryption sources are inconsistent, and as long as the encryption sources of each execution body can be unified, the problem that the encryption ciphertext of the multi-mode execution body is inconsistent can be solved. In the embodiment of the present invention, based on the above concept principle, when the encryption application on the execution entity needs to use different types of secret sources in the process of running the protocol process, a request for applying for the secret source needs to be sent to the scheduler first, and is obtained from the scheduler in a unified manner, and then the scheduler performs a unified reply on the secret source requests of each execution entity by running different secret source synchronization flows, so that the encryption ciphertexts of each execution entity are consistent. The secret source synchronization process comprises the following steps: a random value synchronization process, an encryption key parameter synchronization process and a byte number synchronization process.
Example 2
On the basis of the above embodiment 1, an embodiment of the present invention provides another secret source normalization mechanism for multimode executor encryption application, where the mechanism mainly performs normalization for a random value application, and includes the following steps:
as shown in fig. 3, at the execution body end, the random value synchronization process includes:
s301: when a random value is required to be used in a protocol, sending a random value application request to a scheduler, wherein the random value application request carries executive body number information, process number information, protocol number information and session number information;
specifically, the executable number refers to a unique number of each executable; the protocol numbers are used for distinguishing different protocol types, and the protocol types suitable for the embodiment of the invention comprise an SSH protocol and an SNMP protocol; a protocol can start a plurality of processes, and the process number refers to the unique number of each process; a process may include multiple sessions, with a session number referring to a unique number for each session.
S302: and receiving the random value sent by the scheduler, and continuously operating the corresponding protocol process according to the random value.
As shown in fig. 4, at the scheduler, the random value synchronization process includes:
s401: waiting for receiving a random value application request of an executive body, wherein the random value application request carries executive body number information, process number information, protocol number information and conversation number information;
s402: after receiving the random value application request, judging whether random value information which is the same as the process number information, the protocol number information and the session number information carried by the current random value application request is stored, if so, executing a step S403; if not, go to step S404;
s403: sending the random value corresponding to the stored random value information to the corresponding executive body, and continuing S405;
s404: generating and managing random value information, generating a random value corresponding to the random value information, sending the random value to a corresponding execution body, storing the random value, and continuing to execute the step S405;
s405: judging whether random value application requests of all executors are received or not, and if so, deleting the stored random value information; if not, the process returns to step S401.
Specifically, the random value application is used to solve a situation that a part of messages in a protocol carries random values or a part of parameters in the messages are generated and used to generate random values, such as an SSH protocol and an SNMP protocol. Generally, there are multiple instances or connections for encryption application, for example, SSH can establish multiple connections at the same time, so in the process of requesting for a secret source, it is necessary to consider distinguishing the secret sources of different connection applications, and when requesting for a secret source, corresponding identifiers are attached, and it is necessary to distinguish different protocols, and typical identifiers include an execution body number, a protocol number, a session number, and a byte number for requesting. In the embodiment of the invention, when the random value is required to be used in the protocol, the random value is not generated from a local random function, but a random value application message with an execution body number, a protocol number, a session number and an application byte number is sent to a scheduler.
It should be noted that, after the random value applied by the protocol in the executable is used up, the random value is applied to the scheduler in the same manner according to the above flow, and the scheduler regenerates and manages in the same manner, thereby ensuring the consistency of the random values used by all the executable.
Example 3
Some protocols in the protocol stack send messages encrypted by keys, the generation process of the keys needs to call functions in the packaged library, random values are used for generating the keys, and encryption key parameters are synchronously used for solving the problem that the keys of different execution bodies are different, such as an SSH protocol and an SNMP protocol.
On the basis of the above embodiments, the present invention provides another secret source normalization mechanism for multimode executable encryption application, where the mechanism mainly performs normalization on encryption key parameters, and includes the following steps:
as shown in fig. 5, at the executive body end, the encryption key parameter synchronization process includes:
s501: when a key is generated in a protocol, sending an encryption key parameter application request to a scheduler, wherein the encryption key parameter application request carries execution body number information, process number information, protocol number information, session number information and encryption key parameters;
s502: and receiving the encryption key parameters sent by the scheduler, and continuing to operate the corresponding protocol process according to the encryption key parameters.
Specifically, when multiple encryption key parameters are needed in the protocol process, after the synchronized encryption key parameters are received, it is further determined whether all the multiple encryption key parameters have been completed synchronously, if not, the encryption key parameter application request is sent again, and if all the encryption key parameters have been completed synchronously, the corresponding protocol process continues to be operated.
As shown in fig. 6, at the scheduler, the encryption key parameter synchronization process includes:
s601: waiting for receiving an encryption key parameter application request of an executive, wherein the encryption key parameter application request carries executive number information, process number information, protocol number information, session number information and encryption key parameters;
s602: after receiving the encryption key parameter application request, judging whether the encryption key parameter application request is received for the first time, if so, executing the step S603; if not, go to step S604;
specifically, the scheduling end stores application records of each execution entity, so that it can be determined whether the encryption key parameter application of the process number, the protocol number and the session number is received for the first time by querying the records: if the original record does not have the encryption key parameter application request corresponding to the protocol number, the process number and the session number, the request is considered to be received for the first time; otherwise, it is not the first time.
S603: storing the number information of the executive body and the encryption key parameter, sending the encryption key parameter to the corresponding executive body, and continuing to execute the step S605;
s604: sending the stored encryption key parameter to the corresponding executive body, and continuing to execute the step S605;
s605: judging whether encryption key application requests of all executives are received or not, and if so, deleting the stored encryption key parameters; if not, the process returns to step S601.
Specifically, in this embodiment, the scheduler only stores the encryption key parameter of the first received executable, and sends the key parameter back to the requesting executable, and when other executors request the corresponding encryption key parameter, the scheduler sends the received key parameter of the first executable to the other executors, and the requests for other encryption key parameters all send the key parameter information of the first received executable.
For example, the system includes 3 execution blocks in total: an execution 1, an execution 2, and an execution 3. The scheduler receives the encryption key parameters of the executive body 2 for the first time, and the encryption key parameters sent to the three executive bodies are all the encryption key parameters of the executive body 2; in the subsequent process, the scheduler sends the encryption key parameters received from the execution entity 2 for the other encryption key parameters applied by each execution entity, so as to ensure the consistency of the encryption key parameters generated by the three execution entities.
Example 4
The management software (such as SSH) sends corresponding configuration according to a user query function executive body, because the processing performance of each heterogeneous processor is different, the number of bytes of a plaintext message sent back to a query user each time is different, and for a message transmitted by a ciphertext, the number of bytes sent by the plaintext message is different, so that the content and the length of the encrypted message are possibly different, and the judgment of a scheduler is failed, therefore, the protocol needs to synchronize the number of bytes sent to the scheduler before the number of bytes are sent.
On the basis of each embodiment of the embodiment, the embodiment of the invention provides another secret source normalization mechanism for multimode executor encryption application, which mainly performs normalization aiming at the number of bytes, and comprises the following steps:
as shown in fig. 7, at the execution entity, the byte number synchronization process includes:
s701: before the byte number of the returned message, sending a byte number application request to a scheduler, wherein the byte number application request carries execution body number information, process number information, protocol number information, session number information and byte number;
s702: receiving the byte number sent by the scheduler, and continuing to operate the corresponding protocol process according to the byte number.
As shown in fig. 8, at the scheduler end, the byte number synchronization process includes:
s801: waiting for receiving a byte number application request of an execution body, wherein the byte number application request carries execution body number information, process number information, protocol number information, session number information and byte number;
s802: recording the information of the execution body number and the byte number after receiving the byte number application request;
s803: judging whether byte number application requests of all executables under the corresponding process numbers, the corresponding protocol numbers and the corresponding session numbers are received or not, if so, executing step S804; if not, returning to the step S801;
s804: comparing the byte number of all the execution bodies, determining the minimum value of the byte number, modifying the byte number of the execution body of which the byte number is not the minimum value to be the minimum value, and managing the residual byte number to be sent; the minimum number of bytes is then sent to all executors.
Specifically, managing the number of bytes remaining to be sent (i.e., the execution block whose number of bytes is not the minimum value) refers to: and subtracting the minimum value of the number of bytes from the original number of bytes of the execution body to obtain the remaining number of bytes to be sent of the execution body, and then issuing at a proper time.
The invention designs a secret source normalization mechanism by analyzing the reason of causing the inconsistent performance of the encryption application, so that the multimode executive system applies secret source information such as random values, encryption keys, byte numbers and the like to the scheduler, and normalizes the secret sources, thereby ensuring that the cryptographs generated by different executors are consistent in performance, solving the problem of inconsistent performance of the encryption application in the multimode executive system and being beneficial to the scheduler to carry out arbitration judgment.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (3)
1. The secret source normalization mechanism facing the multimode executive encryption application is characterized by comprising the following steps:
the method comprises the steps that a scheduler receives requests for applying for a secret source sent by each executive body, wherein the secret source refers to parameter information influencing encryption;
the scheduler returns the same secret source to different executors according to the secret source type of the request and the secret source synchronous flow corresponding to each secret source type so as to enable the encrypted cryptograph of each executer to be consistent;
the dense source synchronization process specifically includes: a secret source synchronization flow at an execution side and a secret source synchronization flow at a dispatcher side;
the secret source is a random value; correspondingly, the secret source synchronization process at the execution body end is referred to as a random value synchronization process at the execution body end, and specifically includes:
step A1.1: when a random value is required to be used in a protocol, sending a random value application request to a scheduler, wherein the random value application request carries execution body number information, process number information, protocol number information and conversation number information;
step A1.2: receiving a random value sent by the scheduler, and continuously operating a corresponding protocol process according to the random value;
the dense source synchronization process at the scheduler end is referred to as a random value synchronization process at the scheduler end, and specifically includes:
step B1.1: waiting for receiving a random value application request of an executive;
step B1.2: after receiving the random value application request, judging whether random value information which is the same as the process number information, the protocol number information and the session number information carried by the current random value application request is stored, if so, executing a step B1.3; if not, executing the step B1.4;
step B1.3: sending the random value corresponding to the stored random value information to the corresponding executive body, and continuing to execute the step B1.5;
step B1.4: generating and managing random value information, generating a random value corresponding to the random value information at the same time, sending the random value to a corresponding execution body, storing the random value, and continuing to execute the step B1.5;
step B1.5: judging whether random value application requests of all executors are received or not, and if so, deleting the stored random value information; if not, returning to the step B1.1.
2. The secret source normalization mechanism of claim 1, wherein the secret source is an encryption key parameter; correspondingly, the secret source synchronization process at the executive body end is called as an encryption key parameter synchronization process at the executive body end, and specifically comprises the following steps:
step A2.1: when a key is generated in a protocol, sending an encryption key parameter application request to a scheduler, wherein the encryption key parameter application request carries execution body number information, process number information, protocol number information, session number information and encryption key parameters;
step A2.2: receiving an encryption key parameter sent by the scheduler, and continuing to run a corresponding protocol process according to the encryption key parameter;
the secret source synchronization process at the scheduler end is referred to as an encryption key parameter synchronization process at the scheduler end, and specifically includes:
step B2.1: waiting for receiving an encryption key parameter application request of an executive body;
step B2.2: after receiving the encryption key parameter application request, judging whether the encryption key parameter application request is received for the first time, if so, indicating that no corresponding encryption key application request exists, and executing the step B2.3; if not, executing the step B2.4;
step B2.3: storing the number information of the executive body and the encryption key parameter, sending the encryption key parameter to the corresponding executive body, and continuing to execute the step B2.5;
step B2.4: sending the stored encryption key parameters to the corresponding executive bodies, and continuing to execute the step B2.5;
step B2.5: judging whether encryption key application requests of all executives are received or not, and if so, deleting the stored encryption key parameters; if not, returning to the step B2.1.
3. The secret source normalization mechanism facing the multimode executive encryption application is characterized by comprising the following steps:
the method comprises the steps that a scheduler receives requests for applying for a secret source sent by each executive body, wherein the secret source is the byte number of a returned message;
the scheduler returns the same cipher source to different executives according to the byte number synchronous flow so as to ensure that the encrypted ciphertexts of each executor are consistent;
at the execution end, the byte number synchronization process includes:
step A3.1: before the byte number of the returned message, sending a byte number application request to a scheduler, wherein the byte number application request carries execution body number information, process number information, protocol number information, session number information and byte number;
step A3.2: receiving the byte number sent by the scheduler, and continuously operating a corresponding protocol process according to the byte number;
at the scheduler end, the byte number synchronization process includes:
step B3.1: waiting for receiving a byte number application request of an execution body, wherein the byte number application request carries execution body number information, process number information, protocol number information, session number information and byte number;
step B3.2: recording the number information and the number of bytes of the execution after receiving the byte number application request;
step B3.3: judging whether byte number application requests of all executors under the corresponding process numbers, the corresponding protocol numbers and the corresponding session numbers are received or not, if so, executing the step B3.4; if not, returning to the step B3.1;
step B3.4: comparing the byte numbers of all the execution bodies, determining the minimum value of the byte numbers, modifying the byte number of the execution body of which the byte number is not the minimum value to be the minimum value, and managing the remaining byte number to be sent; the minimum number of bytes is then sent to all executors.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010899528.2A CN112152799B (en) | 2020-08-31 | 2020-08-31 | Secret source normalization mechanism for multimode executive encryption application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010899528.2A CN112152799B (en) | 2020-08-31 | 2020-08-31 | Secret source normalization mechanism for multimode executive encryption application |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112152799A CN112152799A (en) | 2020-12-29 |
| CN112152799B true CN112152799B (en) | 2022-11-18 |
Family
ID=73890322
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010899528.2A Active CN112152799B (en) | 2020-08-31 | 2020-08-31 | Secret source normalization mechanism for multimode executive encryption application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112152799B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115225311B (en) * | 2022-05-20 | 2023-07-21 | 中国人民解放军战略支援部队信息工程大学 | Pseudo bracket ciphertext proxy method and system based on openSSL transformation |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1916838A (en) * | 2005-08-16 | 2007-02-21 | 国际商业机器公司 | Random number generator and method for generating random number seed |
| CN110162983A (en) * | 2019-04-25 | 2019-08-23 | 中国人民解放军战略支援部队信息工程大学 | The device and method of consistent encryption and decryption result is obtained in synchronizing redundant system |
| CN110176988A (en) * | 2019-04-25 | 2019-08-27 | 中国人民解放军战略支援部队信息工程大学 | Guarantee that redundancy executes body and encrypts the consistent device and method of behavior |
| KR20200039979A (en) * | 2018-10-08 | 2020-04-17 | 세종대학교산학협력단 | Apparatus and method for order-revealing encryption |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8990569B2 (en) * | 2008-12-03 | 2015-03-24 | Verizon Patent And Licensing Inc. | Secure communication session setup |
-
2020
- 2020-08-31 CN CN202010899528.2A patent/CN112152799B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1916838A (en) * | 2005-08-16 | 2007-02-21 | 国际商业机器公司 | Random number generator and method for generating random number seed |
| KR20200039979A (en) * | 2018-10-08 | 2020-04-17 | 세종대학교산학협력단 | Apparatus and method for order-revealing encryption |
| CN110162983A (en) * | 2019-04-25 | 2019-08-23 | 中国人民解放军战略支援部队信息工程大学 | The device and method of consistent encryption and decryption result is obtained in synchronizing redundant system |
| CN110176988A (en) * | 2019-04-25 | 2019-08-27 | 中国人民解放军战略支援部队信息工程大学 | Guarantee that redundancy executes body and encrypts the consistent device and method of behavior |
Non-Patent Citations (2)
| Title |
|---|
| SADIA SYED等.Novel Data Storage and Retrieval in Cloud Database by using Frequent Access Node Encryption.《2014 International Conference on Contemporary Computing and Informatics (IC3I)》.2015, * |
| 杨萍等.Kerberos协议的安全分析及对策研究.《计算机工程》.2015,(第05期), * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112152799A (en) | 2020-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110545260B (en) | Cloud management platform construction method based on mimicry structure | |
| CN110321695B (en) | Big data system password service method and device | |
| US9817657B2 (en) | Integrated software development and deployment architecture and high availability client-server systems generated using the architecture | |
| CN112242923A (en) | System and method for realizing unified data management network function based on mimicry defense | |
| CN109951546B (en) | Transaction request processing method, device, equipment and medium based on intelligent contract | |
| CN111061685A (en) | Log query method and device, node equipment and storage medium | |
| AU2013277539A1 (en) | Network based management of protected data sets | |
| CN112152799B (en) | Secret source normalization mechanism for multimode executive encryption application | |
| KR20180027323A (en) | System and method for authenticating critical operations on solid-state drives | |
| JP6403803B2 (en) | Routing method for transferring task instructions between computer systems, computer network infrastructure, and computer program | |
| CN115941182A (en) | Method, computing device and storage medium for network key update | |
| US8112629B2 (en) | Stateless challenge-response protocol | |
| Dodis et al. | End-to-End Encrypted Zoom Meetings: Proving Security and Strengthening Liveness | |
| WO2024017274A1 (en) | Virtual machine cloning method and apparatus, and storage medium | |
| Corin et al. | A secure compiler for session abstractions | |
| CN111400743B (en) | Transaction processing method, device, electronic equipment and medium based on blockchain network | |
| US10158486B1 (en) | Synchronization of key management services with cloud services | |
| WO2024040846A1 (en) | Data processing method and apparatus, electronic device, and storage medium | |
| CN108347471B (en) | Method, device and system for acquiring third-party user information | |
| CN115766064A (en) | Password application method, device, equipment and storage medium | |
| US20230359642A1 (en) | Method, devices and system for data exchange between a distributed database system and devices | |
| WO2018028359A1 (en) | Service processing method and device, and storage medium and electronic device | |
| US20160142422A1 (en) | System for cross-host, multi-thread session alignment | |
| Unruh | Termination-insensitive computational indistinguishability (and applications to computational soundness) | |
| CN116192853B (en) | Multi-cluster management 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 |