Account information management method and device, electronic equipment and storage medium
By completely deleting the account information when deleting the user account in the operating system and adding the created identified information, the security risks of the account creation are solved, and the security of the system is improved.
Patent Information
- Application Number
- CN202411533027.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-30
- Publication Date
- 2025-03-18
AI Technical Summary
After deleting user accounts, the existing operating system cannot effectively prevent the account from being created again, resulting in security risks.
When deleting a user account, completely delete the account information in the basic file directory, and add the created identified information to the target file. The configuration base file directory refuses to create a user account that matches the created identified information again.
Ensure that the account information is completely deleted, reduce the chance of account creation again, improve the security of the operating system, and prevent deleted accounts from being reused or modified system files.
Smart Images
Figure CN119646801A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to an account information management method, device, electronic device and computer-readable storage medium. Background Art
[0002] Account information management is one of the basic functions of the operating system. Account information management supports actions such as account creation and deletion.
[0003] Currently, when the operating system manages account information, for deleting an account, the account information in the directory can be deleted; and for creating an account, the account information can be added to the directory by entering the account information, thereby realizing the creation of the account.
[0004] However, in the current solution, deleted accounts can be created and used again, which may cause security risks to the operating system. Summary of the invention
[0005] The embodiments of the present application provide a method and device for managing account information to solve the problems in the prior art.
[0006] In a first aspect, an embodiment of the present application provides a method for managing account information, the method comprising:
[0007] In response to a deletion operation on the first user account, deleting the account information of the first user account in the basic file directory;
[0008] After the deletion is completed, adding the created identification information of the first user account to the target file in the basic file directory;
[0009] The basic file directory is configured to refuse to re-create a user account that matches the created identification information in the target file.
[0010] In a second aspect, an embodiment of the present application provides a device for managing account information, the device comprising:
[0011] a deleting module, configured to delete the account information of the first user account in the basic file directory in response to a deletion operation on the first user account;
[0012] a recording module, configured to add the created identification information of the first user account to the target file in the basic file directory after the deletion is completed;
[0013] The basic file directory is configured to refuse to re-create a user account that matches the created identification information in the target file.
[0014] In a third aspect, an embodiment of the present application further provides an electronic device, including a processor;
[0015] a memory for storing instructions executable by the processor;
[0016] The processor is configured to execute the instructions to implement the method of the first aspect.
[0017] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, which, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, enables the electronic device to execute the method of the first aspect.
[0018] In an embodiment of the present application, in response to a deletion operation on a first user account, the account information of the first user account in the basic file directory can be deleted, and after the deletion is completed, the created identification information of the first user account is added to the target file of the basic file directory; the basic file directory is configured to refuse to re-create a user account that matches the created identification information in the target file. In an embodiment of the present application, the deletion operation can ensure that the account information corresponding to the first user account in the basic file directory is completely deleted, avoiding leaving the legacy information of the first user account, thereby reducing the probability of the relevant user creating the first user account again. In addition, by configuring the created identification information, when the user account created subsequently matches the created identification information, the user account is considered to be an account that has been created, thereby refusing to create the user account. In this way, it is possible to prevent relevant personnel from logging into the operating system or modifying operating system files by re-creating a deleted user account, thereby providing a security guarantee for the operating system.
[0019] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] Figure 1 It is a flowchart of the steps of a method for managing account information provided by an embodiment of the present application;
[0021] Figure 2 It is a flowchart of the specific steps of an account information management method provided by an embodiment of the present application;
[0022] Figure 3 This is an account deletion flow chart provided by an embodiment of the present application;
[0023] Figure 4This is an account creation flow chart provided in the embodiment of the present application.
[0024] Figure 5 It is a block diagram of an account information management device provided in an embodiment of the present application;
[0025] Figure 6 is a block diagram of an apparatus of the present application;
[0026] Figure 7 It is a schematic diagram of the structure of the server in some embodiments of the present application. DETAILED DESCRIPTION
[0027] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0028] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally a class, and the number of objects is not limited. For example, the first object can be one or more. In addition, the term "and / or" in the specification and claims is used to describe the association relationship of associated objects, indicating that three kinds of relationships can exist, for example, A and / or B can be represented: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the front and back associated objects are a kind of "or" relationship. In the embodiment of the present application, the term "multiple" refers to two or more, and other quantifiers are similar.
[0029] Figure 1 , is a flowchart of a method for managing account information provided by an embodiment of the present application, such as Figure 1 As shown, the method may include:
[0030] Step 101: In response to a deletion operation on a first user account, the account information of the first user account in the basic file directory is deleted.
[0031] In an embodiment of the present application, an account management application may be installed in the electronic device to implement the management of the operating system accounts. For example, in a Linux operating system scenario, the account management application may be a shadow-utils program. The shadow-utils program is used to manage accounts and shadow password files. The installation package of shadow-utils includes: a program required to convert a password file into a password format supported by shadow-utils, and a program for managing user and group accounts.
[0032] Specifically, the account management application creates an account through a create command (useradd) and deletes an account through a delete command (userdel). In addition, the account management application also maintains a basic file directory, which is used to store account information. The delete command initiated for the first user account can delete the account information of the first user account under the basic file directory.
[0033] For example, for the shadow-utils program of the Linux operating system, for the created test account, the basic file directories maintained by the shadow-utils program include:
[0034] The " / home / test" folder stores the basic account information of the test account;
[0035] The " / var / spool / mail / test" file contains the identification information of the test account;
[0036] " / etc / group" file, which stores the account group information of the test account;
[0037] The " / etc / passwd" file contains the password information of the test account.
[0038] In response to a deletion operation on a first user account (such as a test account), the embodiment of the present application can completely delete the account information corresponding to the first user account (such as a test account) in the basic file directory (including basic account information, identification information, account group information, password information, etc. of the test account), thereby ensuring that after the deletion, there is no legacy information of the first user account in the basic file directory.
[0039] In the related art, when deleting an account using a delete command, all the account information of the account is often not completely deleted, resulting in the existence of the account's legacy information in the basic file directory after the account is deleted. The existence of the legacy information may cause relevant personnel to use the legacy information to try to repair the account and make some system modifications by changing the account, thus causing huge hidden dangers in the system.
[0040] In addition, in the account management of the operating system, if a deleted account can be recreated, it is also a major hidden danger for operating systems with high security requirements. Therefore, the embodiment of the present application aims to implement a method for managing account information, which is used to prevent relevant personnel from using the remaining information of a deleted account to log in to the operating system or modify the operating system files by recreating the account, thereby providing a security guarantee for the operating system.
[0041] Specifically, in this step, the embodiment of the present application can use a deletion instruction to mark all account information related to the first user account to be deleted in the basic file directory, thereby ensuring that the account information corresponding to the first user account in the basic file directory is completely deleted to avoid leaving any legacy information of the first user account. This can greatly reduce the probability of the relevant user creating the first user account again.
[0042] Step 102: After the deletion is completed, add the created identification information of the first user account to the target file in the basic file directory.
[0043] The basic file directory is configured to refuse to re-create a user account that matches the created identification information in the target file.
[0044] In the embodiment of the present application, after the deletion is completed, the legacy information of the first user account no longer exists in the basic file directory. In order to ensure that the relevant personnel cannot use other means to create the first user account again in the future, the embodiment of the present application can add the created identification information of the first user account to the target file in the basic file directory. Specifically, for the above example, the basic file directory may have a target file " / etc / passwd". The embodiment of the present application can add the created identification information of the first user account to the target file " / etc / passwd". The created identification information records the name, identifier and other information of the first user account, and the basic file directory is configured to refuse to create a user account that matches the created identification information in the target file again. In this way, when the account management application creates a new account later, if the name and identifier of the newly created account match the name and identifier of the created identification information in the target file, the new account is considered to be an account that has been created. In order to avoid repeated account creation, the account management application can refuse to create the new account. In this way, it can be prevented that the relevant personnel log in to the operating system or modify the operating system files by recreating the deleted account, thereby providing a security guarantee for the operating system.
[0045] In summary, in response to the deletion operation on the first user account, the embodiment of the present application can delete the account information of the first user account in the basic file directory, and after the deletion is completed, add the created identification information of the first user account to the target file of the basic file directory; the basic file directory is configured to refuse to re-create a user account that matches the created identification information in the target file. In the embodiment of the present application, the deletion operation can ensure that the account information corresponding to the first user account in the basic file directory is completely deleted, avoiding leaving the legacy information of the first user account, thereby reducing the probability of the relevant user creating the first user account again. In addition, by configuring the created identification information, when the user account created subsequently matches the created identification information, the user account is considered to be an account that has been created, thereby refusing to create the user account. In this way, it is possible to prevent relevant personnel from logging into the operating system or modifying operating system files by re-creating a user account that has been deleted, thereby providing a security guarantee for the operating system.
[0046] Figure 2 is a flowchart of the specific steps of an account information management method provided in an embodiment of the present application, such as Figure 2 As shown, the method may include:
[0047] Step 201: In response to a deletion operation on a first user account, the account information of the first user account in the basic file directory is deleted.
[0048] This step may specifically refer to the above step 101, which will not be described in detail here.
[0049] Optionally, the basic file directory includes an identification directory file, and the identification directory file is used to record identification information of the created user account; step 201 may specifically include sub-step 211:
[0050] Sub-step 2011: In response to a deletion operation on a first user account, if identification information of the first user account is found in the identification directory file, the account information of the first user account in the basic file directory is deleted.
[0051] In an embodiment of the present application, the basic file directory may include an identification directory file " / var / spool / mail / test", and the identification directory file records the identification information of the created user account. For example, assuming that the test account is a created account, the identification information of the test account (including the account identification and the identification of the account group to which the account belongs) may be added to the identification directory file " / var / spool / mail / test". Based on the above-mentioned maintenance method for the identification directory file " / var / spool / mail / test", when deleting the first user account later, it is possible to first query whether the identification information of the first user account exists in the identification directory file " / var / spool / mail / test". If the first user account is found, it is determined that the first user account exists in the current account management application, and the account information of the first user account in the basic file directory is deleted. If the first user account is not found, it is determined that the first user account does not exist in the current account management application, and a prompt message is displayed to prompt the user that the first user account does not currently exist and the deletion operation cannot be performed.
[0052] Optionally, step 201 may specifically include sub-steps 2012-2013:
[0053] Sub-step 2012: calling the native deletion instruction of the account system to delete the basic account information in the account information of the first user account in the basic file directory.
[0054] Sub-step 2013: calling the automatic increase and deletion instruction of the account system, and deleting the remaining account information of the first user account except the basic account information in the basic file directory.
[0055] In the embodiment of the present application, for sub-steps 2122-2123, the account system may have a native deletion instruction, which identifies the information (basic account information) that needs to be deleted by default when deleting a user account. However, the native deletion instruction often cannot delete all account information of the user account, resulting in the existence of residual information after deletion. Therefore, the embodiment of the present application can implement a self-increment deletion instruction, which can be used to delete the remaining account information in the account information of the first user account in the basic file directory except the basic account information.
[0056] Specifically, when executing the deletion operation of the first user account, the embodiment of the present application may first call the native deletion command of the account system to delete the basic account information in the account information of the first user account in the basic file directory. Then, the self-increment deletion command of the account system is called to delete the remaining account information in the account information of the first user account except the basic account information, so as to ensure that after the deletion, there is no remaining information of the first user account in the basic file directory, thereby preventing relevant personnel from using the remaining information of the deleted account to log in to the operating system or modify the operating system files by re-creating the account, thereby improving the security of the system.
[0057] Step 202: after the deletion is completed, generating the created identification information of the first user account according to the account name, account identifier and account group identifier of the first user account and adding it to the password directory file;
[0058] Among them, the target file is a password directory file; the created identification information includes a first field recording the account name, and a second field recording the account ID and the account group ID; the first field is used to indicate that a user account with the account name cannot be created again; the second field is used to indicate that a user account with the account ID and the account group ID cannot be created again.
[0059] In an embodiment of the present application, the account name of the user account reflects the name of the user account; the account identifier of the user account can be a unique identifier used to distinguish different user accounts, and the account group identifier of the user account reflects the account group to which the user account belongs.
[0060] In the account management of the operating system, if a deleted account can be created again, it will also be a major hidden danger for an operating system with higher security. This specifically means that for the sake of system security, the account system of the embodiment of the present application does not allow a user account with the same account name, the same account ID, and the same account group ID to be created again after deletion. This can prevent relevant personnel from logging into the operating system or modifying the operating system files by re-creating the account, thereby providing a security guarantee for the operating system.
[0061] Specifically, after completing the deletion of the account information of the first user account, the embodiment of the present application can generate the created identification information of the first user account according to the account name, account ID and account group ID of the first user account and add it to the password directory file, wherein the created identification information includes a first field recording the account name and a second field recording the account ID and the account group ID; the first field is used to indicate that the user account with the account name cannot be created again; the second field is used to indicate that the user account with the account ID and the account group ID cannot be created again.
[0062] In this way, when the account system subsequently creates a new account, if any of the account name, account ID, and account group ID of the newly created account matches the content recorded in the created identification information, the new account is considered to be an account that has been created. In order to avoid the repeated creation of deleted accounts, the account management application can refuse to create the new account. In this way, it can be avoided that relevant personnel log in to the operating system or modify the operating system files by re-creating a deleted account, thereby providing a security guarantee for the operating system. In addition, avoiding the repeated creation of deleted accounts can also prevent the deleted user account ID from combining with the deleted user name to access the kernel function in the case of a user account ID vulnerability in the kernel, thereby preventing the problem of cracking the operating system, which can reduce the probability of causing system abnormalities.
[0063] For example, for the test user account, assuming that the account ID of the test user account is 1001 and the account group ID is 1001, the generated created identification information may be "test_del_tmp:x:1001:1001", wherein the first field "test_del_tmp" indicates that the user account with the account name of test cannot be created again, and the second field "1001:1001" indicates that the user account with the account ID 1001 and the account group ID 1001 is created again. That is, the test user account cannot be created again subsequently.
[0064] It should be noted that, preferably, the target file is the password directory file " / etc / passwd". Of course, the target file can also be other files in the basic file directory, such as " / etc / group" file, " / var / spool / mail / test" file, etc. This embodiment of the application does not limit this.
[0065] In summary, for the deletion process of a user account in the account system, you can refer to Figure 3 Taking deleting the test user account as an example, the deletion process includes:
[0066] S1. Trigger the command to delete the test user account.
[0067] S2. Check whether there is a test user account in " / var / spool / mail / test".
[0068] If S3 and the test user account exist, execute S4 and delete the account information of the test user account in the basic file directory.
[0069] S6. If the test user account does not exist, the execution ends.
[0070] After S4 is executed, S5 is executed to write the created identification information of the test user account into the " / etc / passwd" file.
[0071] After S5 is executed, the execution ends.
[0072] Optionally, the method may further include:
[0073] Step 203: When creating a second user account, if it is detected that the record information of the second user account is not recorded in the preset record file directory, and the created identification information of the second user account does not exist in the target file, the account information of the second user account is added to the basic file directory, and the record information of the second user account is added to the record file directory, and the record file directory is configured to not open access rights to external users.
[0074] In the embodiment of the present application, the account management application can implement an account system and support an account creation function. In addition, the account management application can maintain a record file directory, and the record file directory can record the information of the created user account in a preset manner. When creating a user account later, it can be determined whether the user account to be created has been created before by searching whether the information of the user account to be created exists in the record file directory, that is, when the information of the user account to be created exists in the record file directory, it is determined that the user account to be created has been created before.
[0075] In addition, the basic file directory maintained by the account management application may have a target file. In the embodiment of the present application, the created identification information of the deleted user account may be added to the target file. The created identification information is used to indicate that the corresponding user account has been deleted. In this way, when the account management application subsequently creates a new account, if the information of the newly created account matches the created identification information in the target file, the new account is considered to be an account that has been created and deleted. In order to avoid repeated account creation, the account management application may refuse to create the new account. In this way, it is possible to prevent relevant personnel from logging into the operating system or modifying operating system files by recreating a deleted account.
[0076] Specifically, based on the above design, when creating a second user account, the account management application of the embodiment of the present application can first query in the record file directory and the target file. If it is detected that there is no record information of the second user account in the record file directory, and the created identification information of the second user account does not exist in the target file, it is determined that the second user account is not a user account that has been created or deleted, which meets the security requirements of the account system of the embodiment of the present application. At this time, the account management application can add the account information of the second user account in the basic file directory and add the record information of the second user account in the record file directory. Among them, adding the account information of the second user account in the basic file directory is used to realize the persistent storage of the information of the second user account. The account information of the second user account can be entered by the user through a visual interface. The account information includes identity information such as account number, password, identification information, account group information, etc. In addition, adding the record information of the second user account in the record file directory is used to characterize that the second user account is a created user account.
[0077] It should be noted that the log file directory is configured to not open access rights to external users. Therefore, external users cannot see and tamper with the information in the log file directory, which improves the security of the account system.
[0078] Optionally, the account information includes: basic account information, identification information, account group information, and password information; step 203 may specifically include sub-steps 2031-2034:
[0079] Sub-step 2031: adding basic account information of the second user account to the user directory file in the basic file directory.
[0080] Sub-step 2032: adding identification information of the second user account to the identification directory file of the basic file directory.
[0081] Sub-step 2033: adding the account group information of the second user account to the account group directory file of the basic file directory.
[0082] Sub-step 2034: adding the password information of the second user account to the password directory file in the basic file directory.
[0083] In the embodiment of the present application, for sub-steps 2031-2034, taking the test user account as an example, the basic file directory maintained by the account management application includes:
[0084] User directory file: " / home / test", which stores the basic account information of the test account;
[0085] Identify the directory file: " / var / spool / mail / test", which stores the identification information of the test account;
[0086] Account group directory file: " / etc / group", which stores the account group information of the test account;
[0087] Password directory file: " / etc / passwd", which stores the password information of the test account.
[0088] When adding the account information of the second user account to the basic file directory, the basic account information of the second user account can be added to the user directory file; the identification information of the second user account can be added to the identification directory file; the account group information of the second user account can be added to the account group directory file; and the password information of the second user account can be added to the password directory file, thereby completing the persistent storage of the account information of the second user account.
[0089] Optionally, the record file directory includes a first subdirectory and a second subdirectory; the record information includes identification information and a target folder name; step 203 may specifically include sub-steps 2035-2036:
[0090] Sub-step 2035: Add the identification information of the second user account to the first sub-directory.
[0091] Sub-step 2036: Combine the account name of the second user account with preset symbols and / or randomly generated characters in a preset combination manner to obtain the target folder name, and use the target folder name to name the second sub-directory.
[0092] In the embodiment of the present application, for sub-steps 2035-2036, the record file directory includes a first sub-directory: " / var / user / file" and a second sub-directory. The first sub-directory: " / var / user / file" is used to record the identification information of the second user account to be created (including the account identification and the account group identification), and the second sub-directory specifically records the account name of the second user account in the form of folder naming.
[0093] It should be noted that, since the record file directory is configured not to open access rights to external users, the information in the first subdirectory does not open access rights to external users, making the maintenance and use of the record file directory more secure. In addition, when the second subdirectory records the account name of the second user account by naming the folder, the account name of the second user account can be combined with preset symbols and / or randomly generated characters to obtain the target folder name, which increases the complexity of folder naming and the difficulty of being cracked, thereby improving the security of the account system.
[0094] For example, taking the test user account as an example, after combining the account name test with the preset symbol "￥" and / or the randomly generated character "@#", the resulting second subdirectory folder is named "￥test@#".
[0095] Optionally, step 203 may further include sub-step 2037:
[0096] Sub-step 2037: If the identification information of the second user account is not recorded in the first sub-directory and the folder name of the second sub-directory does not include the account name of the second user account, determine that the record information of the second user account is not recorded in the record file directory.
[0097] In an embodiment of the present application, when creating a second user account, a query can be made in the record file directory to determine whether the second user account is an account that has been created. Specifically, the first subdirectory and the second subdirectory can be queried in the record file directory. If the identification information of the second user account is not recorded in the first subdirectory and the folder name of the second subdirectory does not include the account name of the second user account, it is determined that the record file directory does not record the record information of the second user account.
[0098] Optionally, step 203 may further include sub-step 2038:
[0099] Sub-step 2038: When creating the second user account, if it is detected that the record information of the second user account is recorded in the preset record file directory, the creation of the second user account is stopped.
[0100] In an embodiment of the present application, when creating a second user account, a query can be made in the record file directory to determine whether the second user account is an account that has been created. Specifically, the first subdirectory and the second subdirectory can be queried in the record file directory. If the identification information of the second user account is recorded in the first subdirectory, or the folder name of the second subdirectory includes the account name of the second user account, it is determined that the record information of the second user account is recorded in the record file directory. At this time, it is considered that the second user account is a user account that has been created, and the current creation of the second user account can be stopped to avoid repeated creation of user accounts.
[0101] In summary, for the process of creating a user account in the account system, you can refer to Figure 4 Taking the creation of a test user account as an example, the creation process includes:
[0102] M1. Trigger the instruction to create the test user account.
[0103] M2. Check whether the test user account exists in " / var / user / file".
[0104] M3: If the test user account exists, execute M4: add the account information of the test user account to the basic file directory.
[0105] M6. If the test user account does not exist, the execution ends.
[0106] After M4 is executed, M5 is executed to write the information of the test user account into the " / var / user / file" file.
[0107] After M5 is executed, the execution ends.
[0108] In summary, in response to the deletion operation on the first user account, the embodiment of the present application can delete the account information of the first user account in the basic file directory, and after the deletion is completed, add the created identification information of the first user account to the target file of the basic file directory; the basic file directory is configured to refuse to re-create a user account that matches the created identification information in the target file. In the embodiment of the present application, the deletion operation can ensure that the account information corresponding to the first user account in the basic file directory is completely deleted, avoiding leaving the legacy information of the first user account, thereby reducing the probability of the relevant user creating the first user account again. In addition, by configuring the created identification information, when the user account created subsequently matches the created identification information, the user account is considered to be an account that has been created, thereby refusing to create the user account. In this way, it is possible to prevent relevant personnel from logging into the operating system or modifying operating system files by re-creating a user account that has been deleted, thereby providing a security guarantee for the operating system.
[0109] Figure 5 : is a block diagram of an account information management device provided in an embodiment of the present application, the device comprising:
[0110] A deleting module 201, configured to delete the account information of the first user account in the basic file directory in response to a deletion operation on the first user account;
[0111] A recording module 202, configured to add the created identification information of the first user account in the target file of the basic file directory after the deletion is completed;
[0112] The basic file directory is configured to refuse to re-create a user account that matches the created identification information in the target file.
[0113] Optionally, the device further comprises:
[0114] A creation module, used for adding the account information of the second user account to the basic file directory and adding the record information of the second user account to the record file directory when creating a second user account, if it is detected that the record information of the second user account is not recorded in the preset record file directory, and the created identification information of the second user account does not exist in the target file, and the record file directory is configured to not open access rights to external users.
[0115] Optionally, the deletion module 201 includes:
[0116] A first deletion submodule, configured to call a native deletion instruction of the account system to delete the basic account information in the account information of the first user account in the basic file directory;
[0117] The second deletion submodule is used to call the automatic increase and deletion instruction of the account system, and delete the remaining account information of the first user account except the basic account information in the basic file directory.
[0118] Optionally, the recording module 202 includes:
[0119] a generating submodule, configured to generate created identification information of the first user account according to the account name, account identifier and account group identifier of the first user account and add the identification information to the password directory file;
[0120] Among them, the created identification information includes a first field recording the account name and a second field recording the account ID and the account group ID; the first field is used to indicate that a user account with the account name cannot be created again; the second field is used to indicate that a user account with the account ID and the account group ID cannot be created again.
[0121] Optionally, the account information includes: basic account information, identification information, account group information, and password information;
[0122] The creation module includes:
[0123] A first adding submodule, configured to add basic account information of the second user account to a user directory file in the basic file directory;
[0124] A second adding submodule, configured to add identification information of the second user account in an identification directory file of the basic file directory;
[0125] A third adding submodule, configured to add the account group information of the second user account to the account group directory file in the basic file directory;
[0126] The fourth adding submodule is used to add the password information of the second user account in the password directory file of the basic file directory.
[0127] Optionally, the record file directory includes a first subdirectory and a second subdirectory; the record information includes identification information and a target folder name;
[0128] The creation module includes:
[0129] a fifth adding submodule, configured to add the identification information of the second user account to the first subdirectory;
[0130] The naming submodule is used to combine the account name of the second user account with preset symbols and / or randomly generated characters in a preset combination method to obtain the target folder name, and use the target folder name to name the second subdirectory.
[0131] Optionally, the device further comprises:
[0132] The first determination module is used to determine that the record information of the second user account is not recorded in the record file directory when the identification information of the second user account is not recorded in the first subdirectory and the account name of the second user account is not included in the folder naming of the second subdirectory.
[0133] Optionally, the device further comprises:
[0134] The first determining module is used to stop creating the second user account if it is detected that the record information of the second user account is recorded in a preset record file directory when creating the second user account.
[0135] Optionally, the basic file directory includes an identification directory file, and the identification directory file is used to record identification information of the created user account;
[0136] The deleting module 201 includes:
[0137] The third deletion submodule is used to delete the account information of the first user account in the basic file directory if the identification information of the first user account is found in the identification directory file in response to the deletion operation on the first user account.
[0138] In summary, in response to the deletion operation on the first user account, the embodiment of the present application can delete the account information of the first user account in the basic file directory, and after the deletion is completed, add the created identification information of the first user account to the target file of the basic file directory; the basic file directory is configured to refuse to re-create a user account that matches the created identification information in the target file. In the embodiment of the present application, the deletion operation can ensure that the account information corresponding to the first user account in the basic file directory is completely deleted, avoiding leaving the legacy information of the first user account, thereby reducing the probability of the relevant user creating the first user account again. In addition, by configuring the created identification information, when the user account created subsequently matches the created identification information, the user account is considered to be an account that has been created, thereby refusing to create the user account. In this way, it is possible to prevent relevant personnel from logging into the operating system or modifying operating system files by re-creating a user account that has been deleted, thereby providing a security guarantee for the operating system.
[0139] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0140] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.
[0141] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.
[0142] An embodiment of the present application provides an account information management device, including a memory and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by one or more processors to include methods for performing one or more of the above embodiments.
[0143] Figure 6 8 is a block diagram of an account information management device 800 according to an exemplary embodiment. For example, the device 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
[0144] Reference Figure 6 , the device 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output (I / O) interface 812 , a sensor component 814 , and a communication component 816 .
[0145] The processing component 802 generally controls the overall operation of the device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.
[0146] The memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
[0147] The power supply component 806 provides power to the various components of the device 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 800.
[0148] The multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
[0149] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the device 800 is in an operating mode, such as a call mode, a recording mode, and a voice information processing mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.
[0150] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.
[0151] The sensor assembly 814 includes one or more sensors for providing various aspects of status assessment for the device 800. For example, the sensor assembly 814 can detect the open / closed state of the device 800, the relative positioning of components, such as the display and keypad of the device 800, and the sensor assembly 814 can also search for changes in the position of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, the orientation or acceleration / deceleration of the device 800, and the temperature change of the device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
[0152] The communication component 816 is configured to facilitate wired or wireless communication between the device 800 and other devices. The device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency information processing (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
[0153] In an exemplary embodiment, the apparatus 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.
[0154] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the device 800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
[0155] Figure 71 is a schematic diagram of the structure of the server in some embodiments of the present application. The server 1900 may have relatively large differences due to different configurations or performances, and may include one or more central processing units (CPU) 1922 (for example, one or more processors) and memory 1932, and one or more storage media 1930 (for example, one or more mass storage devices) storing application programs 1942 or data 1944. Among them, the memory 1932 and the storage medium 1930 can be short-term storage or permanent storage. The program stored in the storage medium 1930 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the server. Furthermore, the central processing unit 1922 can be configured to communicate with the storage medium 1930 and execute a series of instruction operations in the storage medium 1930 on the server 1900.
[0156] The server 1900 may also include one or more power supplies 1926, one or more wired or wireless network interfaces 1950, one or more input and output interfaces 1958, one or more keyboards 1956, and / or, one or more operating systems 1941, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
[0157] A non-transitory computer-readable storage medium, when the instructions in the storage medium are executed by a processor of a device (server or terminal), enables the device to execute the above-mentioned embodiment method.
[0158] A non-temporary computer-readable storage medium, when the instructions in the storage medium are executed by the processor of the device (server or terminal), enables the device to perform the description of the method of the above embodiment, so it will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the computer program product or computer program embodiment involved in this application, please refer to the description of the method embodiment of this application.
[0159] In addition, it should be noted that: the embodiment of the present application also provides a computer program product or a computer program, which may include computer instructions, which may be stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor may execute the computer instructions so that the computer device performs the description of the method of the above embodiment, so it will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the computer program product or computer program embodiment involved in this application, please refer to the description of the method embodiment of this application.
[0160] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the application disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.
[0161] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.
[0162] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.
[0163] The above is a detailed introduction to an account information management method, device, electronic device and computer-readable storage medium provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for a person skilled in the art, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A method for managing account information, characterized in that: The method comprises: In response to a deletion operation on the first user account, deleting the account information of the first user account in the basic file directory; After the deletion is completed, adding the created identification information of the first user account to the target file in the basic file directory; The basic file directory is configured to refuse to re-create a user account that matches the created identification information in the target file.
2. The method for managing account information according to claim 1, characterized in that: The method further comprises: When creating a second user account, if it is detected that the record information of the second user account is not recorded in the preset record file directory, and the created identification information of the second user account does not exist in the target file, the account information of the second user account is added to the basic file directory, and the record information of the second user account is added to the record file directory, and the record file directory is configured to not open access rights to external users.
3. The method for managing account information according to claim 1, characterized in that: The deleting the account information of the first user account in the basic file directory includes: Invoke a native deletion instruction of the account system, and delete the basic account information in the account information of the first user account in the basic file directory; The automatic increase and deletion instruction of the account system is called to delete the remaining account information of the first user account except the basic account information in the basic file directory.
4. The method for managing account information according to claim 1, characterized in that: The target file is a password directory file; The step of adding the created identification information of the first user account to the target file in the basic file directory includes: generating created identification information of the first user account according to the account name, account identifier and account group identifier of the first user account and adding the identification information to the password directory file; Among them, the created identification information includes a first field recording the account name and a second field recording the account ID and the account group ID; the first field is used to indicate that a user account with the account name cannot be created again; the second field is used to indicate that a user account with the account ID and the account group ID cannot be created again.
5. The method for managing account information according to claim 2, characterized in that: The account information includes: basic account information, identification information, account group information, and password information; The adding the account information of the second user account in the basic file directory includes: Adding basic account information of the second user account to the user directory file in the basic file directory; Adding identification information of the second user account in the identification directory file of the basic file directory; Adding the account group information of the second user account to the account group directory file of the basic file directory; Add the password information of the second user account to the password directory file in the basic file directory.
6. The method for managing account information according to claim 2, characterized in that: The record file directory includes a first subdirectory and a second subdirectory; the record information includes identification information and a target folder name; Adding the record information of the second user account in the record file directory includes: adding identification information of the second user account to the first subdirectory; According to a preset combination method, the account name of the second user account is combined with preset symbols and / or randomly generated characters to obtain the target folder name, and the target folder name is used to name the second subdirectory.
7. The method for managing account information according to claim 6, characterized in that: The method further comprises: If the identification information of the second user account is not recorded in the first subdirectory and the folder naming of the second subdirectory does not include the account name of the second user account, it is determined that the record information of the second user account is not recorded in the record file directory.
8. The method for managing account information according to claim 2, characterized in that: The method further comprises: When creating the second user account, if it is detected that the record information of the second user account is recorded in the preset record file directory, the creation of the second user account is stopped.
9. The method for managing account information according to claim 1, characterized in that: The basic file directory includes an identification directory file, and the identification directory file is used to record identification information of the created user account; The deleting the account information of the first user account in the basic file directory in response to the deletion operation on the first user account includes: In response to a deletion operation on the first user account, if identification information of the first user account is found in the identification directory file, the account information of the first user account in the basic file directory is deleted.
10. A device for managing account information, characterized in that: The device comprises: a deleting module, configured to delete the account information of the first user account in the basic file directory in response to a deletion operation on the first user account; a recording module, configured to add the created identification information of the first user account to the target file in the basic file directory after the deletion is completed; The basic file directory is configured to refuse to re-create a user account that matches the created identification information in the target file.
11. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the method as claimed in any one of claims 1 to 9.
12. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the method as claimed in any one of claims 1 to 9.