Plug-in implementation method and device of nano-management password device and computer readable medium

Abstract

The invention provides a plug-in implementation method and device for a nano-management password device and a computer readable medium, and the method comprises the steps: firstly obtaining a plug-in package of the password device, then analyzing the content of the plug-in package, persistently storing basic information into a database, and loading an interface program into a memory; therefore, when the password service needs to be realized, the corresponding interface program can be directly called from the memory to be connected with the target password equipment, so that the password service is realized. Through the mode, the corresponding password equipment can be rapidly managed only by acquiring the plug-in packages provided by different password equipment manufacturers and analyzing and loading the plug-in packages, and an interface program for calling the password equipment does not need to be written in a code, so that the workload of repeatedly writing and modifying the code is reduced, the flexibility of password evaluation is improved, and the security evaluation efficiency is improved. And the development and maintenance cost is effectively reduced.

Description

Technical Field

[0001] The present application relates to the field of information technology, and in particular to a plug-in implementation method, device, and computer-readable medium for managing cryptographic devices. Background Art

[0002] Commercial cryptographic application security assessment, referred to as "cryptographic assessment," refers to the activities of testing, analyzing, evaluating, and verifying the compliance, correctness, and effectiveness of commercial cryptographic technologies, products, and services used in network and information systems in accordance with relevant laws, regulations, and standards. When some industries need to use cloud platforms as enterprise infrastructure, cryptographic assessments are required to verify whether the cryptographic devices connected to the cloud platform (such as cryptographic service platforms, cryptographic machines, cryptographic cards, etc.) can effectively encrypt the core data within the cloud platform (images, snapshots, sensitive user information, platform passwords, logs, etc.) to ensure data confidentiality and integrity, and effectively protect network and information security.

[0003] During the cryptographic review process, the integration of the cloud platform and cryptographic devices takes a long time. This is because each cryptographic device manufacturer requires different parameters and interface programs. Therefore, a separate set of code must be maintained for each manufacturer's cryptographic device. As the number of cryptographic devices continues to increase, development and maintenance costs also continue to increase. If a subsequent manufacturer modifies the interface program or the parameters within the interface program, the cloud platform must also adapt and release a new version of the integration code. Cloud platform users must then upgrade accordingly, resulting in very high operation and maintenance costs. Summary of the Invention

[0004] One purpose of the present application is to provide a plug-in implementation method, device and computer-readable medium for managing cryptographic devices.

[0005] To achieve the above objectives, the present application provides a plug-in implementation method for managing cryptographic devices, the method comprising:

[0006] Obtain a plug-in package for a cryptographic device, wherein the plug-in package includes basic information and an interface program of the cryptographic device;

[0007] Parse the content of the plug-in package, save the basic information persistently in the database, and load the interface program into the memory;

[0008] When a password service needs to be implemented, the corresponding interface program is called from the memory to connect to the target password device to implement the password service.

[0009] Furthermore, obtain the plug-in package of the password device, including:

[0010] The plug-in package of the password device uploaded by the user is obtained through the interactive interface, or the plug-in package synchronized by other devices is obtained through the content distribution network.

[0011] Furthermore, parsing the content of the plug-in package, persisting the basic information in a database, and loading the interface program into memory includes:

[0012] Scan the folder for storing the plug-in package and read the content of the plug-in package in the folder;

[0013] The content of the plug-in package is parsed, the basic information is persistently saved in a database, and the interface program is loaded into memory.

[0014] Furthermore, the method further comprises:

[0015] When the password device needs to be deleted, the interface program of the password device loaded in the memory, the basic information of the password device stored in the database, and the plug-in package of the password device stored locally are deleted.

[0016] Furthermore, after parsing the content of the plug-in package, persisting the basic information in a database, and loading the interface program into memory, the method further includes:

[0017] In the interactive interface, the password device of the plug-in package is displayed as a managed password device.

[0018] Furthermore, the basic information includes the plug-in type;

[0019] When a password service needs to be implemented, the corresponding interface program is called from the memory to connect to the target password device to implement the password service, including:

[0020] Select the interface program based on the plug-in type required for the cryptographic service to be implemented;

[0021] The interface program is called from the memory to connect to the target cryptographic device to implement the cryptographic service.

[0022] Furthermore, the plug-in package also includes connection information required to connect to the cryptographic device;

[0023] Calling the interface program from the memory to connect to the target cryptographic device to implement the cryptographic service includes:

[0024] The interface program is called from the memory, and the target cryptographic device is connected based on the connection information to implement the cryptographic service.

[0025] Furthermore, the plug-in package is a Jar file.

[0026] Based on another aspect of the present application, a plug-in implementation device for a managed cryptographic device is also provided, which includes a memory for storing computer program instructions and a processor for executing computer program instructions, wherein when the computer program instructions are executed by the processor, the device is triggered to execute the plug-in implementation method of the managed cryptographic device.

[0027] An embodiment of the present application also provides a computer-readable medium on which computer program instructions are stored. The computer program instructions can be executed by a processor to implement the plug-in implementation method of the managed cryptographic device.

[0028] Compared with the existing technology, this application provides a plug-in implementation solution for managing cryptographic devices. This solution first obtains the plug-in package of the cryptographic device, wherein the plug-in package includes the basic information of the cryptographic device and the interface program. Then, the content of the plug-in package can be parsed, the basic information can be persisted in the database, and the interface program can be loaded into the memory. Therefore, when it is necessary to implement a cryptographic service, the corresponding interface program can be directly called from the memory to connect to the target cryptographic device to implement the cryptographic service. In this way, it is only necessary to obtain the plug-in packages provided by different cryptographic device manufacturers, parse and load them, and the management of the corresponding cryptographic device can be quickly completed. It is no longer necessary to write the interface program for calling the cryptographic device in the code, which reduces the workload of repeatedly writing and modifying code, increases the flexibility of the password review, and effectively reduces the development and maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Other features, objects and advantages of the present application will become more apparent upon reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0030] Figure 1 A processing flow chart of a plug-in implementation method for managing a cryptographic device provided in an embodiment of the present application

[0031] Figure 2 A schematic diagram of an implementation method of plug-in management in an embodiment of the present application;

[0032] Figure 3 This is a schematic diagram of the process of the plug-in package parsed by the cloud platform in an embodiment of the present application;

[0033] Figure 4 This is a schematic diagram of loading and unloading plug-ins in memory in an embodiment of the present application;

[0034] Figure 5 This is a schematic diagram of the interaction process when calling a plug-in to implement a password service in an embodiment of the present application;

[0035] The same or similar reference numerals in the drawings represent the same or similar components. DETAILED DESCRIPTION

[0036] The present application is described in further detail below with reference to the accompanying drawings.

[0037] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0038] In a typical configuration of the present application, the terminal and the equipment of the service network each include one or more processors (CPUs), input / output interfaces, network interfaces and memories.

[0039] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0040] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology for information storage. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc-read only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission medium that can be used to store information that can be accessed by a computing device.

[0041] The embodiment of the present application provides a plug-in implementation method for managing cryptographic devices. The method first obtains a plug-in package for the cryptographic device, wherein the plug-in package includes basic information and an interface program of the cryptographic device. Then, the content of the plug-in package can be parsed, the basic information can be persisted in a database, and the interface program can be loaded into the memory. Thus, when a cryptographic service needs to be implemented, the corresponding interface program can be directly called from the memory to connect to the target cryptographic device to implement the cryptographic service. In this way, it is only necessary to obtain the plug-in packages provided by different cryptographic device manufacturers, parse and load them, and the management of the corresponding cryptographic device can be quickly completed. It is no longer necessary to write the interface program for calling the cryptographic device in the code, which reduces the workload of repeatedly writing and modifying the code, increases the flexibility of the cryptographic review, and effectively reduces the development and maintenance costs.

[0042] In practical scenarios, the execution subject of the method may include a user device, a network device, or a device formed by integrating a user device and a network device via a network, or an application running on the above-mentioned device. The user device includes but is not limited to various terminal devices such as computers, mobile phones, and tablet computers; the network device includes but is not limited to network hosts, single network servers, servers concentrated in a network of multiple servers, or servers in a distributed cloud network. The distributed cloud network herein is composed of a large number of hosts or network servers based on cloud computing.

[0043] Figure 1 The present invention provides a method for implementing a plug-in management method for a cryptographic device, which includes at least the following steps:

[0044] Step S101: Obtain a plug-in package for a cryptographic device.

[0045] The cloud platform can provide various implementations for obtaining the plug-in package for the cryptographic device. For example, an interactive control for uploading the plug-in package can be provided in the interactive interface, allowing the user to upload the plug-in package for the cryptographic device through the interactive control, and then the interactive interface can obtain the plug-in package uploaded by the user through the interactive interface. Alternatively, the cloud platform can also deploy a relevant CDN (Content Delivery Network), thereby obtaining the plug-in package synchronized by other devices through the content delivery network and downloading the plug-in package to the cloud platform's storage space.

[0046] The specific contents of the plug-in package include at least basic information about the cryptographic device and an interface program. The basic information may include the plug-in name, UUID, version number, description, and type. This basic information helps users initially identify the type of plug-in package and the corresponding cryptographic device manufacturer, allowing them to select the required plug-in based on this information. The interface program is a program module used to invoke the relevant cryptographic services provided by the manufacturer's cryptographic device. For example, the interface program can invoke encryption and decryption services, HMAC (Hash-based Message Authentication Code) encryption services, and decryption services.

[0047] Step S102: parsing the content of the plug-in package, persisting the basic information in a database, and loading the interface program into a memory.

[0048] Step S103: When a password service needs to be implemented, the corresponding interface program is called from the memory to connect to the target password device to implement the password service.

[0049] The plug-in package includes the relevant data required for management and can be implemented in the form of a jar (Java Archive) file in practical scenarios. After obtaining the plug-in package for the cryptographic device, the cloud platform can store it in a preset folder. Therefore, when needed, the cloud platform can scan the folder storing the plug-in package, read the contents of the plug-in package in the folder, parse the contents of the plug-in package, persist the basic information in a database, and load the interface program into memory.

[0050] For JAR file parsing, the cloud platform scans all JAR files in the corresponding folder, reads their contents, and extracts the required data from the .class files. Basic information is persisted in a database, while the interface program is loaded into memory and used as a plug-in to connect to the cryptographic device and invoke the corresponding cryptographic service.

[0051] For example, taking the plug-in package of manufacturer XX1 as an example, the plug-in package is a jar file. When defining basic information, the name is XX1, the UUID is a randomly selected 32-bit string of letters and numbers, and the version number is 1.0. In addition, corresponding categories, description information, etc. can also be added. In some embodiments of the present application, after this information is persisted to the database, the cryptographic devices of the plug-in package can be displayed as managed cryptographic devices in the interactive interface, so that they can be displayed to the user at any time during the interaction process, helping the user to quickly understand the version information of the plug-in package, a brief functional description, its type, the corresponding cryptographic device manufacturer, etc., so that the user can select the required plug-in based on this information.

[0052] Since the basic information includes the plug-in type, when it is necessary to implement a cryptographic service, you can first select an interface program according to the plug-in type required for the cryptographic service to be implemented, and then call the interface program from the memory to connect to the target cryptographic device to implement the cryptographic service. For example, in the solution of the embodiment of the present application, the plug-in type can be set according to the needs of the actual scenario. For example, based on the scenario type, it can be divided into SSO and cryptographic compliance, etc., and based on the manufacturer type, it can be divided into manufacturer A, manufacturer B and manufacturer C, etc. In the actual scenario, the plug-in type can be defined by the corresponding field, and the scenario type can be defined by the type field, where the type field of the SSO plug-in type is SSO, and the type field of the cryptographic compliance plug-in type is crypto, and the manufacturer type can be defined by the vendor field. Therefore, when it is necessary to implement a certain cryptographic service, you can access and select the appropriate interface program according to the required plug-in type, so as to connect to the cryptographic device that meets the current needs to provide the required target cryptographic service.

[0053] The content stored in memory is the content in the plug-in package that is actually used to implement cryptographic service calls, such as encryption and decryption services, HMAC encryption services, and decryption services. The interface programs used to call these cryptographic services are stored in memory. When the cloud platform needs to call the corresponding cryptographic service, it can directly use the interface program loaded into memory to use the corresponding cryptographic service.

[0054] The advantage of this is that the calling logic does not need to be fixed in the code. For example, if the interface of a certain cryptographic service of the manufacturer needs to be replaced, according to the solution in the prior art, this part of the code needs to be modified in the entire product code, a new version of the code is released, and then the customer environment is updated on the cloud platform. The whole process involves the overall modification and release process of the code, and the operation and maintenance costs are relatively high. After using the solution in the embodiment of the present application, it is only necessary to change the content in the jar package corresponding to the cryptographic device and upload it to the cloud platform. The cloud platform can automatically parse and load it into the memory in the customer environment, and automatically call the modified interface program to implement the corresponding cryptographic service when needed. There is no need to modify the entire product code and re-release it, which greatly improves the speed of problem solving and reduces operation and maintenance costs.

[0055] In addition, the plug-in package may also include the connection information required to connect to the cryptographic device. This connection information refers to the parameters used to call the relevant cryptographic services, such as protocol information, IP address, port, application identifier, key number, etc., so that when the cloud platform implements the cryptographic service, the interface program can be called from the memory and the target cryptographic device can be connected based on the connection information to implement the cryptographic service.

[0056] When a password device needs to be deleted, it is only necessary to delete the interface program of the password device loaded in the memory, the basic information of the password device stored in the database, and the plug-in package of the password device stored locally. This process also does not involve the modification and release of the product code.

[0057] Therefore, through this processing method, no matter how many manufacturers' cryptographic devices are, they can be quickly managed, and when changes and deletions are made, since there is no need to write the interface program for calling the cryptographic device in the code, the workload of repeated writing and modifying the code is reduced, the flexibility of the cryptographic review is increased, and the development and maintenance costs are effectively reduced.

[0058] In the actual cloud platform password review scenario, to complete the password review, the cloud platform needs to manage the cryptographic devices and call the interfaces provided by the cryptographic devices to complete encryption and decryption. In essence, the cloud platform needs to be able to call the interfaces of cryptographic devices from different manufacturers, connect these cryptographic devices, and provide cryptographic services for related data in the cloud platform through the cryptographic devices. In order to be able to manage all cryptographic devices, it is necessary to be able to adaptively load the interface programs of the cryptographic devices. In this solution, the interface programs of various cryptographic devices are used as plug-ins. When needed, they are loaded in like plug-ins, and when not needed, they can be uninstalled. The entire management process does not require any changes to the cloud platform code. The specific implementation method of this solution is as follows:

[0059] 1. Plug-in management.

[0060] Figure 2 The specific form of plug-in package management is shown. The plug-in packages of cryptographic devices from different manufacturers are stored in the form of jar packages. The plug-in packages can be uploaded from the UI (User Interface) or downloaded through CDN. At the same time, relevant pages can be provided for users to manage.

[0061] Regarding plugin additions: When the cloud platform starts up, it scans all JAR files in the corresponding folder, reads their contents, and extracts the required data from the .class files. Basic information can be persisted in the database, while interface programs are loaded into memory.

[0062] For example, for a plug-in jar file from manufacturer XX1, when defining basic information, the name is XX1, the UUID is a randomly selected 32-bit string of letters and numbers, and the version number is 1.0. In addition, corresponding categories and descriptions can be added. In some embodiments of the present application, after this information is persisted to the database, the cryptographic devices in the plug-in package can be displayed as managed cryptographic devices in the interactive interface, allowing users to quickly understand the plug-in package's version information, a brief functional description, its type, the corresponding cryptographic device manufacturer, and other information during the interaction process, allowing users to select the required plug-in based on this information. The content stored in memory is the content in the plug-in package that actually implements cryptographic service calls, such as encryption and decryption services, HMAC encryption services, and decryption services. The interface programs used to call these cryptographic services are stored in memory. When the cloud platform needs to call the corresponding cryptographic service, it can directly use the interface program loaded into memory to access the corresponding cryptographic service. The advantage of this is that the calling logic does not need to be hard-coded into the code. For example, if the interface of a manufacturer's cryptographic service needs to be replaced, according to the solution in the prior art, this part of the code needs to be modified in the entire product code, a new version of the code needs to be released, and then the customer environment on the cloud platform needs to be updated. The entire process involves the overall modification and release process of the code, which has high operation and maintenance costs. After using the solution provided by the embodiment of the present application, after the content of the jar package corresponding to the modified cryptographic device is uploaded to the cloud platform, the cloud platform can automatically parse and load it into the memory in the customer environment, and automatically call the modified interface program to implement the corresponding cryptographic service when needed, without the need to modify the entire product code and re-release it, thereby greatly improving the speed of problem solving and reducing operation and maintenance costs.

[0063] The plug-in package's JAR file (also known as a jar package) is implemented by cryptographic device manufacturers or cloud platform operators according to a specific code format. The contents of this jar package provide the capabilities required to implement cryptographic services, such as HMAC for integrity encryption, SM4 encryption for confidentiality, and connection information required to connect to cryptographic resources, such as IP addresses, ports, and keys. Compiling and packaging this content into a code package generates the corresponding cryptographic device plug-in package. Figure 3 The diagram shows the process of parsing plugin packages on the cloud platform. First, the cloud platform's management node (MN) initiates loading via the plugin driver, scanning for JAR packages in the local path. Based on the scanned JAR packages, the platform parses their contents and loads plugins from various vendors, enabling the cloud platform to utilize the various capabilities provided by the JAR packages.

[0064] Regarding the deletion of the plug-in: delete the interface program of the password device loaded in the memory and the basic information of the password device stored in the database, as well as the jar package of the password device stored locally. Figure 4 As shown, various plug-ins from various manufacturers are loaded into the memory. The cloud platform can use these plug-ins to connect to the corresponding manufacturer's cryptographic devices to implement cryptographic services. For example, plug-in plugin2 connects to the corresponding manufacturer's cryptographic device 2, plug-in plugin3 connects to the corresponding manufacturer's cryptographic device 3, etc. At the same time, more plug-ins (such as plugin5) can be loaded, and existing plug-ins (such as plugin1) can be uninstalled.

[0065] 2. Calling the plug-in.

[0066] After the plug-in has been loaded into the memory, the interface program for connecting to the cryptographic devices of various manufacturers will exist in the memory. Then, when needed, the plug-in loaded into the memory can be directly used to connect to the manufacturer's cryptographic devices, thereby realizing the corresponding cryptographic services, such as integrity / confidentiality encryption and decryption services. The complete calling process is as follows Figure 5 As shown, taking the integrity / confidentiality encryption and decryption service in the password review scenario as an example, when the above-mentioned password service needs to be implemented, the cloud platform accesses the specific plug-in in the memory according to the required plug-in type, calls the plug-in to connect to the password device of a specific manufacturer to perform related processing of the password service, and returns the result through the called plug-in after calculating the processing result, thereby completing a call to the password service through the plug-in.

[0067] In this way, cryptographic devices from any number of manufacturers can be quickly managed, and when changes and deletions are made, there is no need to write the interface program for calling the cryptographic device into the code, which reduces the workload of repeated code writing and modification, increases the flexibility of cryptographic evaluation, and effectively reduces development and maintenance costs.

[0068] Based on the same inventive concept, embodiments of the present application also provide a plug-in implementation device for a managed cryptographic device. The corresponding method for this device is the plug-in implementation of the managed cryptographic device in the aforementioned embodiments, and its principle of solving the problem is similar to that of the aforementioned method. The plug-in implementation device for a managed cryptographic device provided in embodiments of the present application includes a memory for storing computer program instructions and a processor for executing the computer program instructions. When the computer program instructions are executed by the processor, the device is triggered to implement the methods and / or technical solutions of the aforementioned multiple embodiments of the present application.

[0069] Specific implementations of the device may include user devices, network devices, or devices formed by integrating user devices and network devices via a network, or may also be applications running on the above devices. The user devices include, but are not limited to, various terminal devices such as computers, mobile phones, and tablet computers; the network devices include, but are not limited to, network hosts, single network servers, servers concentrated in a network of multiple servers, or servers in a distributed cloud network. The distributed cloud network herein is composed of a large number of hosts or network servers based on cloud computing.

[0070] In particular, the methods and / or embodiments of the present application can be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for executing the method shown in the flowchart. When the computer program is executed by a processing unit, the above-mentioned functions defined in the method of the present application are performed.

[0071] It should be noted that the computer-readable medium described in this application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. Computer-readable media may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this application, a computer-readable medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device.

[0072] In the present application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0073] Computer program code for performing the operations of the present application can be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0074] The flow chart or block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the equipment, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, program segment or a part of code, and the module, program segment or a part of code include one or more executable instructions for realizing the logical function of the specification. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented with a dedicated system for hardware that performs the function or operation of the specification, or can be implemented with a combination of dedicated hardware and computer instructions.

[0075] As another aspect, the present application further provides a computer-readable medium, which may be included in the device described in the above embodiments, or may exist independently without being incorporated into the device. The computer-readable medium carries one or more computer program instructions, which can be executed by a processor to implement the methods and / or technical solutions of the above embodiments of the present application.

[0076] It should be noted that the present application can be implemented in a combination of software and / or software and hardware, for example, can be implemented using an application specific integrated circuit (ASIC), a general purpose computer or any other similar hardware device. In certain embodiments, the software program of the present application can be executed by a processor to implement the above steps or functions. Similarly, the software program of the present application (including related data structures) can be stored in a computer-readable recording medium, for example, a RAM memory, a magnetic or optical drive or a floppy disk and similar devices. In addition, some steps or functions of the present application can be implemented using hardware, for example, as a circuit that cooperates with a processor to perform each step or function.

[0077] It is obvious to those skilled in the art that the present application is not limited to the details of the above-mentioned exemplary embodiments, and that the present application can be implemented in other specific forms without departing from the spirit or basic characteristics of the present application. Therefore, no matter from which point of view, the embodiments should be regarded as exemplary and non-restrictive. The scope of the present application is defined by the appended claims rather than the above description, and it is intended that all changes that fall within the meaning and scope of the equivalent elements of the claims are included in the present application. Any figure marks in the claims should not be regarded as limiting the claims involved. In addition, it is obvious that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices stated in the device claim can also be implemented by one unit or device through software or hardware. Words such as first and second are used to indicate names and do not indicate any specific order. The numerical order of the serial numbers corresponding to the steps does not indicate any specific execution order. The steps can be executed in any order combination under the premise of conforming to the execution logic.

Claims

1. A plug-in implementation method for managing cryptographic devices, characterized in that: The method comprises: Obtain a plug-in package for a cryptographic device, wherein the plug-in package includes basic information and an interface program of the cryptographic device; Parse the content of the plug-in package, save the basic information persistently in the database, and load the interface program into the memory; When a password service needs to be implemented, the corresponding interface program is called from the memory to connect to the target password device to implement the password service.

2. The method according to claim 1, characterized in that Get the plug-in package for the password device, including: The plug-in package of the password device uploaded by the user is obtained through the interactive interface, or the plug-in package synchronized by other devices is obtained through the content distribution network.

3. The method according to claim 1, characterized in that Parsing the contents of the plug-in package, persisting the basic information in a database, and loading the interface program into memory, including: Scan the folder for storing the plug-in package and read the content of the plug-in package in the folder; The content of the plug-in package is parsed, the basic information is persistently saved in a database, and the interface program is loaded into memory.

4. The method according to claim 1, wherein The method further comprises: When the password device needs to be deleted, the interface program of the password device loaded in the memory, the basic information of the password device stored in the database, and the plug-in package of the password device stored locally are deleted.

5. The method according to claim 1, wherein After parsing the contents of the plug-in package, persisting the basic information in a database, and loading the interface program into memory, the process further includes: In the interactive interface, the password device of the plug-in package is displayed as a managed password device.

6. The method according to claim 1, wherein The basic information includes the plug-in type; When a password service needs to be implemented, the corresponding interface program is called from the memory to connect to the target password device to implement the password service, including: Select the interface program based on the plug-in type required for the cryptographic service to be implemented; The interface program is called from the memory to connect to the target cryptographic device to implement the cryptographic service.

7. The method according to claim 6, characterized in that The plug-in package also includes the connection information required to connect to the cryptographic device; Calling the interface program from the memory to connect to the target cryptographic device to implement the cryptographic service includes: The interface program is called from the memory, and the target cryptographic device is connected based on the connection information to implement the cryptographic service.

8. The method according to claim 1, characterized in that The plug-in package is a Jar file.

9. A plug-in implementation device for managing a cryptographic device, the device comprising a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein: When the computer program instructions are executed by the processor, the device is triggered to execute the method according to any one of claims 1 to 8.

10. A computer-readable medium having computer program instructions stored thereon, wherein the computer program instructions can be executed by a processor to implement the method according to any one of claims 1 to 8.

Images