Password management method, device and system and readable storage medium

Abstract

The invention discloses a password management method, device and system and a readable storage medium, and relates to the technical field of security, the password management method, device and system are applied to a password management module of terminal equipment, the terminal equipment further comprises a target application program, and the method comprises the steps that first warning information generated by a server side is received, the first warning information is used for representing that a password leakage risk exists in a specified account of the target application program; and displaying the first warning information through a system pop-up window. After the password management module of the terminal equipment receives the first warning information, a user does not need to independently set each application program, and the password management module can display the first warning information in time through the system pop-up window, so that the operation of the user is simplified, and the warning information can be sent in time.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of security, and more particularly, to a password management method, device, system and readable storage medium. BACKGROUND

[0002] At present, a user can generally log in to an application program corresponding to an account through the account and a password corresponding to the account. In some cases, the account and the password corresponding to the application program can be leaked. Although the user can be informed of the account and the password being leaked through the application program, the user needs to perform a relatively complex operation to be informed of the account and the password being leaked through the application program. Therefore, the user currently has difficulty in learning the message that the account and the password can be leaked in a timely manner. SUMMARY

[0003] The present application provides a password management method, device, system and readable storage medium.

[0004] In a first aspect, the present application provides a password management method applied to a password management module of a terminal device, the terminal device further comprising a target application program, and the method comprises: receiving first warning information generated by a server, the first warning information being used to represent that a specified account of the target application program has a risk of password leakage; and displaying the first warning information through a system pop-up window.

[0005] In a second aspect, the present application further provides a password management device, comprising: a receiving unit and a prompting unit. The receiving unit is configured to receive first warning information generated by a server, the first warning information being used to represent that a specified account of the target application program has a risk of password leakage; and the prompting unit is configured to display the first warning information through a system pop-up window.

[0006] In a third aspect, the present application further provides a password management system, comprising a terminal device and a server, the terminal device comprising a password management module and a target application program, the terminal device being connected with the server; and the password management module is configured to execute the password management method of the first aspect.

[0007] In a fourth aspect, the present application further provides a computer readable storage medium, the computer readable storage medium storing program codes, the program codes being executable by a processor to execute the method of the first aspect.

[0008] The password management method, device, system and readable storage medium provided by the embodiment of the application are applied to a password management module of a terminal device, the terminal device further comprises a target application program, first, first warning information generated by a server is received; and then the first warning information is displayed through a system pop-up window. The first warning information is used to represent that a specified account of the target application program has a risk of password leakage. If an application program corresponding to the risk of password leakage displays warning information on an official website or in the application program, the user can not make the application program in a foreground running state at any time, and thus cannot obtain the warning information in time. In the application, after receiving the first warning information, the password management module of the terminal device can display the first warning information in time through the system pop-up window, and the user does not need to separately set each target application program, thereby simplifying the operation of the user, improving the timeliness of the user obtaining the message of the possible leakage of the account and the password, and enabling the warning information to be delivered in time. Therefore, the user can easily and timely obtain the message of the possible leakage of the account and the password.

[0009] Other features and advantages of the embodiments of the application will be described in the following description, and some will become apparent from the description, or will be learned through practice of the embodiments of the application. The purposes and other advantages of the embodiments of the application can be achieved and obtained through the structures specifically indicated in the written description, claims, and drawings. BRIEF DESCRIPTION OF DRAWINGS

[0010] In order to more clearly illustrate the technical solutions in the embodiments of the application, the following will briefly introduce the drawings needed to be used in the embodiment description. Obviously, the drawings in the following description are only some embodiments of the application, and other drawings can be obtained by those skilled in the art without creative effort on the basis of these drawings.

[0011] Figure 1 An application scenario diagram of the password management method provided by the embodiment of the application is shown;

[0012] Figure 2 A method flowchart of the password management method provided by the embodiment of the application is shown;

[0013] Figure 3 A method flowchart of the password management method provided by another embodiment of the application is shown;

[0014] Figure 4 A method flowchart of the password management method provided by another embodiment of the application is shown;

[0015] Figure 5 A structural block diagram of the password management device provided by the embodiment of the application is shown;

[0016] Figure 6 a structural block diagram of a password management system provided by an embodiment of the present application is shown;

[0017] Figure 7 a structural block diagram of a terminal device provided by an embodiment of the present application is shown;

[0018] Figure 8 a structural block diagram of a computer readable storage medium provided by an embodiment of the present application is shown. DETAILED DESCRIPTION

[0019] In order to enable persons skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. The components of the embodiments of the present application described and shown in the drawings herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed present application, but only represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by persons skilled in the art without creative work are within the scope of protection of the present application.

[0020] It should be noted that: similar reference numerals and letters represent similar items in the following drawings, therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. Meanwhile, in the description of the present application, the terms "first", "second", etc. are only used to distinguish the description, and cannot be understood as indicating or implying relative importance.

[0021] At present, a user can generally log in to an application program corresponding to an account through the account and a password corresponding to the account. In some cases, the account and the password corresponding to the application program can be leaked, although the user can be informed of the account and the password being leaked through the application program. However, if the user wants to be informed of the account and the password being leaked through the application program, the user needs to perform a relatively complex operation, so that the user currently has difficulty in learning the message that the account and the password can be leaked in time. How to enable the user to easily learn the message that the account and the password can be leaked in time is a problem to be solved.

[0022] At present, some enterprises can inform the user through official websites, official application programs, etc. when an account or password leakage event occurs or can occur, or can push the account or password leakage event through the official application program.

[0023] However, the inventors found in research that the method of informing the user through the official website or the official application program is difficult to inform the user of the account and password leakage in a timely manner, resulting in poor timeliness of the user obtaining the leaked message. And the push of the account or password leakage event through the official application program is generally different for different enterprises. In order to ensure that the official application program has the permission of pushing information, the user needs to set the permission for each official application program. Thus, the user needs to perform a more complex operation.

[0024] Therefore, in order to solve or partially solve the above problems, the present application provides a password management method, device, system and readable storage medium.

[0025] Please refer to Figure 1 , Figure 1 An application scenario diagram of a password management method is shown, that is, a password management scenario 100, which includes a terminal device 110 and a user 120.

[0026] The terminal device 110 shown in Figure 1 is a smart phone, and the user 120 can use the terminal device 110. The terminal device 110 can include a target application program. Specifically, the terminal device 110 can run an operating system, and the target application program can run in the operating system. The data corresponding to the target application program can be stored in the memory of the terminal device 110. When the target application program needs to be run, the corresponding data in the memory can be called by the processor of the terminal device 110, so as to run the target application program. The terminal device 110 further includes a password management module, which can be represented by passwordManager in some embodiments.

[0027] In the process of using the terminal device 110 by the user 120, the password management module can display first warning information through a system pop-up window, wherein the first warning information is used to represent that a specified account of the target application program has a risk of password leakage. For detailed introduction, please refer to the subsequent embodiments.

[0028] Please refer to Figure 2 , Figure 2 A method flowchart of a password management method provided by an embodiment of the present application is shown. The password management method can be applied to Figure 1In the illustrated password management scenario, the terminal device can specifically use its password management module as the execution entity for implementing the password management method. This password management method may include steps S110 and S120.

[0029] Step S110: Receive a first warning message generated by the server. The first warning message is used to indicate that there is a risk of password leakage for a specified account of the target application.

[0030] As described above, the terminal device may include a password management module, and may also include a target application. For example, the target application may be an instant messaging application; a streaming music application; or an online video application.

[0031] It should be noted that the password management module can be a system-level application. For example, this password management module can be a system application pre-installed on the terminal device at the factory; it can also be a system application embedded in the terminal device's operating system. The password management module reserves a designated interface, which can then communicate with various target applications. This allows the module to obtain a first warning message indicating a risk of password leakage for a specific account within the target application, and display this warning message via a system pop-up. This reduces the difficulty for users to perform actions to obtain the warning message promptly. Detailed explanations can be found in the following description. The target application is an application installed by the user on top of the operating system running on the terminal device to achieve certain functions.

[0032] In this context, target users on the terminal device can run the target application to access its corresponding functions. It's understood that during the process of running the target application on the terminal device, the target user can log in using the account and password associated with the target application. These accounts and passwords can be pre-created by the user, for example, through the target application itself, or through the official website of the target application.

[0033] For example, a target user can create an account A1 and a password A2 for the target application A, and then log in using account A1 and password A2 when using the target application A.

[0034] In some embodiments, the password management module can also pre-store the account corresponding to the target application and the password corresponding to the specified account used by the target user. Thus, in the subsequent process of running the target application by the target user, if the password management module detects that the target user needs to input the account and the password corresponding to the target application for login, the password management module can call the pre-stored account and the password to realize login, so that the user can quickly and conveniently log in.

[0035] For example, when the target user opens the target application or the official website of the target application, if the interface for inputting the account and the password is detected, the password management system can be triggered, and the interface for inputting the account and the password can be automatically filled according to the pre-stored account and the password corresponding to the target application, so as to complete the input of the account and the password.

[0036] Optionally, the password management system can be triggered when the interface for inputting the account and the password is detected and the user inputs the account. At this time, the password corresponding to the account input by the user can be found according to the pre-stored account and the password corresponding to the target application, and the password in the interface for inputting the account and the password can be automatically filled, so as to complete the input of the password.

[0037] Optionally, before automatically filling the account and the password in the interface for inputting the account and the password, the password management module can also generate inquiry information, wherein the inquiry information is used to inquire whether the user automatically fills the account or the password. After obtaining the determination operation of the user for the inquiry information, the account and the password in the interface for inputting the account and the password are automatically filled.

[0038] It can be understood that the target application can correspond to a respective server. The server can be used to store the account and the password corresponding to the target application created by the user, and the server can also be used to provide services for the execution of the target application. For example, if the target application is a video online application, the server corresponding to the video online application can store the account and the password corresponding to the video application, and can also provide the video application with online video playing and the like.

[0039] In a case where the specified account of the target application program exists a risk of password leakage, the server corresponding to the target application program can generate first warning information. If the first warning information is only announced on the official website of the target application program or displayed in the target application program, the target user can not browse the official website of the target application program in time, or can not make the target application program run at any time, so that the target user can not know the first warning information in time, and thus the target user can not know the risk of password leakage of the specified account in time. The specified account is the account corresponding to the target user in the target application program. For example, if the accounts corresponding to the target application program include account B, account C and account D, and the account corresponding to the target user in the target application program is account C, it can be determined that account C is the specified account.

[0040] Therefore, in some embodiments, the first warning information generated by the server can be received by the password management module of the terminal device, so that the first warning information can be displayed by the password management module subsequently.

[0041] For some embodiments, the first warning information generated by the server can be obtained by the target end, and then the first warning information can be forwarded to the password management module by the target end. For example, the password management module can have a communication connection with the target application program, so that the target end can be the target application program; or the password management module can have a communication connection with the management server, so that the target end can be the management server. The specific way in which the password management module receives the first warning information can be understood with reference to the subsequent embodiments.

[0042] It can be understood that the risk of password leakage can be that the password of the specified account has been leaked, or that the specified account has been abnormally logged in, for example, logged in an area other than a commonly used login area.

[0043] Step S120: displaying the first warning information through a system pop-up window.

[0044] After the password management module receives the first warning information, the first warning information can be directly displayed through a system pop-up window.

[0045] It should be noted that the system pop-up window is generally a window or a prompt box automatically popped up by an operating system or an application program running on the terminal device in a specific case. Thus, information such as information, reminders or warnings can be displayed to the target user through the popped-up window or prompt box. Therefore, for the embodiments of the present application, the password management module can control the terminal device to display the system pop-up window as an application program, so as to display the first warning information through the system pop-up window.

[0046] Since the system pop-up window is automatically popped up at the operating system level, the target user can see the first warning information displayed through the system pop-up window in time regardless of the application program or interface, thereby achieving timely delivery of the first warning information to the target user. Moreover, the password management module displays the first warning information through the system pop-up window, without the need for the user to separately set the permission of each target application program, thereby reducing the operation difficulty of the user and making it easier for the user to timely learn the message that the account and password may be leaked.

[0047] The first warning information can include identity information of a specified enterprise and a processing suggestion. The specified enterprise is the enterprise corresponding to the target application program, and the processing suggestion can be used to prompt the target user to modify the password of the specified account of the target application program. For detailed introduction of the first warning information, refer to subsequent embodiments.

[0048] In some embodiments, after obtaining the first warning information, the password management module can also display the first warning information in the form of an information card in the terminal device. The information card can be a card preselected and displayed in a specified area of the display screen of the terminal device, and the corresponding information can be displayed in the information card. The information card can be pre-associated with the password management module, so that the password management module associated with the information card can automatically push the first warning information to the information card after obtaining the first warning information.

[0049] It can be understood that the information card is generally in the main interface of the operating system of the terminal device, so that the first warning information displayed in the information card can be displayed in the main interface, so that the target user can timely obtain the first warning information.

[0050] The password management method provided in the embodiments of the present application is applied to a password management module of a terminal device, and the terminal device further includes a target application program. First, the first warning information generated by a server is received. Then, the first warning information is displayed through a system pop-up window. The first warning information is used to represent that a specified account of the target application program has a password leakage risk. If the application program corresponding to the password leakage risk displays warning information on an official website or in the application program, the user can not always make the application program run in time, so as to timely obtain the warning information. In the present application, after receiving the first warning information, the password management module of the terminal device can timely display the first warning information through the system pop-up window, without the need for the user to separately set each target application program, thereby simplifying the operation of the user, improving the timeliness of the user obtaining the message of leakage, and making the warning information timely delivered. Therefore, the user can easily and timely learn the message that the account and password may be leaked.

[0051] Please refer to Figure 3 , Figure 3 A method flowchart of a password management method provided by an embodiment of the present application is shown. The password management method can be applied to Figure 1 The terminal device in the password management scenario shown can specifically take the password management module of the terminal device as an execution subject for executing the password management method. The password management method can include steps S210 and S260.

[0052] Step S210: receiving first warning information generated by a server, the first warning information being used to represent that a specified account of the target application program has a risk of password leakage.

[0053] Step S220: displaying the first warning information through a system pop-up window.

[0054] Among them, steps S210 and S220 have been described in detail in the foregoing embodiments, and will not be described here again.

[0055] Step S230: obtaining a corrected password in response to a password set by the target user for the specified password.

[0056] In some embodiments, the target user can modify the specified password on the basis of the first warning information displayed by the password management module. The specified password is the password corresponding to the specified account, that is, the password corresponding to the account that may have a risk of password leakage in the first warning information.

[0057] For example, the target user can determine the specified account that may have a risk of password leakage according to the first warning information, and then run the target application program corresponding to the specified account to set the specified password of the specified account in a specified page. The specified page is a page corresponding to the specified account, and the specified page can be used to set the password, for example, the specified page can be a password reset page.

[0058] Among them, the target user can set the password through the input module of the terminal device. For example, the input module can be a keyboard, and the user can input the password through the keyboard to set the password for the specified password, where the keyboard can be a physical keyboard or a virtual keyboard. For another example, the input module can be a microphone, so that the target user can issue a sound, and then the terminal device acquires the sound issued by the target user and performs voice recognition on the sound to obtain the corresponding password, thereby setting the password for the specified password.

[0059] Thus, the corrected password can be obtained in response to the password set by the target user for the specified password. That is, the password input by the target user in the specified page is the password set by the target user for the specified password. Thus, the corrected password can be obtained in response to the password set by the target user for the specified password. That is, the password input by the target user in the specified page is the password set by the target user for the specified password.

[0060] Optionally, before obtaining the corrected password in response to the target user setting the password for the specified password, the system can automatically jump to the specified page, and the step S229 can be further included.

[0061] Step S229: displaying a specified page corresponding to the specified account, wherein the specified page is used for setting a password.

[0062] For some embodiments, after displaying the first warning information through the system pop-up window, the password management module can automatically jump to the specified page corresponding to the specified account before obtaining the corrected password in response to the target user setting the password for the specified password, so that the target user does not need to actively run the target application program corresponding to the specified account, and the target user does not need to operate to enter the specified page. While not reducing security, the processing flow of the target user modifying the password due to the password leakage event is simplified, the operation amount of the target user is reduced, and the efficiency of changing the password is improved overall.

[0063] It should be noted that how to set the specific business decision of the password management module can be pre-set by the personnel developing the password management module, or can be set by the manufacturer of the terminal device, and the present application does not make specific limitations. Among them, the business decision includes whether to automatically jump to the specified interface corresponding to the specified account before obtaining the corrected password in response to the target user setting the password for the specified password.

[0064] Step S240: detecting whether the corrected password matches the historical password of the specified account.

[0065] Further, after obtaining the corrected password set by the user, the corrected password can be detected, and specifically, whether the corrected password matches the historical password of the specified account can be detected. The historical password of the specified account is the password used by the specified account in the past, that is, the historical password includes the password currently used by the specified account in the case of displaying the first warning information through the system pop-up window, and the password used by the specified account in the past before displaying the first warning information through the system pop-up window.

[0066] It should be noted that the historical password of the specified account can include multiple passwords, or can only have one password.

[0067] For some embodiments, the password management module can pre-store the historical password of the specified account, so that after obtaining the corrected password set by the user, the historical password of the specified account can be read in the password management module, and the corrected password and the historical password of the specified account are compared to determine whether the corrected password matches the historical password of the specified account.

[0068] For example, the password management module can pre-store the historical passwords of each account corresponding to the target user, and after obtaining the correction password set by the user, the target application program corresponding to the correction password can be determined, and then the corresponding specified account can be determined, so that the historical password corresponding to the specified account is determined in the pre-stored historical passwords of each account corresponding to the target user.

[0069] The determination of whether the correction password matches the historical password of the specified account can be that if the same password as the correction password is found in the historical password of the specified account, it is determined that the correction password matches the historical password of the specified account; if the same password as the correction password is not found in the historical password of the specified account, it is determined that the correction password does not match the historical password of the specified account.

[0070] For other embodiments, the correction password and the historical password of the specified account can also be detected by verifying the codes. Specifically, step S240 can further include steps S241 to S244.

[0071] Step S241: Obtain the first verification value of the historical password.

[0072] Step S242: Obtain the second verification value of the correction password.

[0073] Step S243: If the first verification value and the corresponding second verification value satisfy the specified condition, it is determined that the correction password matches the corresponding historical password, wherein the specified condition includes that there is a verification value in the first verification value that is the same as the second verification value.

[0074] Step S244: If the first verification value and the corresponding second verification value do not satisfy the specified condition, it is determined that the correction password does not match the corresponding historical password.

[0075] Specifically, the first verification value of the historical password can be obtained first, and then the second verification value of the correction password can be obtained. The first verification value can be a value obtained by calculating the historical password by a specified algorithm, and the second verification value can also be a value obtained by calculating the historical password by a specified algorithm. For example, the specified algorithm can be a hash algorithm, such as SHA256 hash algorithm or SHA512 hash algorithm. It can be understood that the specific hash algorithm can be flexibly selected.

[0076] The first verification value can be obtained by calculating the historical password by a specified algorithm after obtaining the historical password by the method described above, or it can be obtained by searching the historical verification list. Specifically, step S241 can further include step S2411.

[0077] Step S2411: searching for the standard check value corresponding to the historical password in the pre-acquired historical check list as the first check value of the historical password, wherein the historical check list comprises at least one historical password and the standard check value corresponding to each historical password.

[0078] That is, the historical check list can be pre-stored in the password management module, wherein the historical check list comprises at least one historical password and the standard check value corresponding to each historical password. That is, the historical password acquired can be pre-calculated by a specified algorithm to obtain the standard check value corresponding to the historical password, and then the historical check list is generated based on the historical password and the corresponding standard check value and stored in the password management module. In some embodiments, the historical check list can be denoted as historyHash.

[0079] Optionally, the historical check list can also store the date of occurrence of the leakage of the historical password corresponding to the historical password to provide more dimensional information to the target user.

[0080] Further, after acquiring the historical password of the specified account, the standard check value corresponding to the historical password can be searched in the historical check list as the first check value of the historical password. Specifically, the same historical password as the historical password of the specified account can be searched in the historical check list, and then the standard check value corresponding to the same historical password is taken as the first check value.

[0081] In some embodiments, after displaying the first warning information through the system pop-up window, the check value of the password corresponding to the specified account can be acquired, and similarly, the check value of the password corresponding to the specified account can be calculated by a specified algorithm, so as to obtain the check value of the password corresponding to the specified account and the specified account associated with the check value. Then the calculated check value is stored as the historical password corresponding to the specified account in the historical check list, and the historical password corresponding to the specified account and the standard check value corresponding to the historical password are updated.

[0082] Further, the first check value and the second check value can be compared to detect whether the corrected password matches the historical password of the specified account. Specifically, if the first check value and the corresponding second check value satisfy a specified condition, it is determined that the corrected password matches the corresponding historical password; if the first check value and the corresponding second check value do not satisfy the specified condition, it is determined that the corrected password does not match the corresponding historical password. The specified condition includes that there is a check value in the first check value which is the same as the second check value.

[0083] It can be known from the foregoing introduction that the historical password corresponding to the specified account can include multiple passwords or only one password, so that if the first check value has the same check value as the second check value, it indicates that the historical password has the same password as the corrected password, at this time, it can be determined that the corrected password matches the corresponding historical password, at this time, step S250 can be jumped to execute. If the first check value does not have the same check value as the second check value, it indicates that the historical password has the same password as the corrected password, at this time, it can be determined that the corrected password does not match the corresponding historical password, then step S260 can be jumped to execute. At this time, the specified password can be modified to the current corrected password.

[0084] In the embodiments provided in the present application, the detection of whether the corrected password matches the historical password is displayed through the first check value and the second check value, which can improve the accuracy of determining whether the match.

[0085] Step S250: If the corrected password matches the historical password of the specified account, the target user is prompted to modify the specified password again, and the operation of obtaining the corrected password in response to the password set by the target user for the specified password and the subsequent operation are executed until the current obtained corrected password does not match the historical password of the specified account, and the specified password is modified to the current corrected password.

[0086] In the case where the corrected password matches the historical password of the specified account, it indicates that the current corrected password set by the target user may have been used in the past, and the current corrected password still has the risk of password leakage, at this time, the target user is prompted to modify the specified password again, and the operation of obtaining the corrected password in response to the password set by the target user for the specified password and the subsequent operation are executed until the current obtained corrected password does not match the historical password of the specified account, and the specified password is modified to the current corrected password. Therefore, it can be ensured that the set corrected password is different from the password in the historical password, and it can be ensured that the current corrected password is an unreleased password, and the current corrected password as the specified password can ensure that the modified specified password is an unreleased password, thereby improving the security.

[0087] It can be understood that the specified account with the risk of password leakage in the first warning information can be multiple, so that the password management module can also detect whether the target user has modified the specified password of each specified account, if the specified password of each specified account has not been modified, the user can also be prompted to modify the specified password which has not been modified until the target user has modified the specified password of each specified account. The related content of the password detection module in response to the modification of the specified password by the target user can be referred to the foregoing introduction, which will not be described here.

[0088] Optionally, even if the corrected password is detected to match the historical password of the specified account, the target user can not be willing to modify the specified password again at this time. Therefore, for some embodiments, the target user can also input an ignore identifier so as to make the password management module stop prompting the target user to modify the specified password. Specifically, step S250 can further include steps S251-S253.

[0089] Step S251: display an operation control.

[0090] Step S252: if the ignore identifier input by the target user through the operation control is detected, modify the specified password to the corrected password, wherein the ignore identifier is used to represent stopping prompting the user to perform the modification operation again.

[0091] Step S253: if the ignore identifier input by the target user through the operation control is not detected, prompt the target user to modify the specified password again, and return to perform the operation of obtaining the corrected password in response to the password set by the target user for the specified password and subsequent operations until the currently obtained corrected password does not match the historical password of the specified account, and modify the specified password to the current corrected password.

[0092] For some embodiments, in the case where the corrected password is detected to match the historical password of the specified account, the password management module can display an operation control. For example, a prompt information and an operation control can be displayed in a specified area of the display screen of the terminal device, wherein the prompt information is used to inquire whether the target user ignores the prompt of modifying the specified password again, and the operation control can include an operation control corresponding to “yes” and an operation control corresponding to “no”.

[0093] Therefore, the target user can input the ignore identifier by operating the operation control corresponding to “yes”, and can also operate the operation control corresponding to “no” to input a continue prompt identifier. The operation of the target user on the operation control can be that the target user clicks the operation control on the real screen, or the target user utters “yes” or “no” so that the terminal device obtains the voice of “yes” or “no” and performs voice recognition on the voice to confirm whether the target user operates the operation control corresponding to “yes” or the operation control corresponding to “no”. The ignore identifier is used to represent stopping prompting the user to perform the modification operation again.

[0094] Further, if the ignore identifier input by the target user through the operation control is detected, it indicates that the target user wants the password management module to stop prompting the password modification again at this time. The specified password can be directly modified to the corrected password. It should be noted that the operation control corresponding to "Yes" in the above example can be detected, so that it is determined that the ignore identifier input by the target user through the operation control is detected.

[0095] If the ignore identifier input by the target user through the operation control is not detected, the target user is prompted to modify the specified password again, and the operation of obtaining the corrected password in response to the password set by the target user for the specified password and the subsequent operation are returned to be executed until the corrected password currently obtained does not match the historical password of the specified account, and the specified password is modified to the current corrected password.

[0096] It should be noted that the operation control corresponding to "No" in the above example can be detected, so that it is determined that the ignore identifier input by the target user through the operation control is not detected. The input of the target user can also be not detected within a threshold time after the operation control is displayed, so that it can be determined at this time that the ignore identifier input by the target user through the operation control is not detected. For example, the threshold time can be 10s, 15s, 30s, etc.

[0097] Step S260: If the corrected password does not match the corresponding historical password, the specified password is modified to the current corrected password.

[0098] If the corrected password does not match the corresponding historical password, the specified password can be modified to the current corrected password.

[0099] The password management method provided by the embodiment of the application is applied to a password management module of a terminal device, and the terminal device further includes a target application program. First, a first warning information generated by a server is received. Then, the first warning information is displayed through a system pop-up window. A corrected password is obtained in response to a password set by a target user for a specified password. Whether the corrected password matches a historical password of the specified account is detected. If the corrected password matches the historical password of the specified account, the target user is prompted to modify the specified password again, and the operation of obtaining the corrected password in response to the password set by the target user for the specified password and the subsequent operation are returned to be executed until the corrected password currently obtained does not match the historical password of the specified account, and the specified password is modified to the current corrected password. In the embodiment of the application, the first check value and the second check value are used to display the detection of whether the corrected password matches the historical password, which can improve the accuracy of the judgment of whether the password matches. In addition, it can be ensured that the modified specified password is a password that has not been leaked, and the security is improved.

[0100] Please refer to Figure 4 , Figure 4 A method flowchart of a password management method provided by an embodiment of the present application is shown. The password management method can be applied to Figure 1 The terminal device in the password management scenario shown can specifically take the password management module of the terminal device as an execution subject for executing the password management method. The password management method can include steps S310 and S380.

[0101] Step S310: Obtain first warning information forwarded by a target end, wherein the target end is configured to receive and forward first warning information generated by a service end.

[0102] It can be understood that the enterprises corresponding to different accounts of a target user can be different, and the service ends corresponding to different enterprises are also different. If a communication connection is directly established between the password management module in the terminal device and the plurality of service ends, it is relatively difficult, and is not conducive to the deployment of the password management module in the terminal device.

[0103] Therefore, in some embodiments, a communication connection can be established between the target end and the service ends corresponding to the plurality of enterprises, and a communication connection can be established between the target end and the password management module, so that the target end can receive the first warning information generated by the service end, and then forward the first warning information to the password management module. Detailed information about the first warning information can be referred to the foregoing embodiments, and will not be described here.

[0104] For example, the target end can be a target application program. Since the service end corresponding to each enterprise has a communication connection with the target application program of the enterprise itself, and the target application program is deployed in the terminal device. The password management module deployed in the terminal device can establish a communication connection with the target application program also deployed in the terminal device, for example, the password management module can provide a specified interface, so that the target application program can realize communication with the password management module by calling the specified interface. Therefore, the first warning information generated by the service end can be directly sent to the target application program in the terminal device, and then the target application program can call the specified interface of the password management module to forward the first warning information to the password management module, so that the password management module receives the first warning information generated by the service end.

[0105] In another example, the target end can be a management server. The management server can be a server built by a terminal device manufacturer, such as a server built by an original equipment manufacturer (OEM) background. In some embodiments, the management server can be referred to as server. The management server can be pre-connected with a service end corresponding to each enterprise, and the management server is connected with the password management module. For example, the management server can communicate with the password management module through a designated interface of the password management module. Thus, the first warning information generated by the service end can be directly sent to the management server, and then the management server can call the designated interface of the password management module to forward the first warning information to the password management module, so that the password management module receives the first warning information generated by the service end.

[0106] The management server can receive the first warning information from the service end through manual docking or automatic message receiving, etc. For example, the management server can build a monitoring mechanism to actively capture the first warning information generated by the service end, thereby improving the comprehensiveness of information collection.

[0107] For some embodiments, the first warning information can include identity information of the specified enterprise, type of the specified enterprise, time information of the risk of password leakage, and processing suggestion information. For example, the identity information of the specified enterprise can be represented by source, such as the name of the enterprise or the name of the official website corresponding to the enterprise, etc. The type of the specified enterprise can represent the type of the target application corresponding to the specified enterprise, such as financial type or social type, etc. The time information of the risk of password leakage can include, for example, that the account created between x1 year y2 month and x2 year y2 month has been leaked. The processing suggestion information can include, for example, modifying the password, logging out of the account, etc. Optionally, the first warning information can also include specific function modules involved, such as that the specified function module receives attacks, and the password of the account related to the specified function module has been leaked.

[0108] The specific content included in the above first warning information can be directly generated by the service end, then sent to the target end, and then forwarded to the password management module by the target end.

[0109] Optionally, in the case of the target end being a management server, the first warning information generated by the service end can further only include information representing that the specified account of the target application program has a risk of password leakage, and the management server can perform data analysis on the first warning information after obtaining the first warning information, thereby obtaining identity information of the specified enterprise, a type of the specified enterprise, time information of the risk of password leakage, and processing suggestion information, and then forwarding the identity information of the specified enterprise, the type of the specified enterprise, the time information of the risk of password leakage, and the processing suggestion information to the password management module as the first warning information.

[0110] The data analysis on the first warning information can be performed by manual analysis, or can be implemented by combining a neural network model such as a text model and a classification model, which is not limited in the embodiments of the application.

[0111] Optionally, in some embodiments, when the service end detects that the specified account of the target application program has a risk of password leakage, the service end can select the target application program as the target end or the management server as the target end according to the severity of the risk of password leakage. The severity is positively correlated with the time of the risk of password leakage and the number of the specified accounts having the risk of password leakage.

[0112] For example, a threshold severity can be preset, so that when the severity of the risk of password leakage is less than or equal to the threshold severity, the target application program can be selected as the target end, and when the severity of the risk of password leakage is greater than the threshold severity, the management server can be selected as the target end. Thus, for a password leakage risk with low severity, the target application program of the terminal device can be directly notified to forward the password management module, and for a password leakage risk with high severity, the management server can perform data analysis on the first warning information before forwarding the password management module.

[0113] Step S320: displaying the first warning information through a system pop-up window.

[0114] The step S320 has been described in detail in the foregoing embodiments, and will not be described here.

[0115] Step S330: obtaining an initial account and an initial password input by the target user in response to an account and password input operation of the target user.

[0116] In some embodiments, after receiving the first warning information generated by the service end, the password management module can update the historical verification list based on the first warning information. Wherein, updating the historical verification list is to update the historical password and the standard verification value corresponding to the historical password. For example, it can be determined based on the first warning information whether the specified account already exists in the historical verification list, if it exists, the specified password corresponding to the specified account in the first warning information can be associated and stored with the specified account, similarly, the verification value of the specified password can be further obtained by a specified algorithm as the standard verification value corresponding to the specified account and stored with the specified account. If it does not exist, a new specified account can be created in the historical verification list, and the above specified password and the standard verification value corresponding to the specified password can be stored with the specified account.

[0117] The target user can perform the account and password input operation through the terminal device. For example, the target user can open the target application, and perform the account and password input operation of the target application in the displayed login interface of the target application; for another example, the target user can open the official website corresponding to the target application, and perform the account and password input operation of the target application in the login interface displayed on the official website.

[0118] Therefore, the password management module can detect that the account and password input operation of the target user is triggered, and obtain the initial account and initial password input by the target user in response to the account and password input operation of the target user. Wherein, the initial account is the account input by the target user through the account and password input operation, and the initial password is the password input by the target user through the account and password input operation.

[0119] Step S340: whether there is a specified account same as the initial account.

[0120] For some embodiments, if there is a specified account same as the initial account, it indicates that the initial account has a risk of password leakage, so it can jump to step S350 to further judge whether the initial password has a risk of leakage; and if there is no specified account same as the initial account, it indicates that the initial account has no risk of password leakage, so the initial password also has no risk of being leaked. At this time, it can jump to step S380.

[0121] It should be noted that whether there is a specified account same as the initial account can be searched in the account stored in the terminal device.

[0122] Step S350: if there is a specified account same as the initial account, the specified account same as the initial account is taken as a target specified account.

[0123] Further, it can be determined whether there is a specified account identical to the initial account, where the specified account is an account with a password leakage risk. For example, it can be determined whether there is a specified account identical to the initial account in the historical verification list stored by the password management module. If a specified account identical to the initial account is found, the specified account identical to the initial account can be taken as the target specified account.

[0124] For example, if the historical verification list includes a specified account K1, a specified account K2, and a specified account K3, and the initial account is K2, it can be determined that the specified account K2 is identical to the initial account K2. In this case, the specified account K2 can be taken as the target specified account.

[0125] Step S360: detecting whether the initial password matches a target historical password, where the target historical password is a historical password of the target specified account.

[0126] Further, it can be detected whether the initial password matches a target historical password, where the target historical password is a historical password of the target specified account. It should be noted that whether the initial password matches the target historical password means whether the initial password is identical to the target historical password.

[0127] For example, continuing the above example, if the specified account K2 in the historical verification list is determined to be the target specified account, and the historical password M2 corresponding to the specified account K2 stored in the historical verification list, the historical password M2 can be taken as the target historical password.

[0128] In another example, whether the initial password matches the target historical password can also be determined by comparing a verification value corresponding to the initial password with a verification value corresponding to the target historical password. Specifically, the verification value corresponding to the initial password can be obtained first. Similarly, the initial password can be calculated by a specified algorithm to obtain the verification value corresponding to the initial password. Then, the standard verification value corresponding to the target historical password can be obtained from the historical verification list, and the verification value corresponding to the initial password is compared with the standard verification value to determine whether the initial password matches the target historical password. In the case where the verification value corresponding to the initial password is identical to the standard verification value, it can be determined that the initial password matches the target historical password. In the case where the verification value corresponding to the initial password is different from the standard verification value, it can be determined that the initial password does not match the target historical password.

[0129] Thus, if it is detected that the initial password matches the target historical password, it indicates that the initial password input by the user for the initial account may have a risk of password leakage, and in this case, step S370 can be executed. If it is detected that the initial password does not match the target historical password, the target user can be asked whether the initial account and the initial password need to be stored in the password database.

[0130] The password management module can store a password database, and the password database can include a specified account, identity information of a specified enterprise corresponding to the account, and a historical password corresponding to the account. For example, the account can be represented by account, the password corresponding to the account can be represented by password, and the identity information of the specified enterprise can be represented by source, where the specified enterprise is the enterprise corresponding to the account. Thus, in the password database, each set of {source, {account, password}} can be recorded in the form of {source, {account, password}}, each set of {source, {account, password}} including an enterprise, an account corresponding to the enterprise, and a password of the account.

[0131] It can be understood that storing the initial account and the initial password in the password database can include creating a new initial account in the password database and storing other data related to the initial account; or it can include updating the data related to the initial account if the initial account already exists in the password database.

[0132] For example, the enterprise corresponding to the initial account can be determined first, and then it can be determined whether there is an enterprise in the password database that is the same as the enterprise corresponding to the initial account. If there is an enterprise in the password database that is the same as the enterprise corresponding to the initial account, the account corresponding to the enterprise in the password database that is the same as the enterprise corresponding to the initial account can be replaced by the initial account, and the password corresponding to the enterprise in the password database that is the same as the enterprise corresponding to the initial account can be replaced by the initial password.

[0133] Optionally, before the replacement, the target user can be asked whether to replace. For example, similar to asking the target user whether to ignore modifying the specified password again, the terminal device can display prompt information and operation controls in a specified area of the display screen of the terminal device, so that the target user can operate the operation controls, and the terminal device can thus determine whether the target user selects to replace. For details, please refer to the foregoing embodiments, which will not be described here. If it is determined that the target user inputs to replace, the account corresponding to the enterprise in the password database that is the same as the enterprise corresponding to the initial account can be replaced by the initial account, and the password corresponding to the enterprise in the password database that is the same as the enterprise corresponding to the initial account can be replaced by the initial password.

[0134] In the case that the user input is not replaced, the same enterprise as the initial account in the password database and information associated with the same enterprise can be deleted, and then a new enterprise corresponding to the initial account is created in the password database, and the initial account corresponding to the enterprise, the initial account and the initial password are stored in association.

[0135] If there is no enterprise identical to the initial account, a new enterprise corresponding to the initial account is created in the password database, and the initial account corresponding to the enterprise, the initial account and the initial password are stored in association.

[0136] Optionally, before creating a new enterprise corresponding to the initial account in the password database, the target user can also be asked whether to store the initial account and the initial password this time. For example, similar to asking the target user whether to ignore the specified password modification again, the terminal device can display prompt information and operation controls in a specified area of the display screen, so that the target user can operate the operation controls, and the terminal device can know whether the target user stores the initial account and the initial password this time. For details, please refer to the foregoing embodiments, which will not be repeated here. In the case that the target user inputs confirmation to store the initial account and the initial password this time, the initial account corresponding to the enterprise can be created in the password database, and the initial account corresponding to the enterprise, the initial account and the initial password are stored in association.

[0137] In the case that the target user inputs confirmation not to store the initial account and the initial password this time, the initial account and the initial password can not be stored.

[0138] Step S370: If the initial password matches the target historical password, a second warning information is generated, wherein the second warning information is used to represent that the initial password has a risk of being leaked.

[0139] In the case that the initial password matches the target historical password, it is represented that the initial password input by the user has a risk of password leakage. At this time, a second warning information can be generated, wherein the second warning information is used to represent that the initial password has a risk of being leaked.

[0140] Similar to the first warning information, the first warning information can also be displayed through a system pop-up window; the second warning information can also be displayed in the form of an information card in the terminal device. For details, please refer to the foregoing embodiments, which will not be repeated here.

[0141] Optionally, the user can also be prompted to modify the initial password.

[0142] Step S380: If there is no specified account identical to the initial account, it is inquired whether the target user needs to store the initial account and the initial password into the password database.

[0143] In the case that there is no specified account identical to the initial account, it is characterized that there is no risk of password leakage for the initial account, and thus there is also no risk of leakage for the initial password. At this time, it can be inquired whether the target user needs to store the initial account and the initial password into the password database. For the details of storage into the password database, reference can be made to the foregoing description of the steps, which will not be repeated here.

[0144] The password management method provided by the embodiment of the present application is applied to a password management module of a terminal device, and the terminal device further comprises a target application program. First, a first warning information forwarded by a target terminal is acquired, wherein the target terminal is configured to receive and forward the first warning information generated by a service terminal. Then, the first warning information is displayed through a system pop-up window. In response to an account and password input operation of the target user, an initial account and an initial password input by the target user are obtained. If there is a specified account identical to the initial account, the specified account identical to the initial account is taken as a target specified account. Whether the initial password matches a target historical password is detected, wherein the target historical password is a historical password of the target specified account. If the initial password matches the target historical password, a second warning information is generated, wherein the second warning information is configured to represent that the initial password has a risk of leakage. In the embodiment of the present application, the target terminal comprises a target application program or a management server. In addition to passively receiving the first warning information sent from the service terminal, the target terminal can also actively capture information, thereby improving the comprehensiveness of information collection and the timeliness of message transmission to the target user. In addition, in the embodiment of the present application, in the case that the target user inputs the initial account and the initial password, whether the initial password has a risk of leakage is detected, and the target user is prompted to modify the initial password in a timely manner in the case that there is a risk of leakage, thereby helping the target user to avoid misusing the historical password that has been leaked, and improving the security.

[0145] Please refer to Figure 5 , Figure 5 A structure block diagram of a password management device provided by the embodiment of the present application is shown, which comprises a receiving unit 510 and a prompting unit 520.

[0146] The receiving unit 510 is configured to receive a first warning information generated by a service terminal, and the first warning information is configured to represent that a specified account of the target application program has a risk of password leakage. The first warning information comprises identity information of a specified enterprise, a type of the specified enterprise, time information of the risk of password leakage, and processing suggestion information.

[0147] Optionally, the receiving unit 510 is further configured to acquire the first warning information forwarded by a target end, wherein the target end is configured to receive and forward the first warning information generated by the service end.

[0148] The prompting unit 520 is configured to display the first warning information through a system pop-up window.

[0149] Optionally, the prompting unit 520 is further configured to obtain a corrected password in response to a password set by the target user for a specified password, detect whether the corrected password matches a historical password of the specified account, if the corrected password matches the historical password of the specified account, prompt the target user to modify the specified password again, and return to perform the operation of obtaining the corrected password in response to the password set by the target user for the specified password and subsequent operations until the corrected password currently acquired does not match the historical password of the specified account, and modify the specified password to the corrected password currently acquired.

[0150] Optionally, the prompting unit 520 is further configured to acquire a first check value of the historical password, acquire a second check value of the corrected password, if the first check value and the corresponding second check value satisfy a specified condition, determine that the corrected password matches the corresponding historical password, wherein the specified condition includes that there is a same check value in the first check value and the second check value, and if the first check value and the corresponding second check value do not satisfy the specified condition, determine that the corrected password does not match the corresponding historical password.

[0151] Optionally, the prompting unit 520 is further configured to search for a standard check value corresponding to the historical password in a historical check list acquired in advance as the first check value of the historical password, wherein the historical check list includes at least one historical password and a standard check value corresponding to each historical password.

[0152] Optionally, the prompting unit 520 is further configured to display an operation control, if it is detected that the target user inputs an ignore identifier through the operation control, modify the specified password to the corrected password, wherein the ignore identifier is used to represent that the user is prompted to stop performing the modification operation again, and if it is not detected that the target user inputs the ignore identifier through the operation control, prompt the target user to modify the specified password again, and return to perform the operation of obtaining the corrected password in response to the password set by the target user for the specified password and subsequent operations until the corrected password currently acquired does not match the historical password of the specified account, and modify the specified password to the corrected password currently acquired.

[0153] Optionally, the prompting unit 520 is further configured to display a specified page corresponding to the specified account, wherein the specified page is used to set a password.

[0154] Optionally, the prompting unit 520 is further configured to obtain an initial account and an initial password input by the target user in response to the account of the target user and the password input operation; if there is a specified account same as the initial account, the specified account same as the initial account is taken as a target specified account; and it is detected whether the initial password matches a target historical password, wherein the target historical password is a historical password of the target specified account; and if the initial password matches the target historical password, second warning information is generated, wherein the second warning information is used to represent that the initial password has a risk of being leaked.

[0155] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described device and unit can refer to the corresponding process in the foregoing method embodiments, which will not be described here.

[0156] In several embodiments provided in the present application, the coupling between units can be electrical, mechanical or other forms of coupling. In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0157] Please refer to Figure 6 , Figure 6 A structure block diagram of a password management system provided by an embodiment of the present application is shown. Wherein, Figure 6 The password management system 600 shown in the figure comprises a terminal device 110 and a server 620, the terminal device 110 comprises a password management module 113 and a target application program 114, the terminal device 110 is connected with the server 620; the password management module 113 is used to execute the password management method described in each embodiment. For specific method introduction, please refer to the foregoing embodiments, which will not be described here.

[0158] Please refer to Figure 7 , Figure 7A structure block diagram of a terminal device provided by an embodiment of the present application is shown. The terminal device 110 can be a smart phone, a desktop computer, a vehicle-mounted computer, a server or a tablet computer, etc. The terminal device 110 in the present application can include a password management module 113 and a target application program 114, and can further include one or more of the following components: a processor 111, a memory 112, and one or more application programs, wherein the processor 111 is electrically connected to the memory 112, and the one or more programs are configured to perform the method as described in the foregoing embodiments. The password management module 113 and the target application program 114 can be stored in the memory 112.

[0159] The processor 111 can include one or more processing cores. The processor 111 connects various parts in the entire terminal device 110 by various interfaces and lines, performs various functions of the terminal device 110 and processes data by running or executing instructions, programs, code sets or instruction sets stored in the memory 112, and calling data stored in the memory 112. Alternatively, the processor 111 can be implemented in at least one of a hardware form of a digital signal processing (Digital Signal Processing, DSP), a field-programmable gate array (Field-Programmable Gate Array, FPGA), and a programmable logic array (Programmable Logic Array, PLA). The processor 111 can be integrated with a combination of one or more of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU), and a modem. Among them, the CPU is mainly used to process operating systems, user interfaces, computer programs, etc.; the GPU is used to render and draw display content; and the modem is used to process wireless communication. It can be understood that the above-mentioned modem can also not be integrated into the processor 111, but can be realized by a separate communication chip. Specifically, one or more processors 111 can execute the method as described in the foregoing embodiments.

[0160] For some embodiments, the memory 112 can include a random access memory (Random Access Memory, RAM) and can also include a read-only memory (Read-Only Memory). The memory 112 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 112 can include a program storage area and a data storage area, wherein the program storage area can store instructions for implementing an operating system, instructions for implementing at least one function, instructions for implementing various method embodiments described below, etc. The data storage area can also store data created by the terminal device 110 in use, etc.

[0161] Referring to Figure 8 Fig. 8 shows a structural block diagram of a computer readable storage medium provided by an embodiment of the present application. The computer readable medium 800 stores program codes, which can be invoked by a processor to execute the methods described in the above method embodiments.

[0162] The computer readable storage medium 800 can be an electronic memory such as a flash memory, an EEPROM (Electrically Erasable Programmable Read-Only Memory), an EPROM, a hard disk, or a ROM. Alternatively, the computer readable storage medium 800 comprises a non-transitory computer-readable storage medium. The computer readable storage medium 800 has a storage space for program codes 810 to execute any of the above methods. These program codes can be read from or written to one or more computer program products. The program codes 810 can be compressed in an appropriate form, for example.

[0163] Finally, it should be noted that the above embodiments are only used to illustrate but not limit the technical solutions of the present application; even though the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacements for some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A password management method characterized by, A password management module applied to a terminal device, the terminal device further comprising a target application program, the method comprising: receiving first warning information generated by a server, the first warning information being used to represent that a specified account of the target application program has a risk of password leakage; displaying the first warning information through a system pop-up window.

2. The method of claim 1, wherein, After the first warning information is displayed through the system pop-up window, the method further comprises: obtaining a corrected password in response to a password set by the target user for a specified password; detecting whether the corrected password matches a historical password of the specified account; if the corrected password matches the historical password of the specified account, prompting the target user to modify the specified password again, and returning to perform the operation of obtaining the corrected password in response to the password set by the target user for the specified password and subsequent operations until the currently obtained corrected password does not match the historical password of the specified account, and modifying the specified password to the current corrected password.

3. The method of claim 2, wherein, The detection of whether the corrected password matches the historical password of the specified account comprises: obtaining a first check value of the historical password; obtaining a second check value of the corrected password; if the first check value and the corresponding second check value satisfy a specified condition, it is determined that the corrected password matches the corresponding historical password, wherein the specified condition includes that there is a check value same as the second check value in the first check value; if the first check value and the corresponding second check value do not satisfy the specified condition, it is determined that the corrected password does not match the corresponding historical password.

4. The method of claim 3, wherein, The obtaining of the first check value of the historical password comprises: finding a standard check value corresponding to the historical password in a pre-obtained historical check list as the first check value of the historical password, wherein the historical check list comprises at least one historical password and a standard check value corresponding to each historical password.

5. The method of claim 2, wherein, The prompting of the target user to modify the specified password again, and the returning to perform the operation of obtaining the corrected password in response to the password set by the target user for the specified password and subsequent operations until the currently obtained corrected password does not match the historical password of the specified account, and the modifying of the specified password to the current corrected password, comprise: displaying an operation control; if the target user inputs an ignore identifier through the operation control, the specified password is modified to the corrected password, wherein the ignore identifier is used to represent that the user is stopped from being prompted to perform the modification operation again; if the target user does not input the ignore identifier through the operation control, the target user is prompted to modify the specified password again, and the operation of obtaining the corrected password in response to the password set by the target user for the specified password and subsequent operations are performed until the currently obtained corrected password does not match the historical password of the specified account, and the specified password is modified to the current corrected password.

6. The method of claim 2, wherein, Before the obtaining of the corrected password in response to the password set by the target user for the specified password, the method further comprises: displaying a specified page corresponding to the specified account, wherein the specified page is used to set a password.

7. The method of claim 1, wherein, After the first warning information is displayed through the system pop-up window, the method further comprises: In response to the target user's account and password input operation, an initial account and an initial password input by the target user are obtained; If there is a specified account identical to the initial account, the specified account identical to the initial account is taken as a target specified account; It is detected whether the initial password matches a target historical password, wherein the target historical password is a historical password of the target specified account; If the initial password matches the target historical password, second warning information is generated, wherein the second warning information is used to represent that the initial password has a risk of being leaked.

8. The method of claim 1, wherein, The receiving server generates first warning information, including: The target end forwards the first warning information generated by the service end, wherein the target end is used to receive and forward the first warning information generated by the service end.

9. The method of claim 7, wherein, The target end includes a target application program or a management server.

10. The method according to any one of claims 1 to 8, characterized in that, The first warning information includes identity information of a specified enterprise, a type of the specified enterprise, time information of a risk of password leakage, and processing suggestion information.

11. A password management apparatus characterized by comprising: A password management module applied to a terminal device, the terminal device further includes a target application program, and the device includes: A receiving unit is configured to receive first warning information generated by a service end, the first warning information being used to represent that a specified account of the target application program has a risk of password leakage; A prompting unit is configured to display the first warning information through a system pop-up window.

12. A password management system characterized by, The password management system includes a terminal device and a service end, the terminal device includes a password management module and a target application program, and the terminal device is connected with the service end; The password management module is configured to execute the password management method in any one of claims 1-9.

13. A computer-readable storage medium, characterized in that, The computer readable storage medium stores program code, and the program code can be called and executed by the processor to execute the method in any one of claims 1-9.

Images