CN115248931A - Plug-in method and device for encryption algorithm in block chain technology and related product - Google Patents

Plug-in method and device for encryption algorithm in block chain technology and related product Download PDF

Info

Publication number
CN115248931A
CN115248931A CN202210976906.1A CN202210976906A CN115248931A CN 115248931 A CN115248931 A CN 115248931A CN 202210976906 A CN202210976906 A CN 202210976906A CN 115248931 A CN115248931 A CN 115248931A
Authority
CN
China
Prior art keywords
project
plug
host
warehouse
creating
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210976906.1A
Other languages
Chinese (zh)
Inventor
阮安邦
魏明
王佳帅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Octa Innovations Information Technology Co Ltd
Original Assignee
Beijing Octa Innovations Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Octa Innovations Information Technology Co Ltd filed Critical Beijing Octa Innovations Information Technology Co Ltd
Priority to CN202210976906.1A priority Critical patent/CN115248931A/en
Publication of CN115248931A publication Critical patent/CN115248931A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/602—Providing cryptographic facilities or services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The application discloses a plug-in method, a plug-in device and a related product of an encryption algorithm in a block chain technology, wherein an ID is distributed to a plug-in project and a host project by creating the plug-in project and the host project and based on a set ID logic offset; creating a project warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are located in the same project warehouse; declaring a pseudo plug-in project at said same project repository, said pseudo plug-in project for managing cryptographic algorithm code entries; and accessing the encryption algorithm code entry to call an encryption algorithm and loading the encryption algorithm into a set plug-in frame by starting the pseudo plug-in project based on the plug-in project to form the encryption plug-in of the host project, and recording the encryption plug-in the project warehouse, so that the encryption plug-in can be realized based on the plug-in when the encryption algorithm is updated, and the updating cost of the encryption algorithm is reduced.

Description

Plug-in method and device for encryption algorithm in block chain technology and related product
Technical Field
The present application relates to the field of block chain technologies, and in particular, to a plug-in method and apparatus for an encryption algorithm in a block chain technology, and a related product.
Background
The block chain is a chain formed by blocks, and each block stores certain information which are connected into the chain according to the time sequence generated by each block. This chain is maintained in all servers, and as long as one server can work in the entire system, the entire blockchain is secure. These servers, referred to as nodes in the blockchain system, provide storage space and computational support for the entire blockchain system. If the information in the block chain is to be modified, more than half of the nodes must be authenticated and the information in all the nodes must be modified, and the nodes are usually held in different hands of different subjects, so that the information in the block chain is extremely difficult to tamper with.
In the application process of the block chain technology, block nodes of a terminal are involved, each block node is equivalent to a terminal, and necessary codes and resource packages must be loaded on the block nodes to participate in the operation of the whole system of the block chain. Among these, the encryption algorithm is a very important function for the blockchain. When the function implementation of the encryption algorithm is implemented in a static library, resulting in the need to update the encryption algorithm, the entire dynamic library must be updated, resulting in a higher update cost.
Disclosure of Invention
Based on the above problems, the embodiments of the present application provide a plug-in method and apparatus for an encryption algorithm in a block chain technology, and a related product.
The embodiment of the application discloses the following technical scheme:
a method of plug-in of encryption algorithms in blockchain technology, comprising:
creating a plug-in project and a host project, and distributing IDs to the plug-in project and the host project based on a set ID logic offset;
creating a project warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are located in the same project warehouse;
declaring a pseudo plug-in project at said same project repository, said pseudo plug-in project for managing cryptographic algorithm code entries;
and accessing the encryption algorithm code entry to call an encryption algorithm and loading the encryption algorithm into a set plug-in framework by enabling the pseudo plug-in project based on the plug-in project so as to form the encryption plug-in of the host project and record the encryption plug-in the project warehouse.
Optionally, the creating a plug-in project and a host project includes: and analyzing the created object declaration folder to determine a warehouse address and a dependent data packet, and creating a plug-in project and a host project according to the warehouse address and the dependent data packet.
Optionally, the allocating IDs to the plug-in project and the host project based on the set ID logical offset includes: and distributing IDs for the plug-in project and the host project according to the set ID logic offset and the set ID anchor point location.
Optionally, the creating a project warehouse according to the plug-in project ID and the hosting project ID, so that the plug-in project and the hosting project are located in the same project warehouse, includes: and acquiring the configured warehouse attribute, and creating a project local warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are positioned in the same project local warehouse.
Optionally, said declaring a pseudo plug-in project at said same project repository, said pseudo plug-in project for managing cryptographic algorithm code entries, comprises: according to the set generic argument, defining the generic argument as an execution entry of the cryptographic algorithm code to create a pseudo plug-in project declaration and manage the cryptographic algorithm code entry by the pseudo plug-in project.
Optionally, the creating a pseudo plug-in project declaration and managing the cryptographic algorithm code entry by the pseudo plug-in project according to the set generic argument and defining the generic argument as the execution entry of the cryptographic algorithm code comprises: and determining a script code module for creating the pseudo plug-in project, embedding the set generic arguments into the script code, and defining the generic arguments as an execution entry of the encryption algorithm code so as to create a pseudo plug-in project statement and manage the encryption algorithm code entry through the pseudo plug-in project.
Optionally, the pseudo plug-in project is a script plug-in, or a binary plug-in, or an object plug-in.
Optionally, the accessing, by enabling the pseudo plug-in project based on the plug-in project, the encryption algorithm code entry calls an encryption algorithm and loads the encryption algorithm into a set plug-in framework to form an encryption plug-in of the host project, and the encryption plug-in is recorded in the project repository, where the method includes: and setting a code dependency mode by enabling the pseudo plug-in project based on the plug-in project, so that the encryption algorithm code entry is accessed to call an encryption algorithm and is loaded into a set plug-in framework to form an encryption plug-in of the host project, and the encryption plug-in is recorded in the project warehouse.
Optionally, the dependency pattern includes a local dependency that enables the cryptographic plug-in to be invoked locally, a remote dependency that enables the cryptographic plug-in to be invoked remotely as a third party component.
A plug-in device for encryption algorithms in block chain technology, comprising:
the first program unit is used for creating a plug-in project and a host project and distributing IDs to the plug-in project and the host project based on the set ID logic offset;
a second program unit, configured to create a project repository according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are located in the same project repository;
a third program unit, configured to declare a dummy plug-in project in the same project warehouse, where the dummy plug-in project is used for managing an encryption algorithm code entry;
and the fourth program unit is used for accessing the encryption algorithm code entry to call an encryption algorithm and loading the encryption algorithm into a set plug-in framework by enabling the pseudo plug-in project based on the plug-in project so as to form the encryption plug-in of the host project and record the encryption plug-in the project warehouse.
An electronic device comprising a memory having an executable program stored thereon and a processor that executes the executable program to perform the steps of:
creating a plug-in project and a host project, and allocating IDs to the plug-in project and the host project based on a set ID logic offset;
creating a project warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are located in the same project warehouse;
declaring a pseudo plug-in project at said same project repository, said pseudo plug-in project for managing cryptographic algorithm code entries;
and accessing the encryption algorithm code entry to call an encryption algorithm and loading the encryption algorithm into a set plug-in framework by enabling the pseudo plug-in project based on the plug-in project so as to form the encryption plug-in of the host project and record the encryption plug-in the project warehouse.
In the technical solution of the embodiment of the present application, by creating a plug-in project and a host project, and based on a set ID logical offset, IDs are allocated to the plug-in project and the host project; creating a project warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are located in the same project warehouse; declaring a pseudo plug-in project at said same project repository, said pseudo plug-in project for managing cryptographic algorithm code entries; and accessing the encryption algorithm code entry to call an encryption algorithm and loading the encryption algorithm into a set plug-in frame by starting the pseudo plug-in project based on the plug-in project to form the encryption plug-in of the host project, and recording the encryption plug-in the project warehouse, so that the method can be realized based on the plug-in when the encryption algorithm is updated, and the updating cost of the encryption algorithm is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic flowchart illustrating a plug-in method for an encryption algorithm in a block chain technique according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a plug-in device for an encryption algorithm in the block chain technology according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an electronic device in an eighth embodiment of the present application;
fig. 4 is a schematic hardware structure diagram of an electronic device according to a ninth embodiment of the present application.
Detailed Description
It is not necessary for any particular embodiment of the invention to achieve all of the above advantages at the same time.
In order to make those skilled in the art better understand the technical solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a schematic flowchart illustrating a plug-in method for an encryption algorithm in a block chain technique according to an embodiment of the present application; as shown in fig. 1, it includes:
s101, creating a plug-in project and a host project, and distributing IDs to the plug-in project and the host project based on a set ID logic offset;
s102, creating a project warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are located in the same project warehouse;
s103, declaring a pseudo plug-in project in the same project warehouse, wherein the pseudo plug-in project is used for managing an encryption algorithm code entry;
s104, based on the plug-in project, the pseudo plug-in project is enabled, so that the encryption algorithm code entry is accessed to call an encryption algorithm and is loaded into a set plug-in framework, an encryption plug-in of the host project is formed, and the encryption plug-in is recorded in the project warehouse.
Optionally, in step S101, creating a plug-in project and a host project includes: and analyzing the created object declaration folder to determine a warehouse address and a dependent data packet, and creating a plug-in project and a host project according to the warehouse address and the dependent data packet.
By analyzing the target declaration folder, the warehouse address and the dependent data packet can be quickly determined, so that the speed of creating the plug-in project and the host project is improved.
In this embodiment, the created target declaration folder may be specifically analyzed through a written script code file, an address of the target declaration file is specified in the script code file, a warehouse address and a dependent data packet are obtained from the address of the target declaration file, the address of the warehouse is specifically a warehouse address for storing a code, and the dependent data packet includes all data packets required for implementing encryption.
Optionally, the assigning IDs for the plug-in project and the host project based on the set ID logical offset includes: and distributing IDs for the plug-in project and the host project according to the set ID logic offset and the set ID anchor point location.
Through the logic offset and the set ID anchor point location, the allocation of the IDs of the plug-in project and the host project can be accurately realized. Specifically, the IDs of the plug-in project and the host project may be allocated by, for example, segment allocation.
Specifically, two logical offsets and an ID anchor location may be used, and the allocation of the IDs of the plug-in project and the host project is realized. Specifically, the ID of the plug-in project and the ID of the host project are calculated respectively by taking the ID anchor location as a starting point and taking the logical offset as a step size.
Optionally, the creating a project warehouse according to the plug-in project ID and the hosting project ID, so that the plug-in project and the hosting project are located in the same project warehouse, includes: and acquiring the configured warehouse attribute, and creating a project local warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are positioned in the same project local warehouse.
In this embodiment, the plug-in project and the host project may be located in the same project local repository specifically by means of a mapping relationship between the plug-in project ID and the host project ID and the project local repository.
In this embodiment, the repository attribute includes a local property or a remote property, and for this reason, if the repository attribute is the local property, a project local repository is created according to the plug-in project ID and the host project ID, otherwise, a new project repository is created,
optionally, said declaring a pseudo plug-in project at said same project repository, said pseudo plug-in project for managing cryptographic algorithm code entries, comprises: according to the set generic argument, defining the generic argument as an execution entry of the cryptographic algorithm code to create a pseudo plug-in project declaration and manage the cryptographic algorithm code entry by the pseudo plug-in project.
Optionally, the creating a pseudo plug-in project declaration and managing cryptographic algorithm code entries by the pseudo plug-in project according to the set generic argument and defining the generic argument as an execution entry of the cryptographic algorithm code includes: and determining a script code module for creating the pseudo plug-in project, embedding the set generic argument into the script code, and defining the generic argument as an execution entry of the encryption algorithm code to create a pseudo plug-in project statement and manage the encryption algorithm code entry through the pseudo plug-in project, so that the security performance of the encryption algorithm is improved, and the attack is avoided.
Optionally, the pseudo plug-in project is a script plug-in, or a binary plug-in, or an object plug-in.
Optionally, the accessing, by enabling the pseudo plug-in project based on the plug-in project, the encryption algorithm code entry calls an encryption algorithm and loads the encryption algorithm into a set plug-in framework to form an encryption plug-in of the host project, and the encryption plug-in is recorded in the project repository, where the method includes: and setting a code dependency mode by starting the pseudo plug-in project based on the plug-in project, so that the encryption algorithm code entry is accessed to call an encryption algorithm and is loaded into a set plug-in framework to form an encryption plug-in of the host project, and the encryption plug-in is recorded in the project warehouse, thereby facilitating the quick embedding and calling of the plug-in and facilitating the subsequent upgrading of the encryption algorithm.
Optionally, the dependency pattern includes a local dependency that enables the cryptographic plug-in to be invoked locally, a remote dependency that enables the cryptographic plug-in to be invoked remotely as a third party component.
Fig. 2 is a schematic structural diagram of a plug-in device for an encryption algorithm in the block chain technology according to an embodiment of the present application; as shown in fig. 2, it includes:
a first program unit 201, configured to create a plug-in project and a host project, and assign IDs to the plug-in project and the host project based on a set ID logical offset;
a second program unit 202, configured to create a project repository according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are located in the same project repository;
a third program unit 203, configured to declare a dummy plug-in project in the same project repository, where the dummy plug-in project is used for managing cryptographic algorithm code entries;
a fourth program unit 204, configured to access the encryption algorithm code entry to call an encryption algorithm and load the encryption algorithm into a set plug-in framework by enabling the dummy plug-in project based on the plug-in project, so as to form an encryption plug-in of the host project, and record the encryption plug-in the project repository.
Optionally, the first program element is further adapted to: and analyzing the created object declaration folder to determine a warehouse address and a dependent data packet, and creating a plug-in project and a host project according to the warehouse address and the dependent data packet.
Optionally, the first program unit is further configured to allocate IDs to the plug-in project and the host project according to the set ID logical offset and the set ID anchor location.
Optionally, the second program element is further configured to: and acquiring the configured warehouse attribute, and creating a project local warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are positioned in the same project local warehouse.
Optionally, the third program element is further configured to: according to the set generic argument, defining the generic argument as an execution entry of the cryptographic algorithm code to create a pseudo plug-in project declaration and manage the cryptographic algorithm code entry by the pseudo plug-in project.
Optionally, the third program element is further configured to: : determining a script code module for creating the pseudo plug-in project, embedding a set generic argument into the script code, and defining the generic argument as an execution entry of the encryption algorithm code to create a pseudo plug-in project declaration and manage the encryption algorithm code entry by the pseudo plug-in project.
Optionally, the pseudo plug-in project is a script plug-in, or a binary plug-in, or an object plug-in.
Optionally, the fourth program element is further configured to: and setting a code dependency mode by enabling the pseudo plug-in project based on the plug-in project, so that the encryption algorithm code entry is accessed to call an encryption algorithm and is loaded into a set plug-in framework to form an encryption plug-in of the host project, and the encryption plug-in is recorded in the project warehouse.
Optionally, the dependency pattern includes a local dependency that enables the cryptographic plug-in to be invoked locally, a remote dependency that enables the cryptographic plug-in to be invoked remotely as a third party component.
Fig. 3 is a schematic structural diagram of an electronic device in an eighth embodiment of the present application; as shown in fig. 3, the electronic device includes a memory 301 and a processor 302, the memory stores an executable program, and the processor executes the executable program to perform the following steps:
creating a plug-in project and a host project, and allocating IDs to the plug-in project and the host project based on a set ID logic offset;
creating a project warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are located in the same project warehouse;
declaring a pseudo plug-in project at said same project repository, said pseudo plug-in project for managing cryptographic algorithm code entries;
and accessing the encryption algorithm code entry to call an encryption algorithm and loading the encryption algorithm into a set plug-in framework by enabling the pseudo plug-in project based on the plug-in project so as to form the encryption plug-in of the host project and record the encryption plug-in the project warehouse.
FIG. 4 is a schematic diagram of a hardware structure of an electronic device according to a ninth embodiment of the present application; as shown in fig. 4, the hardware structure of the electronic device may include: the electronic device 400 includes a computing unit 401 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 402 or a computer program loaded from a storage unit 406 into a Random Access Memory (RAM) 403. In the RAM 403, various programs and data required for the operation of the device 400 can also be stored. The calculation unit 401, the ROM 402, and the RAM 403 are connected to each other via a bus 404. An input/output (I/O) interface 405 is also connected to bus 404.
A number of components in the electronic device 400 are connected to the I/O interface 405, including: an input unit 406, an output unit 407, a storage unit 408, and a communication unit 409. The input unit 406 may be any type of device capable of inputting information to the electronic device 400, and the input unit 406 may receive input numeric or character information and generate key signal inputs related to user settings and/or function controls of the electronic device. Output unit 407 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, a video/audio output terminal, a vibrator, and/or a printer. The storage unit 404 may include, but is not limited to, a magnetic disk, an optical disk. The communication unit 409 allows the electronic device 400 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers, and/or chipsets, such as bluetooth (TM) devices, wiFi devices, wiMax devices, cellular communication devices, and/or the like.
Computing unit 401 may be a variety of general and/or special purpose processing components with processing and computing capabilities. Some examples of the computing unit 401 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The calculation unit 401 executes the respective methods and processes described above. For example, in some embodiments, the above steps may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 40. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 400 via the ROM 402 and/or the communication unit 409. In some embodiments, the computing unit 401 may be configured to perform the above steps in any other suitable manner (e.g., by means of firmware).
The electronic device of the embodiments of the present application exists in various forms, including but not limited to:
(1) Mobile communication devices, which are characterized by mobile communication capabilities and are primarily targeted at providing voice and data communications. Such terminals include smart phones (e.g., iphones), multimedia phones, functional phones, and low-end phones, among others.
(2) The ultra-mobile personal computer equipment belongs to the category of personal computers, has calculation and processing functions and generally has the characteristic of mobile internet access. Such terminals include PDA, MID, and UMPC devices, such as ipads.
(3) Portable entertainment devices such devices may display and play multimedia content. Such devices include audio and video players (e.g., ipods), handheld game consoles, electronic books, as well as smart toys and portable car navigation devices.
(4) The server is similar to a general computer architecture, but has higher requirements on processing capability, stability, reliability, safety, expandability, manageability and the like because of the need of providing highly reliable services.
(5) And other electronic devices with data interaction functions.
It should be noted that, in the present specification, all the embodiments are described in a progressive manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus and system embodiments, since they are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described embodiments of the apparatus and system are merely illustrative, and the modules illustrated as separate components may or may not be physically separate, and the components suggested as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only one specific embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A plug-in method of encryption algorithm in block chain technology is characterized by comprising the following steps:
creating a plug-in project and a host project, and allocating IDs to the plug-in project and the host project based on a set ID logic offset;
creating a project warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are located in the same project warehouse;
determining a script code module for creating the pseudo plug-in project, embedding a set generic argument into the script code, and defining the generic argument as an execution entry of the encryption algorithm code to create a pseudo plug-in project statement and manage the encryption algorithm code entry by the pseudo plug-in project;
and setting a code dependency mode by enabling the pseudo plug-in project based on the plug-in project, so that the encryption algorithm code entry is accessed to call an encryption algorithm and is loaded into a set plug-in framework to form an encryption plug-in of the host project, and the encryption plug-in is recorded in the project warehouse.
2. The method according to claim 1, wherein the creating of the plug-in project and the host project comprises: and analyzing the created object declaration folder to determine a warehouse address and a dependent data packet, and creating a plug-in project and a host project according to the warehouse address and the dependent data packet.
3. The method according to claim 1, wherein the assigning IDs to the plug-in project and the host project based on the set logical offset of IDs comprises: and distributing IDs for the plug-in project and the host project according to the set ID logic offset and the set ID anchor point location.
4. The method according to claim 1, wherein creating a project repository from the plug-in project ID and the hosting project ID, such that the plug-in project and the hosting project are located in the same project repository, comprises: and acquiring the configured warehouse attribute, and creating a project local warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are positioned in the same project local warehouse.
5. The method of claim 1, wherein the dependency pattern comprises a local dependency that enables the encryption plug-in to be invoked locally, and a remote dependency that enables the encryption plug-in to be invoked remotely as a third party component.
6. A plug-in device for encryption algorithm in block chain technology, comprising:
the first program unit is used for creating a plug-in project and a host project and distributing IDs to the plug-in project and the host project based on the set ID logic offset;
a second program unit, configured to create a project repository according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are located in the same project repository;
a third program unit for determining a script code module for creating the pseudo plug-in project, embedding a set generic argument into the script code, and defining the generic argument as an execution entry of the cryptographic algorithm code, so as to create a pseudo plug-in project declaration and manage the cryptographic algorithm code entry by the pseudo plug-in project;
and the fourth program unit is used for setting a code dependency mode by enabling the pseudo plug-in project based on the plug-in project, so that the encryption algorithm code entry is accessed to call an encryption algorithm and is loaded into a set plug-in framework to form an encryption plug-in of the host project, and the encryption plug-in is recorded in the project warehouse.
7. The apparatus according to claim 6, wherein the creating plug-in project and host project comprises: and analyzing the created object declaration folder to determine a warehouse address and a dependent data packet, and creating a plug-in project and a host project according to the warehouse address and the dependent data packet.
8. The apparatus according to claim 6, wherein said creating a project repository from the plug-in project ID and the hosting project ID, such that the plug-in project and the hosting project are located in the same project repository, comprises: and acquiring the configured warehouse attribute, and creating a project local warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are positioned in the same project local warehouse.
9. An electronic device, comprising a memory and a processor, wherein the memory stores an executable program, and the processor executes the executable program to perform the following steps:
creating a plug-in project and a host project, and allocating IDs to the plug-in project and the host project based on a set ID logic offset;
creating a project warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are located in the same project warehouse;
determining a script code module for creating the pseudo plug-in project, embedding a set generic parameter into the script code, and defining the generic parameter as an execution entry of the encryption algorithm code, so as to create a pseudo plug-in project declaration and manage the encryption algorithm code entry through the pseudo plug-in project;
and setting a code dependency mode by enabling the pseudo plug-in project based on the plug-in project, so that the encryption algorithm code entry is accessed to call an encryption algorithm and is loaded into a set plug-in framework to form an encryption plug-in of the host project, and the encryption plug-in is recorded in the project warehouse.
10. A computer storage medium storing a computer-executable program that, when executed, performs the steps of:
creating a plug-in project and a host project, and allocating IDs to the plug-in project and the host project based on a set ID logic offset;
creating a project warehouse according to the plug-in project ID and the host project ID, so that the plug-in project and the host project are located in the same project warehouse;
determining a script code module for creating the pseudo plug-in project, embedding a set generic parameter into the script code, and defining the generic parameter as an execution entry of the encryption algorithm code, so as to create a pseudo plug-in project declaration and manage the encryption algorithm code entry through the pseudo plug-in project;
and setting a code dependency mode by enabling the pseudo plug-in project based on the plug-in project, so that the encryption algorithm code entry is accessed to call an encryption algorithm and is loaded into a set plug-in framework to form an encryption plug-in of the host project, and the encryption plug-in is recorded in the project warehouse.
CN202210976906.1A 2022-08-15 2022-08-15 Plug-in method and device for encryption algorithm in block chain technology and related product Pending CN115248931A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210976906.1A CN115248931A (en) 2022-08-15 2022-08-15 Plug-in method and device for encryption algorithm in block chain technology and related product

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210976906.1A CN115248931A (en) 2022-08-15 2022-08-15 Plug-in method and device for encryption algorithm in block chain technology and related product

Publications (1)

Publication Number Publication Date
CN115248931A true CN115248931A (en) 2022-10-28

Family

ID=83699180

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210976906.1A Pending CN115248931A (en) 2022-08-15 2022-08-15 Plug-in method and device for encryption algorithm in block chain technology and related product

Country Status (1)

Country Link
CN (1) CN115248931A (en)

Similar Documents

Publication Publication Date Title
CN109032691B (en) Applet running method and device and storage medium
CN111726399B (en) Docker container secure access method and device
CN110009321B (en) Transfer method and system based on block chain intelligent contract
CN110245518B (en) Data storage method, device and equipment
CN109726067B (en) Process monitoring method and client device
CN111782338A (en) Data processing method and system based on intelligent contract of block chain
CN113271364B (en) Sharing system, method, computer device and storage medium of service arrangement data
CN110652728A (en) Game resource management method and device, electronic equipment and storage medium
CN113965402A (en) Configuration method and device of firewall security policy and electronic equipment
CN115269056A (en) Encryption module plug-in method and device based on class loader and related product
CN113050985A (en) Front-end engineering dependence automatic registration method and device
CN115391801A (en) Method and device for updating encryption module in block chain system and related products
CN115270161A (en) Encryption method and device based on encryption plug-in and related product
CN115248931A (en) Plug-in method and device for encryption algorithm in block chain technology and related product
CN115878510A (en) Page table modifying method, page table verifying method, page table modifying device, page table verifying device and electronic equipment
CN113806730B (en) Method, system, equipment and medium for inputting security password
CN115760391A (en) Intelligent contract changing method and device in block chain, electronic equipment and storage medium
CN113986132A (en) Method, device and related product for sharing storage resources in heterogeneous network
CN108874696B (en) Automatic testing method and device for multi-authority safety storage equipment and electronic equipment
CN115348087A (en) Rapid encryption method and device based on metadata and related products
Lee et al. Mobile collaborative computing on the fly
CN115618382A (en) Storage method and device for shared data in alliance chain and electronic equipment
CN115906150A (en) Method and device for accessing sensitive data in alliance chain and electronic equipment
CN115248930A (en) Encryption method and device applied to block chain and related product
WO2017028729A1 (en) Method, apparatus, and electronic device for determining whether an application program is an authorized application program

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination