WO2019178981A1 - 自定义规则密码管理方法、装置、终端设备及存储介质 - Google Patents

自定义规则密码管理方法、装置、终端设备及存储介质 Download PDF

Info

Publication number
WO2019178981A1
WO2019178981A1 PCT/CN2018/094189 CN2018094189W WO2019178981A1 WO 2019178981 A1 WO2019178981 A1 WO 2019178981A1 CN 2018094189 W CN2018094189 W CN 2018094189W WO 2019178981 A1 WO2019178981 A1 WO 2019178981A1
Authority
WO
WIPO (PCT)
Prior art keywords
rule
password
type
target
identifier
Prior art date
Application number
PCT/CN2018/094189
Other languages
English (en)
French (fr)
Inventor
周泓宇
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019178981A1 publication Critical patent/WO2019178981A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/45—Structures or tools for the administration of authentication
    • G06F21/46—Structures or tools for the administration of authentication by designing passwords or checking the strength of passwords
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management

Definitions

  • the present application relates to the field of computers, and in particular, to a method, an apparatus, a terminal device, and a storage medium for managing a custom rule password.
  • the embodiment of the present application provides a method, a device, a terminal device, and a storage medium for managing a custom password, so as to solve the problem that the current user password is easily leaked and deciphered.
  • the embodiment of the present application provides a method for managing a custom rule password, including:
  • the original password is processed by using at least one of the rule types to generate a target password.
  • the embodiment of the present application provides a custom rule password management apparatus, including:
  • An identifier obtaining module configured to obtain a password generating instruction, and obtain a target rule identifier and an original password based on the password generating instruction;
  • a target rule file obtaining module configured to acquire, according to the target rule identifier, a target rule file corresponding to the target rule identifier from at least one rule file, where the target rule file includes rule execution logic and at least one a rule type, wherein at least one of the rule types has an irreversible transformation rule type;
  • the target password generating module is configured to process the original password by using at least one of the rule types according to the rule execution logic to generate a target password.
  • an embodiment of the present application provides a terminal device, including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, where the processor executes the computer The following steps are implemented when reading the instruction:
  • the original password is processed by using at least one of the rule types to generate a target password.
  • the embodiment of the present application provides one or more non-volatile readable storage media storing computer readable instructions, when the computer readable instructions are executed by one or more processors, such that the one or Multiple processors perform the following steps:
  • the original password is processed by using at least one of the rule types to generate a target password.
  • FIG. 1 is a flowchart of a method for managing a custom rule password in Embodiment 1 of the present application.
  • FIG. 2 is a specific flow chart of step S10 of FIG. 1.
  • FIG. 3 is a specific flow chart before step S20 in FIG. 1.
  • FIG. 4 is a specific flow chart of step S21 of Figure 3.
  • FIG. 5 is a specific flowchart of step S22 in FIG.
  • FIG. 6 is a schematic block diagram of a custom rule password management apparatus in Embodiment 2 of the present application.
  • FIG. 7 is a schematic diagram of a terminal device in Embodiment 4 of the present application.
  • FIG. 1 is a flow chart showing a method for managing a custom rule password in this embodiment.
  • the custom rule password management method can be applied in an application, and the password corresponding to the rule file can be calculated in real time according to the user's unique original password and the rule file saved in the database, thereby effectively implementing the password management of the user.
  • the rule password management method is specifically applicable to an application installed on a terminal device.
  • the terminal device is a device that can perform human-computer interaction with the user, including but not limited to devices such as a computer, a smart phone, and a tablet.
  • the method for managing a custom rule password includes the following steps:
  • S10 Acquire a password generation instruction, and obtain a target rule identifier and an original password based on the password generation instruction.
  • the password generation instruction refers to an instruction for acquiring the target rule identifier and the original password.
  • the target rule identifier is an identifier used to uniquely identify the target rule file.
  • the target rule file refers to the rule file that the user wants to obtain.
  • the rule file refers to the storage carrier set by the save rule, and may be saved in the form of a file (.txt) in a text format, and the file in the text format is stored according to a certain logic.
  • the function of the sorting combination ie, rule execution logic
  • the application encrypts the original password by calling the rule file and executing the function in the rule file.
  • the original password refers to the password uniquely used by the user. In the custom rule password management method, the user only needs to uniquely remember the original password.
  • an application that implements custom rule password management
  • the application acquires a password generation instruction input by the user, and can quickly and conveniently acquire the target rule identifier and the original based on the password generation instruction. password.
  • step S10 as shown in FIG. 2, a password generation instruction is acquired, and the target rule identifier and the original password are obtained based on the password generation instruction, including the following steps:
  • S11 Display an identifier acquisition interface and an original password acquisition interface according to the password generation instruction.
  • the identifier acquisition interface refers to an interface for obtaining the target rule identifier displayed on the application terminal
  • the original password acquisition interface refers to an interface for obtaining the original password displayed on the display of the application terminal, the identifier acquisition interface and the original password acquisition.
  • the interface includes, but is not limited to, obtaining a corresponding target rule identifier and a original password by means of key input, voice input, and the like.
  • the identifier acquisition interface and the original password acquisition interface are displayed on the terminal display to provide an interface platform for obtaining user input information, and the target rule identifier and the original password input by the user are successfully obtained.
  • the application can provide the input rule information and the original password by using the identifier acquisition interface and the original password interface by providing input information such as key input and voice input.
  • S20 Obtain a target rule file corresponding to the target rule identifier from the at least one rule file, where the target rule file includes a rule execution logic and at least one rule type, and the at least one rule type has an irreversible transformation The type of rule.
  • the rule execution logic refers to the order in which the functions corresponding to the rule types are executed in the rule setting.
  • the rule type is the type of the operation rule that encrypts the password. From the concept of rule type, the concept of rule setting can be understood naturally and simply: rule setting refers to a collection of rule types that are combined by at least one rule type in a custom sorting manner (ie, rule execution logic). In the perspective of setting the rule creation rules of the development platform, it is actually an operation program composed of at least one function corresponding to the rule type in a custom sorting manner.
  • the irreversible transformation rule type refers to a rule type in which the value encrypted by the rule type is a value that cannot be deduced and deciphered before encryption.
  • the rule file ID is used as the target rule identifier.
  • the application needs to pass the rule file ID. (such as Ping An Auto Insurance, Ping An Life Insurance and Ping An Property Insurance) to obtain the saved target rule documents (such as Ping An Auto Insurance.rule, Ping An Life Insurance.rule and Ping An Property Insurance.rule) to obtain the rule file ID according to the obtained target rule file.
  • the login password corresponding to the account of Ping An Auto Insurance, Ping An Life Insurance and Ping An Property Insurance.
  • step S20 as shown in FIG. 3, the custom rule password management is performed before the step of acquiring the target rule file corresponding to the target rule identifier from the at least one rule file based on the target rule identifier.
  • the method also includes pre-creating and saving at least one rules file.
  • the steps of pre-creating and saving at least one rule file include:
  • each rule setting includes a corresponding rule execution logic and at least one rule type, and the at least one rule type has an irreversible change rule type.
  • a rule type can be implemented and represented by a corresponding function, for example: using add(pwd, num) function to represent one of the rule types, the rule type represents a kind Addition rule, where pwd represents the current password, num represents the value added in the addition operation, when num takes 123456, that is, the function is represented as add(pwd, 123456), the specific operation process of the addition rule is pwd+ 123456 (that is, add 123456 to the current password).
  • rule execution logic custom sort
  • combining the three rule types according to the rule execution logic can obtain 6 different rule settings.
  • the operation of the rule type is more complicated and the number of rule types is larger, the more types of rule settings are, the more the passwords are calculated according to the rule settings, and the security of encryption is higher.
  • the irreversible transformation rule type refers to a rule type that is encrypted by the rule type and cannot decipher and decipher the value before encryption.
  • the original password is first MD5 encrypted, assuming the original The password is 123456
  • the value encrypted by the interception method based on MD5 encryption can be expressed as 32-bit hexadecimal number "E10ADC3949BA59ABBE56E057F20F883E”
  • the first ten digits of "E10ADC3949” are intercepted, converted into decimal number "966549846345”, and then intercepted.
  • the six digits get "846345", and the intercepted value 846345 cannot be reversed to 123456.
  • it is also possible to adopt other types of irreversible transformation rules such as the type of irreversible transformation rule such as the interception method of SHA-1 (one of the secure hash algorithms).
  • At least one rule setting is obtained, where the rule setting includes a corresponding rule execution logic and at least one rule type, and at least one irreversible conversion rule exists in at least one rule type set by each rule A type indicating that at least one rule type set by the rule may be an irreversible transformation rule type, or may include at least one irreversible transformation rule type and other rule types.
  • the corresponding rule execution logic that is, the custom sort combination of the rule type
  • the rule set obtained by the at least one rule type can ensure that the password generated according to the rule setting has the characteristics of diversity and high security, and can Effectively prevent password leakage.
  • There is an irreversible transformation rule type in at least one rule type which can ensure that the password generated according to the rule setting cannot obtain the original password by reverse derivation and deciphering, thereby greatly improving the security of the original password.
  • step S21 as shown in FIG. 4, at least one rule setting is acquired, where each rule setting includes a corresponding rule execution logic and at least one rule type, at least one rule type
  • each rule setting includes a corresponding rule execution logic and at least one rule type, at least one rule type
  • S211 Acquire at least one type of rule preset, and the type of the irreversible change rule exists in the rule type.
  • some basic and commonly used rule types are preset. For example, in the normal case, only the original password represented by 6 digits is encrypted and converted, and before and after encryption. The passwords are all expressed in the form of 6 digits, and the rule type can be preset in accordance with the characteristics of the 6 digits.
  • the irreversible transformation rule type is a type of rule that cannot be deprecated by any rule setting. Therefore, when the rule type is preset, the irreversible transformation rule type is also required to be preset.
  • the at least one rule type that is preset and saved in the database is obtained, and the irreversible conversion rule type is included in the at least one rule type, and the preset rule type may be determined according to the preset rule type. Meet the needs of the combination rule setting.
  • the preset rule type is required for the at least one rule type. If at least one of the preset rule types has a rule type required for the combination rule setting, the custom rule combination of the rule types required for the combination rule setting is performed, and at least one rule setting is obtained.
  • rule type add (pwd, num), invert(pwd), and MD5(6)(pwd)
  • invert() refers to the inversion operation, where the specific operation rule is: If the value is 111111, the inversion operation is 1000000-111111; MD5(6) indicates the interception method based on MD5 encryption, and the final intercepted value is the last 6 bits
  • Combination (Specification 0! is 1) Six different rule settings can be obtained.
  • rule type is disclosed to the user, and the user can know how the rule type specifically performs the encryption operation, which can reduce the user's concern about the opaque rule type, and the user can also perform calculation and verification according to the public rule type.
  • the security and reliability of password management can be further improved without resorting to the application itself.
  • the preset rule type is required for the at least one rule type. If the preset at least one rule type lacks the rule type set by the combination rule, for example, the rule setting requirement can process the original password in which the letter appears, and if the original password is zls123, the preset rule type is add ( Pwd,123456) When encrypting the original password zls123, zls123+123456 will not be able to process the letters in the password. Therefore, you need to create the type of rules you need to solve the combination rule settings that solve the alphabet problem.
  • the original password is zls123
  • the original password is zls123
  • the original rule zls123 can be directly operated by the new rule type to obtain an av579, and then combined with other rule types (including at least one irreversible change rule type) that meet the composition rule for custom sorting. Combined, you can get the corresponding rule settings.
  • the original password is encrypted by using a more complicated and more rule type to further improve the security of the encryption.
  • the “rule type custom sorting combination” is “rule execution logic”, and it can be understood that the custom sorting combination of the rule type is equivalent to the function corresponding to the rule type in the rule setting in the application. The logical order of execution.
  • S22 Create and save a corresponding at least one rule file according to at least one rule setting, and configure a corresponding rule identifier for the rule file.
  • the corresponding at least one rule file is created according to the at least one rule setting, the rule file is saved in the database, and the rule file is configured with a corresponding rule identifier, so that the user can identify by the application according to the rule.
  • the rule file is quickly called for the identification of the uniquely identified rule file, and the encryption operation is performed according to the rule file.
  • step S22 creating and saving a corresponding at least one rule file according to at least one rule setting, and configuring a corresponding rule identifier for the rule file includes the following steps:
  • S221 Create at least one rule file according to at least one rule setting.
  • At least one corresponding rule file is created, and the rule file stores, in a plaintext manner, a function corresponding to the rule type combined in a certain logical order.
  • S222 Encrypt the content of the at least one rule file, and save the encrypted at least one rule file in a database.
  • the rule type is public to the user, it is not desirable for other users to be public (except for sharing in the rule type library), therefore, the content in the rule file, that is, the function corresponding to the rule type should be Encryption processing is performed, and the specific encryption processing method can be implemented by using base64 encoding. If the content of the rules file is stored, the base64 encoding encryption process is as follows:
  • the content can be stored in the rule file.
  • the base64 decoding can be used to obtain the plaintext of the function corresponding to the rule type saved in the pre-encryption rule file.
  • the content of the rule file is encrypted, the security of the rule file can be improved, and the function corresponding to the rule type stored in the rule file is protected.
  • S30 Perform the logic according to the rule, and process the original password by using at least one rule type to generate a target password.
  • the target password is the password that the user wants to obtain.
  • the target password is the original password uniquely owned by the user, and is obtained according to at least one rule type saved in the target rule file, and the original password is calculated and processed according to the rule execution logic corresponding to the target rule file. Further, the target password will be displayed in a limited time, that is, it needs to be regenerated after a preset period of time to be displayed, so as to ensure the security of the password. By simply remembering the original password, the user can reduce the memory burden of the user and improve the efficient management of the password.
  • the generated target password is unable to obtain the original password of the user by deciphering, and the original password is uniquely owned by the user, and the original password is generated according to the rule execution logic in the target rule file and the at least one rule type to generate the target password.
  • the security of the password users do not have to worry about the original password leaked out.
  • the custom rule password management method only saves the rule file without saving the user's original password. Even if the rule file is leaked, the rule setting is known by other users, and the user's original password cannot be obtained according to the rule file, so the password can be guaranteed. Management security.
  • the target rule identifier acquires a target rule file corresponding to the target rule identifier from at least one rule file, where the target rule file includes rule execution logic and at least one rule type.
  • the at least one rule type has an irreversible transformation rule type, and based on the rule execution logic and the at least one rule type, the diversity and high security of the password generated according to the target rule file can be ensured, and the problem that the password is easily leaked is effectively prevented.
  • Adding an irreversible transformation rule type to at least one rule type ensures that the password generated according to the rule setting cannot be decrypted by the reverse decryption to obtain the original password, thereby greatly improving the security of the rule setting and generating the password.
  • the user is also allowed to perform custom creation of rule types, which can effectively manage passwords and improve encryption security.
  • Creating and saving a corresponding at least one rule file according to at least one rule setting, encrypting content of the at least one rule file, and saving the encrypted at least one rule file in a database, and performing content of the at least one rule file Encryption can improve the security of the rule file and protect the type of rule corresponding to the function saved in the rule file.
  • the original password is processed by using at least one rule type to generate a target password. Under the basis of obtaining the target rule file (including rule execution logic and at least one rule type), only a unique original password is obtained.
  • the target password can be generated in real time according to the target rule file, and the password of the required account can be created according to the original password uniquely owned by the user, and the security of managing the password can be ensured by saving only the rule file without saving the original password. Achieve effective password management.
  • FIG. 6 is a schematic block diagram showing a custom rule password management apparatus corresponding to the custom rule password management method in the first embodiment.
  • the custom rule password management apparatus includes an identification password acquisition module 10, a target rule file acquisition module 20, and a target password generation module 30.
  • the implementation functions of the identification password acquisition module 10, the target rule file acquisition module 20, and the target password generation module 30 are in one-to-one correspondence with the steps corresponding to the custom rule password management method in the first embodiment. To avoid redundancy, the present embodiment is different. A detailed description.
  • the identifier password obtaining module 10 is configured to obtain a password generation instruction, and acquire the target rule identifier and the original password based on the password generation instruction.
  • the target rule file obtaining module 20 is configured to obtain, according to the target rule identifier, a target rule file corresponding to the target rule identifier from the at least one rule file, where the target rule file includes a rule execution logic and at least one rule type, at least one There are irreversible transformation rule types in the rule types.
  • the target password generating module 30 is configured to process the original password by using at least one rule type according to the rule execution logic to generate a target password.
  • the identification password acquisition module 10 includes an interface generation unit 11 and an identification password acquisition unit 12.
  • the interface generating unit 11 is configured to display an identifier obtaining interface and an original password obtaining interface according to the password generation instruction.
  • the identifier password obtaining unit 12 is configured to obtain the target rule identifier and the original password through the identifier obtaining interface and the original password interface.
  • the custom rule password management apparatus further includes a rule file creation and saving module 40, and the rule file creation and storage module 40 includes a rule setting acquisition unit 41 and a rule file creation and holding unit 42.
  • the rule setting obtaining unit 41 is configured to obtain at least one rule setting, where each rule setting includes a corresponding rule execution logic and at least one rule type, and the at least one rule type has an irreversible change rule type.
  • the rule file creation and holding unit 42 is configured to create and save the corresponding at least one rule file according to the at least one rule setting, and configure the rule file with a corresponding rule identifier.
  • the rule setting acquisition unit 41 includes a rule type acquisition sub-unit 411, a first rule setting acquisition sub-unit 412, and a second rule setting acquisition sub-unit 413.
  • the rule type obtaining sub-unit 411 is configured to obtain at least one preset rule type, and the irreversible transform rule type exists in the rule type.
  • the first rule setting acquisition sub-unit 412 is configured to: if the preset at least one rule type has a rule type required for the combination rule setting, perform a custom sorting combination on the rule type required for the combination rule setting, and obtain At least one rule setting.
  • the second rule setting acquisition sub-unit 413 is configured to: if the preset at least one rule type lacks the rule type set by the combination rule, create a rule type required for the combination rule setting, and perform the required rule type Customize the sort combination to get at least one rule setting.
  • the rule file creation holding unit 42 includes a rule file creation sub-unit 421 and a rule file encryption storage sub-unit 422.
  • the rule file creation subunit 421 is configured to create at least one rule file according to at least one rule setting.
  • the rule file encryption saving subunit 422 is configured to encrypt the content of the at least one rule file, and save the encrypted at least one rule file in the database.
  • the embodiment provides one or more non-volatile readable storage media having computer readable instructions that, when executed by one or more processors, cause the one or more processors to execute The method for managing the custom rule password in Embodiment 1 is implemented. To avoid repetition, details are not described herein again. Alternatively, when the computer readable instructions are executed by one or more processors, causing the one or more processors to perform the functions of implementing the modules/units in the custom rule password management device of Embodiment 2, in order to avoid duplication , no longer repeat them here.
  • Fig. 7 is a schematic diagram of a terminal device in this embodiment.
  • the terminal device 50 includes a processor 51, a memory 52, and computer readable instructions 53 stored in the memory 52 and operable on the processor 51.
  • the processor 51 implements the various steps of the custom rule password management method of Embodiment 1 when the computer readable instructions 53 are executed, such as steps S10, S20, and S30 shown in FIG.
  • the processor 51 executes the computer readable instructions 53
  • the functions of the modules/units of the custom rule password management apparatus in Embodiment 2 are implemented, as shown in FIG. 6, the identification password acquisition module 10, the target rule file acquisition module 20, and the target password.
  • the function of module 30 is generated.
  • computer readable instructions 53 may be partitioned into one or more modules/units, one or more modules/units being stored in memory 52 and executed by processor 51 to complete the application.
  • the one or more modules/units may be an instruction segment of a series of computer readable instructions 53 capable of performing a particular function, which is used to describe the execution of computer readable instructions 53 in the terminal device 50.
  • the computer readable instruction 53 can be divided into the identification password acquisition module 10, the target rule file acquisition module 20, and the target password generation module 30 in Embodiment 2, and the specific functions of each module are as shown in Embodiment 2, in order to avoid duplication. I will not repeat them here.
  • the terminal device 50 can be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server.
  • the terminal device may include, but is not limited to, the processor 51 and the memory 52. It will be understood by those skilled in the art that FIG. 7 is only an example of the terminal device 50, and does not constitute a limitation of the terminal device 50, and may include more or less components than those illustrated, or combine some components, or different components.
  • the terminal device may further include an input/output device, a network access device, a bus, and the like.
  • the processor 51 may be a central processing unit (CPU), or may be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 52 may be an internal storage unit of the terminal device 50, such as a hard disk or a memory of the terminal device 50.
  • the memory 52 may also be an external storage device of the terminal device 50, such as a plug-in hard disk provided on the terminal device 50, a smart memory card (SMC), a Secure Digital (SD) card, and a flash memory card (Flash). Card) and so on.
  • the memory 52 may also include both an internal storage unit of the terminal device 50 and an external storage device.
  • the memory 52 is used to store computer readable instructions 53 and other programs and data required by the terminal device.
  • the memory 52 can also be used to temporarily store data that has been or will be output.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated modules/units if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the processes in the foregoing embodiments, and may also be implemented by computer readable instructions 53 for storing related computer hardware.
  • the computer readable instructions 53 may be stored in a computer readable In the storage medium, the computer readable instructions 53, when executed by the processor, may implement the steps of the various method embodiments described above.
  • the computer readable instructions 53 comprise code of computer readable instructions, the code of which may be in the form of source code, in the form of an object code, an executable file or some intermediate form or the like.
  • the computer readable medium can include any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a removable hard drive, a magnetic disk, an optical disk, a computer memory, a read only memory (ROM, Read-Only) Memory), random access memory (RAM), electrical carrier signals, telecommunications signals, and software distribution media.
  • a recording medium a USB flash drive
  • a removable hard drive a magnetic disk, an optical disk
  • a computer memory a read only memory (ROM, Read-Only) Memory
  • RAM random access memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Storage Device Security (AREA)

Abstract

本申请公开了一种自定义规则密码管理方法、装置、终端设备及存储介质。该自定义规则密码管理方法，包括：获取密码生成指令，基于所述密码生成指令获取目标规则标识和原始密码；基于所述目标规则标识，从至少一个规则文件中获取与所述目标规则标识相对应的目标规则文件，其中，所述目标规则文件包括规则执行逻辑和至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；依据所述规则执行逻辑，采用至少一种所述规则类型对所述原始密码进行处理，生成目标密码。采用该自定义规则密码管理方法管理用户密码时，能够根据用户唯一的原始密码实现对多个账号密码的管理，并且保证密码管理的安全性。

Description

自定义规则密码管理方法、装置、终端设备及存储介质
本申请以2018年3月22日提交的申请号为201810242166.2，名称为“自定义规则密码管理方法、装置、终端设备及存储介质”的中国专利申请为基础，并要求其优先权。
技术领域
本申请涉及计算机领域，尤其涉及一种自定义规则密码管理方法、装置、终端设备及存储介质。
背景技术
当前各种支付方式，如支付宝、微信支付和银行卡等，一般都采用6位数字的验证方式作为支付密码。但是当用户全部使用一套相同的密码时，其风险太大，极易造成密码的泄露；若用户使用不同的密码时，又常常忘记密码，不能对用户密码进行有效的管理。
发明内容
本申请实施例提供一种自定义规则密码管理方法、装置、终端设备及存储介质，以解决当前用户密码容易泄露和被破译的问题。
第一方面，本申请实施例提供一种自定义规则密码管理方法，包括：
获取密码生成指令，基于所述密码生成指令获取目标规则标识和原始密码；
基于所述目标规则标识，从至少一个规则文件中获取与所述目标规则标识相对应的目标规则文件，其中，所述目标规则文件包括规则执行逻辑和至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；
依据所述规则执行逻辑，采用至少一种所述规则类型对所述原始密码进行处理，生成目标密码。
第二方面，本申请实施例提供一种自定义规则密码管理装置，包括：
标识密码获取模块，用于获取密码生成指令，基于所述密码生成指令获取目标规则标识和原始密码；
目标规则文件获取模块，用于基于所述目标规则标识，从至少一个规则文件中获取与所述目标规则标识相对应的目标规则文件，其中，所述目标规则文件包括规则执行逻辑和 至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；
目标密码生成模块，用于依据所述规则执行逻辑，采用至少一种所述规则类型对所述原始密码进行处理，生成目标密码。
第三方面，本申请实施例提供一种终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
获取密码生成指令，基于所述密码生成指令获取目标规则标识和原始密码；
基于所述目标规则标识，从至少一个规则文件中获取与所述目标规则标识相对应的目标规则文件，其中，所述目标规则文件包括规则执行逻辑和至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；
依据所述规则执行逻辑，采用至少一种所述规则类型对所述原始密码进行处理，生成目标密码。
第四方面，本申请实施例提供一个或多个存储有计算机可读指令的非易失性可读存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如下步骤：
获取密码生成指令，基于所述密码生成指令获取目标规则标识和原始密码；
基于所述目标规则标识，从至少一个规则文件中获取与所述目标规则标识相对应的目标规则文件，其中，所述目标规则文件包括规则执行逻辑和至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；
依据所述规则执行逻辑，采用至少一种所述规则类型对所述原始密码进行处理，生成目标密码。
本申请的一个或多个实施例的细节在下面的附图和描述中提出，本申请的其他特征和优点将从说明书、附图以及权利要求变得明显。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例的描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施例1中自定义规则密码管理方法的一流程图。
图2是图1中步骤S10的一具体流程图。
图3是图1中步骤S20之前的一具体流程图。
图4是图3中步骤S21的一具体流程图。
图5是图3中步骤S22的一具体流程图。
图6是本申请实施例2中自定义规则密码管理装置的一原理框图。
图7是本申请实施例4中终端设备的一示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
实施例1
图1示出本实施例中自定义规则密码管理方法的一流程图。该自定义规则密码管理方法可应用在应用程序中，能够根据用户唯一的原始密码和在数据库中保存的规则文件实时计算出与规则文件相对应的密码，有效实现用户的密码管理，该自定义规则密码管理方法具体可应用在安装在终端设备上的应用程序中。其中，该终端设备是可与用户进行人机交互的设备，包括但不限于电脑、智能手机和平板等设备。如图1所示，该自定义规则密码管理方法包括如下步骤：
S10：获取密码生成指令，基于密码生成指令获取目标规则标识和原始密码。
其中，密码生成指令是指用于获取目标规则标识和原始密码的指令。目标规则标识是指用于唯一识别目标规则文件的标识。目标规则文件是指用户想要获取的规则文件，规则文件是指保存规则设定的存储载体，具体可以是以文本格式的文件(.txt)形式保存，该文本格式的文件存储着按一定逻辑排序组合的(即规则执行逻辑)与规则类型相对应的函数，应用程序通过调用规则文件，执行规则文件中的函数，实现对原始密码的加密。原始密码是指是指用户唯一使用的密码，在该自定义规则密码管理方法中，用户只需要唯一记住原始密码就足够了。
本实施例中，在实现自定义规则密码管理的应用程序(以下简称应用程序)中，应用程序获取用户输入的密码生成指令，能够基于该密码生成指令快速、便捷地获取到目标规则标识和原始密码。
在一具体实施方式中，步骤S10中，如图2所示，获取密码生成指令，基于密码生成指令获取目标规则标识和原始密码，包括如下步骤：
S11：根据密码生成指令显示标识获取界面和原始密码获取界面。
其中，标识获取界面是指应用程序终端上显示的用于获取目标规则标识的界面，原始密码获取界面是指应用程序终端显示器上显示的用于获取原始密码的界面，标识获取界面和原始密码获取界面包括但不限于通过按键输入、语音输入等方式获取到相应的目标规则标识和原始密码。
本实施例中，应用程序获取用户输入的密码生成指令后在终端显示器上显示标识获取界面和原始密码获取界面，以提供获取用户输入信息的界面平台，顺利获取用户输入的目标规则标识和原始密码。
S12：通过标识获取界面和原始密码界面获取目标规则标识和原始密码。
本实施例中，应用程序可以提供按键输入、语音输入等录入信息的方式通过标识获取界面和原始密码界面获取用户输入的目标规则标识和原始密码。
S20：基于目标规则标识，从至少一个规则文件中获取与目标规则标识相对应的目标规则文件，其中，目标规则文件包括规则执行逻辑和至少一种规则类型，至少一种规则类型中存在不可逆变换规则类型。
其中，规则执行逻辑是指规则类型对应的函数在规则设定中执行的顺序。规则类型是指对密码进行加密的运算规则的类型。从规则类型的概念可以自然、简易地理解规则设定的概念：规则设定是指由至少一种规则类型以自定义排序方式(也即规则执行逻辑)组合而成的规则类型的集合，从在开发平台创建规则设定的角度看，其实就是由至少一种规则类型对应的函数按自定义排序方式组合而成的运算程序。不可逆变换规则类型是指通过该规则类型加密后的值是不能反向推导、破译出加密前的值的规则类型。
本实施例中，基于目标规则标识，例如将规则文件ID作为目标规则标识，用户想要通过登录密码登录平安车险、平安寿险和平安产险的多个账号时，需要在应用程序通过规则文件ID(如平安车险、平安寿险和平安产险)查询获取已保存的目标规则文件(如平安车险.rule、平安寿险.rule和平安产险.rule)，以根据获取的目标规则文件获取规则文件ID为平安车险、平安寿险和平安产险的账号对应的登录密码。
在一具体实施方式中，步骤S20中，如图3所示，在基于目标规则标识，从至少一个规则文件中获取与目标规则标识相对应的目标规则文件的步骤之前，该自定义规则密码管理方法还包括：预先创建并保存至少一个规则文件。
该预先创建并保存至少一个规则文件的步骤包括：
S21：获取至少一种规则设定，每一规则设定包括相对应的规则执行逻辑和至少一种规则类型，至少一种规则类型中存在不可逆变换规则类型。
在创建规则设定的过程中，一种规则类型可以用相对应的函数来实现和表示，例如：用add(pwd,num)函数表示其中的一种规则类型，该规则类型表示的是一种加法运算规则，其中，pwd表示当前密码，num表示该加法运算中增加的数值，当num取123456时，即函数表示为add(pwd，123456)时，该加法运算规则的具体运算过程为pwd+123456(即在当前密码的基础上加上123456)。
可以理解地，当有三种规则类型A()、B()和C()时，对这三种规则类型按照规则执行逻辑(自定义排序)进行组合可以得到6种不同的规则设定。当规则类型的运算更为复杂、规则类型的数量越多时，规则设定的种类就越多样，则根据规则设定计算获取的密码也越多样，加密的安全性就越高。
不可逆变换规则类型是指通过该规则类型加密后的值是不能反向推导、破译出加密前的值的规则类型，例如：采用基于MD5加密的截取法，首先对原始密码进行MD5加密，假设原始密码为123456，则采用基于MD5加密的截取法加密后的值可表示为32位16进制数“E10ADC3949BA59ABBE56E057F20F883E”，截取前十位“E10ADC3949”，转化为10进制数“966549846345”，再截取后六位得到“846345”，由截取后的值846345是无法逆向还原为123456的。除基于MD5加密的截取法，采用其他不可逆变换规则类型也是可以的，如采用SHA-1(安全散列算法中的一种)加密的截取法等不可逆变换规则类型。
本实施例中，获取至少一种规则设定，该规则设定包括相对应的规则执行逻辑和至少一种规则类型，每一规则设定的至少一种规则类型中存在至少一种不可逆变换规则类型，说明该规则设定的至少一种规则类型可以全部是不可逆变换规则类型，也可以同时包括至少一个不可逆变换规则类型和其他规则类型。通过相对应的规则执行逻辑(也即对规则类型的自定义排序组合)和至少一种规则类型获取的规则设定能够保证根据规则设定生成的密码具有多样性和高安全性的特点，能够有效防止密码泄露的问题。在至少一种规则类型中存在不可逆变换规则类型，可以保证根据规则设定生成的密码无法通过反向推导、破译的方式获取原始密码，极大提高原始密码的安全性。
在一具体实施方式中，步骤S21中，如图4所示，获取至少一种规则设定，每一规则设定包括相对应的规则执行逻辑和至少一种规则类型，至少一种规则类型中存在不可逆变换规则类型，包括如下步骤：
S211：获取预设的至少一种规则类型，规则类型中存在不可逆变换规则类型。
在实现自定义规则密码管理的应用程序中，会预先设置一些基础、常用的规则类型，例如在通常情况下，只是对以6位数字表示的原始密码进行加密转换，并且加密前和加密后的密码都是以6位数字的形式表示，则规则类型可以根据6位数字的特点预先设置相应的运算。不可逆变换规则类型是组成任何规则设定所不能缺少的一类规则类型，因此在预设规则类型时，也同样需要预设不可逆变换规则类型。
本实施例中，获取预先设置并保存在数据库中的至少一种规则类型，并且该至少一种规则类型中应存在不可逆变换规则类型，可以根据预设的规则类型判断该预设的规则类型是否满足组合规则设定的需求。
S212：若预设的至少一种规则类型存在组合规则设定所需的规则类型，则对组合规则设定所需的规则类型进行自定义排序组合，获取至少一种规则设定。
本实施例中，在获取预先设置的至少一种规则类型后，根据规则设定的实际需求，判断预设的至少一种规则类型是否存在组合规则设定所需的规则类型。若预设的至少一种规则类型存在组合规则设定所需的规则类型，则对组合规则设定所需的规则类型进行自定义排序组合，获取至少一种规则设定。例如：有规则类型add(pwd,num)、invert(pwd)和MD5(6)(pwd)三种规则类型(其中，invert()指反转运算，该反转运算在这里具体运算规则为：如有数值111111，则反转运算为1000000-111111；MD5(6)表示基于MD5加密的截取法，最终截取的值为后6位)时，可以根据该三种规则类型进行自定义的排序并组合，由
Figure PCTCN2018094189-appb-000001
(规定0！为1)能够得到6种不同的规则设定。具体地，如采用invert(pwd)、add(pwd,num)和MD5(pwd)的组合方式运算，当pwd＝888888，num＝12344时，得到的结果为“846345”，具体运算过程如下：
1)invert->1000000-888888＝111112
2)add 12344->111112+12344＝123456
3)MD5(6)123456->846345
通过从预设的至少一种规则类型中对组合规则设定所需的规则类型进行自定义排序组合，能够得到多种规则设定，用户可以根据不同的规则类型进行自定义规则密码管理，能够实现对密码的有效管理，提高加密的安全性。
需要说明的是，规则类型是对用户公开的，用户能够知道规则类型具体是怎样进行加密运算的，能够减少用户对规则类型不透明的担忧，并且用户还可以根据公开的规则类型 进行运算和检验，而不需完全借助于应用程序本身，可以进一步提高密码管理的安全性和可靠性。
S213：若预设的至少一种规则类型缺少组合规则设定的规则类型，则创建组合规则设定所需的规则类型，并对所需的规则类型进行自定义排序组合，获取至少一种规则设定。
本实施例中，在获取预先设置的至少一种规则类型后，根据规则设定的实际需求，判断预设的至少一种规则类型是否存在组合规则设定所需的规则类型。若预设的至少一种规则类型缺少组合规则设定的规则类型，例如，规则设定要求能够对出现字母的原始密码进行处理，假设原始密码为zls123，则当预设的规则类型如add(pwd，123456)对原始密码zls123进行加密运算时，zls123+123456将无法对密码中的字母进行处理。因此，需要创建能够解决字母问题的组合规则设定所需的规则类型。对于原始密码为zls123，要求能够对字母进行处理的，可以直接创建新的规则类型，或者在原来add(pwd，123456)等规则类型的基础上进行编辑修改后再另存为新的符合组合规则设定所需的规则类型。例如，在add(pwd，123456)的基础上，再添加一种运算情况：令a+1＝b,b+1＝c，……，z+1＝a。则原始密码为zls123时，采用该新的规则类型直接对原始密码zls123进行运算能够得到anv579，并再结合其他符合组成规则设定的规则类型(包括至少一种不可逆变换规则类型)进行自定义排序组合，能够得到相应的规则设定。本实施例中只是举了简单的例子，在实际应用中会采用更复杂、更多的规则类型对原始密码进行加密处理，以进一步地提高加密的安全性。
另外，在实际应用中，每次都创建新的规则类型是比较耗费时间的，因此除了用户通过自身创建规则类型的方式外，还可以在规则类型库中直接选取符合需求的规则类型，并将该规则类型下载到本地规则类型库中。该规则类型库保存大量的多种不同需求的规则类型，供用户使用。需要说明的是，由于组成规则设定的规则类型中存在至少一种不可逆变换规则类型，因此允许用户采用相同的规则设定，该做法不会造成用户原始密码的泄露，能够提高规则设定使用的灵活性。
需要说明的是，步骤S211-S213中“规则类型自定义排序组合”即“规则执行逻辑”，可以理解地，对规则类型自定义排序组合相当于规则设定中规则类型对应的函数在应用程序时执行的逻辑顺序。
S22：根据至少一种规则设定创建并保存相对应的至少一个规则文件，并给规则文件配置相应的规则标识。
本实施例中，根据至少一种规则设定创建相对应的至少一个规则文件，将规则文件保 存在数据库中，并给规则文件配置相应的规则标识，使得用户能够通过应用程序根据规则标识(用于唯一识别规则文件的标识)快速地调用规则文件，并根据规则文件执行加密运算。
在一具体实施方式中，步骤S22中，如图5所示，根据至少一种规则设定创建并保存相对应的至少一个规则文件，并给规则文件配置相应的规则标识，包括如下步骤：
S221：根据至少一种规则设定创建至少一个规则文件。
本实施例中，根据至少一种规则设定，创建相对应的至少一个规则文件，该规则文件以明文方式保存有按一定逻辑排序组合的与规则类型相对应的函数。
S222：对至少一个规则文件的内容进行加密，并将加密后的至少一个规则文件保存在数据库中。
本实施例中，虽然规则类型对用户是公开的，但是对于其他用户并不希望是公开的(除了在规则类型库中共享的)，因此，规则文件中的内容，即规则类型对应的函数应当进行加密处理，具体的加密处理方式可以采用base64编码的方式实现。若存储规则文件的内容，base64编码加密过程如下：
add(pwd，123456)
Invert(pwd)
MD5(pwd)
进行base64编码：
得到：
“YWRkIO+8iHB3ZO+8jDEyMzQ1Nu+8iQpJbnZlcnTvvIhwd2TvvIkKTUQ177yIcHdk77yJ”。
编码后将内容存入规则文件中即可，在后续使用该规则文件的时候，只要进行base64解码即可获取加密前规则文件保存的规则类型对应的函数的明文。本实施例中，将规则文件的内容进行加密，可以提高规则文件的安全性，保护保存在规则文件中规则类型对应的函数。
S30：依据规则执行逻辑，采用至少一种规则类型对原始密码进行处理，生成目标密码。
目标密码是指用户想要获取的密码。本实施例中，目标密码为用户唯一拥有的原始密码，依据目标规则文件中保存的至少一种规则类型，并根据该目标规则文件对应的规则执行逻辑对原始密码进行计算处理后获取。进一步地，该目标密码将限时地显示，即在一预设时间段后需要重新生成才可显示出来，以保证密码的安全性。通过用户只需记住原始密 码的方式，能够减轻用户的记忆负担，提高对于密码的高效管理。并且，生成的目标密码是无法通过破译从而获取用户的原始密码的，该基于用户唯一拥有的原始密码，并根据目标规则文件中规则执行逻辑和至少一种规则类型生成目标密码的方式保证了原始密码的安全性，用户不用担心原始密码泄露出去。
特别地，该自定义规则密码管理方法只保存规则文件而不保存用户的原始密码，即使规则文件泄露，规则设定被其他用户获知，也无法根据规则文件得到用户的原始密码，因此能够保证密码管理的安全性。
本实施例所提供的自定义规则密码管理方法中，目标规则标识从至少一个规则文件中获取与目标规则标识相对应的目标规则文件，其中，目标规则文件包括规则执行逻辑和至少一种规则类型，至少一种规则类型中存在不可逆变换规则类型，基于规则执行逻辑和至少一种规则类型，能够保证根据目标规则文件生成的密码的多样性和高安全性，有效防止密码容易泄露的问题。在至少一种规则类型中加入不可逆变换规则类型，可以保证根据规则设定生成的密码将无法通过反向破译从而获取原始密码，极大提高规则设定生成密码的安全性。此外，还支持用户进行规则类型的自定义创建，能够实现对密码的有效管理，提高加密的安全性。根据至少一种规则设定创建并保存相对应的至少一个规则文件，对至少一个规则文件的内容进行加密，并将加密后的至少一个规则文件保存在数据库中，将至少一个规则文件的内容进行加密，可以提高规则文件的安全性，保护保存在规则文件中函数对应的规则类型。依据规则执行逻辑，采用至少一种规则类型对原始密码进行处理，生成目标密码，在获取目标规则文件(包括规则执行逻辑和至少一种规则类型)的基础下，只需获取唯一的原始密码即可根据目标规则文件实时生成目标密码，能够根据用户唯一拥有的原始密码创建所需账号的密码，并且通过只保存规则文件而不保存原始密码的方式，能够保证对密码进行管理时的安全性，实现有效的密码管理。
应理解，上述实施例中各步骤的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
实施例2
图6示出与实施例1中自定义规则密码管理方法一一对应的自定义规则密码管理装置的原理框图。如图6所示，该自定义规则密码管理装置包括标识密码获取模块10、目标规则文件获取模块20和目标密码生成模块30。其中，标识密码获取模块10、目标规则文件获取模块20和目标密码生成模块30的实现功能与实施例1中自定义规则密码管理方法对应的步骤一一对应，为避免赘述，本实施例不一一详述。
标识密码获取模块10，用于获取密码生成指令，基于密码生成指令获取目标规则标识和原始密码。
目标规则文件获取模块20，用于基于目标规则标识，从至少一个规则文件中获取与目标规则标识相对应的目标规则文件，其中，目标规则文件包括规则执行逻辑和至少一种规则类型，至少一种规则类型中存在不可逆变换规则类型。
目标密码生成模块30，用于依据规则执行逻辑，采用至少一种规则类型对原始密码进行处理，生成目标密码。
优选地，标识密码获取模块10包括界面生成单元11和标识密码获取单元12。
界面生成单元11，用于根据密码生成指令显示标识获取界面和原始密码获取界面。
标识密码获取单元12，用于通过标识获取界面和原始密码界面获取目标规则标识和原始密码。
优选地，该自定义规则密码管理装置还包括规则文件创建保存模块40，规则文件创建保存模块40包括规则设定获取单元41和规则文件创建保存单元42。
规则设定获取单元41，用于获取至少一种规则设定，每一规则设定包括相对应的规则执行逻辑和至少一种规则类型，至少一种规则类型中存在不可逆变换规则类型。
规则文件创建保存单元42，用于根据至少一种规则设定创建并保存相对应的至少一个规则文件，并给规则文件配置相应的规则标识。
优选地，规则设定获取单元41包括规则类型获取子单元411、第一规则设定获取子单元412和第二规则设定获取子单元413。
规则类型获取子单元411，用于获取预设的至少一种规则类型，规则类型中存在不可逆变换规则类型。
第一规则设定获取子单元412，用于若预设的至少一种规则类型存在组合规则设定所需的规则类型，则对组合规则设定所需的规则类型进行自定义排序组合，获取至少一种规则设定。
第二规则设定获取子单元413，用于若预设的至少一种规则类型缺少组合规则设定的规则类型，则创建组合规则设定所需的规则类型，并对所需的规则类型进行自定义排序组合，获取至少一种规则设定。
优选地，规则文件创建保存单元42包括规则文件创建子单元421和规则文件加密保存子单元422。
规则文件创建子单元421，用于根据至少一种规则设定创建至少一个规则文件。
规则文件加密保存子单元422，用于对至少一个规则文件的内容进行加密，并将加密后的至少一个规则文件保存在数据库中。
实施例3
本实施例提供一个或多个存储有计算机可读指令的非易失性可读存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行实现实施例1中自定义规则密码管理方法，为避免重复，这里不再赘述。或者，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行实现实施例2中自定义规则密码管理装置中各模块/单元的功能，为避免重复，这里不再赘述。
实施例4
图7是本实施例中终端设备的示意图。如图7所示，终端设备50包括处理器51、存储器52以及存储在存储器52中并可在处理器51上运行的计算机可读指令53。处理器51执行计算机可读指令53时实现实施例1中自定义规则密码管理方法的各个步骤，例如图1所示的步骤S10、S20和S30。或者，处理器51执行计算机可读指令53时实现实施例2中自定义规则密码管理装置各模块/单元的功能，如图6所示标识密码获取模块10、目标规则文件获取模块20和目标密码生成模块30的功能。
示例性的，计算机可读指令53可以被分割成一个或多个模块/单元，一个或者多个模块/单元被存储在存储器52中，并由处理器51执行，以完成本申请。一个或多个模块/单元可以是能够完成特定功能的一系列计算机可读指令53的指令段，该指令段用于描述计算机可读指令53在终端设备50中的执行过程。例如，计算机可读指令53可被分割成实施例2中的标识密码获取模块10、目标规则文件获取模块20和目标密码生成模块30，各模块的具体功能如实施例2所示，为避免重复，此处不一一赘述。
终端设备50可以是桌上型计算机、笔记本、掌上电脑及云端服务器等计算设备。终端设备可包括，但不仅限于，处理器51、存储器52。本领域技术人员可以理解，图7仅仅是终端设备50的示例，并不构成对终端设备50的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件，例如终端设备还可以包括输入输出设备、网络接入设备、总线等。
所称处理器51可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管 逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
存储器52可以是终端设备50的内部存储单元，例如终端设备50的硬盘或内存。存储器52也可以是终端设备50的外部存储设备，例如终端设备50上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。进一步地，存储器52还可以既包括终端设备50的内部存储单元也包括外部存储设备。存储器52用于存储计算机可读指令53以及终端设备所需的其他程序和数据。存储器52还可以用于暂时地存储已经输出或者将要输出的数据。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，仅以上述各功能单元、模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能单元、模块完成，即将所述装置的内部结构划分成不同的功能单元或模块，以完成以上描述的全部或者部分功能。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的模块/单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实现上述实施例方法中的全部或部分流程，也可以通过计算机可读指令53来指令相关的硬件来完成，所述的计算机可读指令53可存储于一计算机可读存储介质中，该计算机可读指令53在被处理器执行时，可实现上述各个方法实施例的步骤。其中，所述计算机可读指令53包括计算机可读指令的代码，所述计算机可读指令的代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。所述计算机可读介质可以包括：能够携带所述计算机可读指令代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、电载波信号、电信信号以及软件分发介质等。需要说明的是，所述计算机可读介质包含的内容可以根据司法管辖区内立法和专利实践的要求进行适当的增减，例如在某些司法管辖区，根据立法和专利实践，计算机可读介质不包括是电载波信号和电信信号。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者 替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种自定义规则密码管理方法，其特征在于，包括：
    获取密码生成指令，基于所述密码生成指令获取目标规则标识和原始密码；
    基于所述目标规则标识，从至少一个规则文件中获取与所述目标规则标识相对应的目标规则文件，其中，所述目标规则文件包括规则执行逻辑和至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；
    依据所述规则执行逻辑，采用至少一种所述规则类型对所述原始密码进行处理，生成目标密码。
  2. 根据权利要求1所述的自定义规则密码管理方法，其特征在于，在所述基于所述目标规则标识，从至少一个规则文件中获取与所述目标规则标识相对应的目标规则文件的步骤之前，所述自定义规则密码管理方法还包括：预先创建并保存至少一个规则文件；
    所述预先创建并保存至少一个规则文件的步骤包括：
    获取至少一种规则设定，每一所述规则设定包括相对应的规则执行逻辑和至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；
    根据至少一种所述规则设定创建并保存相对应的至少一个规则文件，并给所述规则文件配置相应的规则标识。
  3. 根据权利要求2所述的自定义规则密码管理方法，其特征在于，所述获取至少一种规则设定，包括：
    获取预设的至少一种规则类型，所述规则类型中存在不可逆变换规则类型；
    若所述预设的至少一种规则类型存在组合所述规则设定所需的规则类型，则对组合所述规则设定所需的规则类型进行自定义排序组合，获取至少一种所述规则设定；
    若所述预设的至少一种规则类型缺少组合所述规则设定所述的规则类型，则创建组合所述规则设定所需的规则类型，并对所述所需的规则类型进行自定义排序组合，获取至少一种所述规则设定。
  4. 根据权利要求2所述的自定义规则密码管理方法，其特征在于，所述根据至少一种所述规则设定创建并保存相对应的至少一个规则文件，包括：
    根据至少一种所述规则设定创建至少一个所述规则文件；
    对至少一个所述规则文件的内容进行加密，并将加密后的至少一个所述规则文件保存在数据库中。
  5. 根据权利要求1所述的自定义规则密码管理方法，其特征在于，所述基于所述密码生成指令获取目标规则标识和原始密码，包括：
    根据所述密码生成指令显示标识获取界面和原始密码获取界面；
    通过所述标识获取界面和原始密码界面获取所述目标规则标识和所述原始密码。
  6. 一种自定义规则密码管理装置，其特征在于，包括：
    标识密码获取模块，用于获取密码生成指令，基于所述密码生成指令获取目标规则标识和原始密码；
    目标规则文件获取模块，用于基于所述目标规则标识，从至少一个规则文件中获取与所述目标规则标识相对应的目标规则文件，其中，所述目标规则文件包括规则执行逻辑和至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；
    目标密码生成模块，用于依据所述规则执行逻辑，采用至少一种所述规则类型对所述原始密码进行处理，生成目标密码。
  7. 根据权利要求6所述的自定义规则密码管理装置，其特征在于，所述自定义规则密码管理装置还包括规则文件创建保存模块，用于预先创建并保存至少一个规则文件；
    所述规则文件创建保存模块包括：
    规则设定获取单元，用于获取至少一种规则设定，每一所述规则设定包括相对应的规则执行逻辑和至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；
    规则文件创建保存单元，用于根据至少一种所述规则设定创建并保存相对应的至少一个规则文件，并给所述规则文件配置相应的规则标识。
  8. 根据权利要求7所述的自定义规则密码管理装置，其特征在于，所述规则设定获取单元包括：
    预设规则类型获取子单元，用于获取预设的至少一种规则类型，所述规则类型中存在不可逆变换规则类型；
    第一规则设定获取子单元，用于若所述预设的至少一种规则类型存在组合所述规则设定所需的规则类型，则对组合所述规则设定所需的规则类型进行自定义排序组合，获取至少一种所述规则设定；
    第二规则设定获取子单元，用于若所述预设的至少一种规则类型缺少组合所述规则设定所述的规则类型，则创建组合所述规则设定所需的规则类型，并对所述所需的规则类型进行自定义排序组合，获取至少一种所述规则设定。
  9. 根据权利要求7所述的自定义规则密码管理装置，其特征在于，所述规则文件创建 保存单元，包括：
    规则文件创建子单元，用于根据至少一种所述规则设定创建至少一个所述规则文件；
    规则文件加密保存子单元，用于对至少一个所述规则文件的内容进行加密，并将加密后的至少一个所述规则文件保存在数据库中。
  10. 根据权利要求6所述的自定义规则密码管理装置，其特征在于，所述标识密码获取模块，包括：
    界面生成单元，用于根据所述密码生成指令显示标识获取界面和原始密码获取界面；
    标识密码获取单元，用于通过所述标识获取界面和原始密码界面获取所述目标规则标识和所述原始密码。
  11. 一种终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现如下步骤：
    获取密码生成指令，基于所述密码生成指令获取目标规则标识和原始密码；
    基于所述目标规则标识，从至少一个规则文件中获取与所述目标规则标识相对应的目标规则文件，其中，所述目标规则文件包括规则执行逻辑和至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；
    依据所述规则执行逻辑，采用至少一种所述规则类型对所述原始密码进行处理，生成目标密码。
  12. 根据权利要求11所述的终端设备，其特征在于，在所述基于所述目标规则标识，从至少一个规则文件中获取与所述目标规则标识相对应的目标规则文件的步骤之前，所述处理器执行所述计算机可读指令时还实现如下步骤：预先创建并保存至少一个规则文件；
    所述预先创建并保存至少一个规则文件的步骤包括：
    获取至少一种规则设定，每一所述规则设定包括相对应的规则执行逻辑和至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；
    根据至少一种所述规则设定创建并保存相对应的至少一个规则文件，并给所述规则文件配置相应的规则标识。
  13. 根据权利要求12所述的终端设备，其特征在于，所述获取至少一种规则设定，包括：
    获取预设的至少一种规则类型，所述规则类型中存在不可逆变换规则类型；
    若所述预设的至少一种规则类型存在组合所述规则设定所需的规则类型，则对组合所 述规则设定所需的规则类型进行自定义排序组合，获取至少一种所述规则设定；
    若所述预设的至少一种规则类型缺少组合所述规则设定所述的规则类型，则创建组合所述规则设定所需的规则类型，并对所述所需的规则类型进行自定义排序组合，获取至少一种所述规则设定。
  14. 根据权利要求12所述的终端设备，其特征在于，所述根据至少一种所述规则设定创建并保存相对应的至少一个规则文件，包括：
    根据至少一种所述规则设定创建至少一个所述规则文件；
    对至少一个所述规则文件的内容进行加密，并将加密后的至少一个所述规则文件保存在数据库中。
  15. 根据权利要求11所述的终端设备，其特征在于，所述基于所述密码生成指令获取目标规则标识和原始密码，包括：
    根据所述密码生成指令显示标识获取界面和原始密码获取界面；
    通过所述标识获取界面和原始密码界面获取所述目标规则标识和所述原始密码。
  16. 一个或多个存储有计算机可读指令的非易失性可读存储介质，其特征在于，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如下步骤：
    获取密码生成指令，基于所述密码生成指令获取目标规则标识和原始密码；
    基于所述目标规则标识，从至少一个规则文件中获取与所述目标规则标识相对应的目标规则文件，其中，所述目标规则文件包括规则执行逻辑和至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；
    依据所述规则执行逻辑，采用至少一种所述规则类型对所述原始密码进行处理，生成目标密码。
  17. 根据权利要求16所述的非易失性可读存储介质，其特征在于，在所述基于所述目标规则标识，从至少一个规则文件中获取与所述目标规则标识相对应的目标规则文件的步骤之前，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器还执行如下步骤：预先创建并保存至少一个规则文件；
    所述预先创建并保存至少一个规则文件的步骤包括：
    获取至少一种规则设定，每一所述规则设定包括相对应的规则执行逻辑和至少一种规则类型，至少一种所述规则类型中存在不可逆变换规则类型；
    根据至少一种所述规则设定创建并保存相对应的至少一个规则文件，并给所述规则文件配置相应的规则标识。
  18. 根据权利要求17所述的非易失性可读存储介质，其特征在于，所述获取至少一种规则设定，包括：
    获取预设的至少一种规则类型，所述规则类型中存在不可逆变换规则类型；
    若所述预设的至少一种规则类型存在组合所述规则设定所需的规则类型，则对组合所述规则设定所需的规则类型进行自定义排序组合，获取至少一种所述规则设定；
    若所述预设的至少一种规则类型缺少组合所述规则设定所述的规则类型，则创建组合所述规则设定所需的规则类型，并对所述所需的规则类型进行自定义排序组合，获取至少一种所述规则设定。
  19. 根据权利要求17所述的非易失性可读存储介质，其特征在于，所述根据至少一种所述规则设定创建并保存相对应的至少一个规则文件，包括：
    根据至少一种所述规则设定创建至少一个所述规则文件；
    对至少一个所述规则文件的内容进行加密，并将加密后的至少一个所述规则文件保存在数据库中。
  20. 根据权利要求16所述的非易失性可读存储介质，其特征在于，所述基于所述密码生成指令获取目标规则标识和原始密码，包括：
    根据所述密码生成指令显示标识获取界面和原始密码获取界面；
    通过所述标识获取界面和原始密码界面获取所述目标规则标识和所述原始密码。
PCT/CN2018/094189 2018-03-22 2018-07-03 自定义规则密码管理方法、装置、终端设备及存储介质 WO2019178981A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810242166.2 2018-03-22
CN201810242166.2A CN108537038A (zh) 2018-03-22 2018-03-22 自定义规则密码管理方法、装置、终端设备及存储介质

Publications (1)

Publication Number Publication Date
WO2019178981A1 true WO2019178981A1 (zh) 2019-09-26

Family

ID=63483709

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/094189 WO2019178981A1 (zh) 2018-03-22 2018-07-03 自定义规则密码管理方法、装置、终端设备及存储介质

Country Status (2)

Country Link
CN (1) CN108537038A (zh)
WO (1) WO2019178981A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111130774A (zh) * 2019-12-26 2020-05-08 北京阿尔山区块链联盟科技有限公司 密码生成方法、装置和设备
CN111597547B (zh) * 2020-05-26 2023-04-28 中国联合网络通信集团有限公司 一种密码管理的方法和***
CN112115656B (zh) * 2020-09-23 2024-06-14 恒为科技（上海）股份有限公司 一种快速设置内存条约束的方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102316120A (zh) * 2011-10-17 2012-01-11 北京信息科技大学 基于网络隐私保护的动态密码锁
CN105989309A (zh) * 2015-02-17 2016-10-05 汪风珍 一种密码
US20170083699A1 (en) * 2015-09-23 2017-03-23 Charter Communications Operating, Llc Dynamic inline assistance messaging
CN106888086A (zh) * 2017-02-13 2017-06-23 上海瀚之友信息技术服务有限公司 一种管理账号密码的***及方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101434447B1 (ko) * 2013-09-13 2014-08-27 제이슨 준 이 동적 조합 비밀번호를 이용한 사용자 인증 장치 및 사용자 인증 방법
CN106411516B (zh) * 2016-12-07 2018-12-21 北京海泰方圆科技股份有限公司 固定密码生成方法、装置、动态令牌装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102316120A (zh) * 2011-10-17 2012-01-11 北京信息科技大学 基于网络隐私保护的动态密码锁
CN105989309A (zh) * 2015-02-17 2016-10-05 汪风珍 一种密码
US20170083699A1 (en) * 2015-09-23 2017-03-23 Charter Communications Operating, Llc Dynamic inline assistance messaging
CN106888086A (zh) * 2017-02-13 2017-06-23 上海瀚之友信息技术服务有限公司 一种管理账号密码的***及方法

Also Published As

Publication number Publication date
CN108537038A (zh) 2018-09-14

Similar Documents

Publication Publication Date Title
US11366924B2 (en) Block chain-based data query method, server and storage medium
US11374916B2 (en) Key export techniques
US10284372B2 (en) Method and system for secure management of computer applications
US10116645B1 (en) Controlling use of encryption keys
US10129028B2 (en) Relational encryption for password verification
CN107707347B (zh) 用户密钥的备份方法及装置、用户密钥的导入方法及装置
WO2021012548A1 (zh) 基于区块链的数据处理方法、***、电子装置及存储介质
US10075301B2 (en) Relational encryption for password verification
US10003467B1 (en) Controlling digital certificate use
WO2021139075A1 (zh) 合同的加密和解密方法、装置、设备及存储介质
WO2019178981A1 (zh) 自定义规则密码管理方法、装置、终端设备及存储介质
CN111404892B (zh) 数据监管方法、装置和服务器
CN113127915A (zh) 数据加密脱敏方法、装置、电子设备及存储介质
CN112733180A (zh) 数据查询方法、装置和电子设备
US20150310206A1 (en) Password management
US10462113B1 (en) Systems and methods for securing push authentications
WO2019114084A1 (zh) 多数字位号码的加密、解密方法以及加密、解密服务器
WO2021109810A1 (zh) 一种设置访问口令的方法及装置
US11455404B2 (en) Deduplication in a trusted execution environment
US10043015B2 (en) Method and apparatus for applying a customer owned encryption
CN111949996A (zh) 安全私钥的生成方法、加密方法、***、设备及介质
CN111008236A (zh) 一种数据查询的方法和***
CN115470525B (zh) 一种文件保护方法、***、计算设备及存储介质
CN116933298B (zh) 一种科技成果数据加密处理方法、装置、存储介质及设备
US20230222228A1 (en) Database hierarchical encryption for hybrid-cloud environment

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18910534

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 23/12/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18910534

Country of ref document: EP

Kind code of ref document: A1