Identity authentication method and device

Abstract

The present application relates to an identity authentication method and device, and to the field of identity authentication technology. The method includes the following steps: the client sends a seed request to the server; the server responds to the seed request, randomly generates a seed of preset bytes, encrypts it to obtain an encrypted seed, and sends it to the client; the server and the client process the encrypted seed based on a preset algorithm, in conjunction with a public key and a private key, to obtain the corresponding server-side Key and client-side Key respectively; the server compares the server-side Key and the client-side Key, and if the comparison is consistent, it is determined that the client has passed the identity authentication. The present application improves the UDS standard protocol, based on a randomly generated seed, and uses a preset algorithm to calculate and compare the keys on both sides, without requiring too many keys, and effectively ensures information security while ensuring the reliability of identity authentication.

Description

Technical Field

[0001] The present application relates to the field of identity authentication technology, and in particular to an identity authentication method and device. Background Art

[0002] At present, the diagnostic testers developed by automobile manufacturers mostly use the 27 services of the UDS standard diagnostic protocol to access each node securely, and each node needs to be assigned a different key. However, as the number of vehicle nodes continues to increase, the number of keys will also increase. It will become more and more complicated to use different keys to authenticate and manage the vehicle system, and the key security cannot be guaranteed. Therefore, traditional technical solutions can no longer meet current production needs.

[0003] An identity authentication method technology is now provided to meet current production needs. Summary of the invention

[0004] The present application provides an identity authentication method and device, which improves the UDS standard protocol, calculates and compares the double-sided keys based on a randomly generated seed using a preset algorithm, does not require too many keys, and effectively ensures information security while ensuring the reliability of identity authentication.

[0005] In a first aspect, the present application provides an identity authentication method, the method comprising the following steps:

[0006] The client sends a seed request to the server;

[0007] The server responds to the seed request, randomly generates a seed of preset bytes, encrypts the seed to obtain an encrypted seed, and sends the encrypted seed to the client;

[0008] The server and the client process the encrypted seed based on a preset algorithm to obtain a corresponding server-side Key and client-side Key respectively;

[0009] The server compares the server-side Key and the client-side Key, and if the comparison is consistent, it is determined that the client has passed the identity authentication.

[0010] Specifically, the server and the client process the encrypted seed based on a preset algorithm to obtain the corresponding server-side Key and client-side Key, respectively, including the following steps:

[0011] The client processes the encrypted seed based on the MD5 digest algorithm to obtain client-side digest data;

[0012] The client uses the private key SK of the asymmetric RSA1024 algorithm to decrypt the encrypted seed to obtain the seed;

[0013] The client uses the seed as the key of the AES algorithm to encrypt the client-side summary data to obtain the client-side Key.

[0014] Specifically, the server and the client process the encrypted seed based on a preset algorithm to obtain the corresponding server-side Key and client-side Key, respectively, including the following steps:

[0015] The server processes the encrypted seed based on the MD5 digest algorithm to obtain server-side digest data;

[0016] The server uses the seed as the key of the AES algorithm to encrypt the server-side summary data to obtain the server-side Key.

[0017] Specifically, the server randomly generates a seed of preset bytes and encrypts it to obtain an encrypted seed, and sends it to the client, including the following steps:

[0018] The server randomly generates a seed of preset bytes;

[0019] The server encrypts the seed using the public key PK of the asymmetric RSA1024 algorithm to obtain the encrypted seed.

[0020] Specifically, the seed is 16 bytes;

[0021] The encryption seed is 128 bytes.

[0022] Specifically, the server-side Key and the client-side Key are 16 bytes.

[0023] In a second aspect, the present application provides an identity authentication device, the device comprising:

[0024] A seed request module configured on the client, which is used to send a seed request to the server;

[0025] A seed generation module configured on the server, which is used to respond to the seed request, randomly generate a seed of preset bytes, encrypt the seed to obtain an encrypted seed, and send it to the client;

[0026] A server-side Key generation module configured on the server, which is used to process the encrypted seed to obtain a corresponding server-side Key;

[0027] A client-side Key generation module configured on the client, which is used to process the encrypted seed to obtain a corresponding client-side Key;

[0028] The identity authentication module configured on the server is used to compare the server-side Key and the client-side Key. If the comparison is consistent, it is determined that the client has passed the identity authentication.

[0029] Furthermore, the client-side Key generation module is further used to process the encryption seed based on the MD5 digest algorithm to obtain client-side digest data;

[0030] The client-side Key generation module is also used to decrypt the encrypted seed using the private key SK of the asymmetric RSA1024 algorithm to obtain the seed;

[0031] The client-side Key generation module is also used to use the seed as the key of the AES algorithm to encrypt the client-side summary data to obtain the client-side Key.

[0032] Furthermore, the server-side Key generation module is further used to process the encryption seed based on the MD5 digest algorithm to obtain server-side digest data;

[0033] The server-side Key generation module is also used to use the seed as the key of the AES algorithm to encrypt the server-side summary data to obtain the server-side Key.

[0034] Furthermore, the seed generation module is also used to randomly generate a seed of preset bytes;

[0035] The seed generation module is also used to encrypt the seed using the public key PK of the asymmetric RSA1024 algorithm to obtain the encrypted seed.

[0036] Specifically, the seed is 16 bytes;

[0037] The encryption seed is 128 bytes.

[0038] Specifically, the server-side Key and the client-side Key are 16 bytes.

[0039] The beneficial effects of the technical solution provided by this application include:

[0040] This application improves the UDS standard protocol. Based on randomly generated seeds, it uses a preset algorithm to calculate and compare the keys on both sides. It does not require too many keys and effectively ensures information security while ensuring the reliability of identity authentication. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Terminology explanation:

[0042] UDS: Unified Diagnostic Services, unified diagnostic services;

[0043] AES: Advanced Encryption Standard, Advanced Encryption Standard;

[0044] ABS: Antilock Brake System, anti-lock braking system;

[0045] TPMS: Tire Pressure Monitoring System, tire pressure management system.

[0046] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0047] Figure 1 A flowchart of the steps of the identity authentication method provided in the embodiment of the present application;

[0048] Figure 2 This is a flow chart of secure unlocking of the UDS protocol 27 service in the embodiment of the present application;

[0049] Figure 3 This is a schematic diagram of a model in the 27 service security access model of the UDS diagnostic protocol in an embodiment of the present application;

[0050] Figure 4 This is an improved service authentication flow chart 27 corresponding to the identity authentication method in the embodiment of the present application;

[0051] Figure 5 This is an improved 27 service security access model diagram corresponding to the identity authentication method in the embodiment of the present application. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0053] The embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0054] The embodiment of the present application provides an identity authentication method and device, which uses a preset algorithm to calculate and compare bilateral keys based on a randomly generated seed, does not require too many keys, and effectively ensures information security while ensuring the reliability of identity authentication.

[0055] In order to achieve the above technical effects, the overall idea of ​​this application is as follows:

[0056] An identity authentication method, the method comprising the following steps:

[0057] S1. The client sends a seed request to the server;

[0058] S2. The server responds to the seed request, randomly generates a seed of preset bytes, encrypts it to obtain an encrypted seed, and sends it to the client;

[0059] S3, the server and the client process the encrypted seed based on the preset algorithm to obtain the corresponding server-side Key and client-side Key respectively;

[0060] S4. The server compares the server-side Key and the client-side Key. If the comparison is consistent, it is determined that the client has passed the identity authentication.

[0061] The embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0062] First, see Figures 1 to 5 As shown, the embodiment of the present application provides an identity authentication method, which includes the following steps:

[0063] S1. The client sends a seed request to the server;

[0064] S2. The server responds to the seed request, randomly generates a seed of preset bytes, encrypts it to obtain an encrypted seed, and sends it to the client;

[0065] S3, the server and the client process the encrypted seed based on the preset algorithm to obtain the corresponding server-side Key and client-side Key respectively;

[0066] S4. The server compares the server-side Key and the client-side Key. If the comparison is consistent, it is determined that the client has passed the identity authentication.

[0067] In the embodiment of the present application, the UDS standard protocol is improved, and the calculation and comparison of the bilateral keys are performed using a preset algorithm based on a randomly generated seed. No excessive keys are required, and information security is effectively guaranteed while ensuring the reliability of identity authentication.

[0068] Furthermore, in the past, when automobile manufacturers developed diagnostic testers and used the 27 services of the UDS standard diagnostic protocol to securely access each node, each node needed to be assigned a different key. As the number of vehicle nodes continues to increase, the number of keys will also increase. It will become more and more complicated to use different keys to authenticate and manage the vehicle system, and the security of the keys cannot be guaranteed. By using the public-private key system of the asymmetric encryption algorithm RSA1024, combined with the data digest MD5 algorithm and the symmetric encryption algorithm AES, the 27 service security access process of the UDS standard protocol is improved to achieve identity authentication and key management, effectively solving the problems existing in the previous 27 services and greatly improving the information security of the vehicle.

[0069] Here, we provide additional explanations on the UDS protocol, as follows:

[0070] The UDS protocol is a diagnostic service protocol currently used by most automobile manufacturers. It can complete functions such as parameter calibration, diagnostic testing, and Bootloader download. Since these functions will involve the information security of the vehicle, the current processing methods all need to use the UDS protocol's 27 services for security authentication. UDS's 27 services provide a method to access data or diagnostic services. Only through the seed-key unlocking process can specific services and functions be performed. This service provides a protection mechanism that is used to protect access-restricted diagnostic content. According to the international standard protocol ISO 14229-1-2013 Road vehicles--Unified diagnostic services (UDS)--Part 1 Specification and requirements, the process of secure unlocking of the 27 service is based on the Seed-Key mechanism. The specific process can be divided into the following four stages, as follows: Figure 2 shown.

[0071] It should be noted that the traditional identity authentication process is as follows:

[0072] A1. Client requests a seed from Server.

[0073] A2. Server sends a random seed to Client;

[0074] A3. The client calculates the corresponding key based on the random seed received from the server and sends it to the server;

[0075] A4. Server receives the Key calculated from the Client and compares it with the internally calculated Key. If they are consistent, unlocking is successful, otherwise unlocking fails.

[0076] Client is the client and Server is the server.

[0077] Based on the traditional identity authentication process, each 27 service security unlocking process starts with the Client initiating a Seed request and ends with the Server replying a positive or negative response.

[0078] The above 27 service processes are the security access processes specified by the ISO International Standards Organization, and are also the security access methods followed by most domestic automobile host manufacturers.

[0079] According to the above 27 service security access model, the security of the security unlocking process depends on the security algorithm, and the security algorithm generally adopts a general encryption algorithm, which is generally a public algorithm such as DES / XTEA / AES, so the security of the entire security unlocking process depends on the non-public security algorithm key. Before the client and the server perform security authentication, the client and the server need to have a common key, and then the security authentication can be performed. In the point-to-point authentication process, the above model can be well executed, but in the actual application process, especially for automobile manufacturers, there are many nodes on the vehicle. In order to simplify the modeling, take the vehicle with ABS (anti-lock braking system), GW (gateway), IC (instrument), TPMS (tire pressure management system) four nodes, and the IC (instrument) node can be supplied by two parts manufacturers (IC1 or IC2) respectively. At this time, the Tester (diagnostic instrument) developed by the vehicle manufacturer needs to perform security access to all the above four nodes. In the 27 service security access model of the UDS standard diagnostic protocol, Tester belongs to Client, IC / ABS / TPMS / GW belongs to Server, and the specific identity authentication and key management model is as follows Figure 3 .

[0080] Tester and IC / ABS / TPMS / GW use the same security algorithm and use different keys for identity authentication. For example, key 1 is used when accessing IC and key 2 is used when accessing ABS. Key management is performed through key isolation. For example, IC only has key 1 but no other keys, and ABS only has key 2 but no other keys. Therefore, identity authentication and key management functions can be completed by having unique keys between Tester and nodes.

[0081] Regarding the traditional identity authentication process, its technical solution has the following technical problems:

[0082] First, the Tester needs to have the keys of all nodes, which makes key management more troublesome.

[0083] Secondly, the Tester needs to disclose the key of each node to each node. If the key of a node is leaked, the security of the node cannot be guaranteed.

[0084] Third, if a node has multiple suppliers, such as IC, Figure 3 As shown, IC1 and IC2 have the same key. At this time, the manufacturers of IC1 and IC2 can access each other. The security between them cannot be guaranteed.

[0085] Fourthly, once the key of this solution is confirmed, in order to be compatible with previous products, the key will generally not be changed in the future. If the key is leaked at a certain period of time, it will cause a major risk to the security of the entire product.

[0086] Based on the above technical problems, the technical solution of the embodiment of the present application improves the 27 service processes of the existing UDS standard protocol, making identity authentication and key management simpler and safer, and the technical solution of the embodiment of the present application is compatible with old protocols and codes.

[0087] Specifically, the server and the client process the encrypted seed based on a preset algorithm to obtain the corresponding server-side Key and client-side Key, respectively, including the following steps:

[0088] The client processes the encrypted seed based on the MD5 digest algorithm to obtain client-side digest data;

[0089] The client uses the private key SK of the asymmetric RSA1024 algorithm to decrypt the encrypted seed to obtain the seed;

[0090] The client uses the seed as the key of the AES algorithm to encrypt the client-side summary data to obtain the client-side Key.

[0091] Specifically, the server and the client process the encrypted seed based on a preset algorithm to obtain the corresponding server-side Key and client-side Key, respectively, including the following steps:

[0092] The server processes the encrypted seed based on the MD5 digest algorithm to obtain server-side digest data;

[0093] The server uses the seed as the key of the AES algorithm to encrypt the server-side summary data to obtain the server-side Key.

[0094] Specifically, the server randomly generates a seed of preset bytes and encrypts it to obtain an encrypted seed, and sends it to the client, including the following steps:

[0095] The server randomly generates a seed of preset bytes;

[0096] The server encrypts the seed using the public key PK of the asymmetric RSA1024 algorithm to obtain the encrypted seed.

[0097] Specifically, the seed is 16 bytes;

[0098] The encryption seed is 128 bytes.

[0099] Specifically, the server-side Key and the client-side Key are 16 bytes.

[0100] Based on the above technical solution, a specific implementation process of this application is given, which is as follows:

[0101] Q1. Client requests a seed from Server.

[0102] Q2. The server generates a 16-byte random seed, and then encrypts the seed using the public key PK of the asymmetric RSA1024 algorithm to generate a 128-byte encrypted seed, which is then sent to the client.

[0103] Q3. Based on the 128-byte encrypted Seed received from the Server, the Client first compresses the encrypted key into a 16-byte summary data Hm using the MD5 digest algorithm, then uses the private key SK of the asymmetric RSA1024 algorithm to decrypt the encrypted Seed to obtain the original 16-byte random seed Seed, and finally uses the original 16-byte random seed Seed as the key of the AES algorithm to encrypt Hm to obtain a 16-byte encrypted Key, which is then sent to the Server;

[0104] Q4. The server receives the encryption key calculated by the client and compares it with the key calculated by the server through the MD5 digest algorithm and AES encryption addition. If they are consistent, the unlocking is successful, otherwise the unlocking fails.

[0105] Client is the client and Server is the server.

[0106] It should be noted that the technical solution of the embodiment of the present application uses an asymmetric encryption algorithm RSA1024 to encrypt a randomly generated 16-byte Seed using a public key PK to obtain a 128-byte encrypted Seed, uses the MD5 algorithm to perform summary processing on the encrypted Seed for data compression to obtain a 16-byte data summary Hm, uses the randomly generated 16-byte Seed as the AES key to encrypt the 16-byte data summary Hm for identity authentication, and other algorithms are combined to achieve identity authentication and key management. The improved 27 service authentication process is as follows: Figure 4 As shown;

[0107] The public / private key system of the asymmetric encryption algorithm RSA1024 is used, combined with the data digest MD5 algorithm and the symmetric encryption algorithm AES, to improve the 27 security access service process of the UDS standard protocol to achieve identity authentication and key management, which can effectively solve the four problems existing in the previous 27 service security access. The specific security access model is as follows: Figure 5 .

[0108] Furthermore, based on the technical solutions of the embodiments of the present application, some technical principles are explained as follows:

[0109] First, the public key PK of the asymmetric RSA1024 algorithm is used to encrypt the Seed generated by the server. The encryption and decryption keys of the asymmetric encryption algorithm are different. The Tester has the private key SK and public key PK of the RSA1024 algorithm. IC / ABS / TPMS / GW all have the public key PK of the RSA1024 algorithm. The public key PK can only encrypt data, and the private key SK can only decrypt data. In actual application, the Tester generates the private key and public key of the system, and then releases the public key to the IC / ABS / TPMS / GW. The automobile manufacturer only needs to ensure the security of the Tester's private key, and the entire system is safe. The RSA1024 algorithm is used in this solution to transmit the AES encryption key for identity authentication (that is, the 16-byte random seed generated by the Server). IC / ABS / TPMS / GW securely transmits the AES encryption key used for identity authentication to the Tester through the public key of RSA1024.

[0110] Considering that the computing power of IC / ABS / TPMS / GW on the server side is relatively weak, this solution uses RSA1024 instead of RSA2048. In addition, the public key PK used for encryption is fixed to 3. This greatly reduces the computing power requirements for encryption using the public key PK on the server side, speeding up the operation of the server side.

[0111] Second, use the MD5 digest algorithm to compress the 128-byte encryption Seed to generate a 16-byte Hm as the data input for the AES encryption algorithm. Since the AES algorithm is a 128-bit symmetric encryption algorithm and can only encrypt 16 bytes at a time, the MD5 algorithm is needed to compress the 128-byte encryption Seed to generate a 16-byte Hm in this solution.

[0112] Third, use the AES algorithm to use the 16-byte random seed Seed generated by the server as the key, encrypt the 16-byte Hm generated by the MD5 algorithm to generate a 16-byte encryption Key, and compare the encryption Key results generated by the server and the client to perform identity authentication. If the KEY results are the same, the identity authentication is successful.

[0113] Fourth, the 16-byte random seed Seed is the AES algorithm key, which is randomly generated. For a single node, the 27 service will generate a random AES algorithm key each time. Even if the random key of a single node is cracked, the next time the 27 service will generate a new key, making it meaningless for the key of a single node to be cracked; for multiple nodes, the 27 service will randomly generate a random original Seed (AES algorithm key) when accessing each node, which can ensure that the algorithm key of each node accessed by the Tester is different and changing. The randomness of the algorithm key will greatly increase the difficulty of cracking.

[0114] In a second aspect, the embodiment of the present application provides an identity authentication device based on the technology of the identity authentication method mentioned in the first aspect, and the device includes:

[0115] A seed request module configured on the client, which is used to send a seed request to the server;

[0116] A seed generation module configured on the server, which is used to respond to the seed request, randomly generate a seed of preset bytes, encrypt the seed to obtain an encrypted seed, and send it to the client;

[0117] A server-side Key generation module configured on the server, which is used to process the encrypted seed to obtain a corresponding server-side Key;

[0118] A client-side Key generation module configured on the client, which is used to process the encrypted seed to obtain a corresponding client-side Key;

[0119] The identity authentication module configured on the server is used to compare the server-side Key and the client-side Key. If the comparison is consistent, it is determined that the client has passed the identity authentication.

[0120] In the embodiment of the present application, based on the randomly generated seeds, a preset algorithm is used to calculate and compare the bilateral keys, without the need for too many keys, and information security is effectively guaranteed while ensuring the reliability of identity authentication.

[0121] Furthermore, the client-side Key generation module is further used to process the encryption seed based on the MD5 digest algorithm to obtain client-side digest data;

[0122] The client-side Key generation module is also used to decrypt the encrypted seed using the private key SK of the asymmetric RSA1024 algorithm to obtain the seed;

[0123] The client-side Key generation module is also used to use the seed as the key of the AES algorithm to encrypt the client-side summary data to obtain the client-side Key.

[0124] Furthermore, the server-side Key generation module is further used to process the encryption seed based on the MD5 digest algorithm to obtain server-side digest data;

[0125] The server-side Key generation module is also used to use the seed as the key of the AES algorithm to encrypt the server-side summary data to obtain the server-side Key.

[0126] Furthermore, the seed generation module is also used to randomly generate a seed of preset bytes;

[0127] The seed generation module is also used to encrypt the seed using the public key PK of the asymmetric RSA1024 algorithm to obtain the encrypted seed.

[0128] Specifically, the seed is 16 bytes;

[0129] The encryption seed is 128 bytes.

[0130] Specifically, the server-side Key and the client-side Key are 16 bytes.

[0131] It should be noted that the identity authentication device of the embodiment of the present application is similar to the identity authentication method principle mentioned in the first aspect in terms of technical issues, technical means and technical effects, and will not be elaborated here.

[0132] It should be noted that, in this application, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0133] The above is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

Claims

1. An identity authentication method, characterized in that: The method comprises the following steps: The client sends a seed request to the server; The server responds to the seed request, randomly generates a seed of preset bytes, encrypts the seed to obtain an encrypted seed, and sends the encrypted seed to the client; The server and the client process the encrypted seed based on a preset algorithm to obtain a corresponding server-side Key and client-side Key respectively; The server compares the server-side Key and the client-side Key, and if the comparison is consistent, it is determined that the client has passed the identity authentication; The server and the client process the encrypted seed based on a preset algorithm to obtain a corresponding server-side Key and client-side Key, respectively, including the following steps: The client processes the encrypted seed based on the MD5 digest algorithm to obtain client-side digest data; The client uses the private key SK of the asymmetric RSA1024 algorithm to decrypt the encrypted seed to obtain the seed; The client uses the seed as the key of the AES algorithm to encrypt the client-side summary data to obtain the client-side Key.

2. The identity authentication method according to claim 1, characterized in that: The server and the client process the encrypted seed based on a preset algorithm to obtain a corresponding server-side Key and client-side Key, respectively, including the following steps: The server processes the encrypted seed based on the MD5 digest algorithm to obtain server-side digest data; The server uses the seed as the key of the AES algorithm to encrypt the server-side summary data to obtain the server-side Key.

3. The identity authentication method according to claim 1, characterized in that: The server randomly generates a seed of preset bytes and encrypts it to obtain an encrypted seed, and sends it to the client, including the following steps: The server randomly generates a seed of preset bytes; The server encrypts the seed using the public key PK of the asymmetric RSA1024 algorithm to obtain the encrypted seed.

4. The identity authentication method according to claim 1, characterized in that: The seed is 16 bytes; The encryption seed is 128 bytes.

5. The identity authentication method according to claim 1, characterized in that: The server-side Key and the client-side Key are 16 bytes.

6. An identity authentication device, characterized in that: The device comprises: A seed request module configured on the client, which is used to send a seed request to the server; A seed generation module configured on the server, which is used to respond to the seed request, randomly generate a seed of preset bytes, encrypt the seed to obtain an encrypted seed, and send it to the client; A server-side Key generation module configured on the server, which is used to process the encrypted seed to obtain a corresponding server-side Key; A client-side Key generation module configured on the client, which is used to process the encrypted seed to obtain a corresponding client-side Key; The identity authentication module configured on the server is used to compare the server-side Key and the client-side Key. If the comparison is consistent, it is determined that the client has passed the identity authentication; The client-side Key generation module is also used to process the encryption seed based on the MD5 digest algorithm to obtain client-side digest data; The client-side Key generation module is also used to decrypt the encrypted seed using the private key SK of the asymmetric RSA1024 algorithm to obtain the seed; The client-side Key generation module is also used to use the seed as the key of the AES algorithm to encrypt the client-side summary data to obtain the client-side Key.

7. The identity authentication device as claimed in claim 6, characterized in that: The server-side Key generation module is also used to process the encryption seed based on the MD5 digest algorithm to obtain server-side digest data; The server-side Key generation module is also used to use the seed as the key of the AES algorithm to encrypt the server-side summary data to obtain the server-side Key.

8. The identity authentication device as claimed in claim 6, characterized in that: The seed generation module is also used to randomly generate a seed of preset bytes; The seed generation module is also used to encrypt the seed using the public key PK of the asymmetric RSA1024 algorithm to obtain the encrypted seed.

Images