TWI787974B - Method and system for generating dynamic key - Google Patents

Abstract

This invention provides a method and system for generating a dynamic key, and the method includes: dynamically updating the first key generation protocol currently held by a server based on the risk level of the preset risk event when a preset risk event is detected, so as to obtain a second key generation protocol; sending the dynamically updated second key generation protocol to users by the server, so that the users can exchange the key with the server based on the second key generation protocol. This method increases the cost for the hackers to crack the protocol and improves the security of the key.

Description

Dynamic key generation method and system

The invention belongs to the field of encrypted communication, and in particular relates to a method and system for generating a dynamic key.

This section is intended to provide a background or context for implementations of the invention that are recited in the claims. The descriptions herein are not admitted to be prior art by inclusion in this section.

With the development of the mobile Internet, applications have shown explosive growth. At the same time, the Internet black and gray industry has also emerged and developed, with a scale reaching 100 billion yuan. The Internet black and gray industry obtains the request interface and parameters of the communication between the client and the server through packet capture and reverse analysis, and directly forges the interface protocol and parameters to realize automatic operation. The secure communication between the client and the server is challenged .

In traditional technology, due to the requirement of communication security, the application software on the market generally adopts the open source protocol TLS (Transport Layer Security, Transport Layer Security Protocol) handshake scheme. The open source protocol TLS handshake scheme can assist the client and the server to select the encryption algorithm, MAC algorithm and related keys used when connecting. Before sending the data of the application program, the two parties use the handshake protocol to complete the above matters.

However, in the above-mentioned open source protocol TLS handshake scheme, the client needs to preset some public encryption algorithms and hash methods, so the client key generation algorithm is fixed, and the attacker can obtain the These fixed key generation algorithms can crack the encrypted communication between the client and the server, which will adversely affect the communication security.

Aiming at the above-mentioned problems in the prior art, a method and system for generating a dynamic key are proposed, and the above-mentioned problems can be solved by using the method and system.

The present invention provides the following solutions.

In the first aspect, a dynamic key generation method is provided, including: when a preset risk event is detected, dynamically update the first key generation agreement currently held by the server based on the risk degree of the preset risk event, and obtain the second Second key generation protocol: the server sends the dynamically updated second key generation protocol to the client, so that the client can exchange keys with the server based on the second key generation protocol.

In some embodiments, the server sends the dynamically updated second key generation protocol to the client, and the method further includes: the server receives a key exchange request sent by the client, and the key exchange request includes the current The version number of the key generation protocol held; when the server detects that the version number carried in the key exchange request is inconsistent with the version number of the second key generation protocol, the server will dynamically update the second key generation protocol sent to the client.

In some embodiments, the server dynamically updates the currently held first key generation agreement based on the risk level of the preset risk event, and further includes:

When a preset risk event is detected, the server invalidates the currently held first key generation agreement, and generates a second key generation agreement corresponding to the security level according to the risk degree of the preset risk event;

Wherein, the second key generation protocol includes a preset key operator layer and an agreement body, the agreement body includes agreement logic and agreement data, and the agreement logic is used to indicate one or more target keys adopted by the second key generation protocol Composition rules of operands, the protocol data is used to indicate the operand parameters of one or more target key operands.

In some implementations, the key operand layer contains multiple key operands and is preset at the server and the user end, and the multiple key operands contained in the key operand layer are pre-divided into multiple security level; and, the security level of the second key generation protocol is determined by the security level of the one or more target key operands employed.

In some embodiments, the key operand layer includes: one or more key operands using a secure encryption algorithm, and/or one or more key operands using a custom change algorithm, and/or using a digest One or more keyed operands of the algorithm.

In some implementations, the method further includes: using white-box encryption technology to protect the security of the operator parameters.

In some embodiments, the preset risk events include at least a first preset risk event, a second preset risk event, and a third preset risk event with different risk levels; wherein, the first preset risk event is used to indicate the connection to The proportion of the number of untrusted clients on the server exceeds the preset threshold; the second preset risk event is used to indicate the receipt of an agreement update command sent from the outside; the third preset risk event is used to indicate that the first gold currently held by the server The working time of the key generation protocol exceeds the preset security time.

In some implementations, the server is connected to multiple clients, and the key exchange request sent by the client also includes device fingerprint information; the method also includes: the server collects the device fingerprint information sent by each client, and according to the device Fingerprint information judges whether each client is an untrusted client, and periodically judges whether the proportion of untrusted clients connected to the server exceeds a preset threshold. If it exceeds the preset threshold, the first preset threshold is detected. risk event.

In some embodiments, the preset risk event further includes a fourth preset risk event whose risk degree is greater than the first preset risk event; wherein, the fourth preset risk event is used to instruct the server to repeatedly detect the first preset risk event set risk events.

In some embodiments, the server sends the dynamically updated second key generation protocol to the client, which also includes: the server sends the version number of the second key generation protocol to the client; The terminal initiates a protocol update request, and the protocol update request carries the version number of the second key generation protocol; the server sends the protocol logic and protocol data of the second key generation protocol to the client; Layer, protocol logic and protocol data, implement the second key generation protocol, and re-initiate a key exchange request to the server based on the second key generation protocol.

In some implementation manners, the server issues the protocol logic of the second key generation agreement to the client in a hot update manner.

In some embodiments, the client performs key exchange with the server based on the second key generation agreement, and further includes: the client sends a key exchange request to the server, and the key exchange request includes the second key currently held by the client. The version number of the key generation protocol; when the server detects that the version number carried in the key exchange request is consistent with the version number of the second key generation protocol currently held by the server, it will generate a random number on the server and send the service The random number from the client is sent to the client; the client generates the pre-master key according to the random number of the server, and sends the pre-master key to the server; the client and the server respectively use the second key generation protocol, the pre-master key, Random numbers on the client side and random numbers on the server side generate working keys; the client side and the server side exchange their generated working keys for encrypted communication.

In some embodiments, the method further includes: after the user end generates the pre-master key according to the random number of the server, encrypts the pre-master key with the public key sent by the server, and sends the encrypted pre-master key to To the server; the server uses the private key to decrypt the encrypted pre-master key to obtain the decrypted pre-master key.

In the second aspect, a dynamic key generation system is provided. The system includes: a server and a user; wherein, the server is used to execute: when a preset risk event is detected, the current The first key generation agreement held is dynamically updated to obtain the second key generation agreement; the dynamically updated second key generation agreement is sent to the client; the client is used to execute: based on the second key generation The protocol exchanges keys with the server.

In some implementations, the server is further configured to: receive the key exchange request sent by the client, where the key exchange request includes the version number of the key generation protocol currently held by the client; when it is detected that the key exchange request carries When the version number of the second key generation protocol is inconsistent with that of the second key generation protocol, the dynamically updated second key generation protocol is delivered to the client.

In some implementations, the server is further configured to: when a preset risk event is detected, invalidate the currently held first key generation agreement, and generate a second key with a corresponding security level according to the risk degree of the preset risk event. Key generation protocol; wherein, the second key generation protocol includes a preset key operator layer and an agreement body, the agreement body includes agreement logic and agreement data, and the agreement logic is used to indicate one or Composition rules of multiple target key operands, the protocol data is used to indicate the operand parameters of one or more target key operands.

In some implementations, the key operand layer contains multiple key operands and is preset at the server and the user end, and the multiple key operands contained in the key operand layer are pre-divided into multiple security level; and, the security level of the second key generation protocol is determined by the security level of the one or more target key operands employed.

In some embodiments, the key operand layer includes: one or more key operands using a secure encryption algorithm, and/or one or more key operands using a custom change algorithm, and/or using a digest One or more keyed operands of the algorithm.

In some implementation manners, the system is further configured to: use white-box encryption technology to protect the security of the operator parameters.

In some embodiments, the preset risk events include at least a first preset risk event, a second preset risk event, and a third preset risk event with different risk levels; wherein, the first preset risk event is used to indicate the connection to The proportion of the number of untrusted clients on the server exceeds the preset threshold; the second preset risk event is used to indicate the receipt of an agreement update command sent from the outside; the third preset risk event is used to indicate that the first gold currently held by the server The working time of the key generation protocol exceeds the preset security time.

In some implementations, the server is connected to multiple clients, and the key exchange request sent by the client also includes device fingerprint information; the server is also used to: collect the device fingerprint information sent by each client, according to the device Fingerprint information judges whether each client is an untrusted client, and periodically judges whether the proportion of untrusted clients connected to the server exceeds a preset threshold. If it exceeds the preset threshold, the first preset threshold is detected. risk event.

In some embodiments, the preset risk event further includes a fourth preset risk event whose risk degree is greater than the first preset risk event; wherein, the fourth preset risk event is used to instruct the server to repeatedly detect the first preset risk event set risk events.

In some implementations, the server is further configured to: send the version number of the second key generation protocol to the user when detecting that the version number carried in the key exchange request is inconsistent with the version number of the second key generation protocol terminal; the client is also used to: initiate a protocol update request to the server, and the protocol update request carries the version number of the second key generation protocol; the server is also used to: issue the agreement logic of the second key generation protocol to the client and protocol data; the client is also used to implement the second key generation protocol based on the preset key operator layer, protocol logic, and protocol data, and re-initiate a key to the server based on the second key generation protocol Exchange request.

In some implementation manners, the server issues the protocol logic of the second key generation agreement to the client in a hot update manner.

In some implementations, the client is further configured to: send a key exchange request to the server after the dynamic update is performed based on the second key generation agreement. The key exchange request includes the second key generation currently held by the client. The version number of the protocol; the server is also used to: when it is detected that the version number carried in the key exchange request is consistent with the version number of the second key generation protocol currently held by the server, generate a random number on the server, and send The random number of the server is sent to the client; the client is also used to: generate the pre-master key according to the random number of the server, and send the pre-master key to the server; the client and the server are also used to: respectively use the second key Key generation protocol, pre-master key, random numbers on the client side and random numbers on the server side generate working keys, and encrypted communication is performed by exchanging the working keys generated by each.

In some implementations, the client is further configured to: after generating the pre-master key according to the random number of the server, use the public key sent by the server to encrypt the pre-master key, and send the encrypted pre-master key to to the server; the server is also used to: use the private key to decrypt the encrypted pre-master key to obtain the decrypted pre-master key.

The above at least one technical solution adopted in the embodiment of the present application can achieve the following beneficial effects: in this embodiment, the server can dynamically update the key generation protocol held by the server based on the preset risk control mechanism and send it to the client, The client exchanges keys with the server according to the dynamically updated key generation protocol issued by the server, thereby increasing the cost for attackers to crack the protocol and providing key security. It should be understood that the above description is only an overview of the technical solution of the present invention, so as to understand the technical means of the present invention more clearly, so as to be implemented according to the contents of the description. In order to make the above and other objects, features and advantages of the present invention more comprehensible, specific embodiments of the present invention are illustrated below.

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided for more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

In the present invention, it should be understood that terms such as "comprising" or "having" are intended to indicate the presence of features, figures, steps, acts, components, parts or combinations thereof disclosed in the specification, and are not intended to exclude one or multiple other features, figures, steps, acts, parts, parts or combinations thereof.

In addition, it should be noted that, in the case of no conflict, the embodiments of the present invention and the features in the embodiments can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and examples.

Aiming at the shortcomings of the existing technical solutions, an embodiment of the present invention proposes a method for generating a dynamic key. In the following, the inventive concept of the method is firstly introduced.

The server detects the risk situation in the environment, and when a preset risk event is detected, it dynamically updates the currently held first key generation agreement based on the risk level of the preset risk event to obtain the second key generation protocol. Based on this, the server sends the dynamically updated second key generation protocol to the client, so that the client performs key exchange with the server based on the second key generation protocol. In other words, the server can dynamically update the key generation agreement held by the server based on the preset risk control mechanism, and send it to the client. The client and the server exchange data based on the dynamically updated key generation agreement, thereby improving The cost for the attacker to crack the protocol and improve the communication security performance.

Those skilled in the art may understand that the described application scenario is only an example in which the embodiments of the present invention may be implemented. The scope of application of the embodiments of the present invention is not limited in any way. After introducing the basic principles of the present invention, various non-limiting embodiments of the present invention are described in detail below.

FIG. 1 is a schematic flowchart of a method 100 for generating a dynamic key according to an embodiment of the present application.

As shown in FIG. 1 , the method 100 may include step 101 and step 102 .

Step 101. When a preset risk event is detected, the server dynamically updates the currently held first key generation agreement based on the risk degree of the preset risk event to obtain a second key generation agreement.

Wherein, the preset risk event refers to an event that may pose a risk to the security of the key generation protocol currently held by the server and the client. For example, the preset risk event may be that the client connected to the server is an untrusted client, or that the working time of the currently held key generation protocol exceeds a security duration threshold, and so on.

In a possible implementation manner, in the above step 101, the server dynamically updating the currently held first key generation agreement based on the risk degree of the preset risk event may also include: when a preset risk event is detected , the server invalidates the currently held first key generation agreement, and generates a second key generation agreement corresponding to the security level according to the risk degree of the preset risk event.

It can be understood that, based on prior experience, historical statistical data and other factors to judge the degree of risk, various types of preset risk events can be divided into multiple levels according to the degree of risk. For example, a detected preset risk event indicates that the currently held When the key generation protocol has been breached, the preset risk event can be considered as a first-level risk event. For another example, when another preset risk event detected indicates that the currently held key generation protocol may be at risk of being compromised, then the preset risk event may be considered as a secondary risk event. For another example, if the detected preset risk event indicates that the working time of the currently held key generation protocol has exceeded the safety duration threshold, then the preset risk event can be considered as a third-level risk event, and so on. Based on this, a second key generation protocol whose security level corresponds to the risk degree can be generated, thereby continuously increasing the cost for an attacker to crack the key generation protocol.

Wherein, the second key generation protocol includes a preset key operator layer and an agreement body, the agreement body includes agreement logic and agreement data, and the agreement logic is used to indicate one or more target keys adopted by the second key generation protocol Composition rules for operands, the protocol data is used to indicate the operand parameters of one or more target key operands.

Specifically, a key operand layer including various key operands is preset on both the server end and the user end. Optionally, the key operand layer includes: one or more key operands using secure encryption algorithms such as AES and SM4, and/or using custom changes such as matrix multiplication algorithms and large number remainder algorithms One or more key operands of the algorithm, and/or one or more key operands of digest algorithms such as SHA256, SM3.

For example, Fig. 2 shows an example of a key generation protocol, which includes a preset key operand layer and a dynamically generated agreement body, wherein the preset key operand layer includes AES transformation operands, matrix transformation Key operands such as operands and SHA transformation operands. The dynamically generated agreement body includes the logic area and the data area. The logic area includes the agreement logic, which is used to indicate the composition rules and order of the target key operands used in the key generation agreement. The content of this part can be updated through hot sent to the client. The data area contains the operand parameters of the key operands at all levels in the key operand layer. Optionally, the operand parameters of some of the key operands may be white-box data, and the operand parameters of some other key operands may be plaintext parameters.

In a possible implementation manner, the key operand layer contains multiple key operands and is preset at the server and the user end at the same time, and the multiple key operands contained in the key operand layer are pre-divided into a plurality of security levels; and, the security level of the second key generation protocol is determined by the security level of the one or more target key operands employed.

For example, various key operands in the key operand layer can be divided into first-level operands, second-level operands, and third-level operands according to the transformation security of each key operand. Among them, the first-level operand can represent the operand with the highest security level, accept key factors and operand parameters as input, and use security encryption algorithms such as AES algorithm and SM4 algorithm to protect the security of the transformation result. The second-level operand can represent an operand with a security level second only to the first-level, which accepts key factors and operand parameters as input, and uses custom change algorithms such as matrix multiplication algorithm, large number remainder algorithm, etc. to protect Security of transformation results. Compared with the first-level operand, the second-level operand has a simpler algorithm and has lower performance requirements on the client side. Optionally, a white-box technique may be used to protect the security of the operand parameters of the first-level operands and the second-level operands. The third-level operand can represent an operand with a weaker security level, which accepts key factors and operand parameters as input, and can use the digest algorithm used first to protect the security of the transformation result, where the operand parameters of the digest algorithm are The salt of the digest algorithm, for example, the digest algorithm can be SHA256, SM3, etc. The third-level operator algorithm is simpler than the first-level and second-level operator algorithms, and has lower performance requirements on the client side. Based on this, it can be understood that when the second key generation protocol uses the first-level operand as the target key operand, it has a higher security level than when the second-level operand is used. When the combination of the second key generation protocol uses the primary and secondary operands as target key operands, it has a higher security level than using the primary operand alone. Therefore, the security level of the second key generation agreement can be determined by the security level of one or more target key operands used, and the second key generation corresponding to the security level can be generated according to the risk degree of the detected preset risk event protocol.

In a possible implementation manner, the method further includes: using a white-box encryption technology to protect the security of the operator parameters.

For example, referring to FIG. 2 , the operand parameters of the AES transform operand and the matrix transform operand are stored in the form of white box data.

In a possible implementation manner, the preset risk events include at least a first preset risk event, a second preset risk event, and a third preset risk event with different risk degrees; the first preset risk event may be used to indicate The proportion of the number of untrusted clients connected to the server exceeds the preset threshold; the second preset risk event is used to indicate the receipt of an agreement update command sent from the outside; the third preset risk event is used to indicate that the server currently holds the first The working time of a key generation protocol exceeds a preset security time period.

For example, referring to FIG. 3 , a risk control module may be set on the server side, and the risk control module is provided with multiple risk-driven units, such as a first risk-driven unit, a second risk-driven unit, and a third risk-driven unit. Based on this, for example, when the first risk driver unit detects that the first preset risk event occurs, that is, when it detects that the proportion of the number of untrusted clients connected to the server exceeds the preset threshold, it drives to forcibly update the server’s current status. Some first key generation protocols, the dynamically updated second key generation protocol can be composed of AES operands (first-level operands), matrix change operands (second-level operands) and SHA transformation operands (third-level operands) ) combined participation. Optionally, if the first risk-driven unit detects that the first preset risk event occurs repeatedly, the updated second key generation protocol may include an increased number of AES transformation operators. For another example, before the business party needs to launch a business with higher security requirements, it sends an agreement update command to the server (that is, the second preset risk event occurs), and the second risk driver unit detects the occurrence of the second preset risk event , the driver forcibly updates the first key generation protocol currently held by the server, and the dynamically updated second key generation protocol can be composed of matrix change operands (secondary operands) and SHA transformation operands (tertiary operands) ) combined participation. For another example, when the working time of the first key generation protocol exceeds the preset security time period (that is, the third preset risk event occurs), the third risk driver unit detects the third preset risk event, and drives the forced update of the service The first key generation protocol currently held by the terminal, and the dynamically updated second key generation protocol can be participated by the SHA transformation operator (three-level operator). It can be seen that the risk levels of the first preset risk event, the second preset risk event, and the third preset risk event decrease in order, and the security level of the second key generation protocol generated after dynamic update also decreases in order.

In a possible implementation, the server is connected to multiple clients, and the key exchange request sent by the clients also includes device fingerprint information; the method further includes: the server collects the device fingerprint information sent by each client, Determine whether each client is an untrusted client based on device fingerprint information, and periodically determine whether the proportion of untrusted clients connected to the server exceeds a preset threshold. If it exceeds the preset threshold, the first Preset risk events.

In a possible implementation manner, the preset risk event further includes a fourth preset risk event whose risk degree is greater than the first preset risk event; wherein, the fourth preset risk event is used to indicate that the server detects a repeated The first predetermined risk event. For example, when it is detected that the first preset risk event has repeatedly occurred, the driver will forcefully update the first key generation agreement currently held by the server, and the dynamically updated second key generation agreement can be composed of multiple The combination of AES operator (first-level operator), matrix transformation operator (second-level operator) and SHA transformation operator (third-level operator) is involved. This results in a higher level of security.

Step 102, the server sends the dynamically updated second key generation protocol to the client, so that the client performs key exchange with the server based on the second key generation protocol.

In a possible implementation manner, the server in step 102 sends the dynamically updated second key generation protocol to the client, which also includes: the server receives the key exchange request sent by the client, and the key exchange The request includes the version number of the key generation protocol currently held by the client; when the server judges that the version number carried in the key exchange request is inconsistent with the version number of the second key generation protocol, the server will dynamically update the second key generation protocol. The key generation protocol is delivered to the client.

On the contrary, when the server judges that the version number carried in the key exchange request sent by the client is consistent with the version number of the second key generation protocol, it means that the key generation protocol between the client and the server is consistent, and the server There is no need to further deliver the second key generation protocol it holds to the client.

In a possible implementation manner, the server sends the dynamically updated second key generation protocol to the client, and may further include: the server sends the version number of the second key generation protocol to the client ; The client initiates a protocol update request to the server, and the protocol update request carries the version number of the second key generation protocol; the server sends the protocol logic and protocol data corresponding to the second key generation protocol to the client; The preset key operator layer, protocol logic and protocol data implement the second key generation protocol, and re-initiate a key exchange request to the server based on the second key generation protocol.

In a possible implementation manner, the server issues the agreement logic of the second key generation agreement to the user end in a hot update manner.

For example, referring to Figure 3, the agreement logic issued by the server to the client is a hot update JS file. After receiving the hot update JS file, the client turns into a hot update module and further combines the received agreement data. , The preset key operator layer generates an updated second key generation protocol.

Fig. 4 shows a schematic flow chart of sequentially updating the key generation agreement held by the server and the client. Referring to FIG. 3 , FIG. 4 shows that the communication between the client and the server is realized through the secure communication module in FIG. 3 .

S41. The server sets the currently held first key generation agreement to an invalid state, and simultaneously generates a second key generation agreement, a hot update patch, and a white-box jump table.

S42. The client generates a random number at the client. Wherein, the above S41 may be before or after S42, which is not specifically limited in the present application.

S43. The user end initiates a key exchange request to the server end. The key exchange request includes: the version number of the key generation protocol currently held by the user end, the random number of the user end, and device fingerprint information.

S44. After receiving the key exchange request, the server determines that the version number carried in the key exchange request has expired, and terminates the current key exchange request.

S45. Deliver the dynamically updated version number and certificate of the second key generation protocol to the client.

S46. The client receives and verifies the received certificate.

S47. After the certificate verification is passed, the client sends a protocol update request to the server. The protocol update request carries the version number of the second key generation protocol and is used to request a hot update file and a white-box jump table.

S48. The server issues the hot update js file corresponding to the second key generation protocol (for example, through the protocol logic module) and operator parameters (for example, through the protocol data module) according to the version number sent by the client.

S49. After receiving the hot update js file and the operator parameters, the client executes the hot update based on the preset key operator layer, and stores the version number of the second key generation protocol, the hot update file, and the white box jump table.

S50. The client and the server perform key exchange based on the currently held second key generation protocol.

In a possible implementation manner, the client performs key exchange with the server based on the second key generation agreement, and further includes: the client sends a key exchange request to the server, and the key exchange request includes the key exchange currently held by the client. The version number of the second key generation protocol; when the server detects that the version number carried in the key exchange request is consistent with the version number of the second key generation protocol currently held by the server, generate a server random number, and Send the server random number to the client; the client generates the pre-master key according to the server random number, and sends the pre-master key to the server; the client and the server use the second key generation protocol and pre-master key respectively. key, random numbers on the client side, and random numbers on the server side to generate working keys; the client side and the server side exchange their generated working keys for encrypted communication.

In a possible implementation manner, the method further includes: after the user end generates the pre-master key according to the random number of the server, encrypts the pre-master key with the public key sent by the server, and sends the encrypted pre-master key to The key is sent to the server; the server uses the private key to decrypt the encrypted pre-master key to obtain the decrypted pre-master key.

For example, after the client and the server hold the dynamically updated second key generation agreement at the same time, the server and the client generate the final working key (Skey) based on the second key generation agreement, specifically The working process of key generation is shown in Figure 5, including:

S51. The user end generates a user end random number (cliRand).

S52. The client initiates a key exchange request to the server, and sends the client random number, protocol version number, and device information.

S53. After receiving the request information from the client, the server determines that the protocol version number is the latest version number, and generates a server random number (srvRand).

S54. The server sends the server random number (srvRand), the version number of the second key generation protocol, and the certificate to the client.

S55. After receiving the random number from the server, the client verifies the certificate.

S56. The user end generates a pre-master key (premasterKey) after the certificate verification is passed, and encrypts the pre-master key with the public key issued by the server end.

S57. The client sends the encrypted pre-master key to the server.

S58. The client uses the currently held second key to generate a protocol, and generates a working key according to the pre-master key, the random number on the server side, and the random number on the user side. Wherein, S57 may be performed before or after S58, which is not specifically limited in the present application.

S59. After receiving the encrypted pre-master key, the server uses the private key to decrypt the pre-master key, and uses the currently held second key to generate an agreement, and according to the pre-master key, server random number, user Terminal random numbers generate working keys.

S60. The user end and the server end hold the working key at the same time, and subsequent service messages can be encrypted and communicated with the key.

Referring to Fig. 3, before S60, the above-mentioned communication between the client and the server is realized through the secure communication module of the client and the server, wherein the key factor includes the pre-master key, the random number of the server, Random numbers on the client side. After S60, encryption is carried out by the business message encryption module of the client and the server, and then the key encryption communication is performed.

Based on the same technical concept, an embodiment of the present invention also provides a dynamic key generation system, which is used to execute the dynamic key generation method provided in any of the above embodiments. Fig. 6 is a schematic structural diagram of a dynamic key generation system provided by an embodiment of the present invention.

As shown in FIG. 6 , the system 600 includes: a server 601 and a user 602 . Wherein, the server is used to execute: when a preset risk event is detected, dynamically update the first key generation agreement currently held by the server based on the risk degree of the preset risk event, and obtain the second key generation agreement; Sending the dynamically updated second key generation protocol to the client; the client is used to perform key exchange with the server based on the second key generation protocol.

In some implementations, the server is further configured to: receive the key exchange request sent by the client, where the key exchange request includes the version number of the key generation protocol currently held by the client; when it is detected that the key exchange request carries When the version number of the second key generation protocol is inconsistent with that of the second key generation protocol, the dynamically updated second key generation protocol is delivered to the client.

In some implementations, the server is further configured to: when a preset risk event is detected, invalidate the currently held first key generation agreement, and generate a second key with a corresponding security level according to the risk degree of the preset risk event. Key generation protocol; wherein, the second key generation protocol includes a preset key operator layer and an agreement body, the agreement body includes agreement logic and agreement data, and the agreement logic is used to indicate one or Composition rules of multiple target key operands, the protocol data is used to indicate the operand parameters of one or more target key operands.

In some implementations, the key operand layer contains multiple key operands and is preset at the server and the user end, and the multiple key operands contained in the key operand layer are pre-divided into multiple security level; and, the security level of the second key generation protocol is determined by the security level of the one or more target key operands employed.

In some embodiments, the key operand layer includes: one or more key operands using a secure encryption algorithm, and/or one or more key operands using a custom change algorithm, and/or using a digest One or more keyed operands of the algorithm.

In some implementation manners, the system is further configured to: use white-box encryption technology to protect the security of the operator parameters.

In some embodiments, the preset risk events include at least a first preset risk event, a second preset risk event, and a third preset risk event with different risk levels; wherein, the first preset risk event is used to indicate the connection to The proportion of the number of untrusted clients on the server exceeds the preset threshold; the second preset risk event is used to indicate the receipt of an agreement update command sent from the outside; the third preset risk event is used to indicate that the first gold currently held by the server The working time of the key generation protocol exceeds the preset security time.

In some implementations, the server is connected to multiple clients, and the key exchange request sent by the client also includes device fingerprint information; the server is also used to: collect the device fingerprint information sent by each client, according to the device Fingerprint information judges whether each client is an untrusted client, and periodically judges whether the proportion of untrusted clients connected to the server exceeds a preset threshold. If it exceeds the preset threshold, the first preset threshold is detected. risk event.

In some embodiments, the preset risk event further includes a fourth preset risk event whose risk degree is greater than the first preset risk event; wherein, the fourth preset risk event is used to instruct the server to repeatedly detect the first preset risk event set risk events.

In some implementations, the server is further configured to: send the version number of the second key generation protocol to the user when detecting that the version number carried in the key exchange request is inconsistent with the version number of the second key generation protocol terminal; the client is also used to: initiate a protocol update request to the server, and the protocol update request carries the version number of the second key generation protocol; the server is also used to: issue the agreement logic of the second key generation protocol to the client and protocol data; the client is also used to implement the second key generation protocol based on the preset key operator layer, protocol logic, and protocol data, and re-initiate a key to the server based on the second key generation protocol Exchange request.

In some implementation manners, the server issues the protocol logic of the second key generation agreement to the client in a hot update manner.

In some implementations, the client is further configured to: send a key exchange request to the server after the dynamic update is performed based on the second key generation agreement. The key exchange request includes the second key generation currently held by the client. The version number of the protocol; the server is also used to: when it is detected that the version number carried in the key exchange request is consistent with the version number of the second key generation protocol currently held by the server, generate a random number on the server, and send The random number of the server is sent to the client; the client is also used to: generate the pre-master key according to the random number of the server, and send the pre-master key to the server; the client and the server are also used to: respectively use the second key Key generation protocol, pre-master key, random numbers on the client side and random numbers on the server side generate working keys, and encrypted communication is performed by exchanging the working keys generated by each.

In some implementations, the client is further configured to: after generating the pre-master key according to the random number of the server, use the public key sent by the server to encrypt the pre-master key, and send the encrypted pre-master key to to the server; the server is also used to: use the private key to decrypt the encrypted pre-master key to obtain the decrypted pre-master key.

It should be noted that the system in the embodiment of the present application can realize each process of the foregoing method embodiment, and achieve the same effect and function, which will not be repeated here.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems or computer program products. Accordingly, the present invention can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) having computer-usable program code embodied therein .

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each process and/or block in the flowchart and/or block diagram, and a combination of processes and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing equipment to produce a machine so that the instructions executed by the processor of the computer or other programmable data processing equipment Produce means for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, such that the instructions stored in the computer readable memory produce an article of manufacture including the instruction means , the instruction device implements the functions specified in one or more procedures of the flow chart and/or one or more blocks of the block diagram.

These computer program instructions may also be loaded into a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce computer-implemented The instructions executed above provide steps for implementing the functions specified in the procedure or procedures of the flowchart and/or the block or blocks of the block diagram.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent memory in computer readable media, random access memory (RAM) and/or nonvolatile memory in the form of read only memory (ROM) or flash memory ( flash RAM). The memory is an example of a computer readable medium.

Computer-readable media includes both permanent and non-permanent, removable and non-removable media, and can be implemented by any method or technology for storage of information. Information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for computers include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM) , read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital multifunction Compact Disc (DVD) or other optical storage, magnetic cassette, tape magnetic disk storage or other magnetic storage device or any other non-transmission medium used to store information that can be accessed by a computing device. In addition, while operations of the methods of the present invention are depicted in the figures in a particular order, there is no requirement or implication that these operations must be performed in that particular order, or that all illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step for execution, and/or one step may be decomposed into multiple steps for execution.

Although the spirit and principles of the invention have been described with reference to a number of specific embodiments, it should be understood that the invention is not limited to the specific embodiments disclosed, nor does division of aspects imply that features in these aspects cannot be combined to achieve optimal performance. Benefit, this division is only for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

100: method 101: When a preset risk event is detected, the server dynamically updates the currently held first key generation agreement based on the risk degree of the preset risk event, and obtains the second key generation agreement 102: The server sends the dynamically updated second key generation protocol to the client, so that the client performs key exchange with the server based on the second key generation protocol S41: The server sets the currently held first key generation agreement to an invalid state, and simultaneously generates a second key generation agreement, a hot update patch, and a white-box jump table. S42: The client generates a random number at the client. Wherein, the above-mentioned S41 may be before or after S42, and the present application does not specifically limit this S43: The client initiates a key exchange request to the server. The key exchange request includes: the version number of the key generation protocol currently held by the client, random numbers at the client, and device fingerprint information S44: The server receives the key exchange request, judges that the version number carried in the key exchange request has expired, and then terminates the current key exchange request S45: Sending the version number and certificate of the second key generation protocol held after the dynamic update to the client S46: The client receives and verifies the received certificate S47: The client initiates a protocol update request to the server after the certificate verification is passed, the protocol update request carries the version number of the second key generation protocol and is used to request a hot update file and a white box jump table S48: The server issues the hot update js file corresponding to the second key generation protocol (for example, through the protocol logic module) and the operator parameters (for example, through the protocol data module) according to the version number sent by the client. S49: After receiving the hot update js file and the operator parameters, the client executes the hot update based on the preset key operator layer, and stores the version number of the second key generation agreement, the hot update file, and the white box jump table S50: The client and the server perform key exchange based on the currently held second key generation protocol S51: The client generates a random number at the client (cliRand) S52: The client initiates a key exchange request to the server, and sends the client random number, protocol version number, and device information S53: After receiving the requested information from the client, the server determines that the protocol version number is the latest version number, and generates a server random number (srvRand) S54: The server sends the server random number (srvRand), the version number of the second key generation protocol, and the certificate to the client S55: After receiving the random number from the server, the client verifies the certificate S56: The client generates a pre-master key (premasterKey) after the certificate verification is passed, and encrypts the pre-master key with the public key issued by the server S57: The client sends the encrypted pre-master key to the server S58: The client uses the currently held second key to generate an agreement, and generates a working key according to the pre-master key, the server-side random number, and the client-side random number S59: After receiving the encrypted pre-master key, the server uses the private key to decrypt the pre-master key, and uses the currently held second key to generate an agreement, and according to the pre-master key, server random number, user Terminal random number generates work key S60: The user end and the server end hold the work key at the same time, and subsequent business messages can be encrypted with the key. 600: system 601: server 602: client

The advantages and benefits described herein, as well as other advantages and benefits, will be apparent to those of ordinary skill in the art upon reading the following detailed description of the exemplary embodiments. The drawings are only for the purpose of illustrating exemplary embodiments and are not to be considered as limiting the invention. Also throughout the drawings, the same reference numerals are used to denote the same parts. In the attached picture:

[Fig. 1] is a schematic flow diagram of a method for generating a dynamic key according to an embodiment of the present invention; [Fig. 2] is a schematic diagram of a key generation protocol according to an embodiment of the present invention; [Fig. 3] is a schematic diagram of a dynamic key generation system according to an embodiment of the present invention; [FIG. 4] is a schematic diagram of the timing sequence of the update key generation protocol according to an embodiment of the present invention; [Fig. 5] is a schematic diagram of the sequence of generating a dynamic key according to an embodiment of the present invention; [ FIG. 6 ] is a schematic diagram of a dynamic key generation system according to an embodiment of the present invention.

In the drawings, the same or corresponding reference numerals denote the same or corresponding parts.

101: When a preset risk event is detected, the server dynamically updates the currently held first key generation agreement based on the risk degree of the preset risk event, and obtains the second key generation agreement

102: The server sends the dynamically updated second key generation protocol to the client, so that the client performs key exchange with the server based on the second key generation protocol

Claims (26)

A method for generating a dynamic key, wherein the method includes: when a preset risk event is detected, dynamically performing the first key generation agreement currently held by the server based on the risk degree of the preset risk event. Update to obtain a second key generation protocol; the server sends the dynamically updated second key generation protocol to the client, so that the client can communicate with the second key generation protocol based on the second key generation agreement. The server performs key exchange; wherein, the server dynamically updates the currently held first key generation agreement based on the risk degree of the preset risk event, and further includes: when the preset risk is detected When an event occurs, the server invalidates the currently held first key generation agreement, and generates a second key generation agreement corresponding to the security level according to the risk degree of the preset risk event. The method according to claim 1, wherein the server sends the dynamically updated second key generation protocol to the client, and the method further includes: the server receiving the The key exchange request sent by the client, the key exchange request includes the version number of the key generation protocol currently held by the client; when the server detects that the version number carried in the key exchange request is different from the When the version numbers of the second key generation protocol are inconsistent, the server sends the dynamically updated second key generation protocol to the client. The method according to claim 1, wherein the second key generation protocol includes a preset key operand layer and an agreement body, the agreement body includes agreement logic and agreement data, and the agreement logic is used to indicate Composition rules of one or more target key operands adopted by the second key generation protocol, and the agreement data is used to indicate operand parameters of the one or more target key operands. The method according to claim 3, wherein the key operand layer contains a plurality of key operands and is preset in the server and the user end, and the key operand layer contained in the The plurality of key operands are pre-divided into a plurality of security levels; and, the security level of the second key generation protocol is determined by the adopted security level of the one or more target key operands. The method according to claim 4, wherein the key operand layer includes: one or more key operands using a secure encryption algorithm, and/or one or more key operators using a custom change algorithm element, and/or one or more key operands using a digest algorithm. The method according to claim 3, wherein the method further includes: using white-box encryption technology to protect the security of the operand parameters. The method according to claim 3, wherein the preset risk events include at least a first preset risk event, a second preset risk event, and a third preset risk event with different risk levels; wherein the first The preset risk event is used to indicate that the number of untrusted clients connected to the server exceeds a preset threshold; the second preset risk event is used to indicate the receipt of an agreement update instruction from the outside; the third preset It is assumed that the risk event is used to indicate that the working time of the first key generation protocol currently held by the server exceeds a preset safe duration. The method according to claim 7, wherein the server is connected to multiple clients, and the key exchange request sent by the clients also includes device fingerprint information; the method further includes: The server collects the device fingerprint information sent by each client, judges whether each client is an untrusted client according to the device fingerprint information, and periodically judges all devices connected to the server Whether the proportion of the number of untrustworthy clients exceeds the preset threshold, wherein if the ratio exceeds the preset threshold, the first preset risk event is detected. The method according to claim 7, wherein the preset risk event further includes a fourth preset risk event whose risk degree is greater than the first preset risk event; wherein the fourth preset risk event is used for Instructing the server to repeatedly detect the first preset risk event multiple times. The method according to claim 3, wherein the server sends the dynamically updated second key generation protocol to the client, and further includes: the server sends the second key generation protocol The version number of the second key generation protocol is sent to the client; the client initiates a protocol update request to the server, and the protocol update request carries the version number of the second key generation protocol; the server sends the protocol update request to the server The client sends the agreement logic and the agreement data of the second key generation agreement; the client sends the The second key generation protocol is implemented, and the key exchange request is re-initiated to the server based on the second key generation protocol. The method according to claim 10, wherein the server sends the agreement logic of the second key generation agreement to the client through hot update. The method according to claim 1, wherein the client performs key exchange with the server based on the second key generation agreement, and further includes: the client sends a key exchange to the server request, the key exchange request includes the version number of the second key generation protocol currently held by the client; when the server detects that the version number carried in the key exchange request is different from the When the version number of the second key generation protocol currently held by the server is consistent, generate a random number at the server, and send the random number at the server to the client; The client generates a pre-master key according to the random number of the server, and sends the pre-master key to the server; the client and the server each use the second key generation protocol , the pre-master key, the random number of the client and the random number of the server generate a working key; the client and the server perform encrypted communication by exchanging the respectively generated working keys. The method according to claim 12, wherein the method further includes: after the client generates the pre-master key according to the random number of the server, using the public key sent by the server to pair the Encrypt the pre-master key, and send the encrypted pre-master key to the server; the server uses the private key to decrypt the encrypted pre-master key to obtain the decrypted pre-master key. A dynamic key generation system, wherein the system includes: a server end and a user end; wherein the server end is used to perform: when a preset risk event is detected, based on the risk degree of the preset risk event The first key generation agreement currently held by the server is dynamically updated to obtain a second key generation agreement; the dynamically updated second key generation agreement is sent to the client; the client uses In execution: perform key exchange with the server based on the second key generation agreement; wherein, the server is further configured to: when the preset risk event is detected, make the currently held The first key generation agreement fails, and a second key generation agreement corresponding to the security level is generated according to the risk degree of the preset risk event. The system according to claim 14, wherein the server is further configured to: receive the key exchange request sent by the client, the key exchange request includes the key currently held by the client Generate the version number of the protocol; when it is detected that the version number carried in the key exchange request is inconsistent with the version number of the second key generation protocol, send the dynamically updated second key generation protocol to the client. The system according to claim 14, wherein the second key generation protocol includes a preset key operand layer and an agreement body, the agreement body includes agreement logic and agreement data, and the agreement logic is used to indicate Composition rules of one or more target key operands adopted by the second key generation protocol, and the agreement data is used to indicate operand parameters of the one or more target key operands. The system according to claim 16, wherein the key operand layer contains a plurality of key operands and is preset at the server end and the user end, and the key operand layer contained in the The plurality of key operands are pre-divided into a plurality of security levels; and, the security level of the second key generation protocol is determined by the adopted security level of the one or more target key operands. The system according to claim 17, wherein the key operand layer includes: one or more key operands using a secure encryption algorithm, and/or one or more key operators using a custom change algorithm element, and/or one or more key operands using a digest algorithm. The system according to claim 16, wherein the system is further configured to: use white-box encryption technology to protect the security of the operand parameters. The system according to claim 16, wherein the preset risk events include at least a first preset risk event, a second preset risk event, and a third preset risk event with different risk levels; wherein the first The preset risk event is used to indicate that the proportion of the number of untrusted clients connected to the server exceeds a preset threshold; the second preset risk event is used to indicate the receipt of an agreement update instruction sent from the outside; The third preset risk event is used to indicate that the working time of the first key generation protocol currently held by the server exceeds a preset safe duration. The system according to claim 20, wherein the server is connected to a plurality of the clients, and the key exchange request sent by the clients also includes device fingerprint information; the server is also used to : Collect the device fingerprint information sent by each client, judge whether each client is an untrusted client according to the device fingerprint information, and periodically judge the untrustworthy client connected to the server Whether the proportion of the number of letter users exceeds the preset threshold, wherein if the ratio exceeds the preset threshold, the first preset risk event is detected. The system according to claim 20, wherein the preset risk event further includes a fourth preset risk event whose degree of risk is greater than the first preset risk event; wherein the fourth preset risk event is used for Instructing the server to repeatedly detect the first preset risk event multiple times. The system according to claim 16, wherein the server is further configured to: when detecting that the version number carried in the key exchange request is inconsistent with the version number of the second key generation protocol, send the The version number of the second key generation protocol is sent to the client; the client is also used to: initiate an agreement update request to the server, and the protocol update request carries the version number of the second key generation protocol version number; the server is also used to: issue the agreement logic and the agreement data of the second key generation agreement to the client; the client is also used to: The key operator layer, the protocol logic, and the protocol data implement the second key generation protocol, and re-initiate the key exchange request to the server based on the second key generation protocol. The system according to claim 23, wherein, the server issues the agreement logic of the second key generation agreement to the client in a hot update manner. The system according to claim 14, wherein the client is further configured to: send a key exchange request to the server after the dynamic update is performed based on the second key generation agreement, and the key exchange The request includes the version number of the second key generation protocol currently held by the client; the server is further configured to: when detecting that the version number carried in the key exchange request is different from the current version number of the server When the version number of the second key generation protocol held is the same, generate a server-side random number, and send the server-side random number to the client; the client is also used to: according to the service Generate a pre-master key randomly at the terminal, and send the pre-master key to the server; the client and the server are also used to: use the second key generation protocol, the The master key, the random number at the user end and the random number at the server end generate a working key, and encrypted communication is performed by exchanging the working key generated respectively. The system according to claim 25, wherein the client is further configured to: after generating the pre-master key according to the random number of the server, use the public key sent by the server to The master key is encrypted, and the encrypted pre-master key is sent to the server; the server is also used to: use the private key to decrypt the encrypted pre-master key to obtain the decrypted The pre-master key.

Images