CN103259768B - A kind of message authentication method, system and device - Google Patents

Abstract

The invention discloses a message authentication method, system and device. The method includes: the sending end and the receiving end save the initialized time stamp for each established connection, and periodically update the time stamp. The time stamp includes sending time stamp and receiving time stamp Timestamp; when data needs to be sent through this connection, the sender generates a message authentication code based on the data message to be sent, the saved sending timestamp and key material, and sends the generated message authentication code together with the message to send the data Send to the receiving end; when receiving the message, the receiving end will verify the correctness of the message authentication code according to the saved receiving time stamp, key material and data message in the message. The invention can solve the replay attack problem existing in the existing transmission control protocol authentication option (TCP-AO) technology.

Description

Method, system and device for message authentication

technical field

The invention relates to routing security technology in a communication network, in particular to a message authentication method, system and device.

Background technique

Most of the existing data networks are based on Internet Protocol (IP, Internet Protocol) technology. The router is the core device on the network based on IP technology. It maintains a set of routing tables through the routing protocol running on it, and according to the The routing table forwards received IP packets. The IP data packet sent by the sender is transmitted to the destination after being forwarded by multiple routers. In order to maintain a set of routing tables, routing protocols on different routers need to exchange routing messages to realize the functions of creating, updating, and learning routing table information. Since the routing message is transmitted in the public network, and its channel is shared by multiple network nodes, an attacker can easily intercept and forge or tamper with the routing message. Once the router receives this wrong routing message, it will generate a wrong routing table; when the routing protocol forwards the IP data packet according to the wrong routing table, it will not be able to transmit the data packet to the destination. To solve this problem, an integrity protection mechanism must be provided for routing protocols to prevent attackers from forging or tampering with routing messages. The basic idea of the integrity protection mechanism is to use the key material to generate a message authentication code for the routing message (this process usually uses a one-way function or a threshold one-way function), and send the message authentication code to the receiver along with the message. After receiving the routing message and authentication code, the attacker uses the corresponding key material to verify the message and its authentication code. Only the routing message that passes the verification is the correct message that has not been tampered by the attacker. Since the attacker has no key material, he will not be able to forge, tamper with the message, and generate the correct message authentication code. This mechanism makes only the routing message generated by the router with the key material pass the verification, and the routing message generated by the attacker without the key material will not pass the verification, thus effectively preventing the attacker from forging and tampering with the routing message.

Transmission Control Protocol Authentication Option (TCP-AO, Transmission Control Protocol Authentication Option) is a lot of routing protocols such as Border Gateway Protocol (BGP, Border Gateway Protocol), Path Computation Element (PCE, Path Computation Element), Label Distribution Protocol (LDP, LabelDistribution Protocol) , Multicast Source Discovery Protocol (MSDP, Multicast Source Discovery Protocol) and other integrity protection mechanisms. It defines a new TCP option: authentication (authentication) option. The routing protocol stores the generated message authentication code in this option, and transmits it to the peer end together with the routing protocol, and the peer end judges whether the routing protocol data has been modified by verifying the correctness of the authentication option.

TCP-AO technology uses sequence number (serial number) to prevent replay (replay) attack. The TCP protocol header has a sequence number (sequence number) field with a length of 32 bits. When establishing a connection, the TCP protocol will randomly generate an initial sequence number, and the sequence number will increase accordingly each time the data is sent and received. In this way, each time a routing protocol packet is sent, the TCP sequence number is different. TCP-AO uses this mechanism to prevent replay attacks. However, this serial number-based technique has the following problems:

1. When the sequence number takes all the values in the sequence number value range, the TCP-AO protocol will reuse the previous sequence number. At this time, the attacker can use the same sequence number before the packet to execute the routing protocol. replay attack;

2. When the TCP connection between the routers is disconnected and then reconnected, the sequence numbers before and after the disconnection may overlap, and the attacker may also implement a replay attack at this time;

3. When the router is restarted, the serial numbers of the TCP connections established before and after the restart may also overlap, and at this time, the attacker may also implement a replay attack.

That is to say, when the sequence number appears repeatedly, the attacker can replace the new data packet with the old data packet with the same sequence number to launch a replay attack. Since the message contains routing protocol data, the receiver will receive an old routing protocol data; and if the old routing protocol data is a routing update message, the receiver will use the old routing updating message to replace the current Routing information, that is, the routing protocol will use outdated routing information for routing, resulting in routing failure. It can be seen that solving the problem of replay attacks is very critical to the security of routing protocols.

A current solution to this problem is to increase the length of the sequence number field to reduce the overlap of the sequence number field. Theoretically, as long as the sequence number field is long enough, there will be no problem of sequence number overlap, and there will be no security risks of replay attacks. However, increasing the sequence number field without limit will increase the communication overhead. In practical applications, since the sequence number cannot be truly infinite, theoretically speaking, increasing the sequence number field cannot fundamentally solve the problem of replay attacks.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a message authentication method, system and device to solve the replay attack problem existing in the existing TCP-AO technology.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

The present invention provides a message authentication method, the method comprising:

The sending end and the receiving end save the initial timestamp for each established connection, and periodically update the timestamp, and the timestamp includes a sending timestamp and a receiving timestamp;

When data needs to be sent through the connection, the sending end generates a message authentication code based on the data message to be sent, the saved sending time stamp and key material, and sends the generated message authentication code to the Receiving end;

When receiving the message, the receiving end verifies the correctness of the message authentication code according to the saved receiving time stamp, key material and data packets in the message.

The sending end and the receiving end save the initial timestamp for each established connection, specifically:

The sending end and the receiving end establish a connection through the flow of the three-way handshake protocol, and exchange their respective time stamps;

After the interaction is completed, the sending end and the receiving end save the initialized time stamp for the established connection, and the value of the sending time stamp saved by the sending end is the same as the value of the receiving time stamp saved by the receiving end, and the received time stamp saved by the sending end The value of the time stamp is the same as the value of the sending time stamp saved by the receiving end.

The regularly updated timestamp is specifically:

One of the sending end and the receiving end initiates a time stamp update process when the set timer expires, and during the updating process, the sending end and the receiving end exchange their respective new time stamps;

After the interaction is completed, the sending end and the receiving end update the time stamps saved respectively, and the value of the new sending time stamp of the sending end is the same as the value of the new receiving time stamp of the receiving end, and the new receiving time stamp of the sending end The value of the stamp is the same as the value of the new sending timestamp of the receiving end.

The present invention also provides a message authentication system, the system includes: a sending end and a receiving end,

The sending end and the receiving end are configured to store an initialized timestamp for each established connection, and periodically update the timestamp, where the timestamp includes a sending timestamp and a receiving timestamp;

The sending end is also used to generate a message authentication code according to the data message to be sent, the saved sending time stamp and key material when it is necessary to send data through the connection, and send the generated message authentication code together with the The message is sent to the receiver together;

The receiving end is further configured to, when receiving the message, verify the correctness of the message authentication code according to the stored receiving time stamp, key material and data packets in the message.

The sending end and the receiving end are further used to establish a connection through the process of the three-way handshake protocol, and exchange respective time stamps;

After the interaction is completed, the sending end and the receiving end save the initialized time stamp for the established connection, and the value of the sending time stamp saved by the sending end is the same as the value of the receiving time stamp saved by the receiving end, and the received time stamp saved by the sending end The value of the time stamp is the same as the value of the sending time stamp saved by the receiving end.

One of the sending end and the receiving end initiates a time stamp update process when the set timer expires, and during the updating process, the sending end and the receiving end exchange their respective new time stamps;

After the interaction is completed, the sending end and the receiving end update the time stamps saved respectively, and the value of the new sending time stamp of the sending end is the same as the value of the new receiving time stamp of the receiving end, and the new receiving time stamp of the sending end The value of the stamp is the same as the value of the new sending timestamp of the receiving end.

The present invention also provides a message authentication device, including:

A time stamp processing module, configured to store an initialized time stamp for each established connection, and periodically update the time stamp, the time stamp includes a sending time stamp and a receiving time stamp;

A sending processing module, configured to generate a message authentication code according to the data message to be sent, the saved sending time stamp and key material when the device as the sending end needs to send data through the connection, and send the generated message The authentication code is sent to the receiving end together with the message of sending data;

The receiving processing module is used to verify the correctness of the message authentication code according to the stored receiving time stamp, key material and data message in the message when the device as the receiving end receives the message from the sending end.

The timestamp processing module at the sending end and the timestamp processing module at the receiving end establish a connection through the process of the three-way handshake protocol and exchange their respective timestamps;

After the interaction is completed, the timestamp processing module of the sending end and the timestamp processing module of the receiving end save the initialized timestamp for the established connection, and the value of the sending timestamp saved by the timestamp processing module of the sending end is the same as that saved by the timestamp processing module of the receiving end. The value of the received timestamp is the same, and the value of the received timestamp saved by the timestamp processing module of the sending end is the same as the value of the sent timestamp saved by the timestamp processing module of the receiving end.

One of the time stamp processing modules of the sending end and the receiving end initiates the update process of the time stamp when the set timer expires, and during the update process, the time stamp processing modules of the sending end and the receiving end exchange their respective new time stamps;

After the interaction is completed, the timestamp processing modules of the sending end and the receiving end update their respective saved timestamps, and the value of the new sending timestamp of the sending end is the same as the value of the new receiving timestamp of the receiving end, and the new receiving time stamp of the sending end The value of the stamp is the same as the value of the new sending timestamp of the receiving end.

A message authentication method, system and device provided by the present invention utilize the difference in time stamps to prevent the replay attack problem caused by sequence number repetitions; since the time stamps are updated regularly, even if the sequence numbers are the same, due to time Different stamps will generate different message authentication codes, which can well solve the replay attack problem existing in the existing TCP-AO technology.

Description of drawings

FIG. 1 is a flowchart of a message authentication method according to an embodiment of the present invention;

FIG. 2 is a flowchart of saving an initialized timestamp for an established connection in an embodiment of the present invention;

Fig. 3 is a flow chart of periodically updating a time stamp in an embodiment of the present invention.

Detailed ways

The technical solutions of the present invention will be further elaborated below in conjunction with the accompanying drawings and specific embodiments.

A message authentication method provided by an embodiment of the present invention, as shown in Figure 1, mainly includes:

In step 101, the sending end and the receiving end save an initialized timestamp for each established connection, and periodically update the timestamp, which includes a sending timestamp and a receiving timestamp.

Embodiments of the present invention extend the TCP protocol and define a new TCP-AO timestamp option, as shown in Table 1 below:

kind Length Data

Table 1

Wherein, Kind is the type definition of the option, and the length is one byte. At present, the type definition after 50 is not defined. Therefore, the embodiment of the present invention defines the content of the new TCP-AO timestamp option as follows:

The value of TCP_AO_T is 50, which is used to identify this type as the TCP-AO timestamp option;

Length is the length of the data segment of the TCP-AO timestamp option, and the length of the data segment defining the TCP-AO timestamp option is 10 bytes in the embodiment of the present invention;

The Data field contains two time data, Time1 and Time2, where Time1 is the sending timestamp and Time2 is the receiving timestamp. The time formats of Time1 and Time2 can be in any identification form with a length of no more than 5 bytes, for example, the number of seconds from January 1, 1979 to the current time, and so on. Time1 and Time2 in any time format belong to the protection scope of the present invention.

In this way, the basic form of the TCP-AO timestamp option is shown in Table 2 below:

50 10 Time1 Time2

Table 2

Embodiments of the present invention do not reuse the existing TCP timestamp option, but define a new TCP-AO timestamp option, with the purpose of preventing the existing TCP protocol stack from performing round-trip time measurement (RTTM, Round Trip Time Measurement) and preventing The sequence number wrapping (PAWS, Protection Against Wrapped Sequence number) process causes the TCP-AO processing flow, which leads to an error in the TCP-AO processing flow of the routing protocol. After the embodiment of the present invention defines the TCP-AO timestamp option, the anti-replay attack technology of TCP-AO will be completely distinguished from the existing RTTM and PAWS processes, so that there is no need to change the existing TCP protocol stack The code is updated, and the backward compatibility is good.

Of course, if another method is used, that is, modify the existing TCP timestamp option definition to distinguish the usefulness of the existing timestamp, and then modify the processing flow of the TCP protocol stack so that it can process TCP timestamps in different ways option. This method is also feasible, but this method greatly changes the existing TCP protocol, which will cause compatibility problems. Embodiments of the present invention also cover this approach.

The embodiment of the present invention also defines the timestamp data structure of TCP-AO, that is, two timestamp storage spaces are established for each TCP connection on each router, one is the timestamp of sending data, and the other is the time of receiving data Stamp, as shown in Table 3 below:

source port number destination port number Send Timestamp (SendT) Receive Timestamp (RecvT)

table 3

Among them, the source port number and the destination port number are both 16-bit numbers, which are used to identify a pair of TCP connections. The format descriptions of SendT and RecvT are the same as Time1 and Time2 in Table 2, which represent the sending timestamp and receiving timestamp respectively. .

It should be noted that the embodiment of the present invention defines the format of the timestamp data structure of TCP-AO, but in practical applications, the SendT and RecvT fields may also be combined in the TCPCB data structure. Embodiments of the present invention encompass this approach.

The difference between the timestamp option and the timestamp data structure is that the timestamp option is used to send a timestamp, and the timestamp data structure is used by TCP-AO to generate a message authentication code.

Step 102, when data needs to be sent through the connection, the sending end generates a message authentication code based on the data message to be sent, the saved sending time stamp and key material, and sends the generated message authentication code together with the message sending the data sent to the receiving end.

Step 103, when the receiving end receives the message, it verifies the correctness of the message authentication code according to the saved receiving time stamp, key material and data packets in the message.

In the above step 103, the sending end and the receiving end save the initialized timestamp for each established connection, and the following methods can be used specifically:

The sending end and the receiving end establish a connection through the process of the three-way handshake protocol, and exchange their respective timestamps;

After the interaction is completed, the sending end and the receiving end save the initial timestamp for the established connection, and the value of the sending timestamp saved by the sending end is the same as the value of the receiving timestamp saved by the receiving end, and the receiving timestamp saved by the sending end The value of is the same as the value of the sending timestamp saved by the receiving end.

The following takes the interaction between the TCP client and the TCP server as an example for illustration. When the TCP connection is established, the specific flow of initializing the timestamp data structure in the embodiment of the present invention is shown in FIG. 2, which mainly includes:

In step 201, the TCP client sends a synchronization (SYN) packet to the TCP server, and at the same time sends its own timestamp. This timestamp can be obtained from the system clock.

Wherein, Syn=j, when the TCP client sends the Syn packet (Syn=j) to the TCP server, the value j of the serial number is a data randomly generated between ^0-232 ; the TCP-AO-T sent by the TCP client Time1 in the option (TCP-AO-T1) is the current time when the TCP client sends the SYN packet, and the value of Time2 is 0. After the TCP client finishes sending, it enters the SYN_SEND state and waits for the TCP server to confirm.

Step 202, the TCP server returns an acknowledgment to the TCP client, including the following content: Ack=j+1, Syn=k, TCP-AO-T2, TCP-AO. Among them, Ack=j+1 means that the TCP server confirms the Syn of the TCP client; Syn=k means that the TCP server itself also sends a SYN packet, and the value k of the sequence number is a number randomly generated between ^0-232 ; -AO-T2 is a TCP-AO-T option, Time1 in this option is the current time when the TCP server returns confirmation, and the value of Time2 is the same as that of the TCP-AO-T option (TCP-AO-T1) in step 201 The value of the Time1 field is the same.

After the TCP server returns confirmation, it enters the SYN_RECV state and waits for the confirmation from the TCP client.

Step 203, the TCP client returns an acknowledgment to the TCP server, including the following content: Ack=k+1, TCP-AO-T3, TCP-AO. Wherein, Ack=k+1 represents that the TCP client confirms the Syn of the TCP server; TCP-AO-T3 is a TCP-AO-T option, and Time1 in this option is 0, and the value of Time2 is the same as that of TCP-AO in step 202 The value of the Time1 field of the -T option (TCP-AO-T2) is the same.

After the TCP client returns the confirmation, it enters the ESTABLISHED state and completes the handshake process. The two parties can then exchange routing protocol data.

The time stamp of the interaction between the TCP client and the TCP server will be saved in their respective data structures (shown in Table 3) after being confirmed, and the serial numbers of the TCP client and TCP server will be saved in the corresponding fields of the TCPCB data structure middle.

In this embodiment, when the TCP connection is established, the timestamp information is initialized, so as to prepare for solving the following problem: before and after the TCP connection between the routers is re-established, or before and after the router is restarted, the sequence number may be repeated, and there is a risk of replay attack .

In addition, when the TCP connection lasts for a long time, the sequence number may be repeated, and once it is repeated, it may cause the hidden danger of replay attack. Therefore, the embodiment of the present application needs to update the time stamp regularly. Specifically, the following method can be adopted: when the set timer expires, one of the sending end and the receiving end initiates the updating process of the time stamp. During the updating process, the sending end and the receiving end The receiving end interacts with their new timestamps; after the interaction is completed, the sending end and the receiving end update their respective saved timestamps, and the value of the new sending timestamp of the sending end is the same as the value of the new receiving timestamp of the receiving end. The value of the new receiving timestamp at the receiving end is the same as the value of the new sending timestamp at the receiving end.

The following takes the interaction between the TCP client and the TCP server as an example to illustrate. The specific process of periodically updating the timestamp is shown in Figure 3, which mainly includes:

In step 301, the TCP client sends routing protocol data to the TCP server, and at the same time sends its own new time stamp.

Among them, TCPHD is a TCP protocol header, which generally includes a sequence number; TCP-AO is a TCP authentication option; RPD is routing protocol data, that is, routing protocol data carried by the TCP protocol. TCP-AO-T4 is a TCP-AO-T option. Time1 in this option is the current time when the TCP client sends, and the value of Time2 is 0.

In step 302, the TCP server responds to the new time stamp of the TCP client and sends its own new time stamp at the same time.

Among them, TCPHD is the TCP protocol header, which generally includes sequence number; TCP-AO is the TCP authentication option; RPD is the data of the routing protocol, that is, the routing protocol data carried by the TCP protocol; TCP-AO-T5 is a TCP-AO-T option, Time1 in this option is the current time when the TCP server responds, and the value of Time2 is the value of the Time1 field of the TCP-AO-T option (TCP-AO-T4) in step 301.

In step 303, the TCP client replies with the new time stamp of the TCP server.

Among them, TCPHD is the TCP protocol header, generally including the sequence number; TCP-AO is the TCP authentication option; RPD is the data of the routing protocol, that is, the routing protocol data carried by the TCP protocol; TCP-AO-T6 is a TCP-AO-T option, in which Time1 is 0, and the value of Time2 is the value of the Time1 field of the TCP-AO-T option (TCP-AO-T5) in step 302.

It should be noted that, in the above embodiment, the operation of regularly updating the time stamp data structure is initiated from the TCP client, of course, it may also be initiated from the TCP server in practical applications. The trigger condition of the operation can be a timer. The timer is set on the initiator. When the timer expires, the initiator sends the option of updating the timestamp to the peer. The time of the timer can be configured and adjusted by the operator.

The timestamps of the interaction between the TCP client and the TCP server will be saved in their respective data structures (shown in Table 3) after being confirmed. The process of updating the timestamp data structure has no effect on the processing of sequence numbers.

This embodiment updates the time stamps of each router, which can effectively avoid the following problem: after the TCP connection between routers is maintained for a long time, the sequence number repeats, which will bring hidden dangers of replay attacks.

The main purpose of the aforementioned embodiments is to maintain a TCP-AO timestamp data structure, and maintaining the TCP-AO timestamp data structure is used to complete the integrity protection of the routing protocol.

When the sender needs to send data through the established connection, the method for generating the message authentication code is as follows:

MAC = MAC_alg(traffic_key, message, SendT)

Among them, MAC indicates the message authentication code calculated by the sender, MAC_alg indicates the calculation method of the message authentication code, traffic_key indicates the key material, message indicates the TCP data message, and SendT indicates the sending timestamp corresponding to the connection saved by the sender.

The method for the receiver to verify the correctness of the message authentication code is as follows:

MAC = MAC_alg(traffic_key, message, RecvT)

Among them, MAC represents the message authentication code calculated by the receiving end, MAC_alg represents the calculation method of the message authentication code, traffic_key represents the key material, message represents the TCP data message, and RecvT represents the receiving timestamp corresponding to the connection saved by the receiving end. After the embodiments shown in FIG. 2 and FIG. 3 , it can be guaranteed that the SendT saved at the sending end is the same as the RecvT saved at the receiving end.

Compare the message verification code calculated by the receiving end with the message verification code sent by the sending end. If the two are consistent, the verification is correct; otherwise, the verification is wrong.

It can be seen from this that the embodiments of the present invention can well solve the following problems of the existing TCP-AO technology:

1. When the TCP connection is restarted (including router system restart and TCP connection disconnection and reconnection), the sequence numbers may overlap, causing replay attacks;

2. When the TCP connection time is too long, the sequence numbers may overlap, causing replay attacks.

Regarding the first problem, according to the embodiment of the present invention, since the current system time is taken as the time stamp every time the TCP connection is re-established, the system time is different each time and must be incremented. Therefore, after the timestamp is added to the process of generating message authentication codes, even if the sequence numbers overlap, the generated message authentication codes will be different due to different timestamps. In this way, the replay attack problem when the TCP connection is restarted can be well solved.

For the second problem, according to the embodiment of the present invention, when the TCP connection time is too long, the time stamp will be updated. As long as the time stamp is updated before the sequence number overlaps, the generated message authentication code will be different, thereby solving the TCP connection problem. Replay attack problem when the time is too long.

In addition, in the embodiment of the present invention, the time stamp is only updated periodically and sent through the TCP-AO time stamp option. Therefore, the embodiment of the present invention can save transmission overhead.

In the embodiment of the present invention, the sequence number-based anti-replay attack mechanism designed by TCP-AO itself has not been discarded, so the embodiment of the present invention is an enhancement to the existing TCP-AO mechanism without affecting the existing There is too much impact on the TCP-AO mechanism.

The embodiment of the present invention only changes the generation mechanism of the message authentication code, but does not change the TCP protocol interaction process after adding the TCP-AO timestamp option. Therefore, after adding the functions of this embodiment, the TCP protocol when using the TCP-AO option The approach does not differ from existing standards.

The embodiment of the present invention makes the value of the message authentication code not only determined by the sequence number and routing protocol information, but also determined by the time stamp, thereby preventing the problem of replay attack when the sequence number is repeated. In summary, the embodiments of the present invention can solve the problems existing in the prior art, so that the Internet Security Association and Key Management Protocol (ISAKMP, Internet Security Association and Key Management Protocol) can use the EAP (identity authentication) protocol and the diameter protocol A variety of authentication processes are carried out to meet the needs of key management in router networks with different topological structures.

In addition, corresponding to the message authentication method of the embodiment of the present invention, the embodiment of the present invention also provides a message authentication system, including: a sending end and a receiving end.

The sending end and the receiving end are configured to store an initialized timestamp for each established connection, and periodically update the timestamp, where the timestamp includes a sending timestamp and a receiving timestamp;

The sender is also used to generate a message authentication code according to the data message to be sent, the saved sending time stamp and key material when it needs to send data through the connection, and send the generated message authentication code together with the message sending the data sent together to the receiver;

The receiving end is also used to, when receiving the message, verify the correctness of the message authentication code according to the saved receiving time stamp, key material and data packets in the message.

Preferably, the sending end and the receiving end can be further used to establish a connection through the process of the three-way handshake protocol, and exchange their respective timestamps;

After the interaction is completed, the sending end and the receiving end save the initial timestamp for the established connection, and the value of the sending timestamp saved by the sending end is the same as the value of the receiving timestamp saved by the receiving end, and the receiving timestamp saved by the sending end The value of is the same as the value of the sending timestamp saved by the receiving end.

Preferably, one of the sending end and the receiving end initiates a time stamp update process when the set timer expires, and during the update process, the sending end and the receiving end exchange their respective new time stamps;

After the interaction is completed, the sender and the receiver update their respective saved timestamps, and the value of the new send timestamp of the sender is the same as the value of the new receive timestamp of the receiver, and the value of the new receive timestamp of the sender is It is the same as the value of the new sending timestamp at the receiving end.

The embodiment of the present invention also provides a message authentication device, which has the functions of a sending end and a receiving end, and the device includes: a time stamp processing module, a sending processing module and a receiving processing module.

Wherein, the timestamp processing module is configured to save an initialized timestamp for each established connection, and periodically update the timestamp, the timestamp includes a sending timestamp and a receiving timestamp;

The sending processing module is used to generate a message authentication code according to the data message to be sent, the saved sending time stamp and key material when the device as the sending end needs to send data through the connection, and send the generated message authentication code Send to the receiving end together with the message of sending data;

The receiving processing module is used to verify the correctness of the message authentication code according to the stored receiving time stamp, key material and data message in the message when the device as the receiving end receives the message from the sending end.

Preferably, the timestamp processing module at the sending end and the timestamp processing module at the receiving end establish a connection through the process of the three-way handshake protocol, and exchange their respective timestamps;

After the interaction is completed, the timestamp processing module of the sending end and the timestamp processing module of the receiving end save the initialized timestamp for the established connection, and the value of the sending timestamp saved by the timestamp processing module of the sending end is the same as that saved by the timestamp processing module of the receiving end. The value of the received timestamp is the same, and the value of the received timestamp saved by the timestamp processing module of the sending end is the same as the value of the sent timestamp saved by the timestamp processing module of the receiving end.

Preferably, one of the time stamp processing modules at the sending end and the receiving end initiates a time stamp update process when the set timer expires, and during the update process, the time stamp processing modules at the sending end and the receiving end exchange their respective new timestamp;

After the interaction is completed, the timestamp processing modules of the sending end and the receiving end update their respective saved timestamps, and the value of the new sending timestamp of the sending end is the same as the value of the new receiving timestamp of the receiving end, and the new receiving time stamp of the sending end The value of the stamp is the same as the value of the new sending timestamp of the receiving end.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (9)

1. a kind of message authentication method, which is characterized in that this method includes：

Transmitting terminal and receiving terminal are that the connection each established preserves the timestamp of initialization, and regularly update the timestamp, institute It states timestamp and includes sending time stamp and receiving time stamp；

When needing through the connection transmission data, transmitting terminal is according to data message to be sent, the sending time preserved stamp And key material, message authentication code is generated, and the message authentication code of generation is sent jointly to connect in company with the message of transmission data Receiving end；

When receiving terminal receives the message, according to the data message in receiving time stamp, key material and the message preserved, certification The correctness of the message authentication code；

Wherein, the sending time stamp that transmitting terminal preserves is identical with the receiving time stamp that receiving terminal preserves.

2. message authentication method according to claim 1, which is characterized in that the transmitting terminal and receiving terminal are each established Connection preserves the timestamp of initialization, specially：

The transmitting terminal and receiving terminal establish connection, and the respective timestamp of interaction by the flow of three-way handshake agreement；

After interaction, the transmitting terminal and receiving terminal are that the connection established preserves the timestamp of initialization, and transmitting terminal preserves Sending time stamp value it is identical with the value of receiving time that receiving terminal preserves stamp, what the receiving time of transmitting terminal preservation was stabbed Value is identical with the value of sending time stamp that receiving terminal preserves.

3. message authentication method according to claim 2, which is characterized in that the timestamp that regularly updates is specially：

A wherein side for the transmitting terminal and receiving terminal initiates the renewal process of timestamp when the timer of setting expires, In renewal process, the transmitting terminal and receiving terminal interact respective new timestamp；

After interaction, the transmitting terminal and receiving terminal update the timestamp respectively preserved, and the new transmission of the transmitting terminal The value of the new receiving time stamp of the value of timestamp and receiving terminal is identical, the value of the new receiving time stamp of transmitting terminal with The value of the new sending time stamp of receiving terminal is identical.

4. a kind of message authentication system, which is characterized in that the system includes：Transmitting terminal and receiving terminal,

Transmitting terminal and receiving terminal for preserving the timestamp of initialization for the connection each established, and regularly update the time Stamp, the timestamp include sending time stamp and receiving time stamp；

Transmitting terminal is additionally operable to, when needing through the connection transmission data, according to data message to be sent, the transmission preserved Timestamp and key material generate message authentication code, and the message authentication code of generation are risen in company with the message one of transmission data Give receiving terminal；

Receiving terminal is additionally operable to, when receiving the message, according to the data in receiving time stamp, key material and the message preserved Message, the correctness of message authentication code described in certification；

Wherein, the sending time stamp that transmitting terminal preserves is identical with the receiving time stamp that receiving terminal preserves.

5. message authentication system according to claim 4, which is characterized in that the transmitting terminal and receiving terminal are further used for, Connection, and the respective timestamp of interaction are established by the flow of three-way handshake agreement；

After interaction, the transmitting terminal and receiving terminal are that the connection established preserves the timestamp of initialization, and transmitting terminal preserves Sending time stamp value it is identical with the value of receiving time that receiving terminal preserves stamp, what the receiving time of transmitting terminal preservation was stabbed Value is identical with the value of sending time stamp that receiving terminal preserves.

6. message authentication system according to claim 5, which is characterized in that a wherein side for the transmitting terminal and receiving terminal exists When the timer of setting expires, the renewal process of timestamp is initiated, at no point in the update process, the transmitting terminal and receiving terminal interaction are each From new timestamp；

After interaction, the transmitting terminal and receiving terminal update the timestamp respectively preserved, and the new transmission of the transmitting terminal The value of the new receiving time stamp of the value of timestamp and receiving terminal is identical, the value of the new receiving time stamp of transmitting terminal with The value of the new sending time stamp of receiving terminal is identical.

7. a kind of message authentication device, which is characterized in that including：

Timestamp processing module for preserving the timestamp of initialization for the connection each established, and regularly updates the time Stamp, the timestamp include sending time stamp and receiving time stamp；

Send processing module, for described device as transmitting terminal need by it is described connect transmission data when, according to pending The data message that send, the sending time preserved stamp and key material, generate message authentication code, and by the message authentication code of generation with Message with transmission data sends jointly to receiving terminal；

Receiving processing module, for when described device receives the message from transmitting terminal as receiving terminal, being connect according to what is preserved Receive the data message in timestamp, key material and message, the correctness of certification message authentication code；

Wherein, the sending time stamp that transmitting terminal preserves is identical with the receiving time stamp that receiving terminal preserves.

8. message authentication device according to claim 7, which is characterized in that the timestamp processing module and receiving terminal of transmitting terminal Timestamp processing module, connection, and the respective timestamp of interaction are established by the flow of three-way handshake agreement；

After interaction, the timestamp processing module of transmitting terminal and the timestamp processing module of receiving terminal are that the connection established preserves The timestamp of initialization, and the value of sending time stamp of the timestamp processing module preservation of transmitting terminal and the timestamp of receiving terminal The value of receiving time stamp that processing module preserves is identical, and the receiving time stamp of the timestamp processing module preservation of transmitting terminal takes It is worth identical with the value of sending time stamp that the timestamp processing module of receiving terminal preserves.

9. message authentication device according to claim 8, which is characterized in that the timestamp processing module of transmitting terminal and receiving terminal A wherein side when the timer of setting expires, initiate the renewal process of timestamp, at no point in the update process, transmitting terminal and reception The timestamp processing module at end interacts respective new timestamp；

After interaction, timestamp that the update of the timestamp processing module of transmitting terminal and receiving terminal respectively preserves, and transmitting terminal The value of new sending time stamp is identical with the value of the new receiving time stamp of receiving terminal, the new receiving time stamp of transmitting terminal Value and receiving terminal new sending time stamp value it is identical.