CN113364580B - Key management server, client, key distribution method, and key acquisition method - Google Patents
Key management server, client, key distribution method, and key acquisition method Download PDFInfo
- Publication number
- CN113364580B CN113364580B CN202010151870.4A CN202010151870A CN113364580B CN 113364580 B CN113364580 B CN 113364580B CN 202010151870 A CN202010151870 A CN 202010151870A CN 113364580 B CN113364580 B CN 113364580B
- Authority
- CN
- China
- Prior art keywords
- key
- identifier
- source
- plaintext
- client
- 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/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
-
- 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/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0852—Quantum cryptography
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Electromagnetism (AREA)
- Theoretical Computer Science (AREA)
- Storage Device Security (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application provides a key management server, a client, a key distribution method and a key acquisition method, wherein the client sends a key request to the key management server, the key management server receives the key request, the key management server acquires a key and an identifier of the key from a local key source, the key management server sends the identifier of the key to the client, the client receives the identifier of the key, and because the local key sources are arranged in the client and the key management server, and the local key sources at the two ends store the same corresponding relation between the key and the identifier, the client can acquire a key plaintext corresponding to the identifier from the local key source. In the application, the key management server and the client transmit the key through the identification of the key and the local key source, so that network transmission of a key plaintext is avoided, leakage of the key plaintext is avoided, and safety of the key transmission process is improved.
Description
Technical Field
The present disclosure relates to the field of data encryption technologies, and in particular, to a key management server, a client, a key distribution method, and a key acquisition method.
Background
With the rapid development of internet technology, various services are gradually informationized and networked. The internet technology brings convenience to the development of various services and potential safety hazards, and the potential safety hazards can cause the sensitive data of the user to be revealed and tampered. In the present networking era, the security of data is an important issue that cannot be easily ignored.
Currently, in an internet environment, users encrypt sensitive data and manage keys using a key management service (KeyManagement Service, KMS) system. In the prior key management service system, in the process of key management, the key management service system generates a key plaintext, encrypts the key plaintext to obtain a key ciphertext, and finally transmits the key plaintext and the key ciphertext to a user through a network. However, the key management service system transmits the key plaintext to the user through the network, and there is a possibility that the key plaintext is leaked.
Disclosure of Invention
The application provides a key management server, a client, a key distribution method and a key acquisition method, and aims to solve the problem that a key management service system has a key plaintext in the key management process.
In order to achieve the above object, the present application provides the following technical solutions:
a key management server, comprising:
a key source and a first processor;
the first processor is configured to request a key from the key source if a key request is received;
the key source is used for generating a key according to the request of the first processor and sending the key and the identification of the key to the first processor;
the first processor is further configured to send the identifier of the key to a key requester, where the key source and the key source of the key requester configure the same correspondence between the key and the identifier.
Optionally, in the above key management server, the first processor is further configured to:
generating a master key;
encrypting the key by using the master key to generate a key ciphertext;
and sending the key ciphertext to a key requester.
Optionally, in the above key management server, the key source includes:
a quantum key distribution device.
A client, comprising:
a key source and a second processor;
the second processor is configured to obtain, when receiving an identifier of a key, a key plaintext corresponding to the identifier from the key source, where the key source and a key source of the identifier sender configure the same correspondence between the key and the identifier.
Optionally, in the above client, the second processor is further configured to:
and receiving a key ciphertext sent by the identification sender, wherein the key ciphertext is generated by encrypting a key corresponding to the identification by using the master key.
Optionally, in the above client, the key source includes:
a quantum key distribution device.
A key distribution method, comprising:
under the condition that a key request is received, a key management server acquires a key and an identifier of the key from a local key source;
the key management server sends the identification of the key to a key requester; and the local key source and the key source of the key requester are configured with the same corresponding relation between the key and the identifier.
Optionally, in the above key distribution method, the method further includes:
the key management server generates a master key; encrypting the key by using the master key to generate a key ciphertext; and transmitting the key ciphertext to the key requester.
A key acquisition method comprising:
the client receives the identification of the key;
the client acquires a key plaintext corresponding to the identifier from a local key source; and configuring the corresponding relation between the same key and the identifier in the local key source and the key source of the identifier sender of the key.
Optionally, in the above key obtaining method, the method further includes:
and the client receives the key ciphertext sent by the identifier sender, and the key ciphertext is generated by encrypting the key corresponding to the identifier by using the master key.
The key management server, the client, the key distribution method and the key acquisition method provided by the application, wherein the client sends a key request to the key management server, the key management server receives the key request and acquires the key and the identifier of the key from the local key source, the key management server sends the identifier of the key to the client, and the client receives the identifier of the key. In the application, the key management server and the client transmit the key through the identification of the key and the local key source, so that network transmission of a key plaintext is avoided, leakage of the key plaintext is avoided, and safety of the key transmission process is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic structural diagram of a key management server according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a client according to an embodiment of the present application;
fig. 3 is a schematic flow chart of a key distribution method according to an embodiment of the present application;
fig. 4 is a flow chart of another key distribution method according to an embodiment of the present application;
fig. 5 is a schematic flow chart of a key obtaining method according to an embodiment of the present application;
fig. 6 is a flowchart of another key obtaining method according to an embodiment of the present application;
fig. 7 is a schematic flow chart of data encryption by a client using a key management service system according to an embodiment of the present application;
fig. 8 is a schematic flow chart of a client decrypting encrypted data using a key management service system according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
Fig. 1 shows a schematic structure of a key management server, which includes:
a key source 100 and a first processor 200.
The information interaction process between the key source 100 and the first processor 200 includes:
s101: the first processor 200 generates a master key upon receiving a key request transmitted by a key requester.
S102: the first processor 200 requests a key from the key source 100.
S103: the key source 100 generates a key according to a request of the first processor 200.
S104: the key source 100 sends a key and an identification of the key to the first processor 200.
S105: the first processor 200 receives the key and an identification of the key and encrypts the key using the master key to generate a key ciphertext.
S106: the first processor 200 sends the identity of the key to the key requester, while also sending the key ciphertext to the key requester.
The key source 100 and the key source of the key requester are configured with the same correspondence between the key and the identifier. Thus, the key requester can obtain the key corresponding to the identification from its own key source based on the identification generated by the key source 100.
It should be noted that, the key requester finally receives the key ciphertext and the key identifier sent by the first processor 200. In the network transmission process of the key requester and the first processor 200, the key is transmitted in the form of ciphertext, so that the disclosure of the plaintext of the key can be avoided, and the security of the key transmission process is improved.
Alternatively, in embodiments of the present application, key source 100 includes, but is not limited to, a quantum key distribution (quantum key distribution, QKD) device.
Specifically, the client, as a key requester, transmits a key request to the first processor 200. After receiving the key request, the first processor 200 generates a master key and sends the key request to the key source 100. After receiving the key request sent by the first processor 200, the key source 100 generates a key and sends the key and the identity of the key to the first processor 200. After receiving the key and the identity of the key, the first processor 200 encrypts the key using the master key, generates a key ciphertext, and destroys the key. Finally, the first processor 200 sends the key ciphertext and the identity of the key to the client. When the client encrypts the data, the client acquires a key plaintext corresponding to the identifier from a key source according to the identifier, encrypts the data according to the key plaintext, and then destroys the key plaintext.
It should be noted that the foregoing specific implementation is merely illustrative.
In the embodiment of the application, the first processor generates a master key and requests a key from a key source when receiving a key request sent by a key requester. The key source generates a key according to the request of the first processor and sends the key and the identification of the key to the first processor. The first processor receives the key and an identification of the key and encrypts the key using the master key to generate a key ciphertext. The first processor sends the identity of the key to the key requester, while also sending the key ciphertext to the key requester. Because the local key sources are arranged in the key management server and the key requester, and the local key sources of the key management server and the key requester store the same corresponding relation between the key and the identifier, the key requester can acquire the key plaintext corresponding to the identifier from the local key sources. In the method, the key is transmitted between the key management server and the key requester through the identification of the key and the local key source, so that network transmission of a key plaintext is avoided, leakage of the key plaintext is avoided, and safety of the key transmission process is improved.
Fig. 2 shows a schematic structural diagram of a client, the client comprising:
a key source 300 and a second processor 400.
The information interaction process between the key source 300 and the second processor 400 includes:
s201: the second processor 400 generates a key request based on the identification in case of receiving the identification identifying the key transmitted by the sender.
S202: the second processor 400 sends the key request to the key source 300.
S203: the key source 300 receives the key request and sends the key plaintext corresponding to the identification to the second processor 400.
S204: the second processor 400 receives the key plaintext corresponding to the identification and encrypts the data according to the key plaintext.
The key source 300 and the key source of the identifier sender are configured with the same correspondence between the key and the identifier.
In addition, the identifier sender sends the identifier to the second processor 400, and also sends the key ciphertext to the second processor 400. And the key ciphertext is generated by the identification sender by using a key corresponding to the master key encryption identification.
It should be noted that, the second processor 400 obtains the key plaintext corresponding to the identifier from the key source 300 according to the identifier of the key sent by the identifier sender, so as to avoid the transmission of the key in the form of plaintext in the network, thereby preventing the leakage of the key plaintext and improving the security of the key transmission process.
Alternatively, in embodiments of the present application, key source 300 includes, but is not limited to, a quantum key distribution device.
Specifically, the process of encrypting the data by the client is as follows: the second processor 400 sends a key request to the identity sender, the identity sender receives the key request, generates a master key, generates a key and an identity of the key according to the key request, and secondly, the identity sender encrypts the key by using the master key to obtain a key ciphertext. The identity sender then sends the identity of the key and the key ciphertext to the second processor 400. When the second processor 400 encrypts data, the second processor 400 transmits a key request to the key source 300, acquires a key plaintext corresponding to the identifier transmitted by the identifier transmitter from the key source 300 according to the key request, thereby encrypting the data using the key plaintext, and then destroys the key plaintext.
The process of decrypting the encrypted data by the client is as follows: the second processor 400 transmits the encrypted data, as well as the locally stored key ciphertext, to a sender of the key ciphertext (i.e., the identity sender, which may be specifically a server). The server decrypts the key ciphertext by using the master key stored by the server to obtain a key plaintext. The server decrypts the encrypted data by using the key plaintext to obtain the data plaintext, and sends the data plaintext to the user. Therefore, in the process of decrypting the encrypted data by the client, the secret key is transmitted in the network in the form of ciphertext, so that the leakage of the plaintext of the secret key can be prevented, and the safety of the secret key transmission process is improved.
It should be noted that the foregoing specific implementation is merely illustrative.
In the embodiment of the application, when receiving the identifier of the key sent by the identifier sender, the second processor obtains a key plaintext corresponding to the identifier from the key source, and encrypts data by using the key plaintext. Because the local key sources are arranged in the identifier sender and the client, and the local key sources of the identifier sender and the client store the same corresponding relation between the key and the identifier, the client can acquire the key plaintext corresponding to the identifier from the local key sources. In the method, the key is transmitted between the identifier sender and the client through the identifier of the key and the local key source, so that network transmission of a key plaintext is avoided, leakage of the key plaintext is avoided, and safety of a key transmission process is improved.
Corresponding to the key management server provided in the embodiment of the present application, fig. 3 shows a flow chart of a key distribution method, which is applied to the key management server, and includes:
s301: the key management server obtains the key and the identity of the key from the local key source upon receipt of the key request.
Wherein the local key source includes, but is not limited to, a quantum key distribution device.
S302: the key management server sends an identification of the key to the key requester.
The local key source and the key source of the key requester are configured with the same corresponding relation between the key and the identifier.
It should be noted that, in the embodiment of the present application, the key requester includes, but is not limited to, a client.
In the embodiment of the application, the key management server obtains the key and the identifier of the key from the local key source under the condition of receiving the key request, and sends the identifier of the key to the key requester. Because the local key sources are arranged in the key management server and the key requester, and the local key sources of the key management server and the key requester store the same corresponding relation between the key and the identifier, the key requester can acquire the key plaintext corresponding to the identifier from the local key sources. In the method, the key is transmitted between the key management server and the key requester through the identification of the key and the local key source, so that network transmission of a key plaintext is avoided, leakage of the key plaintext is avoided, and safety of the key transmission process is improved.
It should be noted that, the key management server sends the key identifier to the key requester, and also sends the key ciphertext to the key requester.
Optionally, fig. 4 shows a flow chart of another key distribution method, applied to a key management server, including:
s401: and the key management server generates a master key under the condition of receiving the key request, and acquires the key and the identification of the key from the local key source.
S402: the key management server encrypts the key using the master key to generate a key ciphertext.
S403: the key management server sends the key ciphertext to the key requester.
S404: the key management server sends an identification of the key to the key requester.
In the embodiment of the application, the key management server generates a master key under the condition of receiving a key request, acquires a key and an identifier of the key from a local key source, encrypts the key by using the master key, generates a key ciphertext, sends the key ciphertext to a key requester, and sends the identifier of the key to the key requester. Because the local key sources are arranged in the key management server and the key requester, and the local key sources of the key management server and the key requester store the same corresponding relation between the key and the identifier, the key requester can acquire the key plaintext corresponding to the identifier from the local key sources. In the method, the key is transmitted between the key management server and the key requester through the identification of the key and the local key source, so that network transmission of a key plaintext is avoided, leakage of the key plaintext is avoided, and safety of the key transmission process is improved.
Corresponding to the client provided in the embodiment of the present application, fig. 5 shows a flowchart of a key obtaining method, including:
s501: the client receives an identification of the key.
S502: the client obtains a key plaintext corresponding to the identity from a local key source.
The corresponding relation between the same key and the identifier is configured in the local key source and the key source of the identifier sender of the key.
In the embodiment of the application, the client receives the identifier of the key, and obtains a key plaintext corresponding to the identifier from the local key source. Because the local key sources are arranged in the identifier sender and the client, and the local key sources of the identifier sender and the client store the same corresponding relation between the key and the identifier, the client can acquire the key plaintext corresponding to the identifier from the local key sources. In the method, the key is transmitted between the identifier sender and the client through the identifier of the key and the local key source, so that network transmission of a key plaintext is avoided, leakage of the key plaintext is avoided, and safety of a key transmission process is improved.
Optionally, fig. 6 shows a flow chart of another key acquisition method, including:
s601: the client receives an identification of the key.
S602: the client obtains a key plaintext corresponding to the identity from a local key source.
S603: the client receives the key ciphertext sent by the identification sender.
The identifier sender includes, but is not limited to, a key management server, and the key ciphertext is generated by the identifier sender by encrypting a key corresponding to the identifier by using a master key.
In the embodiment of the application, the client receives the identifier of the key, acquires the key plaintext corresponding to the identifier from the local key source, and receives the key ciphertext sent by the identifier sender. Because the local key sources are arranged in the identifier sender and the client, and the local key sources of the identifier sender and the client store the same corresponding relation between the key and the identifier, the client can acquire the key plaintext corresponding to the identifier from the local key sources. In the method, the key is transmitted between the identifier sender and the client through the identifier of the key and the local key source, so that network transmission of a key plaintext is avoided, leakage of the key plaintext is avoided, and safety of a key transmission process is improved.
When the client performs data encryption, fig. 7 shows a specific implementation manner of information interaction between the key management server 500 and the client 600, including:
s701: the client 600 transmits a key request to the key management server 500.
S702: the key management server 500 receives the key request, generates a master key, and obtains the key and an identification of the key from a local key source.
S703: the key management server 500 encrypts the key using the master key to obtain a key ciphertext.
S704: the key management server 500 transmits the identification of the key and the key ciphertext to the client 600.
S705: the client 600 obtains the key plaintext corresponding to the identification from the local key source and encrypts the data using the key plaintext.
When the client decrypts the encrypted data, fig. 8 shows a specific implementation of information interaction between the key management server 500 and the client 600, including:
s801: the client 600 transmits the encrypted data and the locally stored key ciphertext to the key management server 500.
S802: the key management server 500 decrypts the key ciphertext using the master key stored by itself to obtain the key plaintext.
S803: the key management server 500 decrypts the encrypted data using the key plaintext, resulting in the data plaintext.
S804: the key management server 500 sends the data plaintext to the user.
In the embodiment of the application, the client sends the key request to the key management server, the key management server receives the key request, and acquires the key and the identifier of the key from the local key source, the key management server sends the identifier of the key to the client, and the client receives the identifier of the key. In the application, the key management server and the client transmit the key through the identification of the key and the local key source, so that network transmission of a key plaintext is avoided, leakage of the key plaintext is avoided, and safety of the key transmission process is improved.
In the above embodiments, the interaction between the key management server and the client is merely an example, and in practice, the key management server and the client are not necessarily interaction devices of each other, and the interaction with the client can be implemented as long as the interaction devices are the same as the function of the key management server. Also, the above-described interaction with the key management server can be achieved as long as the function is the same as that of the client.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (6)
1. A key management server, comprising:
a key source and a first processor;
the first processor is used for generating a master key and requesting a key from the key source under the condition of receiving a key request;
the key source is used for generating a key according to the request of the first processor and sending the key and the identification of the key to the first processor;
the first processor is further configured to encrypt the key by using the master key, generate a key ciphertext, send the key ciphertext and the identifier of the key to a key requester, configure the same correspondence between the key and the identifier in the key source of the key requester, so that the key requester obtains a key plaintext corresponding to the identifier from its key source according to the identifier, and encrypt data according to the key plaintext, and destroy the key plaintext.
2. The key management server of claim 1, wherein the key source comprises:
a quantum key distribution device.
3. A client, comprising:
a key source and a second processor;
the second processor is used for acquiring a key plaintext corresponding to the identifier from the key source under the condition that the key ciphertext and the identifier of the key are received, destroying the key plaintext after encrypting data according to the key plaintext, and configuring the same corresponding relation between the key and the identifier in the key source of the identifier sender; and the key ciphertext is generated by using the key corresponding to the master key encryption identifier.
4. A client according to claim 3, wherein the key source comprises:
a quantum key distribution device.
5. A key distribution method, comprising:
the key management server generates a master key under the condition of receiving a key request, and acquires a key and an identifier of the key from a local key source;
the key management server encrypts the key by using the master key, generates a key ciphertext, and sends the key ciphertext and the key identifier to a key requester; the local key source and the key source of the key requester are configured with the same corresponding relation between the key and the identifier, so that the key requester obtains a key plaintext corresponding to the identifier from the key source according to the identifier, encrypts data according to the key plaintext and then destroys the key plaintext.
6. A key acquisition method, comprising:
the client receives the cipher text of the key and the identification of the key;
the client acquires a key plaintext corresponding to the identifier from a local key source, encrypts data according to the key plaintext and then destroys the key plaintext; the local key source and the key source of the sender of the identifier of the key are configured with the same corresponding relation between the key and the identifier; and the key ciphertext is generated by encrypting the key corresponding to the identifier by using a master key.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010151870.4A CN113364580B (en) | 2020-03-06 | 2020-03-06 | Key management server, client, key distribution method, and key acquisition method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010151870.4A CN113364580B (en) | 2020-03-06 | 2020-03-06 | Key management server, client, key distribution method, and key acquisition method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113364580A CN113364580A (en) | 2021-09-07 |
| CN113364580B true CN113364580B (en) | 2023-05-09 |
Family
ID=77524185
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010151870.4A Active CN113364580B (en) | 2020-03-06 | 2020-03-06 | Key management server, client, key distribution method, and key acquisition method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113364580B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110601838A (en) * | 2019-10-24 | 2019-12-20 | 国网山东省电力公司信息通信公司 | Identity authentication method, device and system based on quantum key |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109039615A (en) * | 2018-10-15 | 2018-12-18 | 北京天融信网络安全技术有限公司 | Utilize the method and relevant device and storage medium of SSL VPN agreement acquisition quantum key |
-
2020
- 2020-03-06 CN CN202010151870.4A patent/CN113364580B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110601838A (en) * | 2019-10-24 | 2019-12-20 | 国网山东省电力公司信息通信公司 | Identity authentication method, device and system based on quantum key |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113364580A (en) | 2021-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5204090B2 (en) | Communication network, e-mail registration server, network device, method, and computer program | |
| CN102176709B (en) | Method and device with privacy protection function for data sharing and publishing | |
| KR100734162B1 (en) | Method and apparatus for secure distribution of public/private key pairs | |
| US6256733B1 (en) | Access and storage of secure group communication cryptographic keys | |
| US20150074393A1 (en) | Method, Apparatus, and System for Implementing Media Data Processing | |
| US20130339726A1 (en) | File server apparatus and file server system | |
| JP2020505849A (en) | Digital certificate management method and device | |
| CN102333093A (en) | Data encryption transmission method and system | |
| CN103516516A (en) | File safe sharing method, system and terminal | |
| US12010216B2 (en) | Computer-implemented system and method for highly secure, high speed encryption and transmission of data | |
| CN111080299B (en) | Anti-repudiation method for transaction information, client and server | |
| WO2015180604A1 (en) | Secret communication control method, secret communication method, and apparatus | |
| US10063655B2 (en) | Information processing method, trusted server, and cloud server | |
| US11528127B2 (en) | Computer-implemented system and method for highly secure, high speed encryption and transmission of data | |
| CN113300999B (en) | Information processing method, electronic device, and readable storage medium | |
| CN111698264A (en) | Method and apparatus for maintaining user authentication sessions | |
| CN109995723B (en) | Method, device and system for DNS information interaction of domain name resolution system | |
| JP2006279269A (en) | Information management device, information management system, network system, user terminal, and their programs | |
| CN113364580B (en) | Key management server, client, key distribution method, and key acquisition method | |
| CN116055141A (en) | Data security transmission method, system, device and storage medium | |
| CN112437436B (en) | Identity authentication method and device | |
| CN113918971A (en) | Block chain based message transmission method, device, equipment and readable storage medium | |
| KR20190115489A (en) | IOT equipment certification system utilizing security technology | |
| KR101793528B1 (en) | Certificateless public key encryption system and receiving terminal | |
| JPH11187008A (en) | Delivering method for cryptographic key |
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 |