WO2016078294A1 - Method and electronic device for realizing file password lock - Google Patents

Abstract

A method for realizing a file password lock, running on an electronic device (2); the file password lock comprises a count enabling identification and usage count; the method comprising the following steps: if comparing a numerical value of the usage count of the file password lock to a numerical value of the usage counts of a user registration information table in the electronic device (2) is allowed according to a numerical value of the count enabling identification, then comparing the numerical value of the usage count of the file password lock to the numerical value of the usage count of the user registration information table; and if the numerical value of the usage count of the file password lock is different from the numerical value of the usage count of the user registration information table, then forbidding a client (1) connected to the electronic device (2) to be matched to the electronic device (2). Also provided is an electronic device (2) for realizing a file password lock. Users are enabled to authorize a device or system in a flexible and safe manner.

Description

Method and electronic device for realizing file password lock Technical field

The present invention relates to a method and an electronic device for implementing a file password lock, and more particularly to a method and an electronic device for implementing a file password lock.

Background technique

With the development of information security technology, people pay more and more attention to the security of devices or systems, and the usage rights of devices or systems are also controlled accordingly. Depending on the usage scenario, the authorization method is also various, including password mode, USBKey mode, SMS authentication mode, serial number authentication mode or license mode.

USBKey is a commonly used authorization method with double security features of physical and password, and has high security performance. However, for the user, the password information is bound to the storage carrier and cannot be copied, transmitted, or modified, resulting in poor flexibility and increased physical cost.

License is also a common authorization method, mainly to realize the license to use the software system. The license exists in the form of files and has good flexibility. However, its application scope is mainly limited to the software field, and the users used are limited. The security is not high.

In summary, the existing authorization method cannot balance flexibility and security, and imposes certain restrictions on the use of users.

Summary of the invention

In view of the above, it is necessary to provide a method for implementing file password lock, which makes people's authority for device or system authorization flexible and secure.

At the same time, it is necessary to provide an electronic device that implements a file password lock, so that people have the flexibility and security to authorize the device or system.

In order to solve the above technical problem, an embodiment of the present invention provides a method for implementing a file password lock. The file password lock includes a number of times of enabling identification and a number of uses. The method includes the following steps: a comparison step of using times, if The identifiable value is obtained by comparing the value of the number of times of using the password lock of the above file with the value of the number of uses of the user registration information table in the electronic device, and registering the value of the number of times of using the password lock with the user. The value of the number of times the information table is used for comparison, when the above file password lock When the value of the number of uses is different from the number of times of use of the user registration information table, the client connected to the electronic device is prohibited from matching the electronic device.

The embodiment of the present invention further provides an electronic device for implementing a file password lock, the electronic device includes a second database and a processor, and the second database stores program instructions, where the file password lock includes a number of times of enabling identification and usage times. The processor processes the program instructions to perform the following steps: using the number comparison step, if the value of the number of times the password is locked is obtained according to the number of times the number of times the password is locked, and the user registration information table in the electronic device Comparing the values of the number of use times, comparing the value of the number of times of using the password lock with the value of the number of times of use of the user registration information table, when the value of the number of times of using the password lock and the use of the user registration information table When the number of times is different, the client connected to the electronic device is prohibited from matching the electronic device.

Compared with the prior art, the implementation method and the electronic device of the file password lock according to the embodiment of the present invention can make the user's authorization mode for the device or the system both flexible and secure.

DRAWINGS

1 is a diagram showing the operating environment of a file password lock recognition system 20 in accordance with an embodiment of the present invention.

2 is a schematic diagram of a component element table of a preferred embodiment of the file combination lock of FIG. 1 in accordance with an embodiment of the present invention.

3 is a schematic diagram of a component element table of a preferred embodiment of the user registration information table of FIG. 1 according to an embodiment of the present invention.

4 is a functional block diagram of a preferred embodiment of the file lock lock recognition system 20 of FIG. 1 in accordance with an embodiment of the present invention.

FIG. 5 is a flow chart of a preferred embodiment of a file password lock identification method according to an embodiment of the present invention.

FIG. 6 is a functional block diagram of a preferred embodiment of a file password lock management system 22 in accordance with an embodiment of the present invention.

detailed description

As shown in FIG. 1, FIG. 1 is a diagram showing an operating environment of a file password lock recognition system 20 according to an embodiment of the present invention. The above-described file password lock recognition system 20 operates in the electronic device 2, and the electronic device 2 includes a second database 21 and a file password lock management system 22. In this embodiment, the electronic device 2 may be a computer, a server, or a tablet computer, and the electronic device 2 may further include a processor. The user database registry and the device identifier of the electronic device 2 are stored in the second database 21 described above. In this embodiment, the components of the user registration information table include a user serial number, a user identifier, a valid identifier, a usage count, a number of times enable identifier, a password enable identifier, a password, and a permission level (as shown in FIG. 3). In this embodiment, the component of the user registration information table is defined as the first The constituent elements have the corresponding numerical values of the first constituent elements, and the corresponding numerical values are defined as the first constituent values. The user of the electronic device 2 may be a plurality of users, and each user corresponds to one user identifier.

The electronic device 2 communicates with a plurality of clients 1 through a connection manner such as a physical connection or a network connection. In this embodiment, the plurality of clients 1 may be a magnetic card, a mobile phone, a USB flash drive, a mobile hard disk, or a tablet computer. Each client 1 includes a first database 10, and the first database 10 stores a file password lock, which is generated by the file password lock management system 22 in the electronic device 2, and a file password lock corresponding to the electronic device 2 One user, the same user's file password lock can be stored in the first database 10 of the plurality of clients 1. In this embodiment, the file password lock is an encrypted file, and the encrypted file includes a plurality of component elements. As shown in FIG. 2, the component elements include an information identifier, a number of times enable identifier, a usage count, a password enable identifier, and a password. And permission levels, etc. In this embodiment, the constituent elements of the file lock are defined as the second component, the second component has a corresponding numerical value, and the corresponding numerical value is defined as the second component value. In this embodiment, the information identifier in the second component includes the device identifier, the user identifier, and the valid identifier.

The corresponding constituent elements of the first component element and the second component element include: a user identifier, a valid identifier, a usage count, a number of times enable identifier, a password enable identifier, a password, and a permission level (as shown in FIG. 2 and FIG. 3). . The initial values of the user identifier, the valid identifier, the number of times of use, the number of times enable identifier, the password enable identifier, and the permission level are set to the same value. For example, the user identifier in FIG. 2 is “zhang”. The effective identification, the number of times of use, the number of times enable identification, the password enable identifier, and the permission level are the initial identification, usage count, number of times enable identifier, password enable identifier, and initial level of the permission level of the user identifier "zhang" in FIG. The values are the same. The password in FIG. 2 is different from the initial value of the password in FIG. 3. In this embodiment, the initial value of the password in FIG. 2 is null, and the initial value of the password in FIG. 3 is not null. .

By configuring the password enable identifier of the file password lock, the password lock of the file lock can be allowed or prohibited. If the password lock of the file lock is allowed, the password in the password lock and the user registration information table are Compare the passwords in the file to see if the two passwords are consistent.

The above privilege level represents the privilege of the user corresponding to the password lock of the above file, and the privilege level can be divided into two or more levels, and each level represents different privilege. In this embodiment, the privilege level is divided into an ordinary user level and a super user level, which respectively correspond to an ordinary user and a super user. The super user completes the configuration of all user information by using the above-mentioned file password lock management system 22. As shown in FIG. 6, the super user can perform maintenance on the ordinary user and the super user, including adding or deleting users and modifying the first element of the user. The value and the encryption key of the file password lock, etc., and the encryption key is set by the file password lock management system 22 for the file password lock. When the super user adds a user through the file password lock management system 22, the first element value of the user is added to the user registration information table, and a file password corresponding to the first element value of the user is generated. Lock; when the above superuser passes the above file password lock management system 22 When the user is deleted, the first element value of the user in the user registration information table is deleted, and at the same time, the user's file password lock is invalid; when the super user modifies the user's first through the file password lock management system 22 In the case of the feature value, the user's file password lock before the modification is invalid, and the superuser must re-generate a new file password lock for the user; when the superuser modifies the encryption key of the file password lock, All file password locks generated by the above superusers are invalid, and the file password lock must be regenerated. When the above file password lock of the ordinary user is lost, the super user can regenerate one of the above file password locks for the ordinary user.

As shown in FIG. 4, FIG. 4 is a functional block diagram of a preferred embodiment of the file password lock recognition system 20 of FIG. 1 in accordance with an embodiment of the present invention. The above-mentioned file password lock recognition system 20 includes one or more modules. In this embodiment, the file password lock recognition system 20 includes a decryption module 200, an information matching module 201, a number enable module 202, a number comparison module 203, and a password enablement. The module 204, the password comparison module 205, and the modification module 206.

The decryption module 200 is configured to decrypt the file password lock, and the decryption can decrypt the file password lock by the encryption key set by the file password lock management system 22 for the file password lock.

The information matching module 201 is configured to determine whether the value of the information identifier in the file password lock corresponds to the information in the electronic device 2. In this embodiment, the information identifier includes a device identifier, a user identifier, and a valid identifier. The value of the above device identifier is an identifier (ID) of the corresponding electronic device 2. The value of the above-mentioned user identification refers to the user name of the user who uses the electronic device 2. The value of the above-mentioned valid identifier indicates whether the above-mentioned file password lock is valid. In this embodiment, the value "0" indicates that the file password lock is valid, and the value "1" indicates that the file password lock is invalid. When the value of the information identifier in the file password lock does not correspond to the information in the electronic device 2, it indicates that the client 1 cannot match the electronic device 2, and the flow ends.

When the value of the information identifier in the file password lock corresponds to the information in the electronic device 2, the number-of-times enabling module 202 is configured to determine whether to allow the value of the "number of uses" in the first component element and the second value. The values of the component "number of uses" are compared. In this embodiment, the number-of-times enabling module 202 implements the determination by viewing the value of the number of times of the password lock in the file lock. For example, when the value of the number-of-times enable flag is "1", the number-of-times enabling module 202 determines that the result is a value that allows the "number of uses" in the first component and the value of the second component "number of uses". comparing. When the value of the number-of-times enable flag is "0", the number-of-times enabling module 202 determines that the result is that the value of the "number of uses" in the first component is prohibited from being compared with the value of the second component "number of uses". .

When the value of "number of uses" in the first component in one client 1 is prohibited from being compared with the value of the corresponding second component "number of uses", the file password of the same user in the other client 1 can be implemented. The lock is used at the same time. If you allow the value of "number of uses" in the first component of client 1 When compared with the corresponding value of the second component "number of uses", the above file password lock is valid only on the client 1, and the file password lock stored in the other client 1 is invalid. Specifically, after the file password lock in the client 1 is used once, the value of the “number of uses” in the first component corresponding to the client 1 and the “number of uses” in the second component are used. When the value is incremented by 1, the value of "number of uses" in the first component corresponding to other client 1 is not consistent with the value of "number of uses" of the second component, so all the file password locks in the other client 1 are invalid. In turn, the uniqueness of the above file password lock is achieved.

When the value of "number of uses" in the first component in one client 1 is allowed to be compared with the value of the corresponding second component "number of uses", the number comparison module 203 is set to store the client 1 The value of "number of uses" in the first component is compared with the value of "number of uses" in the corresponding second component. When the value of "number of uses" in the first component of the client 1 is different from the value of "number of uses" in the corresponding second component, it indicates that the client 1 cannot match the electronic device 2, and the process ends. .

When the value of "number of uses" in the first component of the client 1 is the same as the value of "number of uses" in the corresponding second component (for example, the first user ID in the client 1 is "zhang") The value of "number of uses" in the component is 2, and the value of "number of uses" corresponding to the user identifier "zhang" in the second component is also 2), or when the first component in a client 1 is prohibited. When the value of the "number of uses" is compared with the value of the corresponding second component "number of uses", the password enabling module 204 is configured to determine whether to allow the "password" in the first component of the client 1 The value of " is compared with the value of "password" in the corresponding second component. In this embodiment, the comparison between the value of the "password" in the first component and the value of the "password" in the corresponding second component is achieved by looking at the password in the password lock of the above file. For example, when the value of the component "password enable flag" is "1", it means that the value of "password" in the first component element is allowed to be compared with the value of "password" in the corresponding second component. When the value of the component "password enable flag" is "0", it means that the comparison of the value of "password" in the first component with the value of "password" in the corresponding second component is prohibited.

When the value of the "password" in the first component is allowed to be compared with the value of the "password" in the corresponding second component, the password comparison module 205 is set to set the "password" in the first component. The value is compared with the value of the "password" in the corresponding second component. The value of "password" in the above first element can be provided to the user to input during the process of using the file password lock. When the value of the "password" in the first component is the same as the value of the "password" in the corresponding second component, the modification module 206 is configured to synchronously modify the value of the "number of uses" in the first component. The second component corresponds to the value of "number of uses" and re-encrypts the above file lock for the next use.

When the value of the "password" in the first component is different from the value of the "password" in the corresponding second component, it means that the client 1 cannot match the electronic device 2, and the flow is ended.

As shown in FIG. 5, FIG. 5 is a flowchart of a preferred embodiment of a file password lock identification method according to an embodiment of the present invention.

In step S1, the decryption module 200 decrypts the file password lock, and the decryption can decrypt the file password lock by using the encryption key set by the file password lock management system 22 for the file password lock.

In step S2, it is determined whether the value of the information identifier in the file password lock corresponds to the information in the electronic device 2 described above. In this embodiment, the information identifier includes a device identifier, a user identifier, and a valid identifier. The value of the above device identifier is an identifier (ID) of the corresponding electronic device 2. The value of the above-mentioned user identification refers to the user name of the user who uses the electronic device 2. The value of the above-mentioned valid identifier indicates whether the above-mentioned file password lock is valid. In this embodiment, the value "0" indicates that the file password lock is valid, and the value "1" indicates that the file password lock is invalid. When the value of the information identifier in the file password lock does not correspond to the information in the electronic device 2, the flow ends. When the value of the information identifier in the file password lock corresponds to the information in the electronic device 2, step S3 is performed.

In step S3, the number-of-times enabling module 202 determines whether or not the value of the "number of uses" in the first component element and the value of the second component "number of uses" are allowed to be compared. In this embodiment, the number-of-times enabling module 202 is implemented by viewing the value of the number of times of the password lock in the file password lock. For example, when the value of the number-of-times enable flag is "1", the number-of-times enabling module 202 determines that the result is a value that allows the "number of uses" in the first component and the value of the second component "number of uses". comparing. When the value of the number-of-times enable flag is "0", the number-of-times enabling module 202 determines that the result is that the value of the "number of uses" in the first component is prohibited from being compared with the value of the second component "number of uses". . When it is allowed to compare the value of the "number of uses" in the first constituent element with the value of the second component "number of uses", step S4 is performed; when "the number of uses" in the first constituent element is prohibited When the value is compared with the value of the second component "number of uses", step S5 is performed.

When the value of "number of uses" in the first component in one client 1 is prohibited from being compared with the value of the corresponding second component "number of uses", the file password of the same user in the other client 1 can be implemented. The lock is used at the same time. If the value of "number of uses" in the first component of a client 1 is allowed to be compared with the value of the corresponding second component "number of uses", the above file password lock is valid only on the client 1. The above file password lock stored in other client 1 is invalid. Specifically, after the file password lock in the client 1 is used once, the value of the “number of uses” in the first component corresponding to the client 1 and the “number of uses” in the second component are used. When the value is incremented by 1, the value of "number of uses" in the first component corresponding to other client 1 is not equal to the value of "number of uses" of the second component. Therefore, the file password locks in the other clients 1 above are all invalidated, thereby realizing the uniqueness of the above file password locks in use.

In step S4, the number comparison module 203 compares the value of "number of uses" in the first component stored by the client 1 with the value of "number of uses" in the corresponding second component. When the value of "number of uses" in the first component of the client 1 is different from the value of "number of uses" in the corresponding second component, it indicates that the client 1 cannot match the electronic device 2, and the process ends. . When the value of "number of uses" in the first component of the client 1 is the same as the value of "number of uses" in the corresponding second component (for example, the first user ID in the client 1 is "zhang") The "number of uses" value in the component is 2, and the value of "number of uses" corresponding to the user identifier "zhang" in the second component is also 2), and step S5 is performed.

In step S5, the password enabling module 204 determines whether the value of the "password" in the first component in the client 1 is allowed to be compared with the value of the "password" in the corresponding second component. In this embodiment, determining whether to allow the value of the "password" in the first component to be compared with the value of the "password" in the corresponding second component is by viewing the password enable identifier in the password lock of the file. Realized. For example, when the value of the component "password enable flag" is "1", it means that the value of "password" in the first component element is allowed to be compared with the value of "password" in the corresponding second component element; When the value of the component "password enable flag" is "0", it means that the comparison of the value of "password" in the first component with the value of "password" in the corresponding second component is prohibited. When it is allowed to compare the value of the "password" in the first component in the client 1 with the value of the "password" in the corresponding second component, step S6 is performed; when the client 1 is prohibited When the value of the "password" in the first component in the comparison with the value of the "password" in the corresponding second component is performed, step S7 is performed.

In step S6, the password comparison module 205 compares the value of the "password" in the first component with the value of the "password" in the corresponding second component. The value of "password" in the above first element can be provided to the user to input during the process of using the file password lock. When the value of the "password" in the first component is the same as the value of the "password" in the corresponding second component, step S7 is performed; when the value of the "password" in the first component is corresponding to the first When the values of "passwords" in the two components are different, the flow ends.

In step S7, the modification module 206 synchronously modifies the value of the "number of uses" in the first component and the value corresponding to the "number of uses" in the second component, and re-encrypts the password lock for the next use.

In the above steps, step S5 to step S6 may be performed before step S3, that is, the value of the "password" of the first component element may be compared with the value of the "password" of the second component element, and then performed. The numerical value of the "number of uses" of the first component is compared with the value of the "number of uses" of the second component.

The above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to be limiting, and the present invention will be described in detail with reference to the preferred embodiments thereof, and those skilled in the art should understand that the technical solutions of the present invention may be modified or substituted. Neither should the spirit and scope of the technical solutions of the present invention be deviated.

Industrial applicability

Based on the foregoing technical solutions provided by the embodiments of the present invention, the user's authorization manner for the device or the system has both flexibility and security.

Claims (14)

A method for implementing a file password lock, the method running on an electronic device, wherein the file password lock includes a number of times of enabling identification and a number of uses, the method comprising: The number-of-use comparison step, if the value of the number of times of the number of times the password is allowed to be used is compared with the value of the number of times the user registration information table is used in the electronic device, The value of the number of times the file password lock is used is compared with the value of the number of times the user registration information table is used, when the value of the number of times the file password lock is used is different from the number of times the user registration information table is used. The client connected to the electronic device is prohibited from matching the electronic device. The method for implementing a file password lock according to claim 1, wherein the method further comprises: a modifying step of, when the value of the number of times of using the file password lock is the same as the value of the number of times of using the user registration information table, the value of the number of times the file password lock is used and the number of times the user registration information table is used The value of each is increased by 1. The method for implementing a file password lock according to claim 2, wherein before the modifying step, the method further comprises: a password comparison step, if the value of the password enable identifier in the password lock is allowed to compare the value of the password in the password lock with the value of the password in the corresponding user registry, When the value of the password in the file password lock is different from the value of the password in the corresponding user registration information table, the client connected to the electronic device is prohibited from matching the electronic device. The method for implementing a file password lock according to claim 1, wherein the component of the file password lock further comprises: an information identifier, a password enable identifier, a password, and a permission level, wherein the information identifier includes a device identifier, The user identifier and the valid identifier, the components of the user registration information table include: a user identifier, a valid identifier, a number of times enable identifier, a number of uses, a password enable identifier, a password, and a permission level. The method for implementing a file password lock according to claim 1, wherein the file password lock is stored on a client, and the file password lock of the same user is stored on a plurality of clients. The method for implementing a file password lock according to claim 1, wherein before the step of comparing the number of uses, the method further comprises: In the decrypting step, the file password lock is decrypted by the file encryption lock management system pre-setting the encryption key for the file password lock. The method for implementing a file password lock according to claim 4, further comprising the following steps before the step of comparing the number of uses: The information matching step is to compare the value of the information identifier of the file password lock with the information in the electronic device, when the value of the information identifier of the file password lock is different from the information in the electronic device, The client connected to the electronic device is prohibited from matching the electronic device, and the information in the electronic device includes a device identifier, a user identifier, and a valid identifier. An electronic device for implementing a file password lock, comprising a second database and a processor, wherein the second database stores program instructions, the file password lock includes a number of times enable identification and a number of uses, and the processor processes the program Direct the instructions to perform the following steps: The number-of-use comparison step, if the value of the number of times of the number of times the password is allowed to be used is compared with the value of the number of times the user registration information table is used in the electronic device, The value of the number of times the file password lock is used is compared with the value of the number of times the user registration information table is used, when the value of the number of times the file password lock is used is different from the number of times the user registration information table is used. The client connected to the electronic device is prohibited from matching the electronic device. An electronic device implementing a file password lock according to claim 8, wherein said processor further performs the following steps by processing said program instructions: a modifying step of, when the value of the number of times of using the file password lock is the same as the value of the number of times of using the user registration information table, the value of the number of times the file password lock is used and the number of times the user registration information table is used The value of each is increased by 1. An electronic device implementing a file lock according to claim 9, wherein said processor further performs the following steps before said performing said modifying step by processing said program instruction: a password comparison step, if the value of the password enable identifier in the password lock is allowed to compare the value of the password in the password lock with the value of the password in the corresponding user registry, When the value of the password in the file password lock is different from the value of the password in the corresponding user registration information table, the client connected to the electronic device is prohibited from matching the electronic device. The electronic device for implementing a file password lock according to claim 8, wherein the component of the file password lock further comprises: an information identifier, a password enable identifier, a password, and a permission level, and the information The identifier includes a device identifier, a user identifier, and a valid identifier. The components of the user registration information table include: a user identifier, a valid identifier, a number of times enable identifier, a number of uses, a password enable identifier, a password, and a permission level. The electronic device for implementing a file password lock according to claim 8, wherein the file password lock is stored on the client, and the file password lock of the same user is stored on the plurality of clients. The electronic device implementing the file password lock according to claim 8, wherein the processor further performs the following steps before the step of comparing the number of uses is performed by processing the program instruction: Decrypting step, decrypting the file password lock by using a file encryption key to pre-set an encryption key for the file password lock; The electronic device implementing the file password lock according to claim 11, wherein the processor further performs the following steps before the step of comparing the number of uses is performed by processing the program instruction: The information matching step is to compare the value of the information identifier of the file password lock with the information in the electronic device, when the value of the information identifier of the file password lock is different from the information in the electronic device, The client connected to the electronic device is prohibited from matching the electronic device, and the information in the electronic device includes a device identifier, a user identifier, and a valid identifier.

Images