CN112784254A

CN112784254A - Password management method and device, terminal equipment and storage medium

Info

Publication number: CN112784254A
Application number: CN202011584959.6A
Authority: CN
Inventors: 周军; 蒋洪琳
Original assignee: Shenzhen Hengxin Security Information Technology Co ltd
Current assignee: Shenzhen Hengxin Security Information Technology Co ltd
Priority date: 2020-12-28
Filing date: 2020-12-28
Publication date: 2021-05-11

Abstract

The application is applicable to the technical field of security, and provides a password management method, a device, a terminal device and a storage medium, wherein the password management method comprises the following steps: acquiring user authentication information, and determining user identity information based on the user authentication information; receiving an operation identifier sent by a host terminal; if the operation identification is a first type of operation, acquiring an account name to be managed sent by the host terminal, and generating a random password associated with the account name to be managed; sending the random password to the host terminal; and storing the account name to be managed and the random password in an account list corresponding to the user identity information in an associated manner. According to the password management method and device, when the password is set for the account, the corresponding random password can be generated and stored so as to be extracted and input to the host terminal in the following process, the random password is not easy to be known by others, and the problem that the password stored by the password management tool in the prior art still has the risk of being known by others is solved.

Description

Password management method and device, terminal equipment and storage medium

Technical Field

The present application belongs to the field of security technologies, and in particular, to a password management method, apparatus, terminal device, and storage medium.

Background

With the development of the internet, people have more and more accounts, such as electronic mailboxes, network games and various other software, and meanwhile, the security of the accounts is required to be higher and higher. Generally, people remember account numbers and passwords by themselves, which causes the contradiction between the password memorizing easiness and the security confidentiality.

In the prior art, a user stores various combinations of accounts and passwords in a password management tool to prevent the user from forgetting, and when the user needs to use the password management tool, the user can check the combinations of the accounts and the passwords stored in the tool only by remembering the account and the password of the password management tool. However, the method still has certain potential safety hazard and is not convenient to use.

Disclosure of Invention

The embodiment of the application provides a password management method, a password management device, terminal equipment and a storage medium, wherein a random password can be generated when a password is set for an account, and is stored in association with an account name of the account so as to be extracted and input to a host terminal in the following process, the random password is not easy to be known by others, and the problem that the password stored by a password management tool in the prior art still has the risk of being known by others is solved.

In a first aspect, an embodiment of the present application provides a password management method, including: acquiring user authentication information, and determining user identity information based on the user authentication information; receiving an operation identifier sent by a host terminal; if the operation identification is a first type of operation, acquiring an account name to be managed sent by the host terminal, and generating a random password associated with the account name to be managed; sending the random password to the host terminal so that the host terminal responds to the first type of operation based on the random password; storing the account name to be managed and the random password in an account list corresponding to the user identity information in an associated manner; the account list includes a plurality of account information, and the account information includes an account name and a password.

In a second aspect, an embodiment of the present application provides a password management apparatus, including: the user authentication module is used for acquiring user authentication information and determining user identity information based on the user authentication information; the operation identifier receiving module is used for receiving the operation identifier sent by the host terminal; a random password generation module, configured to, if the operation identifier is a first type of operation, obtain an account name to be managed sent by the host terminal, and generate a random password associated with the account name to be managed; a random password sending module, configured to send the random password to the host terminal, so that the host terminal responds to the first type of operation based on the random password; the account list management module is used for storing the account name to be managed and the random password in an account list corresponding to the user identity information in an associated manner; the account list includes a plurality of account information, and the account information includes an account name and a password.

In a third aspect, an embodiment of the present application provides a terminal device, including: a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the method of any of the above first aspects when executing the computer program.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, including: the computer readable storage medium stores a computer program which, when executed by a processor, implements the method of any of the first aspects described above.

In a fifth aspect, the present application provides a computer program product, which when run on a terminal device, causes the terminal device to execute the method of any one of the above first aspects.

It is understood that the beneficial effects of the second aspect to the fifth aspect can be referred to the related description of the first aspect, and are not described herein again.

Compared with the prior art, the embodiment of the application has the advantages that: compared with the prior art, the method provided by the application can generate the random password when the password is set for the account, and the random password is stored in association with the account name of the account so as to be extracted and input to the host terminal in the following process, the random password is not easy to be known by others, and the problem that the password stored by the password management tool in the prior art still has the risk of being known by others is solved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

FIG. 1 is a flowchart of an implementation of a password management method according to a first embodiment of the present application;

FIG. 2 is a schematic diagram of an application scenario provided in an embodiment of the present application;

FIG. 3 is a diagrammatic illustration of data interaction provided by an embodiment of the present application;

FIG. 4 is a flowchart of an implementation of a password management method according to a second embodiment of the present application;

FIG. 5 is a flowchart of an implementation of a password management method according to a third embodiment of the present application;

FIG. 6 is a flowchart of an implementation of a password management method according to a fourth embodiment of the present application;

FIG. 7 is a flowchart of an implementation of a password management method according to a fifth embodiment of the present application;

FIG. 8 is a flowchart of an implementation of a password management method according to a sixth embodiment of the present application;

FIG. 9 is a flowchart of an implementation of a password management method according to a seventh embodiment of the present application;

FIG. 10 is a schematic structural diagram of a password management apparatus according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".

Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.

In the embodiment of the present application, the main execution body of the flow is a terminal device. The terminal devices include but are not limited to: the password management method comprises the steps of enabling the server, the computer, the smart phone, the tablet computer and the like to execute the password management method. Preferably, the terminal device is a portable device, the terminal device is a device capable of establishing a communication connection with the host terminal to execute the password management method provided by the present application, and the portable device may be a plug-in exemplarily configured with a plug of a serial interface capable of connecting with the host terminal, and the plug is connected to the serial interface of the host terminal to establish a communication connection with the host terminal, in which case, the processor of the terminal device (i.e., the plug-in) may be a microprocessor. Fig. 1 shows a flowchart of an implementation of a password management method according to a first embodiment of the present application, which is detailed as follows:

in S101, user authentication information is acquired, and user identity information is determined based on the user authentication information.

In this embodiment, the user identity information is associated with the user authentication information. For example, the user identity information may be associated with a plurality of user authentication information at the same time, and the user identity information may be determined by acquiring one of the plurality of user authentication information.

In a possible implementation manner, the obtaining of the user authentication information and the determining of the user identity information based on the user authentication information may specifically be: acquiring a user fingerprint image through a fingerprint authentication component, and taking the user fingerprint image as the user authentication information; and taking the user fingerprint image as a query index, and querying and determining user identity information associated with the user fingerprint image in a database of the terminal equipment.

In another possible implementation manner, the obtaining of the user authentication information and the determining of the user identity information based on the user authentication information may specifically be: receiving a user identity password generated based on user operation through a user operation part, and taking the user identity password as the user authentication information; and taking the user identity password as a query index, and querying and determining user identity information associated with the user identity password in a database of the terminal equipment. The user operation part can be a key part or a touch screen; the key part may include five keys of up, down, left, right and confirmation; the touch screen may be a display touch screen, and correspondingly, the user identity password may be a graphical identity password, and the graphical identity password generated based on the user operation is received on the touch screen to determine the user identity information associated with the graphical identity password.

It should be understood that the above-mentioned obtaining of the user authentication information and determining the user identity information based on the user authentication information may also be implemented by voiceprint recognition, that is, determining the user identity information by user authentication information such as voiceprint, and detailed details are not repeated herein. Because the terminal device is often a device with lower processing capability, when processing a voiceprint, the processor of the host terminal can be used to send a voice signal to the host terminal, so that the host terminal generates a voiceprint identifier based on the voice signal, receives the voiceprint identifier, and queries user identity information corresponding to the voiceprint identifier. All the user authentication information described above do not constitute a limitation of the present embodiment.

In S102, the operation identifier transmitted by the host terminal is received.

In this embodiment, the operation identifier is used to identify various operation commands sent by the host terminal. Illustratively, the operation identifier is sent based on a user operation at the host terminal, or the operation identifier may be sent actively by the host terminal after a certain condition is met (for example, entering an interface for managing an account name and a password); the operation identifier may be a character string, and a character string table storing each operation identifier is provided in the terminal device.

It should be understood that the password management method provided in this embodiment is executed on the premise that the terminal device establishes a communication connection with the host terminal, and a specific means for establishing a communication connection may be a wired connection or a wireless connection, which is not limited herein. The host terminal should be installed with a driver program matching with the terminal device to execute the password management method provided by the embodiment. The driver can determine an application program running in a foreground on the host terminal, obtain an application program identifier and a page control indicated by an operation initiated by a user, determine an operation type based on the page control, and generate the operation identifier according to the application program identifier and the operation type and feed the operation identifier back to the terminal equipment. For example, the user may click a confirmation button on the host terminal, where the operation identifier of the driver is generated and sent, and then the driver generates the operation identifier and sends the operation identifier to the terminal device. It should be understood that the application identifier may be replaced by a web page address identifier, and specifically, the driver may determine a web page address in a browser program running in the foreground on the host terminal, to obtain the web page address identifier.

In S103, if the operation identifier is a first type of operation, acquiring the account name to be managed sent by the host terminal, and generating a random password associated with the account name to be managed.

In this embodiment, if the operation identifier is the first type of operation, it indicates that the user registers a new account in the host terminal and the user determines to generate a random password as the password of the new account, or the user modifies the password of an old account in the host terminal and the user determines to generate the random password as the new password of the old account.

Illustratively, a user registers a new account on the host terminal, specifically, the user inputs the account name to be managed on a new account registration interface on the host terminal, and operates the host terminal to send the operation identifier of the first type of operation to the terminal device, specifically, sends the operation identifier of the first type of operation to the terminal device through a driver associated with the terminal device in the host terminal.

Illustratively, a user modifies a password of an old account on the host terminal, specifically, the user enters an interface for inputting a new password after inputting the account name to be managed in an interface for inputting the old account on the host terminal, and operates the host terminal to send an operation identifier of the first type of operation to the terminal device, specifically, sends the operation identifier of the first type of operation to the terminal device through a driver associated with the terminal device in the host terminal.

In a possible implementation manner, the obtaining of the account name to be managed sent by the host terminal and generating the random password associated with the account name to be managed may specifically be: acquiring a new account name which is filled when a user registers a new account and is sent by the host terminal, or an account name of an old account of which a password is changed by the user, and identifying the new account name as the account name to be managed; generating a random password based on a random algorithm, and particularly, generating the random password based on the random algorithm by taking the account name to be managed as a parameter; the random password is associated with the account name to be managed.

It should be understood that, in general, random passwords associated with different account names to be managed are different, so that the situation that the passwords are set to be the same for each account name is avoided, and the passwords of all account names are broken when one password is broken.

In S104, the random password is sent to the host terminal, so that the host terminal responds to the first type of operation based on the random password.

In this embodiment, the sending the random password to the host terminal so that the host terminal responds to the first type of operation based on the random password may specifically be: and sending the random password to the host terminal so that the host terminal associates the random password with the account name to be managed and responds to the first type of operation, namely the host terminal registers a new account with the account name to be managed and the random password or the host terminal modifies the password of the account name to be managed by taking the random password as a new password.

In S105, the account name to be managed and the random password are stored in an account list corresponding to the user identity information in an associated manner.

In this embodiment, the account list includes a plurality of account information, and the account information includes an account name and a password. Illustratively, the account list is associated with the user identity information one to one. By way of example and not limitation, the account list may further include an account summary corresponding to the account information, where the account summary is used to prompt the user for details of the use of the account information, that is, to inform the user on which application or which web page the account information is used to log in.

In this embodiment, the associating and storing the account name to be managed and the random password in the account list corresponding to the user identity information may specifically be: and taking the account name to be managed as the account name of the newly-built account information, taking the random password as the password of the newly-built account information, and storing the newly-built account information into an account list corresponding to the user identity information.

It should be understood that in the prior art, part of the password has a certain service life, the password needs to be replaced regularly, and the repeated password before can not be used, so that the password memory is disordered; in such an application scenario, generally, the random passwords generated each time in this embodiment are different, so that the random passwords which need to be changed at regular time and cannot be repeated are met, and the random passwords are stored in the account list in the terminal device, so that confusion of password memory is avoided, and further, a third-party security risk caused by storing the passwords in the cloud server is also avoided.

In this embodiment, when receiving an operation identifier of a first type of operation from a host terminal, a random password may be generated and stored in association with the account name to be managed, so as to be subsequently extracted and input to the host terminal, and the random password is not easily known by others, thereby solving the problem that the password stored by the password management tool in the prior art still has a risk of being known by others.

Fig. 2 shows a schematic view of an application scenario provided in an embodiment of the present application. Referring to fig. 2, in the application scenario, on the host terminal, the user is registering a new account for the application, but the user needs to make the password of the new account registered at this time complicated enough and does not need to store the password by his own memory. Referring to fig. 2, the user inputs the account name to be managed in the application program on the host terminal, and leaves a blank password input box, and the user operation determines that the operation identifier for sending the first type of operation refers to the terminal device. At this time, by the password management method provided by the application, user authentication information, namely a fingerprint image, is acquired by the fingerprint authentication component, and user identity information is determined based on the fingerprint image, namely, the user performs identity authentication by a fingerprint, and the result of the identity authentication is displayed on the display screen; receiving an operation identifier sent by the host terminal; as shown in the figure, if the operation identifier is a first type of operation, acquiring the account name to be managed sent by the host terminal, and generating a random password associated with the account name to be managed; illustratively, at this time, the user can view the value of the random password according to the operation component, and further can choose to regenerate a new random password or determine to use the random password; sending the random password to the host terminal, namely inputting the random password into the password input box, so that a user can conveniently register a new account on the host terminal; and storing the account name to be managed and the random password in the terminal device in an associated manner, specifically, in an account list corresponding to the user identity information, so as to facilitate the subsequent extraction when the host terminal needs to input the account name to be managed and the random password.

FIG. 3 illustrates a data interaction diagram provided by an embodiment of the present application. Referring to fig. 3, in the application scenario illustrated in fig. 2, the data interaction of the password management method provided by the present application is as follows: after the terminal equipment completes identity authentication, the terminal equipment sends information that the identity authentication is successful to the host terminal; the host terminal sends the operation identifier of the first type of operation to the terminal equipment; the host terminal sends the account name to be managed to the terminal equipment; the terminal device sends the random password associated with the account name to be managed to the host terminal, so that the host terminal responds to the first type of operation based on the random password.

It should be understood that, the sending of the operation identifier of the first type of operation and the sending of the account name to be managed to the terminal device by the host terminal may be simultaneous, or may be sending the operation identifier of the first type of operation first and then sending the account name to be managed.

Fig. 4 shows a flowchart of an implementation of a password management method according to a second embodiment of the present application. Referring to fig. 4, with respect to the embodiment described in fig. 1, the password management method S102 provided in this embodiment further includes S401 to S403, which are detailed as follows:

further, after receiving the operation identifier sent by the host terminal, the method further includes:

in S401, if the operation identifier is a second type of operation, displaying an account list corresponding to the user identity information.

In this embodiment, if the operation identifier is the second type of operation, it indicates that the user is ready to log in an account in the host terminal, and needs to input an account name and a password, and the user determines to select the account name and the password to be input in the terminal device.

Illustratively, when the host terminal is at an interface of a login account, the user sends an operation identifier of a second type of operation to the terminal device through a driver associated with the terminal device in the host terminal, specifically, the driver displays a second type of operation confirmation button on the interface of the login account, and when the user clicks the second type of operation confirmation button, the host terminal sends the operation identifier of the second type of operation to the terminal device.

In a possible manner, the displaying of the account list corresponding to the user identity information may specifically be: inquiring an account list corresponding to the user identity information, and displaying the account list through a display part of the terminal equipment, specifically, displaying all account information in the account list one by one, wherein the display content comprises account names of all account information; illustratively, the display content may include an account summary of the account information; illustratively, the password to display the account information may be operated based on the user's query password.

In S402, first account information is selected from the account list based on a user operation.

In this embodiment, the first account information is determined based on the user operation. That is, the user selects the first account information from the account list while viewing the account list displayed by the display unit.

It should be understood that the user operation is generated by a user through operating an operating component of the terminal device, and the operating component may be a key component, a touch screen component, or a voice control component, which is not limited herein.

In a possible manner, the selecting the first account information from the account list based on the user operation may specifically be: after the display part displays each account information in the account list, user operation is received, and the account information selected by the user in the account list is determined based on the user operation and is identified as the first account information.

In S403, the first account information is sent to the host terminal, so that the host terminal responds to the second type of operation based on the first account information.

In this embodiment, the sending of the first account information to the host terminal so that the host terminal responds to the second type of operation based on the first account information may specifically be: and sending the account name and the password of the first account information to the host terminal so that the host terminal takes the account name and the password of the first account information as the account name and the password of the login account to respond to the second type of operation.

It should be understood that, in the password management method provided in the present embodiment, the terminal device corresponds to the input means of the host terminal, and inputs the account name and the password of the first account information into the host terminal.

In this embodiment, first account information is selected from the displayed account list based on a user operation, and the first account information is sent to the host terminal to respond to the second type of operation, that is, to respond to a login operation of the user on the host terminal.

Fig. 5 shows a flowchart of an implementation of a password management method according to a third embodiment of the present application. Referring to fig. 5, with respect to the embodiment described in fig. 1, the password management method S102 provided in this embodiment includes S501, which is detailed as follows:

in this embodiment, the account list further stores a scene identifier corresponding to each piece of account information in a correlated manner, that is, the account information in the account list corresponds to the scene identifier.

Further, the receiving the operation identifier sent by the host terminal includes:

in S501, the operation identifier sent by the host terminal and the scene identifier of the current usage scene are received.

In this embodiment, in addition to receiving the operation identifier sent by the host terminal, a scene identifier of a current usage scene is also received; the scenario identifier is used to identify a current operating environment of the host terminal, for example, a web page being browsed by the host terminal, or an application program being operated by the host terminal, and preferably the host terminal is in a login link (which may also be a registration link or a password modification link equal to a link related to account management) of the web page or the application program.

Illustratively, the host terminal registers a new account on the target web page, and if the user determines to generate a random password as the password of the new account, the operation identifier and the scenario identifier sent by the host terminal are accepted, where the operation identifier is the first type of operation identifier, and the scenario identifier is used to identify the target web page.

It should be understood that the scene identifier is generated by a driver related to the terminal device in the host terminal, and specifically, the driver may determine an application running in the foreground on the host terminal, so as to obtain an application identifier; the driver program can also determine the current webpage address of the browser program operated in the foreground on the host terminal to obtain a webpage address identifier; the scene identification may be the application identification or the web page address identification. In particular, when the driver obtains the scene identifier, an operation identifier may be generated based on the scene identifier and sent to the terminal device.

Further, the password management method S102 provided in this embodiment includes S502 to S504, that is, after receiving the operation identifier sent by the host terminal, the method further includes:

in S502, if the operation identifier is a second type of operation, a plurality of pieces of second account information associated with the scene identifier are selected from the account list and displayed.

In this embodiment, the account list is associated with the user identity information, and the detailed description of the second type of operation may refer to the related description in S401, which is not described herein again. The selecting and displaying of the second account information associated with the scene identifier from the account list may specifically be: and extracting the account list based on the user identity information, extracting all account information associated with the scene identifier in the account list, taking the account information as the second account information, and displaying the second account information through a display component.

In S503, target account information is selected from the second account information based on a user operation.

In this embodiment, the selecting of the target account information from the second account information based on the user operation may specifically be: and after the plurality of pieces of second account information are displayed, receiving user operation, and selecting target account information from the plurality of pieces of second account information displayed based on the user operation. For details of the user operation, reference may be made to the description of the above method embodiment, and details are not repeated herein.

In S504, the target account information is sent to the host terminal, so that the host terminal responds to the second type of operation based on the target account information.

In this embodiment, the sending the target account information to the host terminal so that the host terminal responds to the second type of operation based on the target account information may specifically be: and sending the account name and the password of the target account information to the host terminal so that the host terminal takes the account name and the password of the target account information as the account name and the password of a login account to respond to the second type of operation in the current use scene corresponding to the scene identification.

In this embodiment, by obtaining the scene identifier of the current usage scene, the account associated with the current usage scene can be extracted more accurately to complete the second type of operation, that is, the user is allowed to complete the login operation of the current usage scene on the host terminal.

Fig. 6 shows a flowchart of an implementation of a password management method according to a fourth embodiment of the present application. Referring to fig. 6, with respect to the embodiment described in fig. 5, S501 of the password management method provided in this embodiment includes S601 to S602, which are detailed as follows:

further, after receiving the operation identifier sent by the host terminal and the scene identifier of the current usage scene, the method further includes:

in S601, if the operation identifier is a third type of operation, the to-be-stored account information sent by the host terminal is received.

In this embodiment, the information of the account to be saved includes a name of the account to be saved and a password to be saved.

In this embodiment, if the operation identifier is the third type of operation, it indicates that the user saves the account name and the password input in the current usage scenario of the host terminal, and determines to save to the terminal device.

For example, after a user inputs an account name and a password in a current usage scenario of the host terminal, the user sends an operation identifier of the third type of operation to the terminal device through a driver associated with the terminal device in the host terminal, specifically, the driver implants a confirmation button for storing the current account name and the password in the current usage scenario of the host terminal, and when the user clicks the confirmation button, the host terminal sends the operation identifier of the third type of operation to the terminal device.

For example, when a user inputs an account name and a password in a current usage scenario of the host terminal and logs in an account with the account name and the password, the driver asks the user whether to save the current account name and the password, specifically, the driver pops up a popup window to allow the user to select whether to save the current account name and the password, and when the user selects to save the current account name and the password, the host terminal sends the operation identifier of the third type of operation to the terminal device.

In a possible implementation manner, the receiving of the to-be-stored account information sent by the host terminal may specifically be: and receiving the account and the password of the host terminal in the current use scene, namely the account name to be saved and the password to be saved, and packaging the account name to be saved and the password to be saved into the account information to be saved.

In S602, the to-be-saved account information and the scene identifier are stored in an account list corresponding to the user identity information in an associated manner.

In this embodiment, the associating and storing the to-be-saved account information and the scene identifier in the account list corresponding to the user identity information may specifically be: and associating the account information to be stored with the scene identification, and storing the account information to be stored in an account list corresponding to the user identity information, namely the account information to be stored corresponds to the scene identification. It should be understood that the scene identifier may be used as a basis for generating an account summary of the account information when the account information is displayed, and as a reference for selecting the second account information from the account list when the second account information is displayed.

In this embodiment, an account name and a password of the current usage scenario of the host terminal are stored through user operation, so as to extract the account name and the password and send the extracted account name and password to the host terminal for login operation in the current usage scenario.

Fig. 7 shows a flowchart of an implementation of a password management method according to a fifth embodiment of the present application. Referring to fig. 7, with respect to the embodiment described in fig. 1, the password management method S102 provided in this embodiment includes S701 to S702, which are detailed as follows:

in this embodiment, the password in the account information includes an original password configured by the user and a random password corresponding to the original password. In order to increase the complexity of the password in the account information, the random password is used as the effective password of the account information, and the original password is used as the matching password of the account information, at this time, even if the original password is known, the random password cannot be known under the condition of being separated from the terminal equipment or the condition that the terminal equipment cannot pass identity authentication, and the account corresponding to the account information is logged in other terminals.

in S701, if the operation identifier is a second type of operation, receiving a password to be recognized sent by the host terminal, and matching the password to be recognized with the original password.

In this embodiment, the detailed description of the second type of operation may refer to the related description in S401, and is not repeated herein. The receiving of the password to be identified sent by the host terminal and the matching of the password to be identified and the original password may specifically be: after the operation identifier is determined to be the second type of operation, sending a simple password input request to the host terminal (an application program corresponding to the terminal device) so as to receive a simple password input by a user on the host terminal, namely the password to be identified; after receiving the password to be identified, querying an original password matched with the password to be identified, specifically querying an original password having the same value as the password to be identified, that is, querying whether account information corresponding to the original password is stored in the account list corresponding to the identity information by using the password to be identified as the original password.

In S702, if the password to be identified is successfully matched with the original password, the random password corresponding to the original password is sent to the host terminal, so that the host terminal responds to the second type of operation based on the random password.

In this embodiment, if the password to be identified is successfully matched with the original password, it indicates that the password to be identified is used as the original password, and the account list corresponding to the identity information stores account information corresponding to the original password. The sending of the random password corresponding to the original password to the host terminal so that the host terminal responds to the second type of operation based on the random password may specifically be: and extracting a random password corresponding to the original password, and sending the random password to the host terminal so that the host terminal responds to the second type of operation by taking the random password as the password of the login account. It will be appreciated that the host terminal is arranged to respond to the second type of operation as the account name for the login account is derived from user input.

In this embodiment, the random password is used as a valid password of the account information, the original password is used as a matching password of the account information, when an operation identifier of a second type of operation is obtained, the password to be recognized sent by the host terminal is received, the original password matching the password to be recognized is acquired, and the random password corresponding to the original password is sent to the host terminal, so that the host terminal responds to the second type of operation. In this case, the complexity of the password in the account information is increased, and even if the original password is known, the random password cannot be known to log in the account corresponding to the account information on another terminal when the terminal device is detached or when the terminal device cannot pass the authentication.

Fig. 8 shows a flowchart of an implementation of a password management method according to a sixth embodiment of the present application. Referring to fig. 8, with respect to any of the above embodiments, the password management method provided in this embodiment further includes S801 to S803, which are detailed as follows:

further, the password management method further includes:

in S801, if the operation identifier is a fourth type of operation, a backup password of the user is acquired.

In this embodiment, if the operation identifier is the fourth type of operation, the operation identifier indicates that a user performs an account backup operation on the host terminal, and the account backup operation refers to backing up all account information in the terminal device.

In a possible implementation manner, the obtaining of the backup password of the user may specifically be: and receiving the backup password sent by the user on the host terminal. In another possible implementation manner, the obtaining of the backup password of the user may specifically be: acquiring user operation of a user on an operation part of the terminal equipment, and generating the backup password based on the user operation; or, the backup password is generated based on the user authentication information.

It should be understood that, the above detailed description of the operation component and the user authentication information may refer to the related description of the above method embodiment, and will not be described herein again.

In S802, the backup password is used as a key to encrypt and package the user identity information and the account list corresponding to the user identity information, so as to generate a backup file.

In this embodiment, the encrypting and packaging the user identity information and the account list corresponding to the user identity information with the backup password as the key to generate the backup file specifically may be: and packaging all the user identity information in the terminal equipment and the account list corresponding to the user identity information, and encrypting by taking the backup password as a key to generate a backup file. The encryption algorithm described above that encrypts with the backup password as a key may be, for example, a KDF encryption algorithm.

In S803, the backup file is sent to the host terminal or uploaded to a server.

In this embodiment, the backup file is sent to the host terminal, so that other terminal devices except the subsequent terminal device are connected to the host terminal, the backup password is input to the other terminal devices, and all user identity information corresponding to the backup file and an account list (i.e., all account information) corresponding to the user identity information are obtained; and sending the backup file to the server so as to lead the backup file to other host terminals, so that any terminal equipment can be connected with the other host terminals through the backup password to acquire the backup file.

In this embodiment, the stored data in the terminal device is encrypted by the backup password to generate a backup file, so as to implement the functions of data transfer and backup.

Fig. 9 shows a flowchart of an implementation of a password management method according to a seventh embodiment of the present application. Referring to fig. 9, in comparison with any one of the first to fifth embodiments, the password management method S103 provided by this embodiment includes S1031 to S1033, which are detailed as follows:

further, if the operation identifier is a first type of operation, acquiring the account name to be managed sent by the host terminal, and generating a random password associated with the account name to be managed, including:

in S1031, a rule collecting instruction is sent to the host terminal.

In this embodiment, the rule collecting instruction is used to instruct the user to determine password rule information generated by the random password on the host terminal, that is, the rule collecting instruction is sent to the host terminal, so that the user determines the password rule information generated by the random password on the host terminal, so as to generate the random password later.

In S1032, password rule information fed back by the host terminal based on the rule acquisition instruction is received.

In this embodiment, password rule information fed back by the host terminal based on the rule collecting instruction sent in the above S1031 is received, where the password rule information may be one of candidate password rule information selected by the user in the plurality of candidate password rule information in the display interface of the host terminal.

In S1033, the random password is generated according to a preset random generation algorithm and the password rule information.

In a possible implementation manner, the generating the random password according to a preset random generation algorithm and the password rule information may specifically be: and determining algorithm parameters based on the random generation algorithm based on the password rule information, and generating the random password according to the algorithm parameters and the random generation algorithm. Illustratively, based on the password rule information, the algorithm parameter of the random generation algorithm may be determined to be the user ID in the user identity information, or the above-mentioned account name to be managed, or the current system time.

In this embodiment, when a password is set for an account, the random password may be generated according to a preset random generation algorithm and the password rule information, and stored in association with the account name of the account, so as to be subsequently extracted and input to the host terminal.

Fig. 10 shows a schematic structural diagram of an apparatus provided in an embodiment of the present application, corresponding to the method described in the above embodiment, and only shows a part related to the embodiment of the present application for convenience of description.

Referring to fig. 10, the password management apparatus includes: the user authentication module is used for acquiring user authentication information and determining user identity information based on the user authentication information; the operation identifier receiving module is used for receiving the operation identifier sent by the host terminal; a random password generation module, configured to, if the operation identifier is a first type of operation, obtain an account name to be managed sent by the host terminal, and generate a random password associated with the account name to be managed; a random password sending module, configured to send the random password to the host terminal, so that the host terminal responds to the first type of operation based on the random password; the account list management module is used for storing the account name to be managed and the random password in an account list corresponding to the user identity information in an associated manner; the account list includes a plurality of account information, and the account information includes an account name and a password.

Optionally, the password management apparatus further includes: the account list display module is used for displaying an account list corresponding to the user identity information if the operation identifier is a second type of operation; the first account information selecting module is used for selecting first account information from the account list based on user operation; and the first account information sending module is used for sending the first account information to the host terminal so that the host terminal can respond to the second operation based on the first account information.

Optionally, the account list further stores a scene identifier corresponding to each piece of account information in an associated manner; the operation identifier receiving module also comprises a scene identifier receiving module used for receiving the scene identifier of the current use scene sent by the host terminal; the password management apparatus further includes: the second account information display module is used for selecting and displaying a plurality of pieces of second account information associated with the scene identifier from the account list if the operation identifier is a second type of operation; the target account information selecting module is used for selecting target account information from the second account information based on user operation; and the target account information sending module is used for sending the target account information to the host terminal so that the host terminal can respond to the second type of operation based on the target account information.

Optionally, the password management apparatus further includes: the account information to be saved receiving module is used for receiving the account information to be saved sent by the host terminal if the operation identifier is the third type of operation; the account information to be stored comprises an account name to be stored and a password to be stored; and the account information to be saved storage module is used for storing the account information to be saved and the scene identification in an account list corresponding to the user identity information in a correlation mode.

Optionally, the password management apparatus further includes: the password in the account information comprises an original password configured by a user and a random password corresponding to the original password; the password matching module to be recognized is used for receiving the password to be recognized sent by the host terminal and matching the password to be recognized with the original password if the operation identifier is the second type of operation; the random password sending module is further configured to send the random password corresponding to the original password to the host terminal if the password to be identified is successfully matched with the original password, so that the host terminal responds to the second type of operation based on the random password.

Optionally, the password management apparatus further includes: the backup password acquisition module is used for acquiring a backup password of the user if the operation identifier is the fourth type of operation; the backup file generation module is used for encrypting and packaging the user identity information and the account list corresponding to the user identity information by taking the backup password as a key to generate a backup file; and the backup file sending module is used for sending the backup file to the host terminal or uploading the backup file to a server.

Optionally, the random password generating module further includes: the rule acquisition instruction sending module is used for sending a rule acquisition instruction to the host terminal; the password rule information receiving module is used for receiving password rule information fed back by the host terminal based on the rule acquisition instruction; and the random generation algorithm module is used for generating the random password according to a preset random generation algorithm and the password rule information.

It should be noted that, for the information interaction, the execution process, and other contents between the above-mentioned apparatuses, the specific functions and the technical effects of the embodiments of the method of the present application are based on the same concept, and specific reference may be made to the section of the embodiments of the method, which is not described herein again.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

Fig. 11 shows a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in fig. 11, the terminal device 11 of this embodiment includes: at least one processor 110 (only one processor is shown in fig. 11), a memory 111, and a computer program 112 stored in the memory 111 and executable on the at least one processor 110, the steps of any of the various method embodiments described above being implemented when the computer program 112 is executed by the processor 110.

The terminal device 11 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal device may include, but is not limited to, a processor 110, a memory 111. Those skilled in the art will appreciate that fig. 11 is only an example of the terminal device 11, and does not constitute a limitation to the terminal device 11, and may include more or less components than those shown, or combine some components, or different components, for example, and may further include an input/output device, a network access device, and the like.

The Processor 110 may be a Central Processing Unit (CPU), and the Processor 110 may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The storage 111 may in some embodiments be an internal storage unit of the terminal device 11, such as a hard disk or a memory of the terminal device 11. In other embodiments, the memory 111 may also be an external storage device of the terminal device 11, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the terminal device 11. Further, the memory 111 may also include both an internal storage unit and an external storage device of the terminal device 11. The memory 111 is used for storing an operating system, an application program, a BootLoader (BootLoader), data, and other programs, such as program codes of the computer programs. The memory 111 may also be used to temporarily store data that has been output or is to be output.

The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps in the above-mentioned method embodiments.

The embodiments of the present application provide a computer program product, which when running on a mobile terminal, enables the mobile terminal to implement the steps in the above method embodiments when executed.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims

1. A method of password management, comprising:

acquiring user authentication information, and determining user identity information based on the user authentication information;

receiving an operation identifier sent by a host terminal;

if the operation identification is a first type of operation, acquiring an account name to be managed sent by the host terminal, and generating a random password associated with the account name to be managed;

sending the random password to the host terminal so that the host terminal responds to the first type of operation based on the random password;

storing the account name to be managed and the random password in an account list corresponding to the user identity information in an associated manner; the account list includes a plurality of account information, and the account information includes an account name and a password.

2. The password management method according to claim 1, further comprising, after receiving the operation identification transmitted from the host terminal:

if the operation identification is a second type of operation, displaying an account list corresponding to the user identity information;

selecting first account information from the account list based on user operation;

and sending the first account information to the host terminal so that the host terminal responds to the second type of operation based on the first account information.

3. The password management method according to claim 1, wherein the account list further stores a scene identifier corresponding to each of the account information in association with the account list; the receiving the operation identifier sent by the host terminal comprises:

receiving an operation identifier sent by the host terminal and a scene identifier of a current use scene;

after receiving the operation identifier sent by the host terminal, the method further includes:

if the operation identifier is a second type of operation, selecting and displaying a plurality of pieces of second account information associated with the scene identifier from the account list;

selecting target account information from the second account information based on user operation;

and sending the target account information to the host terminal so that the host terminal responds to the second type of operation based on the target account information.

4. The password management method according to claim 3, further comprising, after said receiving the operation identifier sent by the host terminal and the scene identifier of the current usage scene:

if the operation identifier is a third type of operation, receiving account information to be stored sent by the host terminal; the account information to be stored comprises an account name to be stored and a password to be stored;

and storing the information of the account to be stored and the scene identification in an account list corresponding to the user identity information in a correlation manner.

5. The password management method of claim 1, wherein the password in the account information comprises an original password configured by the user and a random password corresponding to the original password; after receiving the operation identifier sent by the host terminal, the method further includes:

if the operation identification is the second type of operation, receiving a password to be identified sent by the host terminal, and matching the password to be identified with the original password;

and if the password to be identified is successfully matched with the original password, sending the random password corresponding to the original password to the host terminal so that the host terminal responds to the second type of operation based on the random password.

6. The password management method according to any one of claims 1 to 5, wherein the password management method further comprises:

if the operation identification is the fourth type of operation, acquiring a backup password of the user;

taking the backup password as a key, encrypting and packaging the user identity information and an account list corresponding to the user identity information to generate a backup file;

and sending the backup file to the host terminal or uploading the backup file to a server.

7. The password management method according to any one of claims 1 to 5, wherein if the operation identifier is a first type of operation, acquiring an account name to be managed sent by the host terminal, and generating a random password associated with the account name to be managed, comprises:

sending a rule acquisition instruction to the host terminal;

receiving password rule information fed back by the host terminal based on the rule acquisition instruction;

and generating the random password according to a preset random generation algorithm and the password rule information.

8. A password management device is characterized by comprising

The user authentication module is used for acquiring user authentication information and determining user identity information based on the user authentication information;

the operation identifier receiving module is used for receiving the operation identifier sent by the host terminal;

a random password generation module, configured to, if the operation identifier is a first type of operation, obtain an account name to be managed sent by the host terminal, and generate a random password associated with the account name to be managed;

a random password sending module, configured to send the random password to the host terminal, so that the host terminal responds to the first type of operation based on the random password;

the account list management module is used for storing the account name to be managed and the random password in an account list corresponding to the user identity information in an associated manner; the account list includes a plurality of account information, and the account information includes an account name and a password.

9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.