A client-side obfuscated network directory server hiding method

Abstract

This invention provides a method for hiding obfuscated network directory servers on a client-side basis, relating to the field of privacy data security protection technology, and solving the current limitations in hiding obfuscated network directory servers. The method includes: constructing a hidden network corresponding to the obfuscated network directory server, which is an IPFS network composed of multiple IPFS nodes; the directory server publishing directory files to the IPFS network, and the IPFS nodes in the IPFS network periodically synchronizing the published directory files by retrieving IPNS records; configuring the IPFS node address and IPNS record for the client, and the client obtaining the directory files of the directory server through the IPNS record after connecting to the specified IPFS node. This invention can both utilize the IPFS network to hide the real IP of the obfuscated network directory server and improve scalability while enabling connected clients to obtain the latest directory information.

Description

Technical Field

[0001] This invention relates to the field of privacy data security protection technology, specifically to a method for obfuscating network directory servers for client-side applications. Background Technology

[0002] With the increasing demand for privacy protection among internet users, obfuscated networks have emerged. Obfuscated networks aim to hide the identity and communication relationships of entities through various technologies, such as message forwarding, data encryption, and traffic obfuscation, thereby providing users with communication privacy protection. Directory servers play a crucial role in obfuscated networks, responsible for storing and distributing information about nodes in the network. This allows new users to access existing node information and successfully join the obfuscated network. Currently, there are two main solutions for obfuscated network directory servers: centralized and decentralized.

[0003] Centralized directory servers, due to their fixed and publicly accessible IP addresses, are vulnerable to various attacks, such as blocked communication channels and DDoS attacks. Furthermore, attackers can potentially discover user identities and threaten user privacy by monitoring inbound and outbound connections to the directory server. Decentralized solutions, also known as distributed directory servers, while addressing the centralization problem to some extent, still face security risks due to a lack of centralized control, complex node discovery processes, and malicious node attacks, as well as deanonymization attacks caused by differences in user network perception.

[0004] Currently, obfuscated networks, including the Tor network, use centralized directory servers, so hiding these centralized directory servers is crucial. Traditional methods include... Figure 1 As shown, users can directly access the obfuscated network directory server through the client to obtain obfuscated network directory information. Since the directory server's IP is fixed and publicly available, attackers can prevent users from accessing the obfuscated network by blocking the directory server.

[0005] A proxy node in a proxy server acts as an intermediary between the client and the directory server, hiding the directory server's IP address. If there is only one proxy node, its failure could disrupt the entire data transmission link, affecting communication between the client and the directory server.

[0006] To ensure that the paths from proxy nodes to their corresponding nodes on the directory server are not singular, a proxy layer with multiple proxy nodes is typically designed between the client and the directory server, such as... Figure 2 As shown, although the client accesses from different proxy nodes, they can all obtain obfuscated network directory information from the directory server. Even if a proxy node is interrupted, the client can still obtain obfuscated network directory information from the directory server by accessing other proxy nodes.

[0007] However, when deploying multiple proxy node servers in the proxy layer, the address of the directory server needs to be configured in the configuration file of each proxy node to ensure that the proxy node can forward requests to the directory server, thereby obtaining obfuscated network directory information. Therefore, this method is cumbersome and inflexible when scaling the proxy layer, as each proxy node can only be configured to forward requests to the directory server address.

[0008] Therefore, how to obtain obfuscated network directory information on the directory server while hiding the directory server address, and how to flexibly expand the intermediate proxy nodes of the proxy layer, has become a key problem that needs to be solved by those skilled in the art. Summary of the Invention

[0009] The purpose of this invention is to address the current limitations in hiding obfuscated network directory servers, including fixed IP addresses with no real hiding, inflexible proxy layer expansion even when the IP is hidden, and a single proxy layer topology. Clients also struggle to obtain real-time updated obfuscated network directory information. Therefore, this invention proposes a client-side method for hiding obfuscated network directory server information. This method utilizes the IPFS network to hide the real IP address of the obfuscated network directory server, thereby reducing the risk of attacks. This invention offers greater flexibility in expanding the IPFS network nodes between the client and the obfuscated network directory server, enabling real-time acquisition of obfuscated network directory information. The IPFS network nodes themselves periodically retrieve directory files from the obfuscated network directory server, ensuring that connected clients receive the latest directory information.

[0010] The present invention employs the following technical solutions to achieve its objective:

[0011] A client-side obfuscated network directory server hiding method includes the following steps:

[0012] S1. Based on IPFS technology, construct a hidden network corresponding to the directory server of the obfuscated network. This hidden network is an IPFS network composed of multiple IPFS nodes.

[0013] S2. Use the IPFS network as an intermediate proxy layer for connecting clients and directory servers, with the directory server publishing directory files to the IPFS network;

[0014] In the S3 IPFS network, IPFS nodes periodically synchronize the directory files published by the directory server by retrieving IPNS records.

[0015] S4. Configure the IPFS node address and IPNS record for the client. After connecting to the specified IPFS node, the client obtains the directory files of the directory server through the IPNS record.

[0016] Specifically, in step S1, each IPFS node has a built-in IPFS component, and the connection between each IPFS node is achieved through the connection of each IPFS component; the directory server of the obfuscated network also has a built-in IPFS component, and the directory server connects to the IPFS node through its built-in IPFS component. The IPFS component of the directory server is used for the publication and transmission of directory files to the IPFS network.

[0017] The topology of the IPFS network and the directory server satisfies the following constraints: at least one IPFS node in the IPFS network maintains a connection with the directory server, and the remaining IPFS nodes maintain mutual connections by constructing a connected graph.

[0018] Configure the client to access the address of any IPFS node in the IPFS network, enabling the client to connect to the IPFS network. Based on the topological connection between the IPFS network and the directory server, any IPFS node configured on the client can access the directory server and transfer the obtained directory files to the client.

[0019] Preferably, during the construction or use phase of the IPFS network, the expansion of the IPFS network is carried out by adding new IPFS nodes. When a new IPFS node needs to be added, any existing IPFS node in the IPFS network is configured as a bootstrap node. The bootstrap node only needs to be directly or indirectly connected to the directory server. Connecting the newly added IPFS node to the bootstrap node realizes the expansion of the IPFS network.

[0020] Specifically, in step S2, the process of the directory server publishing directory files to the IPFS network is as follows:

[0021] First, the obfuscated nodes in the obfuscation network report their status information to the directory server. The directory server collects and summarizes the status information of the obfuscation network and generates the corresponding directory file.

[0022] The directory server then uses its built-in IPFS component to add the directory file to the IPFS network for separate storage using the add command, and generates the access code corresponding to the directory file. Then, it uses the publish command to bind the directory file access code to its IPFS component, thereby publishing it to the IPFS network.

[0023] Preferably, when the directory server binds the directory file access code to its IPFS component, it pre-generates an IPNS record bound to the directory file access code and publishes the IPNS record to the IPFS network. During communication, as the directory file is continuously updated, the binding relationship between the directory file access code and its bound IPNS record remains unchanged. When the client accesses any IPFS node in the IPFS network, it retrieves the directory file by searching for the corresponding IPNS record through that IPFS node.

[0024] Furthermore, in step S3, when any IPFS node needs to synchronously obtain the directory files published by the directory server, the IPNS record generated by the directory server is pre-configured for all IPFS nodes in the IPFS network.

[0025] IPFS nodes that need to synchronously obtain directory files decide whether to obtain the access code of the corresponding directory file from other IPFS nodes that have cached the corresponding IPNS record by querying the IPNS record. Then, based on the obtained access code, the corresponding directory file can be synchronously obtained.

[0026] Specifically, if the IPFS node that needs to synchronously obtain the directory file has cached the corresponding IPNS record, then the IPNS record is directly parsed to obtain the access code of the corresponding directory file; if the IPFS node has not cached the corresponding IPNS record, then the IPFS distributed hash table (DHT) is used to search for IPFS nodes that have cached the IPNS record in the IPFS network, and the access code of the directory file corresponding to the IPNS record is obtained from them.

[0027] Specifically, after obtaining the access code, the IPFS node requests access to the corresponding stored directory file from the IPFS network based on the access code. The IPFS network then retrieves the directory file based on the access code and returns it to the corresponding IPFS node, thus enabling the IPFS node to synchronously obtain the directory file.

[0028] Specifically, in step S4, the process of the client obtaining the directory file through the IPNS record is as follows: After the client connects to any specified IPFS node, it completes the configuration of the IPFS node address and the IPNS record corresponding to the required directory file; the client sends a file request containing the IPNS record to the connected IPFS node; after receiving the file request from the client, the IPFS node extracts the corresponding IPNS record configuration, parses it into an access code, obtains the corresponding directory file according to the access code, and returns it to the client.

[0029] Specifically, directory files can be stored on the storage of any one or more IPFS nodes in the IPFS network. When an IPFS node receives a file request from a client, it first checks whether it has stored the directory file corresponding to the IPNS record. If so, it directly returns the directory file to the client. If it has not stored it, it searches for and retrieves the directory file corresponding to the IPNS record in the IPFS network according to the client's IPNS record configuration, and then returns the directory file to the client, thus realizing the process of the client obtaining the required directory file from the directory server.

[0030] In summary, due to the adoption of this technical solution, the beneficial effects of this invention are as follows:

[0031] This invention effectively hides the true physical address and port information of the directory server by deploying an IPFS network between the client and the obfuscated network directory server. This mechanism significantly reduces the risk of direct network attacks on the directory server and prevents attackers from launching targeted threats through exposed IP addresses, thereby enhancing the overall security and stability of the system.

[0032] Furthermore, this invention achieves a high degree of flexibility in network expansion after the directory server successfully connects to the IPFS network. Newly added IPFS nodes do not need to specify the directory server's specific address or port during startup and configuration; they only need to connect to an existing node in the IPFS network to automatically establish normal communication and data interaction with the directory server. This design not only significantly simplifies the network expansion process but also enables the system to quickly respond to anomalies such as attackers attempting to discover and block IPFS nodes. It maintains service continuity by rapidly deploying new nodes, ensuring the network maintains efficient operation and adjustability in dynamic environments. Attached Figure Description

[0033] The present invention is further described in detail with reference to the following figures, which include 7 figures as follows:

[0034] Figure 1 A schematic diagram illustrating the traditional method of client access to obfuscated network directory servers in existing technologies;

[0035] Figure 2 This is a schematic diagram illustrating how a client accesses a scrambled network directory server through a proxy node in existing technology.

[0036] Figure 3 This is a simplified flowchart illustrating the overall process of the method for obfuscating network directory servers in this invention.

[0037] Figure 4 This is a schematic diagram of the topology of the hidden network of the directory server based on IPFS in this invention;

[0038] Figure 5 This is a schematic diagram illustrating the specific process of a directory server publishing directory files to the IPFS network in this invention.

[0039] Figure 6 This is a schematic diagram illustrating the specific process by which an IPFS node obtains directory files from the IPFS network in this invention.

[0040] Figure 7 This is a schematic diagram illustrating the specific process by which the client obtains directory files from the IPFS node in this invention. Detailed Implementation

[0041] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0042] Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0043] A client-side obfuscation method for hiding network directory servers. Figure 3 The overall process steps of this method are shown and can be viewed simultaneously. The key steps are summarized as follows:

[0044] S1. Based on IPFS technology, construct a hidden network corresponding to the directory server of the obfuscated network. This hidden network is an IPFS network composed of multiple IPFS nodes.

[0045] S2. Use the IPFS network as an intermediate proxy layer for connecting clients and directory servers, with the directory server publishing directory files to the IPFS network;

[0046] In the S3 IPFS network, IPFS nodes periodically synchronize the directory files published by the directory server by retrieving IPNS records.

[0047] S4. Configure the IPFS node address and IPNS record for the client. After connecting to the specified IPFS node, the client obtains the directory files of the directory server through the IPNS record.

[0048] In practical applications, the object to be hidden in this implementation is the obfuscated network directory server, which can be directly referred to as the directory server. Besides the directory server, this implementation also involves an IPFS network and clients; the directory server is responsible for collecting, summarizing, and publishing the directory files of the obfuscated network, which contain the relevant directory information required by the clients; the IPFS network consists of multiple IPFS nodes, responsible for storing and synchronizing the directory files; and the clients obtain the directory files through the IPFS network to support subsequent business applications.

[0049] IPFS (InterPlanetary File System) is a peer-to-peer distributed file system technology that changes the way information is distributed and stored on the network. This technology combines distributed hash tables, incentive layers, Merkle DAG tree data structures, version control, and self-certified naming to form a unique file storage and sharing system. This implementation uses this technology, with adaptive modifications, to be applied to the task of obfuscating network directory servers.

[0050] In general, the method of this embodiment first constructs a directory server hidden network based on IPFS nodes. This hidden network is an IPFS network composed of multiple IPFS nodes. Furthermore, the directory server also has corresponding IPFS components, enabling it to perform functions such as... Figures 5 to 7 In the specific process, it can also be considered an IPFS node, thus enabling it to connect with other IPFS nodes to achieve data communication and interaction. In this embodiment, the IPFS network serves as an intermediate proxy layer connecting the client and the directory server. Utilizing the distributed and decentralized characteristics of the IPFS network, the purpose of decentralized storage of directory files by the directory server can be achieved; utilizing the P2P characteristics of the IPFS network, the client can indirectly access the directory server by accessing the IPFS node, thereby achieving the hiding of directory server IP address, port, and other information from the client.

[0051] Therefore, based on the constructed IPFS network, the directory server first generates a directory file from the collected and aggregated obfuscated network directory information, then adds the directory file to the IPFS network and generates an access code, and finally publishes the directory file to generate an IPNS record. The IPNS record itself is a naming system in IPFS technology, allowing users to create a variable and readable name to point to content in IPFS. An IPNS record can be viewed as a fixed but mutable reference; this reference can point to any IPFS hash. Even if the underlying IPFS content changes, as long as the IPNS record is updated to point to the new hash, users can still access the latest content through the same IPNS address. This provides a mechanism to maintain a persistent reference to dynamic content while preserving the security and integrity of content addressing.

[0052] In this implementation, IPFS nodes periodically synchronize directory files from the IPFS network based on the IPNS records configured during initialization. During this process, the relevant IPFS nodes can retrieve IPNS records using a distributed hash table (DHT). Finally, the client connects to the specified IPFS node based on the configured IPFS node address and IPNS records, and obtains the directory files from the directory server through the IPNS records.

[0053] Because the topology of the obfuscated network itself is constantly changing during application, the directory server periodically generates obfuscated network directory files. When the directory server publishes new directory files, IPFS nodes may cache previous obfuscated network directory files. Therefore, in order to ensure that the directory files obtained by the client are always the latest version and updated in real time, IPFS nodes also periodically synchronize the IPNS records of the directory server to obtain the latest directory files, thereby ensuring that the directory files obtained by the client are also up-to-date in real time.

[0054] This embodiment will now provide a more detailed description of each step in the method. For example... Figure 4 As shown, in step S1, each IPFS node has a built-in IPFS component, and the connection between each IPFS node is achieved through the connection of each IPFS component; the directory server of the obfuscated network also has a built-in IPFS component, and the directory server connects to the IPFS node through its built-in IPFS component. The IPFS component of the directory server is used for the publication and transmission of directory files to the IPFS network.

[0055] The topology of the IPFS network and the directory server satisfies the following constraints: at least one IPFS node in the IPFS network is connected to the directory server, and the remaining IPFS nodes are connected to each other by building a connected graph. This allows the remaining IPFS nodes to indirectly access the directory server when they access the IPFS network.

[0056] exist Figure 4 In the topology shown, node C is directly connected to the obfuscated network directory server, and their IPFS connection is implemented based on their respective IPFS components; nodes B and D are both connected to node C, while node A is connected to node B. Although nodes A, B, and D are not directly connected to the directory server, they can obtain the directory server's address through addressing and thus communicate with it.

[0057] The client only needs to connect to node A to obtain the directory files published by the directory server. This means that the client is configured to access the address of any IPFS node in the IPFS network, enabling the client to access the IPFS network. Based on the topological connection between the IPFS network and the directory server, any IPFS node configured on the client can access the directory server and transfer the obtained directory files to the client.

[0058] As a preferred embodiment of this implementation, during the construction or use phase of the IPFS network, the IPFS network is expanded by adding new IPFS nodes. When a new IPFS node needs to be added, any existing IPFS node in the IPFS network is configured as a bootstrap node. The bootstrap node only needs to be directly or indirectly connected to the directory server. Connecting the newly added IPFS node to the bootstrap node realizes the expansion of the IPFS network. Therefore, the expansion process of IPFS network nodes is more flexible than the expansion configuration of related proxy servers in the prior art.

[0059] Since the directory server has a built-in IPFS component, it can be viewed as an IPFS node to implement related functions, which is reflected in... Figure 5 And in the subsequent flowchart. Therefore, as Figure 5 As shown, in step S2, the process of the directory server publishing directory files to the IPFS network is as follows:

[0060] First, the obfuscated nodes in the obfuscated network report their status information to the directory server. The directory server collects and summarizes the status information of the obfuscated network and generates the corresponding directory file. The summarized status information may include relevant data such as traffic transmission and reception rate, CPU utilization, and memory utilization.

[0061] The directory server then uses its built-in IPFS component to add the directory file to the IPFS network using an add command, storing it separately and generating a corresponding access code for the directory file. The IPFS network can store directory files directly on one or more pre-defined IPFS nodes, or in a completely independent storage device belonging to the network, allowing the directory file to be retrieved and accessed based on the access code. After storage and generation are complete, the directory server uses a publish command to bind the directory file's access code to its IPFS component, generating a corresponding IPNS record and publishing it to the IPFS network.

[0062] In this embodiment, when the directory server binds a directory file access code to its IPFS component, it pre-generates an IPNS record bound to that directory file access code and publishes the IPNS record to the IPFS network. During communication, as the directory file is continuously updated, the binding relationship between the directory file access code and its bound IPNS record remains unchanged. When a client accesses any IPFS node in the IPFS network, it retrieves the directory file by searching for the corresponding IPNS record through that IPFS node.

[0063] like Figure 6 As shown, in step S3, when any IPFS node needs to synchronously obtain the directory files published by the directory server, the IPNS records generated by the directory server are pre-configured for all IPFS nodes in the IPFS network.

[0064] IPNS records can typically be configured on IPFS nodes connected to the directory server, for example... Figure 4 Node C in the IPFS network; if no IPNS record is configured on any IPFS node in the IPFS network, when an IPFS node requests to resolve an IPNS record, it can be done by... Figure 6 As shown in the diagram, requests are made step by step until the IPFS component of the directory server is found. At this point, the directory server is also regarded as an IPFS node.

[0065] When an IPFS node is configured with an IPNS record (meaning it's manually specified in the configuration file), it can only obtain the mapping between the IPNS record and access codes and save this information when it actively requests the IPNS record from the IPFS network. When a directory server publishes directory files and generates the corresponding IPNS record, it publishes the record to the IPFS network. However, other IPFS nodes need to retrieve this record from the network by querying it. Because directory files may change in real time, IPFS nodes periodically request IPNS records from the IPFS network to update the corresponding access codes, thus ensuring that directory files are retrieved synchronously based on the latest access codes.

[0066] Therefore, IPFS nodes that need to synchronously obtain directory files need to determine whether they need to obtain the access code of the directory file corresponding to the IPNS record from other IPFS nodes that have cached the corresponding IPNS record through a query request, and then realize the synchronous acquisition of the corresponding directory file based on the obtained access code.

[0067] In this embodiment, specifically, if the IPFS node that needs to synchronously obtain the directory file has cached the corresponding IPNS record, then the IPNS record is directly parsed to obtain the access code of the corresponding directory file; if the IPFS node has not cached the corresponding IPNS record, then the IPFS distributed hash table DHT is used to search for the IPFS node that has cached the IPNS record in the IPFS network, and the access code of the directory file corresponding to the IPNS record is obtained from it.

[0068] After obtaining the access code, the principle of retrieving the corresponding directory file based on the access code is similar to retrieving an IPNS record. The location of the directory file depends on its storage location; it might be stored on an IPFS node within the IPFS network, on a separate storage device within the IPFS network, or even not sent and stored within the IPFS network. In this case, it's necessary to access the IPFS component corresponding to the directory server, treating the directory server as an IPFS node. The access code is used to request access to the corresponding stored directory file from the IPFS network. The IPFS network retrieves the directory file based on the access code and returns it to the corresponding IPFS node, thus achieving synchronous retrieval of the directory file by the IPFS node.

[0069] Finally, in step S4, as Figure 7 As shown, to obtain directory files for the obfuscated network, the client directly connects to one or more IPFS nodes; the IPFS nodes connected by the client then obtain the required directory files using step S3. Once the client connects to any specified IPFS node, it first needs to configure the IPFS node address and the corresponding IPNS record for the required directory file; the client then sends a file request containing the IPNS record to the connected IPFS node, which can be in the form of an HTTP request.

[0070] After receiving a file request from a client, the IPFS node extracts the corresponding IPNS record configuration, checks whether it already has the relevant cache, and if not, retrieves the required IPNS record according to step S3. Finally, it parses the access code, retrieves the corresponding directory file based on the access code, and returns it to the client.

[0071] In this implementation, since the directory file can be stored on the storage of any one or more IPFS nodes in the IPFS network, when an IPFS node receives a file request from a client, after confirming that the IPNS record and access code are correct, it can first check whether it has stored the directory file corresponding to the IPNS record. If so, it directly returns the directory file to the client; if it has not stored it, it searches for and retrieves the directory file corresponding to the IPNS record in the IPFS network according to the client's IPNS record configuration, and then returns the directory file to the client, thus realizing the process of the client obtaining the required directory file from the directory server.

[0072] The obfuscated network directory server hiding method of this embodiment can be applied to a corresponding computer system, which includes a memory, a processor, and a computer program stored in the memory; when the processor executes the computer program, it implements the steps of the aforementioned obfuscated network directory server hiding method.

[0073] These computer programs or instructions in this embodiment may be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that can perform the function specified in one or more steps of the method.

Claims

1. A method for obfuscating network directory servers for client-side applications, characterized in that, Includes the following steps: S1. Based on IPFS technology, construct a hidden network corresponding to the directory server of the obfuscated network. This hidden network is an IPFS network composed of multiple IPFS nodes. S2. Use the IPFS network as an intermediate proxy layer for connecting clients and directory servers, with the directory server publishing directory files to the IPFS network; In the S3 IPFS network, IPFS nodes periodically synchronize the directory files published by the directory server by retrieving IPNS records. S4. Configure the IPFS node address and IPNS record for the client. After the client connects to the specified IPFS node, it can obtain the directory files of the directory server through the IPNS record. In step S2, the process of the directory server publishing directory files to the IPFS network is as follows: First, the obfuscated nodes in the obfuscation network report their status information to the directory server. The directory server collects and summarizes the status information of the obfuscation network and generates the corresponding directory file. The directory server then uses its built-in IPFS component to add the directory file to the IPFS network for separate storage using the add command and generate the access code corresponding to the directory file. Then, it uses the publish command to bind the directory file access code to its IPFS component, thereby publishing it to the IPFS network. When a directory server binds a directory file access code to its IPFS component, it pre-generates an IPNS record bound to that directory file access code and publishes the IPNS record to the IPFS network. During communication, as the directory file is continuously updated, the binding relationship between the directory file access code and its bound IPNS record remains unchanged. When a client accesses any IPFS node in the IPFS network, it retrieves the directory file by searching for the corresponding IPNS record through that IPFS node. In step S3, when any IPFS node needs to synchronously obtain the directory files published by the directory server, the IPNS record generated by the directory server is pre-configured for all IPFS nodes in the IPFS network. IPFS nodes that need to synchronously obtain directory files decide whether to obtain the access code of the directory file corresponding to the IPNS record from other IPFS nodes that have cached the corresponding IPNS record through a query request, based on whether they have already cached the corresponding IPNS record, and then realize the synchronous acquisition of the corresponding directory file based on the obtained access code; If the IPFS node that needs to synchronously obtain the directory file has cached the corresponding IPNS record, then the IPNS record is directly parsed to obtain the access code of the corresponding directory file; if the IPFS node has not cached the corresponding IPNS record, then the IPFS distributed hash table (DHT) is used to search for IPFS nodes that have cached the IPNS record in the IPFS network, and the access code of the directory file corresponding to the IPNS record is obtained from them.

2. The method for obfuscating network directory servers according to claim 1, characterized in that: In step S1, each IPFS node has a built-in IPFS component, and the connection between each IPFS node is achieved through the connection of each IPFS component; the directory server of the obfuscated network also has a built-in IPFS component, and the directory server connects to the IPFS node through its built-in IPFS component. The IPFS component of the directory server is used for the publication and transmission of directory files to the IPFS network. The topology of the IPFS network and the directory server satisfies the following constraints: at least one IPFS node in the IPFS network maintains a connection with the directory server, and the remaining IPFS nodes maintain mutual connections by constructing a connected graph. Configure the client to access the address of any IPFS node in the IPFS network, enabling the client to access the IPFS network; Based on the topological connection between the IPFS network and the directory server, any IPFS node configured on the client can access the directory server and transfer the obtained directory files to the client.

3. The method for obfuscating network directory servers according to claim 2, characterized in that: During the construction or use phase of the IPFS network, the IPFS network is expanded by adding new IPFS nodes. When a new IPFS node needs to be added, any existing IPFS node in the IPFS network is configured as a bootstrap node. The bootstrap node only needs to be directly or indirectly connected to the directory server. Connecting the newly added IPFS node to the bootstrap node realizes the expansion of the IPFS network.

4. The method for obfuscating network directory servers according to claim 1, characterized in that: After obtaining the access code, the IPFS node requests access to the corresponding stored directory file from the IPFS network based on the access code. The IPFS network then retrieves the directory file based on the access code and returns it to the corresponding IPFS node, thus enabling the IPFS node to synchronously obtain the directory file.

5. The method for obfuscating network directory servers according to claim 1, characterized in that, In step S4, the process of the client obtaining the directory file through the IPNS record is as follows: After the client connects to any specified IPFS node, it completes the configuration of the IPFS node address and the IPNS record corresponding to the required directory file; the client sends a file request containing the IPNS record to the connected IPFS node; after receiving the file request from the client, the IPFS node extracts the corresponding IPNS record configuration, parses it into an access code, obtains the corresponding directory file according to the access code, and returns it to the client.

6. The method for obfuscating a network directory server according to claim 5, characterized in that: Directory files can be stored on the storage of any one or more IPFS nodes in the IPFS network. When an IPFS node receives a file request from a client, it first checks whether it has stored the directory file corresponding to the IPNS record. If so, it directly returns the directory file to the client. If it has not stored it, it searches for and retrieves the directory file corresponding to the IPNS record in the IPFS network according to the client's IPNS record configuration, and then returns the directory file to the client, thus realizing the process of the client obtaining the required directory file from the directory server.

Images