Identity authentication method and device

By generating private keys by mnemonics and using asymmetric encryption, the simplicity and high security of identity authentication are achieved, and the problems of cumbersome and insufficient security of identity authentication information in the prior art are solved.

CN115865369BActive Publication Date: 2024-11-05CHINA UNITED NETWORK COMM GRP CO LTD +2
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202211486656.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-11-24
Publication Date
2024-11-05
Estimated Expiration
2042-11-24

AI Technical Summary

Technical Problem

Among the existing identity authentication methods, multi-factor authentication information is complicated, resulting in cumbersome user operations and insufficient security. Single-factor authentication is easy to be cracked, making it difficult to find a balance between reliability and simplicity.

Method used

The mnemonic word is used to generate a private key, and identity authentication is performed through asymmetric encryption. The user only needs to enter the mnemonic word once, and the client device generates unique verification information. Asymmetric encryption is used during the transmission process to improve security and reliability.

Benefits of technology

It reduces the memory burden and operation cumbersomeness of users, improves the security and reliability of identity authentication, and reduces the risk of information leakage.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115865369B_ABST
    Figure CN115865369B_ABST
Patent Text Reader

Abstract

The present invention discloses an identity authentication method and device, relates to the field of communications, and solves the problem of cumbersome information required for identity authentication. The method comprises: receiving an input mnemonic and obtaining a private key corresponding to the mnemonic; sending a login request to a server according to the private key, the login request including a target identifier pointing to a public key corresponding to the private key, and the public key is stored on the server; receiving an encrypted password returned by the server in response to the login request, the encrypted password being obtained by the server encrypting a specific login password with a public key; decrypting the encrypted password with the private key to obtain a specific login password; generating first verification information according to the specific login password, the first verification information being unique in the verification information received by the server; sending the first verification information to the server so that the server compares the first verification information with the second verification information to obtain a verification result, the second verification information being the verification information generated by the server according to the specific login password; receiving the verification result returned by the server.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] As more and more systems containing private information are connected to the Internet, it becomes more important to ensure the security of system access through identity authentication, especially for systems in enterprises, hospitals, etc.

[0003] In the related technology, identity authentication methods are mainly divided into single-factor authentication and multi-factor authentication. Commonly used single-factor authentication, such as using user ID and password as authentication information, is simple and easy to be cracked. Once leaked during the transmission process, it will face great risks. Multi-factor authentication refers to the addition of other authentication factors, such as biometric parameters, on the basis of single factor. Although it has high security, the authentication information required is cumbersome. How to reduce the required authentication information in the reliable identity authentication process is an urgent problem to be solved now. Summary of the invention

[0004] The present invention provides an identity authentication method and device, which are used to solve the problem of complicated information required in the existing identity authentication process.

[0005] In order to achieve the above object, the present invention adopts the following technical scheme:

[0006] In the first aspect, the present invention provides an identity authentication method, which is applied to a client device, including: receiving an input mnemonic and obtaining a private key corresponding to the mnemonic; sending a login request to a server based on the private key, the login request including a target identifier, the target identifier pointing to a public key corresponding to the private key, and the public key stored on the server; receiving an encrypted password returned by the server in response to the login request, the encrypted password being obtained by the server encrypting a specific login password using a public key; decrypting the encrypted password using the private key to obtain a specific login password; generating first verification information based on the specific login password, the first verification information being unique among all verification information received by the server; sending the first verification information to the server so that the server compares the first verification information with the second verification information to obtain a verification result, the second verification information being the verification information generated by the server based on the specific login password; and receiving the verification result returned by the server.

[0007] In this way, since the user only needs to input the mnemonic once during the identity authentication process, the user only needs to remember the mnemonic, thereby reducing the user's memory burden, reducing the user's tedious operations, and improving the user experience. In addition, since the client device information transmission process adopts asymmetric encryption, and the identity authentication is verified by unique information, the security and reliability of the identity authentication are improved.

[0008] In one possible implementation, generating the first verification information based on a specific login password specifically includes: concatenating the specific login password with relevant information of the client device to obtain a concatenated password; performing at least one compression mapping process on the concatenated password to obtain compressed information; and using part or all of the compressed information as the first verification information.

[0009] In another possible implementation, the specific login password specifically includes: at least one of the MAC address of the client device, user information of the client device logging into the server, and the time of the login request.

[0010] In a possible implementation, the relevant information of the client device specifically includes: at least one of a public key corresponding to the client device, a MAC address of the client device, and user information of the client device logging into the server.

[0011] In a possible implementation, before sending the first verification information to the server, the method further includes: using a private key to digitally sign the first verification information, where the digital signature is used by the server to verify the legitimacy of the first verification information.

[0012] In a possible implementation, before receiving the input mnemonic, the method further includes: in response to the input mnemonic setting operation, determining the input word to be set as the mnemonic; and generating a private key corresponding to the mnemonic according to the mnemonic and the input time of the mnemonic setting operation.

[0013] In a possible implementation, the length of the mnemonic is less than or equal to 32 bytes; at this time, a private key corresponding to the mnemonic is generated according to the mnemonic and the input time of the mnemonic setting operation, including: converting the mnemonic into a binary string; replacing the empty positions of the characters in the binary string with a timestamp, and the timestamp is related to the input time of the mnemonic setting operation; if the length of the binary string is less than 256 bits, it is supplemented with a random number, and the obtained binary string with a length of 256 bits is used as the private key corresponding to the mnemonic.

[0014] In a possible implementation, before receiving the mnemonic inputted above, the method further includes: using the mnemonic as a password, encrypting the private key and saving it in a target path of the client device.

[0015] In a possible implementation, obtaining a private key corresponding to a mnemonic includes: using the mnemonic to obtain the private key from a target path.

[0016] In a possible implementation, before receiving the input mnemonic, the method further includes: generating a public key corresponding to the private key, and sending the public key and the target identifier to the server, so that the server stores the public key and the target identifier accordingly.

[0017] In a second aspect, the present invention provides an identity authentication method, which is applied to a server, comprising: receiving a login request sent by a client device, the login request including a target identifier, the target identifier pointing to a public key, and the public key corresponding to a private key owned by the client device; in response to the login request, encrypting a specific login password using the public key to obtain an encrypted password, and sending the encrypted password to the client device; receiving first verification information sent by the client, comparing the first verification information with the second verification information to obtain a verification result; the first verification information is verification information generated by the client device according to the specific login password, the specific login password is obtained by the client device decrypting the encrypted password according to the private key, and the second verification information is verification information generated by the server according to the specific login password; sending the verification result to the client device.

[0018] In a possible implementation, before comparing the first verification information with the second verification information and obtaining the verification result, it also includes: splicing the specific login password with the relevant information of the client device to obtain a spliced ​​password; performing at least one compression mapping process on the spliced ​​password to obtain compressed information; and using part or all of the compressed information as the second verification information.

[0019] In a possible implementation, the above-mentioned specific login password specifically includes at least one of the MAC address of the client device, the user information of the client device logging into the server, and the time of the login request.

[0020] In a possible implementation, at least one of the MAC address of the client device and the user information of the client device logging into the server is stored in the server and has a corresponding relationship with the target identifier.

[0021] In a possible implementation, the relevant information of the client device includes: at least one of a public key corresponding to the client device, a MAC address of the client device, and user information of the client device logging into the server.

[0022] In a possible implementation, before comparing the first verification information with the second verification information, it also includes: verifying the digital signature of the first verification information; comparing the first verification information with the second verification information, including: if the verification passes, comparing the first verification information with the second verification information.

[0023] In a possible implementation, before receiving the login request sent by the client device, the method further includes: receiving a public key and a target identifier sent by the client device; and storing the public key and the target identifier in correspondence.

[0024] In a third aspect, the present invention provides an identity authentication device, comprising: an information transceiver module for receiving an input mnemonic; a private key extraction module for obtaining a private key corresponding to the mnemonic; a request module for sending a login request to a server based on the private key, the login request including a target identifier, the target identifier pointing to a public key corresponding to the private key, and the public key stored on the server; the information transceiver module is also used to receive an encrypted password returned by the server in response to the login request, the encrypted password being obtained by the server encrypting a specific login password using a public key; a decryption module is used to decrypt the encrypted password using a private key to obtain a specific login password; a generation module is used to generate first verification information based on the specific login password, the first verification information being unique among all verification information received by the server; the information transceiver module is also used to send the first verification information to the server, so that the server compares the first verification information with the second verification information to obtain a verification result, the second verification information being the verification information generated by the server based on the specific login password; the information transceiver module is also used to receive the verification result returned by the server.

[0025] In a fourth aspect, the present invention provides an identity authentication device, comprising: an information transceiver module, used to receive a login request sent by a client device, the login request including a target identifier, the target identifier pointing to a public key, and the public key corresponding to a private key owned by the client device; a public key extraction module, used to obtain a public key corresponding to the private key according to the target identifier; a generation module, used to generate a specific login password; an encryption module, used to encrypt the specific login password using the public key to obtain an encrypted password; the information transceiver module is also used to send the encrypted password to the client device; the information transceiver module is also used to receive first verification information sent by the client, the first verification information is verification information generated by the client device according to the specific login password, and the specific login password is obtained by the client device decrypting the encrypted password according to the private key; the generation module is also used to generate second verification information, the second verification information is verification information generated by the server according to the specific login password; a comparison verification module, used to compare the first verification information with the second verification information to obtain a verification result; the information transceiver module is also used to send the verification result to the client device.

[0026] For the specific description of the second to fourth aspects and their various implementations in this application, reference can be made to the detailed description in the first aspect and its various implementations; and for the beneficial effects of the second to fourth aspects and their various implementations, reference can be made to the analysis of the beneficial effects in the first aspect and its various implementations, which will not be repeated here.

[0027] These and other aspects of the present application will become more apparent from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0029] Figure 1 A schematic diagram of the system architecture of the identity authentication method;

[0030] Figure 2 It is a schematic diagram of the basic hardware structure of the client device 101 and the server 102;

[0031] Figure 3 This is a schematic diagram of the mnemonic setting and private key generation process on the client side;

[0032] Figure 4 A schematic diagram of the method for converting a mnemonic phrase into a private key;

[0033] Figure 5 A schematic diagram of an identity authentication process on the client side;

[0034] Figure 6 A schematic diagram of a method for generating first verification information according to a specific login password;

[0035] Figure 7 A schematic diagram of an identity authentication process on the server side;

[0036] Figure 8 is a schematic diagram of an identity authentication device;

[0037] Fig. 9 A schematic diagram of an identity authentication device. DETAILED DESCRIPTION

[0038] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0039] The terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of the present invention, unless otherwise specified, "plurality" means two or more.

[0040] In order to facilitate understanding of the technical solution of the embodiment of the present application, before introducing the identity authentication method of the embodiment of the present application, some of the terms and technologies involved therein are briefly introduced as follows.

[0041] Public and private keys:

[0042] The public key and private key are an asymmetric key pair obtained through an algorithm. The public key is generated by the private key, and the private key cannot be reversed from the public key. The public key is the public part of the key, and the private key is the non-public part of the key, which is kept by the user. The public key and private key can be used in asymmetric encryption. One key in the key pair is used to encrypt a piece of data, and only the other key in the key pair can be used to decrypt the data. Common practical uses are for encrypted sessions, or digital signatures and verification of digital signatures.

[0043] Mnemonic:

[0044] A mnemonic phrase is a form of plaintext private key, and its purpose is usually to help users save and obtain complex private keys.

[0045] Digital Signature:

[0046] A digital signature is a method of authenticating digital information. It is based on an asymmetric key system and can achieve at least the following three points: message authentication, message integrity, and message non-repudiation.

[0047] Generally speaking, the receiver of a message has a public key, and the sender has a private key corresponding to the public key. The sender uses the private key to digitally sign the message, and the receiver uses the public key to determine the authenticity of the digital signature, thereby identifying the source of the message. Because the private key is confidential and unique, the sender cannot deny the content of the message, ensuring the validity of the information. The digital signature and the information before the signature are a mixed whole, so the digital signature can also be verified to determine whether the message is complete and whether it has been tampered with.

[0048] Elliptic curve public key cryptography algorithm:

[0049] Elliptic Curve Key Algorithm (SM2) is an algorithm that calculates the public key from the private key, but the algorithm cannot reversely derive the private key from the public key. The private key is essentially a 256-bit integer. SM2 can derive two 256-bit integers from the private key, and these two integers can be the corresponding public keys.

[0050] Timestamp

[0051] The timestamp refers to the total number of seconds from 00:00:00 Greenwich Mean Time on January 1, 1970 (08:00:00 Beijing Time on January 1, 1970) to the present.

[0052] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0053] The present invention provides an identity authentication method and device. The identity authentication method can be applied to Figure 1 The system architecture shown in FIG. 1 includes a client device 101 and a server 102 , and the client device 101 and the server 102 can communicate.

[0054] Specifically, the client device 101 and the server 102 may communicate via the Internet, a local area network, or a wireless communication network, and this embodiment does not limit the specific communication method.

[0055] It should be noted that the present application does not limit the number of client devices 101 and servers 102 in the system architecture. Figure 1 A client device 101 and a server 102 are taken as an example for description.

[0056] The client device 101 can store the private key corresponding to the mnemonic, and extract the corresponding private key based on the mnemonic input by the user. When the user inputs the login operation, it can send a login request to the server 102, and use the private key to decrypt the encrypted password sent by the server 102 to obtain a specific login password, and after obtaining the specific login password, process the specific login password to generate the first verification information, and finally send the first verification information to the server 102 for identity authentication.

[0057] Optionally, the client device 101 can also set a mnemonic through a mnemonic setting operation input by the user, and generate a private key corresponding to the mnemonic and a public key corresponding to the private key based on the mnemonic.

[0058] Server 102 can save the public key and related information of client device 101, respond to the login request sent by client device 101, encrypt the specific login password into an encrypted password according to the public key indicated by the target identifier in the login request, and send the encrypted password to the client device. At the same time, the same processing method as client device 101 is adopted to generate second verification information based on the specific login password, and finally the second verification information is used to verify the first verification information sent by client device 101, so as to complete the identity authentication of client device 101.

[0059] The server 102 may carry the entire system that the client device 101 needs to log in through identity authentication, such as an enterprise system or a public service system, or may only carry a key system that the client device needs to perform identity authentication, such as a third-party authentication system.

[0060] The client device 101 in the embodiment of the present application can be a mobile phone, a desktop computer, a tablet computer, a laptop computer, a handheld computer, a wearable electronic device, a handheld computer, an ultra-mobile personal computer (UMPC), a netbook or other electronic device, and the embodiment of the present application does not impose any restrictions on this.

[0061] The server 102 in the embodiment of the present application can be a rack server, a blade server, a tower server or a cabinet server and the like, and the construction method can be a single integrated, clustered or distributed one, which is not limited in the embodiment of the present application.

[0062] The basic hardware structure of the client device 101 and the server 102 is similar, both of which include Figure 2 The computing device shown in FIG. Figure 2 Taking the computing device shown as an example, the hardware structure of the client device 101 and the server 102 is introduced.

[0063] like Figure 2 As shown, the computing device may include a processor 111 , a memory 112 , a communication interface 113 , and a bus 114 . The processor 111 , the memory 112 , and the communication interface 113 may be connected via the bus 114 .

[0064] The processor 111 is the control center of the computing device, and may be a processor or a general term for multiple processing elements. For example, the processor 111 may be a general-purpose central processing unit (CPU) or other general-purpose processors. The general-purpose processor may be a microprocessor or any conventional processor.

[0065] As an embodiment, the processor 111 may include one or more CPUs, such as Figure 2 CPU 0 and CPU 1 are shown in .

[0066] The memory 112 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0067] In a possible implementation, the memory 112 may exist independently of the processor 111, and the memory 112 may be connected to the processor 111 via a bus 114 to store instructions or program codes. When the processor 111 calls and executes the instructions or program codes stored in the memory 112, the identity authentication method provided in the embodiment of the present application can be implemented.

[0068] In the embodiment of the present application, for the server 102 and the client device 101, the software programs stored in the memory 112 are different, and the server 102 and the client device 101 implement different functions. The functions performed by each device will be described in conjunction with the following flowchart.

[0069] In another possible implementation, the memory 112 may also be integrated with the processor 111 .

[0070] The communication interface 113 is used for the computing device to connect with other devices through a communication network, and the communication network may be Ethernet, a radio access network (RAN), a wireless local area network (WLAN), etc. The communication interface 113 may include a receiving unit for receiving data and a sending unit for sending data.

[0071] The bus 114 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 2Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0072] It should be pointed out that Figure 2 The structure shown in the figure does not constitute a limitation on the computing device, except Figure 2 In addition to the components shown, the computing device may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0073] like Figure 3 As shown, on the client device side, an identity authentication method provided by the present application may include the following S201 to S202. The S201 to S202 are specifically the setting of mnemonics and the generation of private keys.

[0074] S201: In response to the user's mnemonic setting operation, the input mnemonic to be set is set as the mnemonic.

[0075] In a possible implementation, the client device 101 may display an operation interface for setting a mnemonic, and the operation interface may include an information input area, and the content input by the user in the input area may include a mnemonic to be set, that is, a mnemonic to be set. After the input operation is completed, the client 101 will set the received mnemonic to be set as a mnemonic.

[0076] For example, the mnemonic can be a custom English word, such as "theordinarypassword", and of course, it can also be at least one of Chinese, English, numbers and symbols.

[0077] S202: Generate a private key corresponding to the mnemonic according to the mnemonic and the input time of the mnemonic setting operation.

[0078] In the above steps, the mnemonic setting operation time is used as a necessary parameter for generating the private key, so that the private key is not the result of conversion based on the single factor of the mnemonic. In this way, if the mnemonic and the private key generation method are known, if the necessary parameter mnemonic setting operation time is missing, the corresponding private key cannot be obtained, which further improves the security of the private key. In addition, the mnemonic setting time is unique as a time parameter, so the uniqueness and complexity of the private key generated based on the mnemonic setting time can also be guaranteed.

[0079] In a possible implementation, the length of the mnemonic to be set input by the user is less than or equal to 32 bytes.

[0080] In one possible implementation, Figure 4 As shown, the method of converting a mnemonic phrase into a private key includes the following steps:

[0081] S2021: Convert the mnemonic to a binary string.

[0082] S2022: Replace the empty positions in the binary string with a timestamp.

[0083] S2023: If the length of the binary string is less than 256 bits, use a random number to make up 256 bits to obtain the private key.

[0084] For example, the client device 101 converts the above-mentioned English mnemonic "theordinarypassword" according to the ASCII code (American Standard Code for Information Interchange). Each bit of the 19-bit English mnemonic corresponds to an 8-bit binary number, and finally a 152-bit binary string is obtained, which is "011101000110100001100101010110111101110010011001000110100101101110011000010111001001111001011100000110000101110010111001011100100110011001001100100100". Taking Beijing time "2022-10-27 16:41:04" as an example, the binary timestamp at this time is a 31-bit binary number "1100011010110100100010000100000". The binary timestamp is concatenated to the empty position after the binary string to generate a 183-bit binary string, which is still less than 256 bits. At this time, the client device 101 will generate a 73-bit random binary number and concatenate it to the 183-bit binary number again. For example, a random number "100100001001001110111010100000010101011000101010101001010100111100010100". Then, the final 256-bit private key will be the concatenation of the three: “01110100011010000110010101101111011100100110010001101001011011100110000101110010011110010111000001100001011100110111 001101110111011011101110010011001001001100011010100100010000010010010010011101110101000000101010110001010101001010100111100010100”.

[0085] It should be noted that in the above embodiment, the mnemonic words are converted into binary strings based on ASCII code, and the splicing method adopts a method of directly connecting multiple data. The above steps are only examples, and the method of converting mnemonics into binary strings and the method of data splicing are not specifically limited in this application.

[0086] In the above embodiment, ASCII code is used to convert the mnemonic because ASCII code is highly versatile and can be supported by most programming languages ​​or systems. In addition, the corresponding characters in the ASCII code can be converted into a binary string with a fixed number of bits, which is convenient for controlling the number of bits of the binary string. The timestamp and random number are used as the generation parameters of the private key, which increases the complexity of the private key and makes the generated private key difficult to be calculated by conventional means.

[0087] In addition, other methods may be selected for generating the private key. The above steps are merely an example and do not constitute a limitation on the scope of this application.

[0088] In some embodiments, on the client device side, the identity authentication method provided by the present application may also include:

[0089] S203: Generate a corresponding public key based on the private key.

[0090] For example, the SM2 algorithm can be used to generate a unique corresponding public key based on the private key.

[0091] In some embodiments, on the client device side, the identity authentication method provided by the present application may also include:

[0092] S204: Using the mnemonic as the password, encrypt the private key and save it in the target path of the client device 101.

[0093] For example, after the mnemonic is successfully set, the private key is encrypted and saved in a document stored locally on the client device 101. The specific encryption and storage method can be document encryption, symmetric encryption, etc., and the embodiments of the present application do not impose any restrictions on this.

[0094] In the above embodiment, the private key is stored in the target path of the client device 101, which can facilitate the quick acquisition of the private key in the subsequent identity authentication process. The encrypted storage method allows the private key to be decrypted and obtained only by the user who has the mnemonic, effectively preventing the private key file from being stolen and used by illegal means, thereby improving the security of the private key.

[0095] In some embodiments, on the client device side, the identity authentication method provided by the present application may also include:

[0096] S205: Send the public key and the target identifier corresponding to the public key to the server 102.

[0097] Specifically, the target identifier may be one of the related information of the client device 101, and the target identifier is used to point to the public key corresponding to the private key stored in the server 102. For example, the target identifier may be the mac address of the client device 101, the motherboard ID number of the client device 101, the information used by the client device 101 to log in to the server 102, etc., which is not limited in any way in the embodiments of the present application.

[0098] For example, the public key and the target identifier corresponding to the public key may be stored on the server through network transmission, hard disk copy transmission, etc., which is not limited in this embodiment.

[0099] Through the above embodiments, the mnemonic can be set by the user input, and the client device 101 generates the corresponding public key and private key based on the set mnemonic. In this way, the user can customize the mnemonic, and the user can independently choose to set a mnemonic that is more convenient to remember, more complex, or meets other needs.

[0100] In addition, in some embodiments, on the client device side, an identity authentication method provided by the present application may also include S211 to S215, which are specifically a process of changing the mnemonic.

[0101] S211: receiving the original mnemonic and the mnemonic to be modified input by the user, responding to the user's mnemonic modification operation, verifying the original mnemonic, and after the verification passes, setting the mnemonic to be modified as the mnemonic.

[0102] It should be understood that the original mnemonic is the current mnemonic, and the mnemonic to be modified is the new mnemonic to be set.

[0103] In a possible implementation, the client device 101 may display an operation interface for modifying the mnemonic, and the operation interface may include an information input area, and the content that the user may input in the input area may include the original mnemonic and the mnemonic to be modified. After the input operation is completed, the client 101 will first verify the original mnemonic. If the input original mnemonic is the same as the current mnemonic set previously, the client 101 will set the received mnemonic to be modified as the mnemonic. If the input original mnemonic is different from the current mnemonic set previously, no modification will be made.

[0104] It is understandable that the updated mnemonic takes effect from the first login after the mnemonic is updated to the next mnemonic modification.

[0105] S212: Generate a new private key corresponding to the mnemonic according to the mnemonic to be modified and the input time of the mnemonic modification operation.

[0106] In some embodiments, on the client device side, the identity authentication method provided by the present application may also include:

[0107] S213: Generate a corresponding new public key based on the new private key.

[0108] In some embodiments, on the client device side, the identity authentication method provided by the present application may also include:

[0109] S214: Using the current mnemonic as the password, encrypt the new private key and save it in the target path of the client device 101 to replace the original private key.

[0110] For example, the original private key is stored in the target path in the form of an encrypted document, the document of the original private key is deleted, replaced with the document of the new private key, and the document of the new private key is encrypted with the current mnemonic.

[0111] In some embodiments, on the client device side, the identity authentication method provided by the present application may also include:

[0112] S215: Send the new public key and the target identifier corresponding to the new public key to the server 102.

[0113] The above mnemonic modification method supports users to change the mnemonic when the mnemonic is leaked or when there is other need, and replaces the corresponding private key and public key, which meets user needs and improves the security of the system.

[0114] like Figure 5 As shown, in some embodiments, on the client device side, the identity authentication method provided by the present application may include the following S301 to S306. S301 to S306 are specifically an identity authentication process.

[0115] S301: receiving a mnemonic phrase input by a user, and obtaining a private key corresponding to the mnemonic phrase.

[0116] In an optional embodiment, when the private key is encrypted and stored on the client device 101, the private key can be obtained by decrypting the private key using a mnemonic phrase.

[0117] For example, the client device 101 may display a login interface having an input box, in which the user may input content including a mnemonic. After receiving the complete input of the mnemonic, the client device 101 uses the mnemonic to decrypt the private key stored in the target path to obtain the corresponding private key.

[0118] S302: Send a login request to the server according to the private key, where the login request includes a target identifier, and the target identifier points to a public key corresponding to the private key, and the public key is stored on the server.

[0119] In this way, based on the target identifier, the server 102 can search for the public key corresponding to the private key owned by the client 101 in the data stored therein, and the public key is stored on the server 102 before the identity authentication process.

[0120] S303: Receive the encrypted password returned by the server in response to the login request, where the encrypted password is obtained by encrypting a specific login password using a public key.

[0121] In a possible implementation, the information included in the specific login password may be at least one of the MAC address of the client device 101, the user information of the client device 101 logging into the server 102, and the time when the login request was issued.

[0122] For example, if the user name of the client device 101 logging in is "login", the mac address is "CC-96-E5-00-4A-E3", and the login request is issued at "2022-10-27 16:41:00", then the specific login password of the client device 101 for this login request can be one of "loginCC96E5004AE320221027164100", "loginCC96E5004AE3" or "CC96E5004AE320221027164100", or other information that may contain this information. In the embodiments of the present application, there is no limitation on this.

[0123] S304: The client device 101 uses the private key to decrypt the encrypted password to obtain a specific login password.

[0124] It should be understood that according to the asymmetric encryption method, information encrypted using a public key can be decrypted by the corresponding private key.

[0125] S305: Generate first verification information according to the specific login password and send it to the server 102. The first verification information is unique among all the verification information received by the server 102.

[0126] like Figure 6 As shown, in an optional implementation, the method for generating the first verification information according to the specific login password may include:

[0127] S3051: Concatenate the specific login password with the relevant information of the client device 101 to obtain a concatenated password.

[0128] Among them, the relevant information of the client device 101 can be at least one of the public key corresponding to the client device 101, the time when the client device 101 sends a login request to the server 102, the MAC address of the client device 101 and the information used by the client device 101 to log in to the server 102.

[0129] For example, the MAC address of the client device 101 is "CC-96-E5-00-4A-E3", the time when the client device 101 sends a login request to the server 102 is "2022.10.31 10:09", and the user name of the client 101 logging into the server 102 is "login", then the relevant information of the client device 101 can be "CC96E5004AE3202210311009login".

[0130] S3052: Perform compression mapping processing on the splicing interface command at least once to obtain compression information.

[0131] For example, the compression mapping process may be a Hash algorithm or a Hash-like algorithm, such as the SHA3 algorithm.

[0132] S3053: Use part or all of the compressed information as the first verification information.

[0133] For example, if the obtained 32-bit Hash value "10010101000011101001010001110101" is compressed information, then the entire Hash value can be used as the first verification information, or the first six digits "100101" can be taken as the first verification information, or the 1st, 5th, 7th, 8th, 9th, 10th, 25th, and 32nd digits "10010001" can be extracted as the first verification information.

[0134] It can be seen from the above embodiments that in the process of generating the first verification information according to the specific login password, the specific login information is first spliced ​​with the relevant information of the client device 101 to obtain the spliced ​​password. Since this information is common to the client device 101 and the server 102, it does not need to be transmitted again during the generation process, so the resource consumption in the transmission process is reduced, and the possibility of information leakage is reduced. In addition, the specific login password is generated according to the discriminative information of the client device 101, which is different from the login passwords received by other devices. Therefore, the first verification information generated according to the specific login password also has a certain uniqueness. Since time is introduced as a parameter in the process of generating the spliced ​​password, the generated first verification information is unique and can prevent wrong login. In addition, the unique first verification information can only be used in this login, and it will be invalid after this login, and it can also prevent being stolen and used. Then, the spliced ​​password is compressed and mapped, which shortens the amount of information, facilitates comparison, reduces the resource usage in the subsequent transmission process, and is also an encryption process for the verification information, further improving the security of the verification information. Finally, all or part of the compressed information is used as the first verification information. The more complete the first verification information is, the higher the reliability is, and the simpler the first verification information is, the fewer resources are needed in information transmission. In practical applications, this can be selected according to needs.

[0135] Of course, there are other ways to generate the first verification information. The above steps are only an example and do not constitute a limitation on the scope of this application.

[0136] S306: Receive the verification result returned by the server 102.

[0137] In a possible embodiment, the verification result returned by the server 102 is generated based on the comparison result of the first verification information and the second verification information. If the comparison results are the same, the authentication is successful, and if the comparison results are different, the authentication fails. The second verification information is generated by the server 102 based on a specific login password and the same data selection strategy and processing strategy as the client device 101. When the authentication is successful, the client device 101 will receive the returned verification result of the successful authentication, such as receiving a message of successful authentication, a prompt of successful login, or obtaining access permission and jumping to the access page of the system to be logged in. When the authentication fails, the client device 101 will receive the returned verification result of the failed authentication, such as receiving a message of failed authentication, a prompt of failed authentication will pop up.

[0138] In a possible implementation, before sending the first verification information, the server 102 uses a private key to digitally sign the first verification information, and the digital signature is used by the server 102 to verify the legitimacy of the received first verification information. Specifically, the server 102 can use the public key corresponding to the private key of the client device 101 to verify the digital signature, thereby verifying whether the sender of the first verification information is the client device 101, and whether the first verification information is complete and has not been tampered with.

[0139] As can be seen from the above embodiments, the identity authentication method provided by the embodiment of the present application only requires the user to remember the mnemonic and enter the mnemonic when logging into the system to complete the identity authentication process, thereby reducing the information that the user needs to remember and reducing the complexity of user operations, thereby improving the user experience. Compared with the solution of using more user privacy information for logging in, the present application can also reduce the risk of leakage of user privacy information. In addition, since the identity authentication method provided by the present application adopts asymmetric encryption to encrypt and decrypt the specific login password transmitted during the authentication process, the security of the information is guaranteed. At the same time, since the first verification information generated by the client device side based on the specific login password is unique among all verification information received by the server, the reliability of the identity authentication process is guaranteed.

[0140] like Figure 7 As shown, on the server side, an identity authentication method provided by the present application may include the following S401 to S405, which are specifically an identity authentication process.

[0141] S401 : receiving a login request sent by the client device 101 , where the login request includes a target identifier, where the target identifier points to a public key, and where the public key corresponds to a private key owned by the client device 101 .

[0142] In this way, based on the target identifier, the server 102 can search for the public key corresponding to the private key owned by the client 101 in the data stored therein.

[0143] In an optional implementation, the data stored in the server 102 includes at least one of the MAC address of the client device 101 and the user information of the client device 101 used to log in to the server 102 .

[0144] Storing the relevant information of the client device 101 on the server can reduce the information transmission during the identity authentication process, thereby reducing the resource usage during the authentication process, and avoid information leakage caused by frequent transmission.

[0145] In an optional implementation, the data stored in the server includes the MAC address of the client device 101 and at least one of the user information of the client device 101 used to log in to the server 102 , and the information has a corresponding relationship with the target identifier of the client device 101 .

[0146] In some possible embodiments, before authenticating the client device 101 , the server 102 receives and stores the public key of the client device 101 and the target identifier corresponding to the public key of the client device 101 .

[0147] S402 : Respond to the login request sent by the client 101 , encrypt the specific login password using the public key corresponding to the target identifier of the client 101 , obtain the encrypted password, and send the encrypted password to the client device 101 .

[0148] In a possible embodiment, the specific login password includes at least one of the MAC address of the client device 101, user information of the client device 101 used to log in to the server 102, and the login request time of the client device.

[0149] For example, if the username of the client device 101 is "login", the mac address is "CC-96-E5-00-4A-E3", and the login request is issued at "2022-10-27 16:41:00", then the specific login password generated by the server 102 for the client device 101 this time can be any one of "loginCC96E5004AE320221027164100", "loginCC96E5004AE3" or "CC96E5004AE320221027164100", or other expressions containing this information.

[0150] In addition, there are other ways to generate a specific login password, and the embodiments of the present application do not impose any specific restrictions on this.

[0151] S403: receiving first verification information sent by the client device 101, the first verification information is generated by the client device 101 according to a specific login password, the specific login password is obtained by the client device 101 using a private key to decrypt the encrypted password

[0152] S404: Generate second verification information according to the specific login password.

[0153] In a possible embodiment, the method for generating the second verification information according to the specific login password may include:

[0154] S4041: Concatenate the specific login password with the relevant information of the client device 101 to obtain a concatenated password.

[0155] In a possible embodiment, the relevant information about the client device 101 includes at least one of a public key corresponding to the client device 101 , a MAC address of the client device 101 , and user information of the client device 101 for logging into the server 102 .

[0156] S4042: Perform compression mapping processing on the splicing interface command at least once to obtain compression information.

[0157] For example, the compression mapping process may be a Hash algorithm or a Hash-like algorithm, such as the SHA3 algorithm.

[0158] S4043: Use part or all of the compressed information as second verification information.

[0159] It should be noted that the embodiment of the present application does not limit the execution order of S403 and S404 in the identity authentication method executed by the above server. Exemplarily, after executing S403, S404 is executed.

[0160] It can be seen that the client device 101 and the server 102 perform the same processing on the specific login password. For example, the client device 101 concatenates the MAC address of the client device 101 with the specific login password obtained after decrypting the encrypted password, performs SHA3 twice, and finally takes the first four digits as the first verification information. Then, the server 102 will also concatenate the MAC address of the client device 101 with the specific login password in the same way, perform SHA3 twice, and finally take the first four digits as the second verification information.

[0161] In the above embodiment, the server 102 encrypts the specific login password with the public key when sending it to the client device 101. The ability to use the corresponding private key to decrypt the specific login password is an authentication of the client device 101. In addition, the compressed mapping of the spelling password can not only reduce the amount of information and facilitate comparison, but also prevent the leakage of specific information of the client device, such as the mac address, thereby improving the security of the information. Finally, using all the compressed information as the second verification information can improve the reliability of the authentication and prevent accidental logins, such as partial information identical due to hash collisions. Using partially compressed information can reduce the resources occupied and enable fast logins.

[0162] S405 : Compare the first verification information with the second verification information to obtain a verification result, and send the verification result to the client 101 .

[0163] It is understandable that, since the client device 101 and the server 102 perform the same processing on the specific login password. Then, the first verification information and the second verification information obtained in this way should be the same. By comparing and determining whether the first verification information and the second verification information are the same, if they are the same, the authentication is successful, and if they are different, the authentication fails. When the authentication is successful, the server 102 sends the verification result of the successful authentication to the client device 101, such as the client device 101 will receive a prompt of successful authentication, or allow the client device 101 to access the system requested to log in, etc. When the authentication fails, the server 102 sends the verification result of the failed authentication to the client device 101, such as the client device 101 will receive a prompt of failed authentication, etc.

[0164] In a possible embodiment, before comparing the first verification information with the second verification information, the server 102 first verifies the digital signature of the first verification information, and only performs the subsequent comparison after the verification is passed.

[0165] It can be seen from the above embodiments that the identity authentication method provided by the embodiment of the present application only needs to save a small amount of distinguishing information of different client devices for the server, and only needs to use this information for processing and verification during identity authentication, thereby reducing the resources required for data transmission and reducing the risk of information leakage during data transmission. Compared with other identity authentication methods using biometric factors or time tokens, the amount of information required is small, the construction and maintenance are relatively simple, and the requirements for the server are low. In addition, the identity authentication method provided by the present application adopts asymmetric encryption, and the server encrypts the specific login password for transmission, so that it can ensure that only the client device with the corresponding secret key can decrypt the information, and this is also an authentication of the identity of the client device. Finally, through the comparison and verification of the first verification information and the second verification information, it is another identity authentication of the client device. Such an authentication process improves the reliability of the identity authentication process and makes the result of the identity authentication more reliable.

[0166] like Figure 8 As shown, in some embodiments, an identity authentication device provided by the present application may include:

[0167] The information transceiver module 501 is used to receive the input mnemonic phrase; it is also used to receive the encrypted password returned by the server in response to the login request, the encrypted password is obtained by the server using the public key to encrypt the specific login password; it is also used to send the first verification information to the server, so that the server compares the first verification information and the second verification information to obtain a verification result, the second verification information is the verification information generated by the server according to the specific login password; it is also used to receive the verification result returned by the server.

[0168] A private key extraction module 502, used to obtain a private key corresponding to a mnemonic;

[0169] The request module 503 is used to send a login request to the server according to the private key, where the login request includes a target identifier, where the target identifier points to a public key corresponding to the private key, and the public key is stored on the server;

[0170] The decryption module 504 is used to decrypt the encrypted password using the private key to obtain a specific login password;

[0171] The generation module 505 is used to generate the first verification information according to the specific login password. The first verification information is unique among all the verification information received by the server, and is specifically used to: splice the specific login password with the relevant information of the client device to obtain the spliced ​​password; perform compression mapping processing on the spliced ​​password at least once to obtain compressed information; and use part or all of the information in the compressed information as the first verification information.

[0172] like Fig. 9 As shown, in some embodiments, an identity authentication device provided by the present application may include:

[0173] The information receiving and sending module 601 is used to receive a login request sent by a client device, where the login request includes a target identifier, where the target identifier points to a public key, and where the public key corresponds to a private key owned by the client device; it is also used to send an encrypted password to the client device; it is also used to receive first verification information sent by the client, where the first verification information is verification information generated by the client device based on a specific login password, and the specific login password is obtained by the client device decrypting the encrypted password based on the private key; it is also used to send a verification result to the client device.

[0174] The public key extraction module 602 is used to obtain the public key corresponding to the private key according to the target identifier;

[0175] The generation module 603 is used to generate a specific login password, which includes at least one of the MAC address of the client device, the user information of the client device logging into the server, and the time of the login request; it is also used to generate second verification information, which is the verification information generated by the server according to the specific login password, and is specifically used to: splice the specific login password with the relevant information of the client device to obtain a spliced ​​password; perform at least one compression mapping process on the spliced ​​password to obtain compressed information; and use part or all of the compressed information as the second verification information.

[0176] The encryption module 604 is used to encrypt the specific login password using the public key to obtain the encrypted password;

[0177] The comparison and verification module 605 is used to compare the first verification information with the second verification information to obtain a verification result.

[0178] An embodiment of the present application also provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each step in the above method embodiment is implemented.

[0179] Among them, the computer readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of readable storage media (non-exhaustive list) include: an electrical connection with one or more wires, a portable computer disk, and a hard disk. Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM), registers, hard disks, optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any other form of readable storage medium in the art in a suitable combination of the above. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an Application Specific Integrated Circuit (ASIC). In the embodiments of the present application, a computer-readable storage medium may be any tangible medium that contains or stores a program, which may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0180] An embodiment of the present application provides a computer program product, which is stored in a non-volatile storage medium and is executed by at least one processor to implement the various steps shown in the above method embodiment.

[0181] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing a computer program instruction on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a readable storage medium, or transmitted from one readable storage medium to another readable storage medium, for example, the computer instructions may be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The readable storage medium may be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0182] Through the description of the above implementation methods, technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above functional units is used as an example. In actual applications, the above functions can be assigned to different functional units as needed, that is, the internal structure of the device is divided into different functional units to complete all or part of the functions described above. The specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0183] Since the devices, readable storage media, and computer program products in the embodiments of the present application can be applied to the above-mentioned identity authentication method, the technical effects that can be obtained can also refer to the above-mentioned method embodiments, and the embodiments of the present application will not be repeated here.

[0184] It should be noted that the above-mentioned units can be independently established processors, or can be integrated into a processor of the controller. In addition, they can be stored in the memory of the controller in the form of program code, and called and executed by a processor of the controller. The processor described here can be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

[0185] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0186] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0187] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0188] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling, direct coupling or communication connection shown or discussed can be realized through an interface, and the interface connection can be electrical, mechanical or other forms.

[0189] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0190] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0191] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. An identity authentication method, characterized in that: Applied to client devices, including: Receive an input mnemonic and obtain a private key corresponding to the mnemonic; Sending a login request to a server according to the private key, wherein the login request includes a target identifier, the target identifier points to a public key corresponding to the private key, and the public key is stored on the server; receiving an encrypted password returned by the server in response to the login request, wherein the encrypted password is obtained by the server encrypting a specific login password using the public key; Decrypt the encrypted password using the private key to obtain the specific login password; the specific login password includes: at least one of the MAC address of the client device, the user information of the client device logging into the server, and the time of the login request; Generate first verification information according to the specific login password, wherein the first verification information is unique among all verification information received by the server; Sending the first verification information to the server, so that the server compares the first verification information with second verification information to obtain a verification result, where the second verification information is verification information generated by the server according to the specific login password; Receive the verification result returned by the server.

2. The method according to claim 1, characterized in that The step of generating the first verification information according to the specific login password includes: splicing the specific login password with the relevant information of the client device to obtain a spliced ​​password; Performing at least one compression mapping process on the splicing command to obtain compression information; Part or all of the compressed information is used as the first verification information.

3. The method according to claim 2, characterized in that The relevant information of the client device includes: At least one of the public key corresponding to the client device, the MAC address of the client device, and user information of the client device logging into the server.

4. The method according to claim 1 or 2, characterized in that: Before sending the first verification information to the server, the method further includes: The first verification information is digitally signed using the private key, and the digital signature is used by the server to verify the legitimacy of the first verification information.

5. The method according to claim 1 or 2, characterized in that: Before receiving the input mnemonic, the method further includes: In response to an input mnemonic setting operation, determining the input word to be set as the mnemonic; A private key corresponding to the mnemonic is generated according to the mnemonic and the input time of the mnemonic setting operation.

6. The method according to claim 5, characterized in that The length of the mnemonic is less than or equal to 32 bytes, and the generating of a private key corresponding to the mnemonic according to the mnemonic and the input time of the mnemonic setting operation includes: Convert the mnemonic to a binary string; Replacing empty positions of characters in the binary string with a timestamp, the timestamp being related to the input time of the mnemonic setting operation; If the length of the binary string is less than 256 bits, it is supplemented with random numbers, and the resulting binary string with a length of 256 bits is used as the private key corresponding to the mnemonic.

7. The method according to claim 6, characterized in that Before receiving the input mnemonic, the method further includes: Using the mnemonic as a password, the private key is encrypted and saved in a target path of the client device.

8. The method according to claim 7, characterized in that The obtaining of a private key corresponding to the mnemonic includes: The private key is obtained from the target path using the mnemonic.

9. The method according to claim 6, characterized in that Before receiving the input mnemonic, the method further includes: A public key corresponding to the private key is generated, and the public key and the target identifier are sent to the server, so that the server stores the public key and the target identifier correspondingly.

10. An identity authentication method, characterized in that: Applicable to servers, including: Receiving a login request sent by a client device, the login request including a target identifier, the target identifier pointing to a public key, and the public key corresponding to a private key owned by the client device; In response to the login request, encrypting the specific login password using the public key to obtain an encrypted password, and sending the encrypted password to the client device; receiving first verification information sent by the client, comparing the first verification information with the second verification information to obtain a verification result; the first verification information is verification information generated by the client device according to the specific login password, the specific login password is obtained by the client device decrypting the encrypted password according to the private key, and the second verification information is verification information generated by the server according to the specific login password, the specific login password includes: at least one of the MAC address of the client device, the user information of the client device logging into the server, and the time of the login request; The verification result is sent to the client device.

11. The method according to claim 10, characterized in that Before comparing the first verification information with the second verification information to obtain a verification result, the method further includes: splicing the specific login password with the relevant information of the client device to obtain a spliced ​​password; Performing at least one compression mapping process on the splicing command to obtain compression information; Part or all of the compressed information is used as the second verification information.

12. The method according to claim 10, characterized in that At least one of the MAC address of the client device and the user information of the client device logging into the server is stored in the server and has a corresponding relationship with the target identifier.

13. The method according to claim 11, characterized in that The relevant information of the client device includes: At least one of the public key corresponding to the client device, the MAC address of the client device, and user information of the client device logging into the server.

14. The method according to claim 10 or 11, characterized in that: Before comparing the first verification information with the second verification information, the method further includes: Verifying the digital signature of the first verification information; The comparing the first verification information with the second verification information includes: When the verification is successful, the first verification information is compared with the second verification information.

15. The method according to claim 10 or 11, characterized in that: Before receiving the login request sent by the client device, the method further includes: Receiving the public key and the target identifier sent by the client device; The public key and the target identifier are stored correspondingly.

16. An identity authentication device, characterized in that: include: An information transceiver module, used to receive input mnemonics; A private key extraction module, used to obtain the private key corresponding to the mnemonic; A request module, configured to send a login request to a server according to the private key, wherein the login request includes a target identifier, the target identifier points to a public key corresponding to the private key, and the public key is stored on the server; The information transceiver module is further used to receive an encrypted password returned by the server in response to the login request, wherein the encrypted password is obtained by the server encrypting a specific login password using the public key; A decryption module, used to decrypt the encrypted password using the private key to obtain the specific login password; The specific login password includes: at least one of the MAC address of the client device, the user information of the client device logging into the server, and the time of the login request; A generating module, configured to generate first verification information according to the specific login password, wherein the first verification information is unique among all verification information received by the server; The information transceiver module is further used to send the first verification information to the server, so that the server compares the first verification information with second verification information to obtain a verification result, wherein the second verification information is verification information generated by the server according to the specific login password; The information transceiver module is also used to receive the verification result returned by the server.

17. An identity authentication device, characterized in that: include: An information transceiver module, used to receive a login request sent by a client device, wherein the login request includes a target identifier, the target identifier points to a public key, and the public key corresponds to a private key owned by the client device; A public key extraction module, used to obtain a public key corresponding to the private key according to the target identifier; A generation module, used to generate a specific login password; The specific login password includes: at least one of the MAC address of the client device, the user information of the client device logging into the server, and the time of the login request; An encryption module, used to encrypt the specific login password using the public key to obtain an encrypted password; The information transceiver module is further used to send the encrypted password to the client device; The information transceiver module is further used to receive first verification information sent by the client, where the first verification information is verification information generated by the client device according to the specific login password, and the specific login password is obtained by the client device decrypting the encrypted password according to the private key; The generating module is further used to generate second verification information, where the second verification information is verification information generated by the server according to the specific login password; A comparison and verification module, used to compare the first verification information with the second verification information to obtain a verification result; The information transceiver module is also used to send the verification result to the client device.