TWI715500B - Authentication system and authentication method - Google Patents

Abstract

An authentication system and an authentication method are provided. The electronic apparatus of the authentication system includes a controller, a processor and a key module, wherein the processor performs a application. In a binding phase, the application generates a digest file according to a key factor information and stores the digest file in a digest table of the electronic apparatus. In a checking phase, the application determines whether the controller is corresponded to a binding device according to the digest file and the key factor information. If the controller is corresponded to the binding device, in an authentication phase, the controller performs an authentication operation of a universal second factor service with a server apparatus according to the digest file corresponding to the binding device in response to a pressing of the key module.

Description

Authentication system and authentication method

The present invention relates to an authentication system and an authentication method, and in particular to an authentication system and an authentication method developed based on the Universal 2nd Factor (U2F) agreement formulated by the FIDO (Fast Identity Online Alliance) alliance .

With the rapid development of Internet technology, the transmission of many important messages, commercial transactions, or financial transactions rely on the Internet to provide services. In order to improve the security of Internet usage, many websites have begun to support the verification method of Universal 2nd Factor (U2F) protocol. However, the user must purchase an additional physical key device specially designed and manufactured for the universal second-factor protocol in order to use the authentication service of the universal second-factor protocol supported by the server website through the computer. As a result, it will increase the user's cost, thereby reducing the user's willingness to use.

In view of this, the present invention provides an authentication system and an authentication method, which not only allows users to use the authentication service of the universal second-factor protocol supported by the website, but also reduces the user's use cost, thereby increasing the user's willingness to use.

The authentication system of the present invention includes an electronic device. The electronic device includes a controller, a processor, and a button module. The controller has a summary table. The processor is coupled to the controller and used to execute the application program. The button module is coupled to and controlled by the controller. During the binding phase, the application generates a summary file based on the key factor information, and stores the summary file in the summary table of the electronic device. During the verification phase, the application determines whether the controller corresponds to the binding device based on the summary file and key factor information. If the controller corresponds to the binding setting, in the authentication stage, the controller responds to the pressing of the button module and performs authentication operation of the common second factor service with the server device according to the summary file corresponding to the binding device.

The authentication method of the present invention includes the following steps. In the binding phase, the application program executed by the processor of the electronic device generates a summary file based on the key factor information and the selection strategy, and stores the summary file in the summary table of the controller of the electronic device. In the verification phase, the application program of the electronic device determines whether the controller corresponds to the bound device according to the summary file and the key factor information. If the controller corresponds to the binding device, in the authentication phase, the controller responds to the pressing of the button module of the electronic device and performs authentication operation of the common second factor service with the server device according to the summary file corresponding to the binding device.

Based on the above, the authentication system and authentication method proposed by the present invention can allow users to use the universal second-factor protocol authentication supported by the server device to improve the security of using the server device service. In addition, the mobile storage device/mobile communication device in the authentication system proposed by the present invention can be any type of existing portable storage device/portable communication device, and the authentication method can be executed by an electronic device, so the user does not need additional Purchase a physical key device specially designed and manufactured for the general second factor agreement. In this way, the cost of verification using the universal second-factor protocol can be effectively reduced, thereby increasing the user's willingness to use.

In order to make the above-mentioned features and advantages of the present invention more comprehensible, the following specific embodiments are described in detail in conjunction with the accompanying drawings.

In order to make the content of the present invention more comprehensible, the following embodiments are specifically cited as examples on which the present invention can indeed be implemented. In addition, wherever possible, elements/components with the same reference numbers in the drawings and embodiments represent the same or similar components.

FIG. 1 is a block diagram and application diagram of an authentication system according to an embodiment of the invention. Please refer to FIG. 1, the authentication system 100 at least includes an electronic device 140, but in other embodiments, the authentication system 100 may further include one of a mobile storage device 120 and a mobile communication device 130.

The mobile storage device 120 is used to store the key identification file KDF as a physical key device. The electronic device 140 can be used to connect with the mobile storage device 120. The electronic device 140 can perform the correlation operation of the common second factor according to the key identification file KDF stored in the mobile storage device 120, and can reflect the pressing of the key module of the electronic device 140 to enable the common second factor supported by the server device 900 The authentication service of the factor agreement, so that the user of the electronic device 140 can use the authentication service of the universal second factor agreement supported by the server device 900.

The mobile communication device 130 is used to transmit the biometric identification confirmation result BIR, where the biometric identification confirmation result BIR is for example a face recognition result or a fingerprint identification result, but the embodiment of the present invention is not limited thereto. The electronic device 140 is used to connect with the mobile communication device 130 in a wired or wireless manner. The electronic device 140 can perform the related calculation of the common second factor according to the biometric confirmation result BIR provided by the mobile communication device 130, and can reflect the pressing of the button module of the electronic device 140 to activate the common second factor supported by the server device 900 The authentication service of the factor agreement, so that the user of the electronic device 140 can use the authentication service of the universal second factor agreement supported by the server device 900.

Moreover, when the electronic device 140 is not connected to an external electronic device (such as the mobile storage device 120 and the mobile communication device 130), the electronic device 140 can perform related operations of the common second factor based on its own information, and can respond to Pressing the button module of the electronic device 140 enables the authentication service of the universal second factor protocol supported by the server device 900, so that the user of the electronic device 140 can use the universal second factor protocol authentication supported by the server device 900 service.

Therefore, even if the user's login account and password on the server device 900 are obtained by others, as long as the bound interface physical device (such as the electronic device 140) is not obtained by another person, or the corresponding authentication physical device (such as a mobile storage device) 120 and the mobile communication device 130) are not obtained by others, the login account and password entered by others cannot pass the verification of the universal second factor protocol of the server device 900, and therefore cannot log in to the user's account.

In an embodiment of the present invention, the mobile storage device 120 can be, for example, a universal serial bus (USB) flash drive or a combination of a USB card reader and a memory card, and the mobile communication device 130 can be, for example, a mobile phone or a tablet computer. But the present invention is not limited to this. In fact, the mobile storage device 120 can be any type of existing portable storage device, and the mobile communication device 130 can be any type of existing portable communication device, so the user's use cost can be reduced.

In an embodiment of the present invention, the electronic device 140 may be, for example, a notebook computer, but the present invention is not limited thereto.

In an embodiment of the present invention, the electronic device 140 can communicate with the server device 900 through wired communication or wireless communication.

In an embodiment of the present invention, the authentication process of the authentication system 100 may include a binding phase, an inspection phase, and an authentication phase, but is not limited thereto. In the binding phase, the electronic device 140 used to perform the verification of the universal second factor protocol can be bound, and one of the mobile storage device 120 and the mobile communication device 130 can be bound to the electronic device 140. When the electronic device 140 is plugged into the mobile storage device 120, in the binding phase, the electronic device 140 can generate the key identification file KDF according to the key factor information KFI0 of the electronic device 140, and send the key identification file KDF to the mobile Storage device 120. In addition, during the binding phase, the electronic device 140 can generate the digest file DGF according to the file status of the key identification file KDF and the key factor information KFI0 of the mobile storage device 120, and store the digest file DGF in the controller of the electronic device 140 ( I will explain later) in which the controller stores a summary table. In this way, the mobile storage device 120 and the electronic device 140 are bound to each other by the key identification file KDF and the digest file DGF.

When the electronic device 140 is connected to the mobile communication device 130, during the binding phase, the mobile communication device 130 will provide the first public key UK1 and the key factor information KFI2 to the electronic device 140, such as the mobile communication device 130 The currently logged-in account (such as e-mail address), the international mobile device identification (IMEI) code of the mobile communication device 130, the phone number of the current user identity module (sim) card, and the mobile communication device 130 The message code randomly generated at the moment of binding of the application of. In addition, during the binding phase, the electronic device 140 can generate a summary file DGF based on the key factor information KFI2 of the mobile communication device 130 and the key factor information KFI0 of the mobile storage device 120, and store the summary file DGF in the summary of the electronic device 140 Table. In this way, the mobile communication device 130 and the electronic device 140 are bound to each other by the first public key UK1 and the digest file DGF.

When the electronic device 140 is not connected to an external electronic device, in the binding phase, the electronic device 140 can generate a summary file DGF according to its key factor information KFI0, and store the summary file DGF in the summary table of the electronic device 140 to Pretend to be bound to a virtual device.

In addition, when the electronic device 140 is plugged into the mobile storage device 120, in the verification phase, the electronic device 140 can verify whether the mobile storage device 120 and the electronic device 140 are bound to each other. In detail, the electronic device 140 can read the key identification file KDF from the mobile storage device 120, and check whether the key identification file KDF in the mobile storage device 120 is valid according to the digest file DGF and the key factor information KFI0 of the electronic device 140 . If the electronic device 140 checks that the key identification file KDF is valid, it means that the mobile storage device 120 and the electronic device 140 have been bound to each other, that is, it is determined that the electronic device 140 corresponds to the bound device (that is, the mobile storage device 120), then In the authentication phase, the electronic device 140 can perform a common second factor service authentication operation with the server device 900 according to the digest file DGF corresponding to the key identification file KDF.

When the electronic device 140 is connected to the mobile communication device 130, in the verification phase, the electronic device 140 can verify whether the mobile communication device 130 and the electronic device 140 are bound to each other. In detail, the mobile communication device 130 can receive the first authentication query CHS1 from the electronic device 140, and according to the first authentication query CHS1, return the first signature SIG1 to the electronic device 140, and the electronic device 140 confirms whether the first signature SIG1 matches The first public key UK1 corresponds to confirm whether the mobile communication device 130 is a bound device. If the mobile communication device 130 is a binding device, the electronic device 140 can perform a common second factor service authentication operation with the server device 900 according to the digest file DGF corresponding to the mobile communication device 130.

When the electronic device 140 is not connected to an external electronic device, in the verification phase, the electronic device 140 can confirm whether the electronic device 140 corresponds to the bound device (here, a virtual device) according to the key factor information KFI0. Generally speaking, the electronic device 140 will be confirmed as corresponding to the binding device, and then the electronic device 140 can perform a common second factor service authentication operation with the server device 900 according to the digest file DGF.

In an embodiment of the present invention, the authentication process of the authentication system 100 may further include a registration phase. In detail, if the electronic device 140 is confirmed to correspond to the bound device, during the registration phase, the electronic device 140 can register the general second factor service with the server device 900 according to the corresponding summary file DGF. As long as the electronic device 140 completes the registration of the general second factor service to the server device 900 according to the digest file DGF, in the authentication phase, the electronic device 140 performs the general second factor service authentication to the server device 900 according to the corresponding digest file DGF You can pass.

FIG. 2 is a flowchart of steps of an authentication method according to an embodiment of the invention. Please refer to FIG. 1 and FIG. 2 together. The authentication method of this exemplary embodiment includes the following steps. First, regardless of whether the mobile storage device 120 is plugged into the electronic device 140 or the mobile communication device 130 is connected to the electronic device 140, the user can determine whether the electronic device 140 is to be connected to an external device (such as the mobile storage device 120 or mobile communication device). The communication device 130) or virtual devices are bound to each other, as shown in step S200. If the decision result of step S200 is yes, then step S210 is executed, otherwise, step S220 is executed. In the binding phase shown in step S210, the application program of the electronic device 140 generates the digest file DGF according to the key factor information KFI0 (or one of the key factor information KFI1 and KFI2) and the selected strategy SEP, and The summary file DGF and the selection strategy SEP are stored in the summary table in the controller of the electronic device 140.

In addition, in the verification phase shown in step S220, the application program of the electronic device 140 determines whether the controller of the electronic device 140 corresponds to the binding device according to the digest file DGF and one of the key factor information KFI0, KFI1, and KFI2. If the controller of the electronic device 140 corresponds to the binding setting, it is determined whether to register the general second factor service with the server device 900, as shown in step S230. If the decision result of step S230 is yes, then in the registration stage shown in step S240, the electronic device 140 registers the general second factor service with the server device 900 according to the digest file DGF. If the decision result of step S230 is no, then in the authentication phase shown in step S250, the controller of the electronic device 140 reacts to the pressing of the button module of the electronic device 140 and communicates with the server according to the summary file DGF of the bound device. The device 900 performs the authentication operation of the universal second factor service.

FIG. 3 is a block diagram of an electronic device according to an embodiment of the invention. 3, the electronic device 140 may include a controller 141, a processor 142, and a button module 144, but the invention is not limited thereto. The controller 141 may include a storage 143 and have an identification code SN. The key module 144 is coupled to the controller 141 and controlled by the controller 141. The processor 142 is coupled to the controller 141. The processor 142 can execute the application program AP, and execute steps S210 and S220 of FIG. 2 through the application program AP, and the controller 141 can execute steps S240 and S250 of FIG. 2 through its firmware.

In an embodiment of the present invention, the processor 142 may be, for example, a central processing unit (CPU), but the present invention is not limited thereto.

In an embodiment of the present invention, the controller 141 may be a microcontroller, for example, but the present invention is not limited thereto.

In an embodiment of the present invention, the storage 143 may be, for example, a Serial Peripheral Interface (SPI) flash memory, but the present invention is not limited thereto.

In an embodiment of the present invention, the electronic device 140 may further include a communication module. The communication module is coupled to the controller 141. The controller 141 can communicate with the server device 900 through a communication module.

FIG. 4 is a detailed step flowchart of step S210 (ie, the binding phase) of FIG. 2 according to an embodiment of the present invention. Please refer to FIGS. 1, 3, and 4 together. The key factor information KFI0 of the electronic device 140 may include the identification code SN of the controller 141, the identification code AP of the above-mentioned application program, and the login account LID of the electronic device 140. The invention is not limited to this. As shown in FIG. 4, step S210 may include detailed steps S2100, S2102, S2104, S2106, and S2108. First, in step S2100, the application AP of the processor 142 can perform a hashing operation based on the identification code SN of the controller 141, the identification code SAP of the application AP, and the login account LID of the electronic device 140 to generate a key identification. File KDF. Then, in step S2102, the application AP of the processor 142 can send the key identification file KDF to the mobile storage device 120.

In an embodiment of the present invention, the identification code SN of the controller 141 may be, for example, the manufacturing number of the controller 141, which is read-only and unique to identify the controller 141, but the present invention is not limited to this . In an embodiment of the present invention, the identification code SAP of the application AP may be, for example, a Globally Unique Identifier (GUID), but the present invention is not limited to this. In an embodiment of the present invention, the login account LID of the electronic device 140 may be, for example, the login account of the operating system of the electronic device 140, but the present invention is not limited to this.

Since the key identification file KDF in the mobile storage device 120 is related to the identification code SN of the controller 141, the identification code SAP of the application AP, and the login account LID of the electronic device 140, even if the mobile storage device 120 is stolen, the mobile storage device The key identification file KDF in 120 cannot be used on other electronic devices. This is because the controller identification code and application identification code of other electronic devices are different from the controller identification code SN of the original electronic device 140 and the identification code SAP of the application program AP, and the login accounts of other electronic devices are the same as the original The login account LID of the electronic device 140 may also be different, so the key identification file KDF in the mobile storage device 120 will be deemed invalid in other electronic devices. In this way, the security of the authentication system 100 can be improved.

In addition, in step S2104, the application AP of the processor 142 can randomly generate the selection strategy SEP. Then, in step S2106, the application AP of the processor 142 can select at least one of the file status of the key identification file KDF and the key factor information KFI1 of the mobile storage device 120 according to the selection strategy SEP to perform a hash operation to generate a summary file DGF. After that, in step S2108, the processor 142 may store the summary file DGF and the corresponding selection strategy SEP in the summary table in the encrypted storage area 1432 of the storage 143.

Furthermore, the file status of the key identification file KDF may include at least one of the creation date, modification date, access date, start location of the file cluster, and the number of file clusters of the key identification file KDF One. In addition, the key factor information KFI1 of the mobile storage device 120 may include at least one of the supplier identification code of the mobile storage device 120, the product identification code of the mobile storage device 120, and the remaining storage space of the mobile storage device 120.

For example, if the selection strategy SEP randomly generated by the application AP of the processor 142 is the creation date of the key identification file KDF, the remaining storage space of the mobile storage device 120, and the number of file clusters of the key identification file KDF, Then the application AP of the processor 142 selects the creation date of the key identification file KDF, the remaining storage space size of the mobile storage device 120 and the number of file clusters of the key identification file KDF to perform a hash operation to generate the digest file DGF, and The summary file DGF and the corresponding selection strategy SEP are stored in the encrypted storage area 1432 of the storage 143.

It is understandable that the selection strategy SEP used to generate the summary file DGF is randomly generated by the application AP of the processor 142, and the summary file DGF generated by the processor 142 and the selection strategy SEP of the summary file DGF are stored in Encrypted storage area 1432, so others cannot know the content of the digest file DGF corresponding to the key identification file KDF, nor how the digest file DGF is generated (because they cannot know the selection strategy SEP of the digest file DGF) , So it can prevent the abstract file DGF from being copied by others. In addition, even if the key identification file KDF is stolen and copied to another mobile storage device, the creation date, modification date, access date and the start of the file cluster of the copied key identification file and the original key identification file The locations are all different, and the vendor ID, product ID, and remaining storage space of another mobile storage device and the original mobile storage device may not be exactly the same. Therefore, during the inspection phase, the application AP of the processor 142 can be According to the summary file DGF and the selected strategy SEP, it is checked that the copied key identification file is invalid. In this way, the security of the authentication system 100 can be improved.

Incidentally, the mobile storage device 120 can be bound to a number of different electronic devices. Therefore, the mobile storage device 120 can store one or more key identification files, wherein the key identification files correspond to different Electronic devices, or different login accounts, or different electronic devices and different login accounts. Similarly, the electronic device 140 can be bound to a plurality of different mobile storage devices. Therefore, the number of the combination of summary files and their selection strategies stored in the encrypted storage area 1432 can be one or more, wherein the summaries The files correspond to different key identification files.

FIG. 5 is a detailed flow chart of step S220 (that is, the checking phase) of FIG. 2 according to an embodiment of the present invention. Please refer to Figure 1, Figure 3 and Figure 5 together. As shown in FIG. 5, when the electronic device 140 is plugged into the mobile storage device 120, step S220 includes detailed steps S2201 to S2205. First, in step S2201, the application AP of the processor 142 checks whether the mobile storage device 120 stores the key identification file KDF. In an embodiment of the present invention, the application AP of the processor 142 can determine whether it is a key identification file KDF according to the file name or extension of the file stored in the mobile storage device 120, but the present invention is not limited to this. If the check result of step S2201 is negative, it means that the key identification file KDF is not stored in the mobile storage device 120, and the application AP of the processor 142 determines that the check has failed, as shown in step S2205, and ends the check. If the check result of step S2201 is yes, it means that the key identification file KDF is stored in the mobile storage device 120, and step S2202 is executed.

In step S2202, the application AP of the processor 142 can check whether the key identification file KDF corresponds to the digest file DGF according to the selection strategy SEP of the digest file DGF in the encrypted storage area 1432. If the check result of step S2202 is no, it means that the key identification file KDF in the mobile storage device 120 does not correspond to the digest file DGF in the encrypted storage area 1432, and the processor 142 determines that the check fails, that is, the controller 141 does not correspond to Bind the device, as shown in step S2205, and end the inspection. If the check result of step S2302 is yes, it means that the key identification file KDF in the mobile storage device 120 corresponds to the digest file DGF in the encrypted storage area 1432, that is, the controller 141 corresponds to the binding device, and step S2203 is executed.

For example, assume that the mobile storage device 120 stores the key identification file KDF, and the encrypted storage area 1432 stores a first summary file and its first selection strategy, and a second summary file and its second selection strategy. First, the application AP of the processor 142 can select at least one of the file status of the key identification file KDF and the key factor information KFI1 of the mobile storage device 120 according to the first selection strategy in the encrypted storage area 1432 to perform a hash operation to generate A first comparison file, and determine whether the first comparison file is the same as the first summary file. If the first comparison file is the same as the first digest file, it means that the key identification file KDF in the mobile storage device 120 corresponds to the first digest file in the encrypted storage area 1432, and step S2203 is executed.

If the first comparison file is different from the first digest file, it means that the key identification file KDF in the mobile storage device 120 does not correspond to the first digest file in the encrypted storage area 1432, and the processor 142 may then perform the encryption according to the encrypted storage area 1432. The second selection strategy selects at least one of the file status of the key identification file KDF and the key factor information KFI1 of the mobile storage device 120 to perform a hash operation to generate a second comparison file, and determine whether the second comparison file is Whether the second summary file is the same.

If the second comparison file is the same as the second summary file, it means that the key identification file KDF in the mobile storage device 120 corresponds to the second summary file in the encrypted storage area 1432, and step S2203 is executed. If the second comparison file is different from the second summary file, it means that the key identification file KDF in the mobile storage device 120 does not correspond to the first summary file and the second summary file in the encrypted storage area 1432, and the processor 142 applies The program AP determines that the check fails (that is, the key identification file KDF is invalid), as shown in step S2205, and ends the check.

In step S2203, the application AP of the processor 142 can perform a hash operation according to the identification code SN of the controller 141, the identification code SAP of the application AP, and the login account LID of the electronic device 140 to check whether the key identification file KDF is correct. If the check result in step S2203 is no, the application AP of the processor 142 determines that the check fails (that is, the key identification file KDF is invalid), as shown in step S2205, and ends the check. If the check result of step S2203 is yes, the processor 142 judges that the key identification file KDF is valid, as shown in step S2204, and proceeds to step S230.

FIG. 6 is a detailed step flowchart of step S210 in FIG. 2 according to another embodiment of the present invention. Please refer to Figure 1, Figure 3 and Figure 6 together. As shown in FIG. 6, when the electronic device is connected to the mobile communication device 130, step S210 includes detailed steps S2100a and S2102a. At this time, the electronic device 140 and the mobile communication device 130 perform asymmetric authentication and asymmetric encryption transmission. . First, in step S2100a, during the binding phase, the application AP of the processor 142 waits for the first biometric confirmation result BIR1 of the mobile communication device 130. In step S2102a, when the first biometric verification result BIR1 is passed, the application AP of the processor 142 receives the key factor information KFI2 from the mobile communication device 130, and then transmits the key factor information KFI2 to the controller 141 to Generate summary file DFG.

FIG. 7 is a detailed step flowchart of step S220 in FIG. 2 according to another embodiment of the present invention. Please refer to Figure 1, Figure 3 and Figure 7 together. As shown in FIG. 7, when the electronic device 140 is connected to the mobile communication device 130, step S220 includes detailed steps S2200a and S2202a. At this time, the electronic device 140 and the mobile communication device 130 perform asymmetric authentication and symmetric encryption transmission. First, in step S2200a, during the verification phase, the application AP of the processor 142 waits for the second biometric verification result BIR2 of the mobile communication device 130. In step S2202a, when the second biometric verification result BIR2 is passed, the application AP of the processor 142 receives the key factor information KFI2 from the mobile communication device 130, and then transmits the key factor information KFI2 to the controller 141 to It is confirmed whether the controller 141 corresponds to the binding device.

In the embodiment of the present invention, while the application AP of the processor 142 waits for the first biometric verification result BIR1 or the second biometric verification result BIR2 of the mobile communication device 130, the mobile communication device 130 generates the first public key UK1 And the first private key IK1, and the application AP of the processor 142 requests the mobile communication device 130 for the first public key UK1, the biometric status BIS, and the key factor information KFI2, where the application stores the first public key UK1. Before the application AP of the processor 142 transmits the key factor information KFI2 to the controller 141, the application of the processor 142 generates the second public key UK2 and the second private key IK2, and the second public key is transmitted to the control unit UK2. 141, so that the controller 141 stores the second public key UK2.

FIG. 8 is a flowchart of detailed steps of an application authentication mobile communication device according to an embodiment of the present invention. Please refer to Figure 1, Figure 3 and Figure 8 together. As shown in FIG. 8, when the application AP of the processor 142 authenticates the mobile communication device 130, the mobile communication device 130 obtains the first authentication query CHS1 from the application AP of the processor 142, and the mobile communication device 130 responds to the first authentication. CHS1 is asked to generate the first signature SIG1 according to the first private key IK1, and the mobile communication device 130 returns the first signature SIG1 to the application AP of the processor 142. The application AP of the processor 142 verifies whether the first signature SIG1 is correct through the first public key UK1 sent by the mobile communication device 130, thereby authenticating the mobile communication device 130.

FIG. 9 is a flowchart of detailed steps of a controller authentication application according to an embodiment of the invention. Please refer to Figure 1, Figure 3 and Figure 9 together. As shown in FIG. 9, when the controller 141 authenticates the application AP of the processor 142, the application AP of the processor 142 obtains the second authentication query CHS2 from the controller 141, and the application AP of the processor 142 reflects the second authentication. CHS2 is asked to generate a second signature SIG2 according to the second private key IK2, and the application AP of the processor 142 returns the second signature SIG2 to the controller 141. The controller 141 verifies whether the second signature SIG2 is correct through the second public key UK2 sent by the application AP of the processor 142, so as to authenticate the application AP of the processor 142.

In the embodiment of the present invention, the electronic device 140 may not be connected to an external electronic device and enable the verification of the common second factor. When the electronic device 140 may not be connected to an external electronic device, in the binding phase, that is, in step S210, the application AP of the processor 142 generates a summary file based on the key factor information KFI0 of the electronic device 140 and the strategy SEP DGF. In the checking phase, that is, in step S220, the application AP of the processor 142 determines whether the controller 141 corresponds to the binding device according to the digest file DGF and the key factor information KFI0 of the electronic device 140.

FIG. 10 is a detailed step flowchart of step S240 (ie, the registration phase) of FIG. 2 according to an embodiment of the present invention. Please refer to Figure 1, Figure 3 and Figure 10 together. As shown in FIG. 10, step S240 includes detailed steps S2400, S2402, S2404, and S2406. First, in step S2400, the controller 141 may send the account and password entered by the user for logging in to the server device 900 to the server device 900. Then, in step S2402, the controller 141 can obtain the corresponding server identification code SVID from the server device 900, and the controller 141 can obtain the digest file DGF corresponding to the key identification file KDF from the processor 142. Next, in step S2404, the controller 141 performs a hash operation according to the random number RNB, the server identification code SVID, and the digest file DGF to generate an information identification code MAC and a public key (Public Key) UK.

In detail, step S2404 may include detailed steps S642 and S644. First, in step S642, the controller 141 can perform a hash operation based on the random number RNB, the server identification code SVID, and the digest file DGF to generate a private key (Private Key) IK and a public key UK. Then, in step S644, the controller 141 can perform a hash operation according to the private key IK, the server identification code SVID, and the digest file DGF to generate the information identification code MAC.

After that, in step S2406, the controller 141 may transmit the random number RNB, the message identification code MAC, and the public key UK to the server device 900 to register the general second factor service with the server device 900. In this way, the server device 900 can map the account and password used to log in to the server device 900 to the public key UK, and complete the registration.

In an embodiment of the present invention, the above-mentioned hash operation can be performed by an existing hash operation method, such as Secure Hash Algorithm (SHA), etc., but the present invention is not limited to this. Depends on actual application or design requirements.

FIG. 11 is a detailed flowchart of step S250 (ie, the authentication phase) of FIG. 2 according to an embodiment of the present invention. Please refer to Figure 1, Figure 3 and Figure 11 together. As shown in FIG. 11, step S250 includes detailed steps S2500, S2502, S2504, and S2506. First, in step S2500, the controller 141 may send the account and password entered by the user to log in to the server device 900 to the server device 900, so that the server device 900 can find the corresponding public key according to the account and password. UK and send certification to inquire CHS. Then, in step S2502, the controller 141 can obtain the authentication query CHS from the server device 900. Then, in step S2504, the controller 141 can generate the signature SIG according to the private key IK in response to the authentication query CHS.

In an embodiment of the present invention, step S2504 may include detailed steps S752, S754, and S756. First, in step S752, the controller 141 can determine whether a specific key of the key module 144 of the electronic device 140 is pressed. If the determination result of step S752 is no, it means that the user may not be located around the electronic device 140 or the user is not using the electronic device 140, then in step S756, the controller 141 will not generate the signature SIG. If the judgment result of step S752 is yes, it means that the user is indeed located around the electronic device 140 and is using the electronic device 140, the controller 141 responds to the authentication query CHS and generates the signature SIG according to the private key IK, as shown in step S754 . In an embodiment of the present invention, if the controller 141 does not return the signature SIG to the server device 900 within a specific time interval, the aforementioned account and password for logging in to the server device 900 will not pass through the server device. 900 is authenticated by the universal second-factor protocol, and the server device 900 will send a message that the universal second-factor authentication has failed to the electronic device 140.

After that, in step S2506, the controller 141 returns the signature SIG to the server device 900, causing the server device 900 to use the signature SIG and the public key UK (that is, the corresponding account and password used to log in to the server device 900). Public key) for authentication of the universal second factor service. In detail, the server device 900 can check whether the signature SIG is valid according to the public key UK. If the server device 900 verifies that the signature SIG is valid, the account and password used to log in to the server device 900 have passed the authentication of the server device 900's universal second factor protocol, so the user can start using the server device 900 online services provided.

According to the above, when the electronic device 140 is plugged into the mobile storage device 120, the controller 141 will confirm the application AP of the processor 142. After the application AP passes the confirmation, the controller 141 then confirms the mobile storage device 120. After the mobile storage device 120 passes the confirmation, the controller 141 activates the authentication operation of the universal second factor service. When the electronic device 140 is connected to the mobile communication device 130, the application AP of the processor 142 will confirm the mobile communication device 130. After the mobile communication device 130 passes the confirmation, the controller 141 then confirms the application AP of the processor 142. After the application AP passes the confirmation, the controller 141 confirms the mobile communication device 130 again. After the mobile communication device 130 passes the confirmation, the controller 141 starts the authentication operation of the universal second factor service.

In summary, the authentication system and authentication method proposed in the embodiments of the present invention allow users to use the universal second-factor protocol authentication supported by the server device to improve the security of using the server device service. In addition, since the mobile storage device/mobile communication device in the authentication system proposed by the embodiment of the present invention can be any type of existing portable storage device/portable communication device, and the authentication method can be performed by the processor in the electronic device And the controller is executed through the application and firmware respectively, so the user does not need to purchase an additional physical key device specially designed and manufactured for the general second-factor protocol. In this way, the cost of verification using the universal second-factor protocol can be effectively reduced, thereby increasing the user's willingness to use.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention. Anyone with ordinary knowledge in the technical field can make some changes and modifications without departing from the spirit and scope of the present invention. The scope of protection of the present invention shall be determined by the scope of the attached patent application.

100: authentication system 120: Mobile storage device 130: mobile communication device 140: Electronic device 141: Controller 142: Processor 143: Storage 1432: Encrypted storage area 144: Button module 900: Server device AP: Application BIR: biometric confirmation result BIR1: The first biometric verification result BIR2: Second biometric identification confirmation result BIS: Biometric Status CHS: Certification inquiry CHS1: First certification inquiry CHS2: Second certification inquiry DGF: Summary File IK: private key IK1: The first private key IK2: second private key KDF: Key Identification File KFI0, KFI1, KFI2: Key factor information of electronic devices LID: login account of the electronic device MAC: information identification code RNB: random number S200, S210, S220, S230, S240, S250, S2100, S2102, S2104, S2106, S2108, S2100a, S2102a, S2201, S2202, S2203, S2204, S2205, S2200a, S2202a, S2400, S2402, S2404, S2406, S642, S644, S2500, S2502, S2504, S2506, S752, S754, S756: steps SAP: Application ID SEP: Select strategy SIFO: Mobile storage device information SIG: signature SIG1: The first signature SIG2: Second signature SN: the identification code of the controller SVID: Server ID UK: Public key UK1: The first public key UK2: The second public key

The accompanying drawings below are a part of the specification of the present invention, and illustrate exemplary embodiments of the present invention. The accompanying drawings and the description of the specification illustrate the principle of the present invention. FIG. 1 is a block diagram and application diagram of an authentication system according to an embodiment of the invention. FIG. 2 is a flowchart of steps of an authentication method according to an embodiment of the invention. FIG. 3 is a block diagram of an electronic device according to an embodiment of the invention. FIG. 4 is a detailed flow chart of step S210 of FIG. 2 according to an embodiment of the present invention. FIG. 5 is a detailed flow chart of step S220 of FIG. 2 according to an embodiment of the present invention. FIG. 6 is a detailed step flowchart of step S210 in FIG. 2 according to another embodiment of the present invention. FIG. 7 is a detailed step flowchart of step S220 in FIG. 2 according to another embodiment of the present invention. FIG. 8 is a flowchart of detailed steps of an application authentication mobile communication device according to an embodiment of the present invention. FIG. 9 is a flowchart of detailed steps of a controller authentication application according to an embodiment of the invention. FIG. 10 is a detailed flowchart of step S240 of FIG. 2 according to an embodiment of the present invention. FIG. 11 is a detailed flow chart of step S250 of FIG. 2 according to an embodiment of the present invention.

100: authentication system 120: Mobile storage device 130: mobile communication device 140: Electronic device 900: Server device BIR: biometric confirmation result CHS1: First certification inquiry DGF: Summary File KDF: Key Identification File KFI0, KFI1, KFI2: Key factor information SEP: Select strategy SIG1: The first signature UK1: The first public key

Claims (33)

An authentication system includes: An electronic device, including: A controller with a summary table; A processor coupled to the controller and used to execute an application program; and A button module, coupled to and controlled by the controller, In a binding phase, the application generates a summary file based on a key factor information and a selection strategy, and stores the summary file and the selection strategy in the summary table. In a verification phase, the application determines whether the controller corresponds to a binding device based on the summary file and the key factor information. When the controller corresponds to the binding setting, the controller responds to a press of the button module and performs a common second factor service with a server device according to the summary file corresponding to the binding device Certification operation. The authentication system according to claim 1, wherein if the controller corresponds to the binding device, in a registration phase, the controller registers the universal second factor service with the server device according to the summary file. The authentication system according to claim 1, wherein the electronic device is plugged into a mobile storage device, In the binding phase, the application program generates a key identification file based on the key factor information of the electronic device and sends the key identification file to the mobile storage device, and the application program randomly The selection strategy is generated, and at least one of the file status of the key identification file and the key factor information of the mobile storage device is selected according to the selection strategy to perform a hash operation to generate the summary file. The authentication system according to claim 3, wherein the key factor information of the electronic device includes an identification code of the controller, an identification code of an application program, and a login account of the electronic device, and the file status includes the The key identifies at least one of the creation date, modification date, access date, the starting location of the file cluster, and the number of file clusters, and the key factor information of the mobile storage device includes the supply of the mobile storage device At least one of the vendor identification code, product identification code, and remaining storage space size. The authentication system according to claim 4, wherein in the verification phase: The application checks whether the key identification file is stored in the mobile storage device to obtain a first result, If the first result is yes, the application program checks whether the key identification file corresponds to the summary file according to the selection strategy to obtain a second result, If the second result is yes, the application program performs a hash operation according to the identification code of the controller, the identification code of the application program, and the login account of the electronic device to check whether the key identification file is correct to obtain A third result, If the third result is yes, the application program determines that the controller corresponds to the bound device. The authentication system according to claim 1, wherein the electronic device is connected to a mobile communication device, and in the binding phase, the application waits for a first biometric confirmation result of the mobile communication device, and When the first biometric verification result is passed, the application program receives the key factor information from the mobile communication device, and then transmits the key factor information to the controller to generate the summary file. The authentication system according to claim 6, wherein in the verification phase, the application program waits for a second biometric confirmation result of the mobile communication device, and When the second biometric verification result is passed, after the application receives the key factor information from the mobile communication device, it sends the key factor information to the controller to confirm whether the controller corresponds to the binding Device. The authentication system according to claim 7, wherein the mobile communication device generates a first public key while the application is waiting for the first biometric verification result or the second biometric verification result of the mobile communication device And a first private key, and the application program requests the first public key, a biometric identification status, and the key factor information from the mobile communication device, wherein the application program stores the first public key, Wherein, before the application program transmits the key factor information to the controller, the application program generates a second public key and a second private key, and the second public key is transmitted to the controller so that the The controller stores the second public key. The authentication system according to claim 8, wherein when the application program authenticates the mobile communication device, the mobile communication device obtains a first authentication query from the application program, and the mobile communication device responds to the first authentication query A first signature is generated according to the first private key, and the mobile communication device returns the first signature to the application. The authentication system according to claim 8, wherein when the controller authenticates the application, the application obtains a second authentication query from the controller, and the application responds to the second authentication query based on the first authentication query The two private keys generate a second signature, and the application program returns the second signature to the controller. The authentication system according to claim 1, wherein the electronic device is not connected to an external electronic device, and in the binding phase, the application program generates the summary according to the key factor information of the electronic device and the retrieval strategy file, In the checking phase, the application program determines whether the controller corresponds to the binding device according to the summary file and the key factor information of the electronic device. The authentication system according to claim 11, wherein the key factor information of the electronic device includes an identification code of the controller, an identification code of an application program, and a login account of the electronic device. The authentication system according to claim 2, wherein in the registration phase: The controller sends the account and password used to log in to the server device to the server device. The controller obtains a server identification code and the summary file from the server device and the processor respectively, and the controller according to A random number, the server identification code, and the summary file are hashed to generate an information identification code and a public key, and the controller transmits the random number, the information identification code and the public key to the server device , To register the universal second factor service with the server device. The authentication system according to claim 13, wherein in the registration phase, the controller performs a hash operation according to the random number, the server identification code, and the digest file to generate a private key and the public key, and the controller According to the private key, the server identification code and the digest file, a hash operation is performed to generate the information identification code. The authentication system according to claim 14, wherein in the authentication phase: The controller sends the account and password used to log in to the server device to the server device, the controller obtains an authentication query from the server device, and the controller responds to the authentication query and generates according to the private key A signature, and the controller returns the signature to the server device, causing the server device to perform authentication of the universal second factor service according to the signature and the public key. The authentication system according to claim 14, wherein in the authentication phase, the controller determines whether a key of the key module is pressed to obtain a judgment result, and if the judgment result is yes, the controller responds to the The authentication query generates the signature based on the private key. The authentication system according to claim 1, wherein the controller has a memory for storing the summary table. An authentication method including: In a binding phase, an application program executed by a processor of an electronic device generates a summary file based on key factor information and a selection strategy, and stores the summary file in a controller of the electronic device Summary table; In a verification stage, the application program of the electronic device determines whether the controller corresponds to a binding device according to the summary file and the key factor information; and If the controller corresponds to the binding device, in an authentication phase, the controller reacts to a pressing of a button module of the electronic device and communicates with a server device according to the summary file corresponding to the binding device. Perform an authentication operation of a universal second factor service. The authentication method described in claim 18 further includes: If the controller corresponds to the binding device, in a registration stage, the controller registers the general second factor service with the server device according to the summary file. The authentication method according to claim 18, wherein the electronic device is plugged into a mobile storage device, and the steps of generating the summary file according to the key factor information and the selection strategy include: Through the application, a hash operation is performed based on the key factor information of the electronic device to generate a key identification file, Randomly generate the selection strategy through the application; and At least one of the file status of the key identification file and the key factor information of the mobile storage device is selected by the application according to the selection strategy to perform a hash operation to generate the summary file. The authentication method according to claim 20, wherein the key factor information of the electronic device includes an identification code of the controller, an identification code of the application program, and a login account of the electronic device, and the file status includes the The key identifies at least one of the creation date, modification date, access date, the starting location of the file cluster, and the number of file clusters, and the key factor information of the mobile storage device includes the supply of the mobile storage device At least one of the vendor identification code, product identification code, and remaining storage space size. The authentication method according to claim 21, wherein the step of checking whether the controller corresponds to the binding device according to the summary file and the key factor information of the electronic device includes: Check whether the key identification file is stored in the mobile storage device through the application to obtain a first result; If the first result is yes, check whether the key identification file corresponds to the summary file through the application according to the selection strategy to obtain a second result; If the second result is yes, the application program performs a hash operation based on the identification code of the controller, the identification code of the application program, and the login account of the electronic device to verify whether the key identification file is correct or not. Get a third result; and If the third result is yes, it is determined through the application that the controller corresponds to the bound device. The authentication method according to claim 18, wherein the electronic device is connected to a mobile communication device, and the authentication method further includes: During the binding phase, the application waits for a first biometric confirmation result of the mobile communication device; and When the first biometric verification result is passed, the application program receives the key factor information from the mobile communication device, and then transmits the key factor information to the controller to generate the summary file. The authentication method described in claim 23 further includes: During the verification phase, the application waits for a second biometric confirmation result of the mobile communication device; and When the second biometric verification result is passed, after the application receives the key factor information from the mobile communication device, it sends the key factor information to the controller to confirm whether the controller corresponds to the binding Device. The authentication method described in claim 24 further includes: While the application is waiting for the first biometric confirmation result or the second biometric confirmation result of the mobile communication device, the mobile communication device generates a first public key and a first private key, and the application Request the first public key, a biometric identification status, and the key factor information from the mobile communication device, wherein the application program stores the first public key; and Before the application program transmits the key factor information to the controller, the application program generates a second public key and a second private key, and transmits the second public key to the controller so that the controller Store the second public key. The authentication method described in claim 25 further includes: When the application program authenticates the mobile communication device, the mobile communication device obtains a first authentication query from the application program; and The mobile communication device responds to the first authentication query to generate a first signature according to the first private key, and the mobile communication device returns the first signature to the application. The authentication method described in claim 25 further includes: When the controller authenticates the application, the application obtains a second authentication query from the controller; and The application program responds to the second authentication query to generate a second signature according to the second private key, and the application program returns the second signature to the controller. The authentication method according to claim 18, wherein the electronic device is not connected to an external electronic device, and the authentication method further includes: In the binding phase, the application program generates the summary file based on the key factor information of the electronic device and the retrieval strategy; and In the checking phase, the application program determines whether the controller corresponds to a binding device according to the summary file and the key factor information of the electronic device. The authentication method according to claim 28, wherein the key factor information of the electronic device includes an identification code of the controller, an identification code of an application program, and a login account of the electronic device. The authentication method according to claim 18, wherein the step of registering the universal second factor service with the server device according to the summary file includes: Send the account and password used to log in to the server device to the server device through the controller; Obtain a server identification code and the summary file from the server device and the processor through the controller; Performing a hash operation based on a random number, the server identification code and the digest file through the controller to generate an information identification code and a public key; and The random number, the information identification code, and the public key are sent to the server device through the controller to register the universal second factor service with the server device. The authentication method according to claim 30, wherein the step of performing a hash operation based on the random number, the server identification code, and the digest file to generate the information identification code and the public key includes: Perform hash operations on the controller according to the random number, the server identification code, and the digest file to generate a private key and the public key; and The controller performs a hash operation according to the private key, the server identification code, and the summary file to generate the information identification code. The authentication method according to claim 31, wherein the step of performing the authentication operation of the universal second factor service with the server device according to the digest file corresponding to the key identification file includes: Send the account and password used to log in to the server device to the server device through the controller, Obtain an authentication query from the server device through the controller; Generate a signature based on the private key in response to the authentication query through the controller; and The signature is returned to the server device through the controller, so that the server device performs authentication of the universal second factor service according to the signature and the public key. The authentication method according to claim 32, wherein the step of generating the signature according to the private key through the controller in response to the authentication query includes: Determine whether a button of the button module is pressed through the controller to obtain a determination result; and If the result of the judgment is yes, the controller is used to respond to the authentication query and generate the signature according to the private key.

Images