Password equipment management method and device, electronic equipment and readable storage medium

Abstract

The invention provides a password equipment management method and device, electronic equipment and a readable storage medium. The password equipment management method comprises the following steps: receiving a trigger operation corresponding to a target button in a password equipment management interface by a user; wherein the password device management interface is a graphical user interface displayed through a target browser, and the graphical user interface comprises at least one password device list; the target browser is a browser based on a Chromium kernel under a Linux system; and in response to a trigger operation corresponding to the target button, executing a user operation event corresponding to the target button so as to manage a password device and / or a driving program through a target database, wherein the driving program is used for identifying the password device. The problem of complex and cumbersome user operation can be avoided, and the operation convenience of the user can be improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a cryptographic device management method, device, electronic device, and readable storage medium. Background Art

[0002] HyperText Transfer Protocol over Secure SocketLayer (HTTPS) is a network protocol for encrypted transmission and identity authentication. During the identity authentication process, the HTTPS protocol uses a password device with a unique user identity, such as an online banking device USB shield, a fingerprint password device, etc.

[0003] In some application scenarios, users need to access the cryptographic device through a browser to complete the entire HTTPS protocol process. However, on some operating system platforms, users can only manage the driver and cryptographic device of the cryptographic device by entering complex commands in the command line of the browser, which causes the user operation to be complicated and cumbersome. Summary of the invention

[0004] The embodiments of the present application provide a cryptographic device management method, apparatus, electronic device, and readable storage medium, which can solve the problem that users manage cryptographic devices by entering complex commands through command lines, which is complicated and tedious.

[0005] In a first aspect, an embodiment of the present application discloses a cryptographic device management method, the method comprising: Receiving a trigger operation corresponding to a target button in a cryptographic device management interface from a user; wherein the cryptographic device management interface is a graphical user interface displayed by a target browser, and the graphical user interface includes at least one cryptographic device list; and the target browser is a browser based on a Chromium kernel under a Linux system; In response to the trigger operation corresponding to the target button, the user operation event corresponding to the target button is executed to manage the password device and / or the driver through the target database; wherein the driver is used to identify the password device.

[0006] Optionally, receiving a trigger operation corresponding to a target button in the password device management interface from a user includes: receiving a trigger operation corresponding to an add button of the password device list by the user; wherein the target button includes the add button; In response to the trigger operation corresponding to the target button, executing the user operation event corresponding to the target button to manage the password device and / or the driver through the target database includes: In response to the trigger operation corresponding to the add button, the user operation event corresponding to the add button is executed to store the driver information of the driver input by the user into the target database, and create a driver management control corresponding to the driver information in the password device list.

[0007] Optionally, in response to the trigger operation corresponding to the add button, executing the user operation event corresponding to the add button to store the driver information input by the user into the target database, and creating a driver management control corresponding to the driver information in the password device list, including: In response to the trigger operation corresponding to the add button, a first dialog box is displayed by adding an event response function; wherein the first dialog box is used to receive the driver information input by the user; Receiving a trigger operation corresponding to a confirmation button in the first dialog box by the user; In response to the triggering operation corresponding to the confirmation button, the driver information is stored in the target database by adding the event response function; By adding the event response function, a driver management control corresponding to the driver information is created, and the driver management control is displayed in the password device list.

[0008] Optionally, receiving a trigger operation corresponding to a target button in the password device management interface from a user includes: receiving a trigger operation corresponding to a first button in a driver management control by the user; wherein the password device list includes the driver management control, and the target button includes the first button; In response to the trigger operation corresponding to the target button, executing the user operation event corresponding to the target button to manage the password device and / or the driver through the target database includes: In response to the trigger operation corresponding to the first button, the user operation event corresponding to the first button is executed to manage the driver corresponding to the driver management control through the target database.

[0009] Optionally, in response to the trigger operation corresponding to the first button, executing the user operation event corresponding to the first button to manage the driver information corresponding to the driver management control through the target database includes: In response to a trigger operation corresponding to a first viewing button, a first information window is created through a first event response function; wherein the first button includes the first viewing button; the first event response function is an event response function corresponding to a first viewing event, and the first viewing event is a user operation event corresponding to the first viewing button; The driver information corresponding to the driver management control is obtained from the target database through the first event response function, and the driver information is displayed in the first information window.

[0010] Optionally, in response to the trigger operation corresponding to the first button, executing the user operation event corresponding to the first button to manage the driver information corresponding to the driver management control through the target database includes: In response to a trigger operation corresponding to a delete button, the driver information corresponding to the driver management control is deleted from the target database by deleting an event response function, and the driver management control is deleted; wherein the first button includes the delete button.

[0011] Optionally, receiving a trigger operation corresponding to a target button in the password device management interface from a user includes: receiving a trigger operation corresponding to a second button in the device management control by the user; wherein the password device list includes the device management control, and the password device corresponding to the device management control is a password device recognized by the target browser through the driver; and the target button includes the second button; In response to the trigger operation corresponding to the target button, executing the user operation event corresponding to the target button to manage the password device and / or the driver through the target database includes: In response to the trigger operation corresponding to the second button, the user operation event corresponding to the second button is executed to manage the password device corresponding to the device management control through the target database.

[0012] Optionally, in response to the trigger operation corresponding to the second button, executing the user operation event corresponding to the second button to manage the password device information corresponding to the device management control through the target database includes: In response to a trigger operation corresponding to the login button, a second dialog box is displayed through a login event response function; wherein the second dialog box is used to receive a device login password input by the user, and the device login password is used to authenticate the user; the second button includes the login button; Receiving a trigger operation corresponding to an unlock button in the second dialog box by the user; In response to the trigger operation corresponding to the unlock button, through the login event response function, when the identity authentication of the user is passed, the device login status contained in the password device information in the target database is updated.

[0013] Optionally, the password device list includes a driver management control; before receiving a trigger operation corresponding to a second button in the device management control by the user, the method further includes: Receiving a trigger operation corresponding to a drop-down button of the drive management control by the user; In response to a trigger operation corresponding to a drop-down button, a device management control included in the driver management control is displayed in the driver management control through a drop-down event response function; wherein the password device corresponding to the device management control in the driver management control is a password device recognized by the target browser through the driver corresponding to the driver management control.

[0014] Optionally, in response to the trigger operation corresponding to the second button, executing the user operation event corresponding to the second button to manage the password device information corresponding to the device management control through the target database includes: In response to a trigger operation corresponding to a second view button, a second information window is created through a second event response function; wherein the second button includes the second view button; the second event response function is an event response function corresponding to a second view event, and the second view event is a user operation event corresponding to the second view button; The password device information is obtained from the target database through the second event response function, and the password device information is displayed in the second information window.

[0015] In a second aspect, an embodiment of the present application discloses a cryptographic device management device, the device comprising: A first receiving module is used to receive a trigger operation corresponding to a target button in a cryptographic device management interface by a user; wherein the cryptographic device management interface is a graphical user interface displayed by a target browser, and the graphical user interface includes at least one cryptographic device list; and the target browser is a browser based on the Chromium kernel under a Linux system; An execution module is used to respond to a trigger operation corresponding to the target button and execute a user operation event corresponding to the target button to manage the password device and / or the driver through a target database; wherein the driver is used to identify the password device.

[0016] In the third aspect, an embodiment of the present application also discloses an electronic device, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other through the communication bus; the memory is used to store executable instructions, and the executable instructions enable the processor to execute the cryptographic device management method as described in the first aspect.

[0017] In a fourth aspect, an embodiment of the present application further discloses a readable storage medium. When instructions in the storage medium are executed by a processor of an electronic device, the processor is enabled to execute the cryptographic device management method as described in the first aspect.

[0018] The embodiments of the present application include the following advantages: The embodiments of the present application provide a method, device, electronic device and readable storage medium for managing a password device. By receiving a trigger operation corresponding to a target button in a password device management interface by a user, since the password device management interface is a graphical user interface displayed by a target browser, and the graphical user interface includes at least one password device list, it is convenient for the user to trigger a button in the password device management interface, thereby triggering a user operation event corresponding to the target button. The operation is simple and intuitive, which can improve the convenience of user operation. The user does not need to enter complex commands. In response to the trigger operation corresponding to the target button, the user operation event corresponding to the target button is executed, thereby managing the password device and / or the driver for identifying the password device through the target database, which can avoid the problem of complex and cumbersome user operations in the related art and improve the actual user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0020] Figure 1 It is a flowchart of the steps of a cryptographic device management method provided in an embodiment of the present application; Figure 2 It is a logical framework diagram of a cryptographic device management method provided in an embodiment of the present application; Figure 3 It is a display effect diagram of a first dialog box provided in an embodiment of the present application; Figure 4 This is one of the display effect diagrams of a password device management interface provided in an embodiment of the present application; Figure 5 This is a display effect diagram of a first information window provided in an embodiment of the present application; Figure 6 This is a display effect diagram of a deletion confirmation window provided in an embodiment of the present application; Figure 7 This is the second display effect diagram of a password device management interface provided in an embodiment of the present application; Figure 8is a display effect diagram of a second dialog box provided in an embodiment of the present application; Fig. 9 This is one of the display effect diagrams of a second information window provided in an embodiment of the present application; Fig.10 This is a second display effect diagram of a second information window provided in an embodiment of the present application; Fig.11 It is a flowchart of a cryptographic device management method provided in an embodiment of the present application; Fig.12 It is a structural block diagram of a cryptographic device management device provided in an embodiment of the present application; Fig.13 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0021] 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.

[0022] In the field of information security, the HTTPS protocol is constructed by the Hypertext Transfer Protocol (HTTP) plus the Transport Layer Security (TLS) or Secure Socket Layer (SSL) protocol. It is a network protocol that can perform encrypted transmission and identity authentication. It mainly uses digital certificates, encryption algorithms, asymmetric keys and other technologies to complete Internet data transmission encryption and achieve Internet transmission security protection.

[0023] During the HTTPS protocol authentication process, a cryptographic device with a unique user identity will be used, such as an online banking device U shield, a fingerprint password device, etc. The cryptographic device generally stores the user's private key, personal certificate, etc. At present, there are two main standards for implementing cryptographic devices: based on the international general interface standard "PKCS#11: Cryptographic Token Interface Standard", and based on the "GMT 0016-2012 Smart Password Key Password Application Interface Specification" issued by the National Cryptography Administration. The above two types of cryptographic device products are rich and mature, and have been used in a large number of information application scenarios, such as online banking services, government information services, etc. In the above scenarios, users need to access the cryptographic device through a browser to complete the entire HTTPS protocol process.

[0024] In the related art, in the Linux system environment, the management of the user's password device by the browser based on the Chromium kernel is implemented through the command line interface. The user can only make the password device recognized by the browser based on the Chromium kernel by typing complex commands in the command line interface. For example, to add a password device based on the PKCS#11 interface standard, you need to enter the following command in the command line interface: "modutil -dbdir sql: / home / user-x / .pki / nssdb / -add "opensc" -libfile / home / user-x / Desktop / P11 / libskftokn3.so".

[0025] Among them, libskftokn3.so is the driver of the user password device. Through this operation, you can add the driver of the user password device so that the browser based on the Chromium kernel can recognize the user's password device through the driver. When the user wants to list the PKCS#11 password devices that the browser can recognize, you need to enter the following command in the command line interface: "modutil -dbdir sql: / home / user-x / .pki / nssdb / -list".

[0026] When the user wants to delete the PKCS#11 cryptographic device, enter the following command in the command line interface: "modutil -delete "opensc" -nocertdb -force -mechanisms RSA:DSA:RC4:DES -libfile libskftokn3.so".

[0027] In the related art, users need to type complex commands in the command line interface to manage the cryptographic device and its driver, which results in complex and cumbersome user operations and greatly reduces the operational convenience for ordinary users.

[0028] Reference Figure 1 , shows a flowchart of a cryptographic device management method provided in an embodiment of the present application, and the cryptographic device management method may specifically include the following steps: Step 101, receiving a trigger operation corresponding to a target button in a cryptographic device management interface from a user; wherein the cryptographic device management interface is a graphical user interface displayed by a target browser, and the graphical user interface includes at least one cryptographic device list; and the target browser is a browser based on the Chromium kernel under a Linux system; Step 102, in response to the trigger operation corresponding to the target button, execute the user operation event corresponding to the target button to manage the cryptographic device and / or the driver through the target database; wherein the driver is used to identify the cryptographic device.

[0029] In the embodiment of the present application, the cryptographic device management method can be applied to the cryptographic device management of Linux system devices. Specifically, a graphical user interface is provided based on the browser of the Chromium kernel under the Linux system, so that the user can manage the cryptographic device and / or the driver of the cryptographic device through the graphical user interface, which can improve the convenience of the user to manage the cryptographic device and enhance the actual user experience. Among them, the Linux system is an operating system, and the Linux system device includes an electronic device running the Linux operating system.

[0030] The target browser can be a Chromium browser, that is, a browser based on the Chromium kernel. The Chromium kernel refers to the core part of the entire Chromium browser, including but not limited to web page rendering function (Blink engine), JavaScript engine (V8), multi-process architecture, network stack, security features, and the rendering engine is responsible for interpreting the syntax of the web page and rendering (displaying) the web page.

[0031] In the embodiment of the present application, a graphical user interface is configured on the front end of the target browser as a cryptographic device management interface, and the graphical user interface is used to interact with the user to facilitate the user to implement management operations on the cryptographic device and / or driver. For example, the user can add / delete the driver of the cryptographic device, view the driver information of the cryptographic device, view the status of the cryptographic device, and view the certificate of the cryptographic device in the cryptographic device management interface.

[0032] In the embodiment of the present application, the password device management interface is displayed on the front page of the target browser, and user interaction is realized through graphical buttons, controls, etc. in the page. Specifically, the password device management interface can be a complete page displayed by the target browser, or it can be a part of the page displayed by the target browser. For example, the password device management interface can be an interface for managing password devices in the setting page of the target browser. This is only an example, and the embodiment of the present application does not limit this.

[0033] In the embodiment of the present application, the cryptographic device management interface may include at least one cryptographic device list, each of which is used to manage one or more cryptographic devices. Specifically, cryptographic devices with the same interface standard can be managed in a cryptographic device list. For example, PKCS#11 cryptographic devices, SKF cryptographic devices, etc. Among them, PKCS#11 is an international universal interface standard, and the SKF interface standard is a C language application development interface standard for smart cryptographic keys in the national secret standard.

[0034] Among them, password devices of the same device type can be managed in a password device list. For example, a Universal Serial Bus (USB) password device is a USB device type, and a fingerprint password device is a fingerprint device type.

[0035] In the embodiment of the present application, the password device management interface may include one or more buttons, and user operations may be received through the buttons. The buttons in the password device management interface may be in the form of text and / or icons. For example, the password device management interface includes an add button, a delete button, a view button, etc. The front end of the password device management interface may be implemented by a front end language, such as Hyper Text Markup Language (HTML), JavaScript scripting language, etc.

[0036] In the embodiment of the present application, the user's triggering operation may be a user action such as a mouse click, a keyboard shortcut, a touch screen click, etc. The user may interact with a button on the password device management interface through an input device to trigger the button.

[0037] In the embodiment of the present application, the backend can define the user operation events corresponding to the buttons in the password device management interface, and register the event response function for the user operation event. The target button can be any button in the password device management interface, each button corresponds to a user operation event, and the backend registers the corresponding event response function for each user operation event. Among them, the backend is a server-side software or system that provides data, logic processing and support for the front end. The backend can be implemented by a programming language, such as C++ language, etc.

[0038] In response to the user's triggering operation on the target button, the backend can execute the user operation event corresponding to the target button through the event response function corresponding to the target button, and manage the cryptographic device and / or driver by interacting with the target database to store and retrieve data. The driver is used to identify the cryptographic device.

[0039] In the embodiment of the present application, the management of the cryptographic device includes the management of the cryptographic device itself and the management of the driver used to identify the cryptographic device. For example, the addition / deletion of the driver of the cryptographic device, the viewing of the driver information, the login / logout of the cryptographic device, the viewing of the status of the cryptographic device, etc. This is only an example, and the embodiment of the present application does not limit this.

[0040] In the embodiment of the present application, the backend can manage the cryptographic device through the target database, and the target database can be used to store driver information, cryptographic device information, and identity authentication information. The event response function can manage the cryptographic device by operating the data in the target database and update the front-end cryptographic device management interface. For example, the target database can be a Network Security Services (NSS) database, and the NSS database can manage certificates and implement network security encryption, identity authentication and other services.

[0041] Figure 2 The following is an exemplary logical framework diagram of a cryptographic device management method provided in an embodiment of the present application. Figure 2 As shown, the front-end can set up front-end components through JavaScript language for cryptographic device and / or driver management. For example, the usbkey_manager components implement user operations such as adding and deleting drivers, viewing driver information, cryptographic device login / logout, and viewing cryptographic device status. The back-end can set up the back-end WebUI through C++ language, such as the usbkey_manager WebUI. The back-end WebUI uses the NSS module to operate the NSS database, thereby implementing event processing for the front-end components.

[0042] Optionally, step 101 may include the following sub-steps: Sub-step A1, receiving a trigger operation corresponding to an add button on a password device list from a user; wherein the target button includes an add button; Step 102 may include the following sub-steps: Sub-step A2, in response to the trigger operation corresponding to the add button, execute the user operation event corresponding to the add button to store the driver information of the driver input by the user into the target database, and create a driver management control corresponding to the driver information in the password device list.

[0043] In an embodiment of the present application, the target browser can identify the cryptographic device through the driver. The cryptographic device management interface includes an add button. Specifically, one add button is set corresponding to one cryptographic device list. The add button is used to add a driver. The user can trigger the add button to generate a user operation event for adding the driver. The user operation event corresponding to the add button is an add event. The back end can pre-register an event response function corresponding to the add event, which is called an add event response function. The user's triggering operation for the add button of the cryptographic device list can be a mouse click on the add button, keyboard input of the shortcut key corresponding to the add button, touch screen click on the add button, etc.

[0044] In the embodiment of the present application, the user can input the driver information through the add button, and the driver information can include the driver name, the driver file name or the driver storage path, etc. For example, the password device management interface also includes an input box corresponding to the password device list, and the user can input the driver information into the input box, and then trigger the add button. The back end executes the add event in response to the triggering operation, thereby storing the driver information in the input box to the target database. This is only an example, and the embodiment of the present application does not limit this.

[0045] In the embodiment of the present application, the user can create a driver management control corresponding to the driver information in the password device list of the target browser front end through the add button, and the driver management control is used to manage the driver corresponding to the driver information. Among them, each driver management control can manage one or more password devices, and the password devices managed under the same driver management control are password devices recognized by the driver corresponding to the driver management control.

[0046] For example, the driver management control may include one or more device management controls, and the device management control is used to manage password devices, so as to facilitate users to perform management operations such as password device login / logout and viewing password device information.

[0047] In the embodiment of the present application, by receiving the trigger operation corresponding to the add button of the password device list by the user, in response to the trigger operation corresponding to the add button, the user operation event corresponding to the add button is executed to store the driver information of the driver input by the user into the target database, and create a driver management control corresponding to the driver information in the password device list. In this way, the back end can add the driver information of the driver to the target database, and the driver management control created by the front end can facilitate the user to manage the driver, realize the user management operation of adding the driver, and improve the convenience of user operation.

[0048] Optionally, sub-step A2 may include the following sub-steps: In response to a trigger operation corresponding to the add button, a first dialog box is displayed by adding an event response function; wherein the first dialog box is used to receive driver information input by a user; Receive a trigger operation corresponding to a confirmation button in the first dialog box from the user; In response to the trigger operation corresponding to the confirmation button, the driver information is stored in the target database by adding an event response function; By adding an event response function, a driver management control corresponding to the driver information is created, and the driver management control is displayed in the password device list.

[0049] In the embodiment of the present application, when a user adds a driver, he needs to input relevant information of the driver, and the user's input can be received through the first dialog box. In response to the trigger operation corresponding to the add button, the add event corresponding to the add button can be executed through the add event response function. Specifically, an input box can be displayed on the password device management interface as the first dialog box through the add event response function, or a modal dialog box can be directly displayed as the first dialog box.

[0050] Among them, after the modal dialog box pops up, other windows will no longer accept user input, and only after the modal dialog box exits, other windows can continue to interact with the user. This is just an example, and the embodiment of the present application does not limit this.

[0051] In an embodiment of the present application, a user can enter driver information in the first dialog box, such as a driver name, file name, and storage path. The first dialog box may include an input box, and the user can directly enter the driver information into the input box. For example, the user can directly paste the copied storage path into the first dialog box. Alternatively, the first dialog box may include a browse button, and the user can browse the local file by triggering the browse button to obtain the storage path of the driver, and automatically enter the storage path into the first dialog box.

[0052] In the embodiment of the present application, the first dialog box may further include a cancel button and an confirm button. When the user triggers the cancel button, the first dialog box may be closed. When the user triggers the confirm button, a user operation event of adding a driver is triggered, and the first dialog box is closed.

[0053] In an embodiment of the present application, in response to the trigger operation corresponding to the OK button, the back end can store the driver information entered by the user in the first dialog box into the target database through the event response function corresponding to the user operation event of adding the driver, namely, the add event response function, and create a driver management control based on the driver information, and display the driver management control in the password device list of the password device management interface.

[0054] Among them, a driver management control can be created according to the driver name in the driver information. The driver management control can be displayed in the same password device list with the add button, indicating that the password device corresponding to the driver management control has the same interface standard and device type as the password devices corresponding to other driver management controls in the password device list. This is only an example, and the embodiments of the present application are not limited to this.

[0055] For example, the backend can implement a message passing (UsbKeysHandler) class for Universal Serial Bus (USB) password devices. The UsbKeysHandler class inherits from WebUI and can register the add event response function through the RegisterMessages function. The add event response function corresponds to the user operation event of the add button. The backend WebUI can operate the NSS database through the NSS module, and the NSS database is the target database, so as to realize the processing of the user operation event corresponding to the add button. Among them, WebUI represents the network user interface (Website UserInterface).

[0056] Specifically, when the user triggers the Add button, the front end sends the user operation event corresponding to the Add button to the UsbKeysHandler class, and the UsbKeysHandler class displays a modal dialog box by adding an event (AddSlot) response function (HandleAddSlot), and the modal dialog box is used as the first dialog box. Then, when the user triggers the OK button of the first dialog box, the UsbKeysHandler class can store the driver information entered by the user in the first dialog box into the NSS database by adding an event response function (HandleAddSlot), and the NSS database is the target database. A driver management control is created based on the driver information and displayed in the password device list of the password device management interface.

[0057] The target database may provide an operation interface corresponding to the interface standard so as to store and retrieve data in the target database through the operation interface. For example, for a cryptographic device and its driver program of the PKCS#11 interface standard, each event response function may operate the NSS database through the PKCS#11 interface provided by the NSS database and update the state of the cryptographic device management interface of the front end. This is only an example, and the embodiments of the present application do not limit this.

[0058] In an embodiment of the present application, in response to a trigger operation corresponding to an add button, a modal dialog box is created by adding an event response function as a first dialog box; a first prompt message and a first input control are displayed in the first dialog box; wherein the first prompt message is used to prompt a user to input driver information, and the first input control is used to receive the driver information input by the user.

[0059] In the embodiment of the present application, the first prompt information may be a text prompting the user to input the name, file name, storage path, and adapted interface standard of the added driver. The first dialog box may include an output box, and the first prompt information may be displayed in the output box. The first input control may include at least one input box, and an input box receives a type of driver information. For example, the first input control may include a name input box, a file name input box, and a storage path input box.

[0060] For example, the ShowModalDialog() method in the UsbKeysHandler class can create and display a modal dialog box pointing to a specific web page. In actual applications, a modal dialog box can be created as the first dialog box through the ShowModalDialog() method, and the first dialog box is displayed on the target browser page where the password device management interface is located.

[0061] Figure 3 The following is an exemplary diagram showing the display effect of a first dialog box. Figure 3 As shown, the first prompt information includes: "Load device driver, enter the driver information you want to add, driver name, driver file name". The first input control includes a name input box and a file name input box. The name input box displays the driver name, and the file name output box displays the driver file name. The first dialog box also includes a browse button, a cancel button, and an OK button. The user can trigger the corresponding user operation event through the trigger button. For example, the name input box displays the driver name "loongmai", and the file name output box displays the following driver file names: " / opt / lm-gm3000user / lib / libgm3000_pkcs11.so".

[0062] In the embodiment of the present application, in response to the trigger operation corresponding to the add button, the user operation event corresponding to the add button is executed by adding an event response function, that is, the first dialog box is displayed by adding an event response function, the trigger operation corresponding to the confirm button in the first dialog box is received by the user, and the driver information is stored in the target database in response to the trigger operation corresponding to the confirm button, and the driver management control corresponding to the driver information is created in the password device list. In this way, the front-end and back-end interaction based on the password device management interface of the target browser can be realized by adding an event response function, so that the user can simply and conveniently add the driver for identifying the password device, which can improve the user's interactive experience.

[0063] Optionally, step 101 may include the following sub-steps: Sub-step A3, receiving a trigger operation corresponding to a first button in the driver management control from a user; wherein the password device list includes the driver management control, and the target button includes the first button; Step 102 may include the following sub-steps: Sub-step A4, in response to the trigger operation corresponding to the first button, executing the user operation event corresponding to the first button, so as to manage the driver corresponding to the driver management control through the target database.

[0064] In the embodiment of the present application, the user can manage the driver corresponding to the driver management control through the driver management control in the password device list in the password device management interface. The management operations of the driver management control include deleting the driver, viewing the driver information, etc. The driver information corresponding to the driver is stored in the target database. The driver can be deleted by accessing the driver information in the target database, and the driver information corresponding to the driver management control can be viewed by searching the target database. This is only an example, and the embodiment of the present application does not limit this.

[0065] In the embodiment of the present application, the driver management control includes a button for managing the driver program, which is called the first button, and the target button includes the first button. The user generates a user operation event corresponding to the first button by triggering the first button, and the back end responds to the trigger operation corresponding to the first button, executes the user operation event corresponding to the first button, and manages the driver program corresponding to the driver management control through the target database by operating the driver program information corresponding to the driver management control in the target database.

[0066] Optionally, sub-step A4 may include the following sub-steps: In response to a trigger operation corresponding to a first viewing button, a first information window is created through a first event response function; wherein the first button includes a first viewing button; the first event response function is an event response function corresponding to a first viewing event, and the first viewing event is a user operation event corresponding to the first viewing button; The driver information corresponding to the driver management control is obtained from the target database through the first event response function, and the driver information is displayed in the first information window.

[0067] In the embodiment of the present application, the password device list of the password device management interface may include one or more driver management controls, each driver management control includes a first view button, and the first button of the driver management control includes a first view button. The user can view the driver information corresponding to the driver management control by triggering the first view button of the driver management control. The driver information displayed in the first information window may come from the driver information entered by the user when the driver management control is created.

[0068] In the embodiment of the present application, the user operation event generated by the user triggering the first view button is the first view event, and the backend can pre-register an event response function corresponding to the first view event, which is called the first event response function. In response to the trigger operation corresponding to the first view button, the first view event can be executed through the first event response function. The user's trigger operation on the first view button can be clicking the first view button with a mouse, inputting the shortcut key corresponding to the first view button on the keyboard, clicking the first view button on the touch screen, etc.

[0069] Specifically, in response to the user's triggering operation on the first view button, a first information window is created through a first event response function, and the driver information corresponding to the driver management control is obtained from the target database, and the driver information is displayed in the first information window.

[0070] The first information window may be a common output box, which is displayed in the password device management interface. Alternatively, the first information window may be a modal dialog box, and the user triggers the first view button to directly display the modal dialog box, which is not limited in the embodiment of the present application. The first information window may also include a close / confirm button, and the user may close the first information window by triggering the close / confirm button.

[0071] The driver information corresponding to the driver management control is obtained from the target database through the first event response function based on the operation interface provided by the target database, and then the driver information is displayed in the first information window.

[0072] For example, the UsbKeysHandler class of the back end registers the first event response function for the first view button, namely the view event (ViewSlot) response function (HandleViewSlot). When the user triggers the first view button, the front end sends the first view event to the UsbKeysHandler class. The UsbKeysHandler class creates a modal dialog box as the first information window through the view event response function (HandleViewSlot), obtains the driver information corresponding to the driver management control from the NSS database, and displays the driver information in the first information window for the user to view. This is just an example, and the embodiments of the present application are not limited to this.

[0073] In the embodiment of the present application, in response to the trigger operation corresponding to the first view button, a first information window is created through a first event response function, the driver information is obtained from the target database, and the driver information is displayed in the first information window. In this way, the user can simply trigger the first view button in the driver management control to view the driver information of the driver corresponding to the driver management control displayed in the first information window, avoiding the problem of cumbersome operation.

[0074] Optionally, sub-step A4 may include the following sub-steps: In response to a trigger operation corresponding to the delete button, the driver information corresponding to the driver management control is deleted from the target database by deleting the event response function, and the driver management control is deleted; wherein the first button includes a delete button.

[0075] In the embodiment of the present application, each driver management control may further include a delete button, and the first button of the driver management control includes a delete button. The user may delete the driver information corresponding to the driver management control stored in the target database and delete the driver management control in the password device list of the password device management interface by triggering the delete button of the driver management control, so that the target browser will not be able to identify the corresponding password device through the driver.

[0076] In the embodiment of the present application, the user operation event generated by the user triggering the delete button is a delete event, and the backend can pre-register an event response function corresponding to the delete event, which is called a delete event response function. In response to the trigger operation corresponding to the delete button, the delete event can be executed through the delete event response function. The user's trigger operation for the delete button can be clicking the delete button with the mouse, inputting the shortcut key corresponding to the delete button on the keyboard, clicking the delete button on the touch screen, etc.

[0077] Specifically, the driver information corresponding to the driver management control in the target database is deleted based on the operation interface provided by the target database through the first event response function, and the driver management control in the password device list is deleted.

[0078] In the embodiment of the present application, in response to the user triggering the delete button, a delete confirmation window can be displayed through the delete event response function, and the delete confirmation window can display the delete confirmation information, and the delete confirmation information is used to prompt the user whether to confirm the deletion of the driver. The delete confirmation window can include a cancel / confirm button. When the user triggers the cancel button, the delete confirmation window is closed. When the user triggers the confirm button, the driver information is deleted from the target database and the driver management control is deleted.

[0079] In the embodiment of the present application, in response to the trigger operation corresponding to the delete button, the driver information corresponding to the driver management control is deleted from the target database through the delete event response function, and the driver management control is deleted. In this way, the driver management control at the front end and the driver information stored in the back end target database can be deleted synchronously, thereby deleting the driver added to the target browser, and the operation is simple and convenient.

[0080] Figure 4 The following is an exemplary diagram showing a display effect of a password device management interface. Figure 4 As shown, the password device management interface is an interface named "Manage password devices" in the setting page of the target browser. The password device management interface includes four password device lists, namely, password device list 1, password device list 2, password device list 3 and password device list 4. The four password device lists can be "PKCS#11 password device list, PKCS#11 fingerprint device list, SKF password device list, SKF fingerprint device list". Currently displayed is password device list 1, which includes multiple driver management controls.

[0081] like Figure 4 As shown, the cryptographic device list 1 includes the prompt text "You have installed the following cryptographic devices", an add button, and four driver management controls, namely, driver management control 1, driver management control 2, driver management control 3, and driver management control 4. For example, the cryptographic device list 1 can display four driver management controls, namely, "Builtin SKF Module, loongmai, NSS InternalPKCS #11 Module, Root Certs". When the user triggers the driver management control, a new window can be displayed, such as Figure 4 As shown, the new window includes a View button and a Delete button.

[0082] like Figure 5As shown in FIG. 1 , the user triggers the first view button (view) of the driver management control 3 to display the first information window (driver information viewer), which displays driver information such as "details, name, path, etc.", and the driver information viewer also includes an OK button, and the user can close the first information window by triggering the OK button. The first information window can display the user's Figure 3 In the first dialog box shown enter the Driver Name and Driver File Name.

[0083] like Figure 6 As shown, the user triggers the delete button (delete) of the driver management control 3, and a delete confirmation window (confirm deletion) is displayed, which displays the prompt text "Are you sure you want to delete this driver?", and the driver information viewer also includes a cancel button and an OK button. The user can close the delete confirmation window by triggering the cancel button, or trigger the OK button to make the backend execute the user operation of deleting the driver.

[0084] Optionally, step 101 may include the following sub-steps: Sub-step A5, receiving a trigger operation corresponding to the second button in the device management control by the user; wherein the password device list includes the device management control, and the password device corresponding to the device management control is a password device recognized by the target browser through the driver; and the target button includes the second button; Step 102 may include the following sub-steps: Sub-step A6, in response to the trigger operation corresponding to the second button, executing the user operation event corresponding to the second button, so as to manage the password device corresponding to the device management control through the target database.

[0085] In the embodiment of the present application, the user can manage the password device corresponding to the device management control through the device management control in the password device list. The management operations of the password device include password device login / logout, viewing password device information, etc. The password device information corresponding to the password device is stored in the target database, and the user can be authenticated according to the password device information. If the identity authentication is passed, the password device is logged in, and the password device information of the password device corresponding to the device management control can be viewed by searching the target database.

[0086] In the embodiment of the present application, the target browser identifies the password device through the driver corresponding to the driver management control, and can create a device management control in the password device management interface for the identified password device. The device management control can be displayed in the corresponding driver management control, indicating that the password device corresponding to the device management control is identified by the driver corresponding to the driver management control.

[0087] In the embodiment of the present application, the button for managing the password device in the device management control is called the second button, and the target button includes the second button. The user generates a user operation event corresponding to the second button by triggering the second button, and the back end responds to the trigger operation corresponding to the second button, executes the user operation event corresponding to the second button, and manages the password device corresponding to the device management control through the target database by operating the password device information corresponding to the device management control in the target database.

[0088] Optionally, sub-step A6 may include the following sub-steps: In response to the trigger operation corresponding to the login button, a second dialog box is displayed through a login event response function; wherein the second dialog box is used to receive a device login password input by a user, and the device login password is used to authenticate the user; the second button includes a login button; Receive a trigger operation corresponding to the unlock button in the second dialog box from the user; In response to the trigger operation corresponding to the unlock button, through the login event response function, if the user's identity authentication is passed, the device login status contained in the password device information in the target database is updated.

[0089] In the embodiment of the present application, the cryptographic device management interface may include one or more cryptographic device lists, and one cryptographic device list corresponds to a cryptographic device of a certain interface standard and device type. For example, a PKCS#11 cryptographic device list, a PKCS#11 fingerprint device list, a SKF cryptographic device list, and a SKF fingerprint device list. Each cryptographic device list includes an add button, and the user can add the driver corresponding to the interface standard and device type of the cryptographic device list through the add button. The process of adding the driver can refer to the relevant description of sub-steps A1 to A2 in the aforementioned embodiment, which will not be repeated here.

[0090] In an embodiment of the present application, the password device list displays the driver management controls corresponding to each driver added by the user. The driver management controls may include a first view button and a delete button. The user can trigger the corresponding user operation event by triggering the button in the driver management control to realize user operations such as viewing and deleting the driver.

[0091] In an embodiment of the present application, the device management control may include a login button, and the second button of the device management control includes a login button. The login button may be directly displayed in the device management control, or the user may trigger the device management control to pop up a new window, and the login button is displayed in the new window, which is not limited in the embodiment of the present application. The user may trigger a user operation event of the login password device by triggering the login button, which is called a login event. The user's triggering operation on the login button may be a mouse click on the login button, keyboard input of the shortcut key corresponding to the login button, touch screen click on the login button, etc. The back end may execute the login event through the event response function corresponding to the user operation event of the login password device, which is called the login event response function, thereby realizing the login operation on the password device.

[0092] Specifically, when a user logs in to a password device, he needs to enter the device login password. The user's input can be received through the second dialog box, and the user is authenticated according to the device login password entered by the user. In response to the trigger operation corresponding to the login button, the second dialog box is displayed through the login event response function. The second dialog box can be an input box displayed in the device management control, or a modal dialog box that pops up. The embodiment of the present application does not limit this.

[0093] In the embodiment of the present application, the second dialog box displays a second prompt message and a second input control. The second prompt message is used to prompt the user to enter the device login password of the password device, and the second prompt message may include information such as the name of the password device. The second input control is used to receive the device login password entered by the user. The second input control can have a hidden display effect on the device login password, automatically converting the numeric password or the letter password into a special symbol for display. This is only an example, and the embodiment of the present application does not limit this.

[0094] In the embodiment of the present application, the second dialog box may further include a cancel button and an unlock button. When the user triggers the cancel button, the second dialog box may be closed. When the user triggers the unlock button, a user operation event of logging into the password device is triggered, and the second dialog box is closed.

[0095] In the embodiment of the present application, in response to the user's trigger operation corresponding to the unlock button in the second dialog box, the backend can authenticate the user through the login event response function according to the password device information stored in the target database and the device login password entered by the user. If the device login password entered by the user matches the password used for identity authentication in the password device information, it means that the user's identity authentication is passed, otherwise the identity authentication fails.

[0096] In the embodiment of the present application, when the user identity authentication is passed, the password device can be communicated with through the login event response function to obtain the password device information of the password device, and the password device information is stored in the target database to update the login status of the password device. When the user checks the status of the password device through the device management control, the password device status information displayed on the front end can be updated according to the password device information stored in the target database.

[0097] For example, when the user triggers the login button, the front end sends the user operation event corresponding to the login button to the UsbKeysHandler class. The UsbKeysHandler class displays a modal dialog box through the login event (LoginSlot) response function (HandleLoginSlot), and the modal dialog box serves as the second dialog box. Then, when the user triggers the unlock button of the second dialog box, the UsbKeysHandler class can operate the NSS database through the PKCS#11 interface provided by the NSS database, and verify the device login password entered by the user in the second dialog box with the identity authentication password of the password device information in the NSS database. When the user's identity authentication is passed, the PKCS#11 cryptographic function can be used to communicate with the password device, obtain the password device information and store it in the NSS database, thereby updating the device login status contained in the password device information to the logged-in status.

[0098] In the embodiment of the present application, by responding to the trigger operation corresponding to the login button, the second dialog box is displayed through the login event response function, and the device login password input by the user can be received through the second dialog box, so as to authenticate the user according to the device login password. The user's trigger operation corresponding to the unlock button in the second dialog box is received, and in response to the trigger operation corresponding to the unlock button, the device login status contained in the password device information in the target database is updated through the login event response function when the user's identity authentication is passed. In this way, it is convenient for users to log in to the password device and improve the security of password device management.

[0099] Optionally, the password device list includes a driver management control; and before sub-step A5, the password device management method further includes: Step 201, receiving a trigger operation corresponding to a drop-down button of a drive management control from a user; Step 202, in response to the trigger operation corresponding to the drop-down button, the device management control included in the driver management control is displayed in the driver management control through the drop-down event response function; wherein the password device corresponding to the device management control in the driver management control is the password device recognized by the target browser through the driver corresponding to the driver management control.

[0100] In the embodiment of the present application, the driver management control may include a drop-down box, and the driver management control displayed in the password device list may only display simple description information of the driver and a drop-down button, and the simple description information may be the name of the driver, etc. The user may open the drop-down box of the driver management control by triggering the drop-down button, and the drop-down box displays the device management controls included in the driver management control.

[0101] In an embodiment of the present application, when the target browser does not identify the cryptographic device through the driver corresponding to the driver management control, the device management control displayed in the drop-down box can be empty, that is, the device management control is not displayed. When the target browser has identified one or more cryptographic devices through the driver corresponding to the driver management control, the drop-down box can display the device management control corresponding to the cryptographic device identified by the target browser. Among them, the number of device management controls that can be displayed in the drop-down box is not limited, and can be determined according to the size of the cryptographic device management interface or the size of the driver management control. This is only an example, and the embodiment of the present application does not limit this.

[0102] In this way, by configuring the device management control in the corresponding driver management control for display, the user can simply and intuitively view the driver corresponding to the password device, or the password device identified by the driver, which can improve the user experience.

[0103] Optionally, sub-step A6 may include the following sub-steps: In response to a trigger operation corresponding to the second view button, a second information window is created through a second event response function; wherein the second button includes a second view button; the second event response function is an event response function corresponding to a second view event, and the second view event is a user operation event corresponding to the second view button; The password device information is obtained from the target database through the second event response function, and the password device information is displayed in the second information window.

[0104] In an embodiment of the present application, a user can view the password device information corresponding to the device management control by triggering the second view button of the device management control, and the second button of the device management control includes a second view button. The password device information displayed in the second information window can be the password device information stored in the target database when the password device corresponding to the device management control is recognized by the driver.

[0105] In the embodiment of the present application, the user operation event generated by the user triggering the second view button is the second view event, and the backend can pre-register an event response function corresponding to the second view event, which is called the second event response function. In response to the trigger operation corresponding to the second view button, the second view event can be executed through the second event response function. The user's trigger operation on the second view button can be clicking the second view button with the mouse, inputting the shortcut key corresponding to the second view button on the keyboard, clicking the second view button on the touch screen, etc.

[0106] Specifically, in response to the user's triggering operation on the second view button, a second information window is created through a second event response function, and the password device information is obtained from the target database, and the password device information is displayed in the second information window. Among them, the second information window can be an ordinary output box, which is displayed in the password device management interface. Alternatively, the second information window can be a modal dialog box, and the user triggers the second view button to directly pop up the modal dialog box, which is not limited in the embodiment of the present application. The second information window can also include a close / confirm button, and the user can close the second information window by triggering the close / confirm button.

[0107] Wherein, the password device information corresponding to the device management control is obtained from the target database based on the operation interface provided by the target database through the second event response function, and then the password device information is displayed in the second information window.

[0108] For example, the UsbKeysHandler class of the back end registers the second event response function for the second view button, namely the view event response function (HandleViewSlot). When the user triggers the second view button, the front end sends the second view event to the UsbKeysHandler class. The UsbKeysHandler class creates a modal dialog box as the second information window through the view event response function (HandleViewSlot), obtains the password device information corresponding to the device management control from the NSS database, and displays the password device information in the second information window for the user to view. This is just an example, and the embodiments of the present application are not limited to this.

[0109] In the embodiment of the present application, in response to the trigger operation corresponding to the second view button, a second information window is created through a second event response function, the password device information is obtained from the target database, and the password device information is displayed in the second information window. In this way, the user can simply view the password device information of the password device corresponding to the device management control displayed in the second information window by triggering the second view button in the device management control, avoiding the problem of cumbersome operation and improving the user experience.

[0110] Figure 7Another display effect diagram of a password device management interface is shown as an example. Figure 7 As shown in the figure, the page where the password device management interface is located is the setting page of the target browser, and the setting menu is displayed on the left. Among them, the user can open the password device management interface by triggering the "Privacy Settings and Security" control. Figure 4 The password device management interface shown, Figure 7 The currently displayed cryptographic device list 1 includes three driver management controls, namely, driver management control 1, driver management control 2, and driver management control 3. For example, the cryptographic device list 1 may display three driver management controls, namely, "NSS Internal PKCS #11 Module, Root Certs, and SKF". The driver management control includes a drop-down box, and the user can open the drop-down box by clicking the drop-down button. The drop-down box displays the device management controls included in the driver management control. Figure 7 In the example, the arrow mark before the name of the driver management control, the arrow opening upward indicates closing the drop-down box, and the arrow opening downward indicates opening the drop-down box. For example, the driver management control 3 includes a device management control, such as Figure 7 Device management control 1 is shown in the figure. In actual applications, the device management control can be named according to the type of password device managed by the device management control. For example, the device management control can be named "USBKey 0" for a USB password device. When the device management control is triggered, a new window can be displayed, which includes a second view button (View) and a login button (Login).

[0111] like Figure 8 As shown, the second dialog box is displayed when the user triggers the login button (login) of the device management control. The second dialog box displays the second prompt information "Login security device, please log in to the password device, password:", which is used to prompt the user to enter the device login password of the password device. For example, when prompting the user to enter the password device labeled "GM3000", the second prompt information can display the prompt text: "Please log in to GM3000". The second dialog box also includes an input box as a second input control. And the second dialog box also includes a cancel button and an unlock button.

[0112] like Fig. 9 and Fig.10 As shown, the second information window is displayed when the user triggers the second view button (view) of the device management control. Fig. 9 The second information window shows the status information of the password device before login. Fig.10 Displays the status information of the password device after login.

[0113] Fig.11Schematic diagram of a method for managing a cryptographic device provided in an embodiment of the present application. Fig.11 As shown, taking the login button of the device management control triggered by the user as an example, the backend implementation mechanism of the password device management method of the embodiment of the present application is explained. Define the user operation event corresponding to the button in the password device management interface of the browser page. The backend can use the following command to define the user operation event corresponding to the button in the password device management interface: "ui webuifresources / cr_components / usbkey_manager / usbkeys_browser_proxyjs".

[0114] Then send the user registration event to the web user interface (WebUI). When the user triggers the button, the user operation event is sent to the message passing class inherited from WebUI, such as the UsbKeysHandler class. The UsbKeysHandler class implements the RegisterMessages function to register event response functions, such as the add event (AddSlot) response function (HandleAddSlot), the view event (ViewSlot) response function (HandleViewSlot), and the login event (LoginSlot) response function (HandleLoginSlot).

[0115] like Fig.11 As shown, the UsbKeysHandler class processes the user operation event triggered by the user on the login button in the device management control through the login event response function. Specifically, a modal dialog box is popped up through the display modal dialog box method as the second dialog box to receive the device login password entered by the user. Among them, the display modal dialog box method is for example the ShowModalDialog() method. In actual applications, when executing a login event, it is possible to first determine whether the password device corresponding to the device management control is already in the login state. If the password device is already logged in, the password device information can be directly obtained. If the password device is not logged in, the password device is logged in and the user identity authentication is performed.

[0116] For example, for a cryptographic device that complies with the PKCS#11 interface standard, the NSS database is operated through the PKCS#11 interface provided by the NSS database. Specifically, it is possible to determine whether the PKCS#11 cryptographic device is already in the logged-in state by checking the cryptographic device login function "PK11 IsLogginIn". If the cryptographic device is already logged in, the cryptographic device information is directly obtained through the function "PK11_GetTokenInfo" to obtain the cryptographic device information. Otherwise, if the cryptographic device is not logged in, the cryptographic device can be logged in through the function "PK11Login" to log in to the cryptographic device, and the user can be authenticated through the authentication function "C_Login". If the authentication is passed, the cryptographic device information is obtained through the function "PK11_GetTokenInfo" to obtain the cryptographic device information and store it in the NSS database.

[0117] Among them, the functions "PK11 IsLogginIn", "PK11_GetTokenInfo", "PK11Login" and "C_Login" are cryptographic functions of the PKCS#11 interface standard.

[0118] In summary, by receiving the user's trigger operation corresponding to the target button in the password device management interface, since the password device management interface is a graphical user interface displayed by the target browser, and the graphical user interface includes at least one password device list, it is convenient for the user to trigger the button in the password device management interface, thereby triggering the user operation event corresponding to the target button. The operation is simple and intuitive, which can improve the user's operation convenience. The user does not need to enter complex commands, and responds to the trigger operation corresponding to the target button to execute the user operation event corresponding to the target button, thereby managing the password device and / or the driver for identifying the password device through the target database, which can avoid the problem of complex and cumbersome user operations in the related art of managing the browser based on the Chromium kernel under the Linux system, and improve the actual user experience.

[0119] It should be noted that, for the method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present application are not limited by the described order of actions, because according to the embodiments of the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present application.

[0120] Reference Fig.12 , shows a structural block diagram of a cryptographic device management device 30 of the present application, and the cryptographic device management device 30 may specifically include: The first receiving module 301 is used to receive a trigger operation corresponding to a target button in a cryptographic device management interface by a user; wherein the cryptographic device management interface is a graphical user interface displayed by a target browser, and the graphical user interface includes at least one cryptographic device list; and the target browser is a browser based on the Chromium kernel under a Linux system; The execution module 302 is used to respond to the trigger operation corresponding to the target button and execute the user operation event corresponding to the target button to manage the password device and / or the driver through the target database; wherein the driver is used to identify the password device.

[0121] Optionally, the first receiving module 301 is specifically used to: receive a trigger operation corresponding to an add button of the password device list by a user; wherein the target button includes an add button; The execution module 302 is specifically used for: responding to the trigger operation corresponding to the add button, executing the user operation event corresponding to the add button to store the driver information of the driver input by the user into the target database, and creating a driver management control corresponding to the driver information in the password device list.

[0122] Optionally, the execution module 302 is specifically configured to: In response to a trigger operation corresponding to the add button, a first dialog box is displayed by adding an event response function; wherein the first dialog box is used to receive driver information input by a user; Receive a trigger operation corresponding to a confirmation button in the first dialog box from the user; In response to the trigger operation corresponding to the confirmation button, the driver information is stored in the target database by adding an event response function; By adding an event response function, a driver management control corresponding to the driver information is created, and the driver management control is displayed in the password device list.

[0123] Optionally, the first receiving module 301 is specifically used to: receive a trigger operation corresponding to a first button in the driver management control by a user; wherein the password device list includes the driver management control, and the target button includes the first button; The execution module 302 is specifically used for: in response to the trigger operation corresponding to the first button, executing the user operation event corresponding to the first button, so as to manage the driver corresponding to the driver management control through the target database.

[0124] Optionally, the execution module 302 is specifically configured to: In response to a trigger operation corresponding to a first viewing button, a first information window is created through a first event response function; wherein the first button includes a first viewing button; the first event response function is an event response function corresponding to a first viewing event, and the first viewing event is a user operation event corresponding to the first viewing button; The driver information corresponding to the driver management control is obtained from the target database through the first event response function, and the driver information is displayed in the first information window.

[0125] Optionally, the execution module 302 is specifically configured to: In response to a trigger operation corresponding to the delete button, the driver information corresponding to the driver management control is deleted from the target database by deleting the event response function, and the driver management control is deleted; wherein the first button includes a delete button.

[0126] Optionally, the first receiving module 301 is specifically configured to: Receive a trigger operation corresponding to a second button in the device management control by a user; wherein the password device list includes the device management control, and the password device corresponding to the device management control is a password device identified by the target browser through a driver; and the target button includes the second button; The execution module 302 is specifically used for: In response to the trigger operation corresponding to the second button, the user operation event corresponding to the second button is executed to manage the password device corresponding to the device management control through the target database.

[0127] Optionally, the execution module 302 is specifically configured to: In response to the trigger operation corresponding to the login button, a second dialog box is displayed through a login event response function; wherein the second dialog box is used to receive a device login password input by a user, and the device login password is used to authenticate the user; the second button includes a login button; Receive a trigger operation corresponding to the unlock button in the second dialog box from the user; In response to the trigger operation corresponding to the unlock button, through the login event response function, if the user's identity authentication is passed, the device login status contained in the password device information in the target database is updated.

[0128] Optionally, the password device list includes a driver management control; the password device management device 30 also includes: The second receiving module is used to receive a trigger operation corresponding to the drop-down button of the drive management control by the user before the first receiving module 301 receives a trigger operation corresponding to the second button in the device management control by the user; The display module is used to respond to the trigger operation corresponding to the drop-down button, and display the device management control included in the driver management control in the driver management control through the drop-down event response function; wherein the password device corresponding to the device management control in the driver management control is the password device recognized by the target browser through the driver corresponding to the driver management control.

[0129] Optionally, the execution module 302 is specifically configured to: In response to a trigger operation corresponding to the second view button, a second information window is created through a second event response function; wherein the second button includes a second view button; the second event response function is an event response function corresponding to a second view event, and the second view event is a user operation event corresponding to the second view button; The password device information is obtained from the target database through the second event response function, and the password device information is displayed in the second information window.

[0130] 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.

[0131] A cryptographic device management apparatus 30 provided in an embodiment of the present application can achieve the same or similar technical effects as the cryptographic device management method of the aforementioned embodiment, which will not be described in detail here.

[0132] 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.

[0133] 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.

[0134] Reference Fig.13 , is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Fig.13 As shown, the electronic device includes: a processor, a memory, a communication interface and a communication bus, and the processor, the memory and the communication interface communicate with each other through the communication bus; the memory is used to store executable instructions or executable programs, and the executable instructions or executable programs enable the processor to execute the cryptographic device management method of the aforementioned embodiment.

[0135] An embodiment of the present application provides a readable storage medium. When instructions in the storage medium are executed by a processor of an electronic device, the processor is enabled to execute the cryptographic device management method of the aforementioned embodiment.

[0136] 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.

[0137] It should be understood by those skilled in the art that the embodiments of the present application can be provided as methods, devices or computer program products. Therefore, the embodiments of the present application can be in the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the embodiments of the present application can be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0138] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems) and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing terminal device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0139] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing terminal device to operate in a predictable manner, so that the instructions stored in the computer readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0140] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0141] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprises" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0142] The above is a detailed introduction to a cryptographic device management method, apparatus, electronic device and 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 general technical personnel in this field, 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 cryptographic device management method, characterized in that: The method comprises: Receiving a trigger operation corresponding to a target button in a cryptographic device management interface from a user; wherein the cryptographic device management interface is a graphical user interface displayed by a target browser, and the graphical user interface includes at least one cryptographic device list; and the target browser is a browser based on a Chromium kernel under a Linux system; In response to the trigger operation corresponding to the target button, the user operation event corresponding to the target button is executed to manage the password device and / or the driver through the target database; wherein the driver is used to identify the password device.

2. The method for managing a cryptographic device according to claim 1, characterized in that: The receiving a trigger operation corresponding to a target button in the password device management interface by a user includes: receiving a trigger operation corresponding to an add button of the password device list by the user; wherein the target button includes the add button; In response to the trigger operation corresponding to the target button, executing the user operation event corresponding to the target button to manage the password device and / or the driver through the target database includes: In response to the trigger operation corresponding to the add button, the user operation event corresponding to the add button is executed to store the driver information of the driver input by the user into the target database, and create a driver management control corresponding to the driver information in the password device list.

3. The method for managing a cryptographic device according to claim 2, characterized in that: In response to the trigger operation corresponding to the add button, executing the user operation event corresponding to the add button to store the driver information input by the user into the target database, and creating a driver management control corresponding to the driver information in the password device list, including: In response to the trigger operation corresponding to the add button, a first dialog box is displayed by adding an event response function; wherein the first dialog box is used to receive the driver information input by the user; Receiving a trigger operation corresponding to a confirmation button in the first dialog box by the user; In response to the triggering operation corresponding to the confirmation button, the driver information is stored in the target database by adding the event response function; By adding the event response function, a driver management control corresponding to the driver information is created, and the driver management control is displayed in the password device list.

4. The method for managing a cryptographic device according to claim 1, characterized in that: The receiving a trigger operation corresponding to a target button in the password device management interface by a user includes: receiving a trigger operation corresponding to a first button in a driver management control by the user; wherein the password device list includes the driver management control, and the target button includes the first button; In response to the trigger operation corresponding to the target button, executing the user operation event corresponding to the target button to manage the password device and / or the driver through the target database includes: In response to the trigger operation corresponding to the first button, the user operation event corresponding to the first button is executed to manage the driver corresponding to the driver management control through the target database.

5. The method for managing a cryptographic device according to claim 4, characterized in that: In response to the trigger operation corresponding to the first button, executing the user operation event corresponding to the first button to manage the driver information corresponding to the driver management control through the target database, includes: In response to a trigger operation corresponding to a first viewing button, a first information window is created through a first event response function; wherein the first button includes the first viewing button; the first event response function is an event response function corresponding to a first viewing event, and the first viewing event is a user operation event corresponding to the first viewing button; The driver information corresponding to the driver management control is obtained from the target database through the first event response function, and the driver information is displayed in the first information window.

6. The method for managing a cryptographic device according to claim 4, characterized in that: In response to the trigger operation corresponding to the first button, executing the user operation event corresponding to the first button to manage the driver information corresponding to the driver management control through the target database, includes: In response to a trigger operation corresponding to a delete button, the driver information corresponding to the driver management control is deleted from the target database by deleting an event response function, and the driver management control is deleted; wherein the first button includes the delete button.

7. The method for managing a cryptographic device according to any one of claims 1 to 6, characterized in that: The receiving a trigger operation corresponding to a target button in the password device management interface by a user includes: receiving a trigger operation corresponding to a second button in the device management control by the user; wherein the password device list includes the device management control, and the password device corresponding to the device management control is a password device recognized by the target browser through the driver; and the target button includes the second button; The step of responding to the trigger operation corresponding to the target button and executing the user operation event corresponding to the target button to manage the password device and / or the driver through the target database includes: In response to the trigger operation corresponding to the second button, the user operation event corresponding to the second button is executed to manage the password device corresponding to the device management control through the target database.

8. The method for managing a cryptographic device according to claim 7, characterized in that: The step of responding to the trigger operation corresponding to the second button, executing the user operation event corresponding to the second button, so as to manage the password device information corresponding to the device management control through the target database, includes: In response to a trigger operation corresponding to the login button, a second dialog box is displayed through a login event response function; wherein the second dialog box is used to receive a device login password input by the user, and the device login password is used to authenticate the user; the second button includes the login button; Receiving a trigger operation corresponding to an unlock button in the second dialog box by the user; In response to the trigger operation corresponding to the unlock button, through the login event response function, when the identity authentication of the user is passed, the device login status contained in the password device information in the target database is updated.

9. The method for managing a cryptographic device according to claim 7, characterized in that: The password device list includes a driver management control; before receiving a trigger operation corresponding to a second button in the device management control by the user, the method further includes: Receiving a trigger operation corresponding to a drop-down button of the drive management control by the user; In response to a trigger operation corresponding to a drop-down button, a device management control included in the driver management control is displayed in the driver management control through a drop-down event response function; wherein the password device corresponding to the device management control in the driver management control is a password device recognized by the target browser through the driver corresponding to the driver management control.

10. The method for managing a cryptographic device according to claim 7, characterized in that: The step of responding to the trigger operation corresponding to the second button, executing the user operation event corresponding to the second button, so as to manage the password device information corresponding to the device management control through the target database, includes: In response to a trigger operation corresponding to a second view button, a second information window is created through a second event response function; wherein the second button includes the second view button; the second event response function is an event response function corresponding to a second view event, and the second view event is a user operation event corresponding to the second view button; The password device information is obtained from the target database through the second event response function, and the password device information is displayed in the second information window.

11. A cryptographic device management device, characterized in that: The device comprises: A first receiving module is used to receive a trigger operation corresponding to a target button in a cryptographic device management interface by a user; wherein the cryptographic device management interface is a graphical user interface displayed by a target browser, and the graphical user interface includes at least one cryptographic device list; and the target browser is a browser based on the Chromium kernel under a Linux system; An execution module is used to respond to a trigger operation corresponding to the target button and execute a user operation event corresponding to the target button to manage the password device and / or the driver through a target database; wherein the driver is used to identify the password device.

12. An electronic device, characterized in that: include: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store executable instructions, and the executable instructions enable the processor to execute the cryptographic device management method according to any one of claims 1 to 10.

13. A readable storage medium, characterized in that: When the instructions in the storage medium are executed by a processor of an electronic device, the processor is enabled to execute the cryptographic device management method according to any one of claims 1 to 10.

Images