KR101369250B1 - Server, client and method for verifying integrity of data in peer to peer based network - Google Patents

Abstract

According to the present invention, in the P2P-based file update or data transfer using the P2P communication protocol, the same hash (so as to verify the integrity of the metadata file when generating the metadata file used as a standard for file transfer between users) may be used. Create and distribute a metadata verification file having a hash value, and verify the integrity of the metadata file by using the metadata verification file downloaded along with the metadata file. Can be detected in advance, greatly improving the security of the P2P type file transfer protocol. In addition, security enhancements make it easier to apply P2P communication protocols to reliable data transmission in business environments.

Description

SERVER, CLIENT AND METHOD FOR VERIFYING INTEGRITY OF DATA IN PEER TO PEER BASED NETWORK}

The present invention relates to a peer-to-peer (P2P) based file transfer method, and in particular, in a P2P-based file update or data transfer using a P2P communication protocol, file transfer between users Create and distribute additional metadata verification files with the same hash value to verify the integrity of the metadata file when creating the metadata file used as the standard of the client. P2P greatly improves the security of the P2P file transfer protocol by verifying the integrity of the metadata file by using the metadata verification file downloaded along with the metadata file to detect whether the metadata file has been tampered with. A server, client, and method for verifying the integrity of data in an underlying network.

In general, P2P technology is a concept of collecting a large number of users into a network, sharing bandwidth and processing information together in the network. Unlike general client-server mode, each client terminal functions as both a client and a server, Is an efficient data transmission approach that enables users to acquire content efficiently and reliably in a collaborative environment.

In other words, P2P refers to a network communication model in which peer nodes of the same layer send and receive files while simultaneously acting as clients and servers, unlike the client-server model.

There is a torrent as a P2P technology which is widely used in the above and P2P technology. Torrent is the application of the concept of grid storage to an open environment such as a P2P network. In the conventional P2P network, data exchange is performed on a per file basis. In the torrent, a file is divided into blocks of a predetermined size ), Data exchange is performed on a divided block basis, and a file is reconstructed into a plurality of blocks.

In such a torrent, a plurality of host computers holding desired files are searched on the Internet, and a plurality of searched host computers simultaneously request different blocks, thereby speeding up the file transfer in the P2P network environment.

Meanwhile, the torrent as described above may be used as an update technology of various programs including an anti virus program as a data transmission and download technology using the Internet.

At this time, in the torrent protocol-based distributed file update, a meta data file called a seed file having information on an update target file is essentially present.

This seed file is an important file that is used as a standard for file transfer between users in the torrent protocol. It is necessary to ensure that the seed file of the server and the seed file delivered to the client are identical.

(Patent Literature)

Korean Patent Publication No. 2009-0115225 (published November 04, 2009)

However, in the conventional torrent protocol, a method or device for verifying the integrity of the seed file has not been implemented yet, so when a malicious seed file is distributed by an attacker, there is a problem in that it cannot detect a malicious attack.

Accordingly, the present invention verifies the integrity of the metadata file when generating a metadata file used as a criterion for file transfer between users in P2P-based file update or data transmission using the P2P communication protocol. By additionally generating and distributing the metadata verification file having the same hash value, the client verifies the integrity of the metadata file using the metadata verification file downloaded together with the metadata file. The present invention provides a server, a client, and a method for verifying data integrity in a P2P based network that can detect whether a meta data file has been tampered with, thereby greatly improving the security of a P2P based file transfer protocol.

The present invention described above is a server device for verifying data integrity in a P2P based network, comprising: a metadata file generator for generating a metadata file; and metadata for generating a metadata verification file for verifying the integrity of the metadata file. A verification file generation unit, an electronic signature unit for digitally signing the metadata verification file, a metadata verification file integrity checking unit for checking the integrity of the digitally signed metadata verification file, and an integrity verification of the metadata file And a control unit for generating a metadata verification file for transmitting the metadata file and the metadata verification file using a peer to peer (P2P) based protocol.

The metadata verification file generation unit may set a hash value recorded in the metadata verification file to the same value as a hash value recorded in the metadata file.

The metadata verification file integrity checker may verify the integrity of the metadata verification file by checking the validity of the digital signature of the metadata verification file and whether the issuer of the digital signature is valid. .

In addition, the metadata verification file integrity checker, if the validity of the digital signature is recognized and the certificate issuer is valid, and if the hash value of the metadata verification file and the hash value of the metadata file are the same, the metadata And verifying the integrity of the data verification file.

In addition, the P2P-based protocol is a torrent protocol.

The meta data file is a seed file having information on a file to be updated.

The present invention also provides a client device for verifying data integrity in a P2P-based network. A metadata verification file integrity checker that checks whether the hash values are the same, an electronic signature checker that checks the validity of the digital signature digitally signed in the metadata verification file and whether the issuer of the digital signature is valid; And a controller that verifies the integrity of the metadata file using the verified metadata verification file, and performs P2P based data transmission using the metadata file when the integrity of the metadata file is verified.

In addition, the P2P-based protocol is a torrent protocol.

The meta data file may be a seed file having information on an update target file.

The present invention also provides a method for verifying data integrity in a P2P based network, the method comprising: generating a metadata file, generating a metadata verification file for verifying the integrity of the metadata file, and verifying the metadata verification file; Performing a digital signature, checking the integrity of the digitally signed metadata verification file, and if the integrity of the metadata verification file is verified, the metadata file and the meta using a P2P based protocol. Transmitting the data verification file.

The generating of the metadata verification file may include setting a hash value recorded in the metadata verification file to the same value as a hash value recorded in the metadata file.

The checking of the integrity of the metadata verification file may include: validating a digital signature digitally signed in the metadata verification file; and if the digital signature is valid, a certificate issuer who issues the digital signature. Characterized in that it comprises the step of checking whether it is legitimate.

The checking of the integrity of the metadata verification file may include: a hash value of the metadata verification file and a hash value of the metadata file when the digital signature is recognized as valid and the certificate issuer is verified as being valid. And checking whether the same is the same, and verifying the integrity of the metadata verification file when the hash value of the metadata verification file and the hash value of the metadata file are the same.

In addition, the P2P-based protocol is a torrent protocol.

The meta data file is a seed file having information on a file to be updated.

The present invention also provides a method for verifying data integrity in a P2P based network, the method comprising: downloading a metadata file and a metadata verification file using a P2P based protocol, checking the integrity of the metadata verification file; If the integrity of the metadata verification file is verified, checking whether a hash value of the metadata verification file whose integrity is verified and a hash value of the metadata file are the same; If the hash values of the metadata file are the same, performing P2P based data transmission using the metadata file.

The checking of the integrity of the metadata verification file may include validating a digital signature digitally signed in the metadata verification file, and if the digital signature is valid, the certificate issuer who issued the digital signature is issued. And checking the legitimacy, and verifying the integrity of the metadata verification file if the certificate issuer is legitimate.

In addition, the P2P-based protocol is a torrent protocol.

The meta data file may be a seed file having information on an update target file.

According to the present invention, in the P2P-based file update or data transmission using the P2P communication protocol, the integrity of the metadata file can be verified when generating a metadata file used as a standard for file transfer between users. In order to generate and distribute additional metadata verification files with the same hash value, the client verifies the integrity of the metadata file using the metadata verification file downloaded along with the metadata file. It is possible to detect whether a file has been tampered with in advance, thereby greatly improving the security of the P2P type file transfer protocol. In addition, due to the improved security, there is an advantage that the P2P communication protocol can be more easily applied to the reliable data transmission in the business environment.

1 is a network configuration diagram of a system for verifying integrity of a P2P based update environment according to an embodiment of the present invention;
2 is a detailed block diagram of a seed file generation server according to an embodiment of the present invention;
3 is a detailed block diagram of a client according to an embodiment of the present invention;
4 is an operation control flowchart of generating a seed file to guarantee integrity in a seed file generation server of a P2P based update system according to an embodiment of the present invention;
5 is an operation control flowchart for verifying the integrity of a seed file in a client of a P2P based update system according to an embodiment of the present invention.

Hereinafter, with reference to the accompanying drawings will be described in detail the operating principle of the present invention. In the following description of the present invention, when it is determined that a detailed description of a known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted. The following terms are defined in consideration of the functions of the present invention, and may be changed according to the intentions or customs of the user, the operator, and the like. Therefore, the definition should be based on the contents throughout this specification.

1 illustrates a network configuration of a system for verifying integrity of a P2P based update environment according to an embodiment of the present invention. In the following description, an operation of verifying the integrity of the metadata file for P2P-based update in the torrent protocol, which is one of the P2P-based protocols, will be described as an example.

The seed file generation server 100 generates a metadata file, that is, a seed file for downloading and updating a distributed program using a P2P based protocol such as a torrent protocol. do. The seed file generation server 100 may be a server of a company that develops and distributes a specific program for commercial purposes. For example, when the specific program is an anti-virus program, the company that developed the program. Can be your server.

In addition, in generating the seed file, the seed file generation server 100 updates a file by additionally generating a metadata verification file that can verify the seed file for verifying the integrity of the seed file, that is, a seed verification file. By validating the seed file through the seed verification file, the client 300 may verify the integrity of the seed file. That is, the seed file generation server 100 generates and distributes a seed verification file paired with the seed file at the time of generation of the seed file. In this case, a hash value of the seed file is recorded in the seed verification file, and the seed file generation server 100 performs a digital signature from the digital signature server to distribute the seed verification file for integrity checking.

The file server 200 stores a file of a program provided by the seed file generation server 100 and uses a seed file to request a client 300 to download or update a file of a specific program. Or a server that provides update files. For example, when the seed file generation server 100 is a server of a company that provides an antivirus program, the seed file generation server 100 may provide an antivirus engine program and a corresponding program to be provided to the client 300 in the file server 200. The update file may be stored in the file server 200, and the file server 200 provides the stored program file and the update file to each client 300.

The client 300 may be a terminal device such as a PC of each user in which a torrent client program is mounted to enable torrent-based distributed file updating. The client 100 downloads the seed file from the file server 200 when the torrent client program is executed, and then downloads a specific program desired by using the seed file.

In addition, the client 300 downloads the seed verification file when the seed file is downloaded and checks the integrity of the seed verification file, and then again checks the integrity of the seed file using the seed verification file, and the integrity of the seed file is verified. In this case, it is possible to cope with malicious external attack that manipulates the seed file by downloading or updating a desired program by using the seed file only.

2 illustrates a detailed block configuration of the seed file generation server 100 according to an embodiment of the present invention.

The seed file generator 102 generates a seed file for enabling the download or update of a specific program using a P2P based protocol such as a torrent protocol. Such a seed file refers to a metadata file that contains information about a file to be updated in a torrent-based distributed file update. The seed file includes each update file as a large file and divided into predetermined sizes. The hash value information for the block is included.

The seed verification file generation unit 104 generates a verification file that can verify the seed file for verifying the integrity of the seed file. That is, the seed verification file generating unit 104 generates a seed verification file paired with the seed file at the time of generation of the seed file, and records a hash value of the seed file in the seed verification file. The same hash value is the same as the hash value recorded in the seed file so that the seed file can be verified by comparing the hash values.

The digital signature unit 110 performs a digital signature on the seed verification file using the digital signature key from the digital signature server 150 to check the integrity of the seed verification file itself.

The seed verification file integrity checker 112 verifies the integrity of the seed verification file by checking whether the digital signature signed in the seed verification file is valid, that is, issued by a valid certificate issuer and whether the digital signature is valid. Check it. In addition, the integrity of the seed verification file is checked by checking whether the hash value recorded in the seed verification file and the hash value recorded in the seed file match.

The communication unit 106 performs data transmission / reception with the file server 200 through a network such as the Internet for transmission of a data file or an update file of a specific program. Such a communication unit 106 may support a P2P communication protocol including, for example, a torrent protocol.

The controller 108 controls the overall operation of the seed file generation server 100. That is, the controller 108 generates a seed verification file for verifying the seed file and the seed file through the seed file generator 102 and the seed verification file generator 104, and the seed signature verification with the digital signature unit 110. The file integrity checker 112 controls the integrity of the seed verification file to be checked. In addition, the controller 108 transmits the seed verification file and the seed file whose integrity is verified as described above to the file server 200 through the communication unit 106 so that each client 300 can be downloaded.

3 shows a detailed block diagram of the client 300 according to an embodiment of the present invention.

The communication unit 302 transmits and receives data for torrent-based distributed file update with the file server 200 or another client through a network such as the Internet. Such a communication unit 302 may support a P2P communication protocol including, for example, a torrent protocol.

The seed verification file integrity checker 308 checks the hash value recorded in the seed verification file and the hash value recorded in the seed file with respect to the seed verification file generated from the seed file generation server 100 to verify the integrity of the seed verification file. Check it.

The digital signature checker 304 checks the integrity of the seed verification file by checking whether the digital signature signed in the seed verification file is valid, that is, issued by a normal certificate issuer, and whether the digital signature is valid. .

The controller 306 downloads the seed file generated by the seed file generation server 100 and the seed verification file for integrity verification of the seed file from the file server 200 through the communication unit 302, and then checks the digital signature checker 304. ) To verify the integrity of the seed verification file. In addition, the seed verification file integrity check unit 308 is controlled to check whether the hash value recorded in the seed verification file and the hash value recorded in the seed file match and verify the integrity of the seed verification file, thereby causing the seed file to be infected with malicious code. Verifies whether the file is a valid file. Subsequently, the controller 306 downloads or updates a desired program using the seed file only when the integrity of the seed file is verified, so that it can cope with a malicious external attack that manipulates the seed file.

4 illustrates an operation control flow for generating a seed file for ensuring integrity in the seed file generation server 100 of the P2P based update system according to an embodiment of the present invention. Hereinafter, embodiments of the present invention will be described in detail with reference to FIGS. 1, 2, and 4. FIG.

First, the control unit 108 of the seed file generation server 100 controls the seed file generation unit 102 to generate a seed file for file transfer (S400). Such a seed file refers to a metadata file that contains information about a file to be updated in a torrent-based distributed file update. The seed file includes each update file as a large file and divided into predetermined sizes. The hash value information for the block is included.

As described above, when the seed file is generated, the controller 108 controls the seed verification file generating unit 104 to generate a seed verification file for verifying the integrity of the seed file (S402). In this case, a hash value identical to a hash value recorded in the seed file is recorded in the seed verification file, and the hash value checks whether the hash value is the same when the integrity check of the seed file using the seed verification file is performed by the client 300. Is used to verify integrity.

As described above, when the seed verification file in which the same hash value is recorded is generated, the controller 108 controls the digital signature unit 110 to digitally sign the seed verification file with the digital signature key received from the digital signature server 150. (S404). The digital signature is used to ensure the integrity of the seed verification file itself. The digital signature is used to verify the integrity of the seed verification file itself by validating the digital signature at the client 300.

Subsequently, when the digital signature for the seed verification file through the digital signature unit 110 is completed, the controller 108 first performs seed verification before transmitting the generated seed file and the seed verification file to the file server 200. It will check if the file was created correctly.

That is, the controller 108 controls the seed verification file integrity checker 112 to check whether the digital signature is valid for the seed verification file completed up to the digital signature, that is, whether the expiration date of the digital signature is valid (S406). .

At this time, if the validity period of the digital signature has elapsed and it is checked that the expiration date of the digital signature is invalid (S408), the controller 108 determines that generation of the seed file has failed (S410), and again from the beginning. It will create a seed file.

On the contrary, if the validity period of the digital signature has not elapsed and the expiration date of the digital signature is checked as valid (S408), the controller 108 checks the certificate issuer who issued the digital signature again and then, by a valid certificate issuer. It is checked whether it is an issued digital signature (S412). For example, if the seed file is generated for the distribution of the antivirus engine V3 program, the legitimate certificate issuer may be "AhnLab," in which case the certificate issuer of the digital signature is not a subject other than "AhnLab." In this case, it can be determined that the valid certificate issuer is not.

At this time, if the certificate issuer of the digital signature is not a valid issuer (S414), the controller 108 determines that generation of the seed file has failed (S410), and generates a seed file from the beginning.

However, in contrast, if the certificate issuer of the digital signature is a legitimate issuer (S414), the controller 108 verifies that the digital description has been issued by a legitimate certificate issuer.

Subsequently, when verification is performed up to the issuer of the digital signature, the controller 108 checks the hash value of the seed verification file and checks whether it matches the hash value of the seed file (S416). Such a hash value check of the seed verification file is performed in advance in case a hash value in the seed verification file is changed in the process of digital signature for self integrity of the seed verification file.

At this time, if the hash value recorded in the seed verification file does not match the hash value recorded in the seed file (S418), the controller 108 determines that generation of the seed file has failed (S410), and again from the beginning. It will create a seed file.

On the contrary, when the hash value recorded in the seed verification file matches the hash value recorded in the seed file (S418), the controller 108 determines that the generation of the seed file is successful (S420). The seed verification file is uploaded to the file server 200 to be distributed to the client 300 (S422).

5 illustrates an operation control flow for verifying the integrity of the seed file in the client 300 of the P2P based update system according to an embodiment of the present invention. Hereinafter, embodiments of the present invention will be described in detail with reference to FIGS. 1, 3, and 5.

First, when a torrent client program is started to install or update a specific program through torrent-based distributed file update, the control unit 306 of the client 300 may access a file server on a network such as the Internet through the communication unit 302. In step S500, the seed file uploaded from the seed file generation server 100 and the seed verification file are downloaded (S500, S502).

As described above, when the seed file and the seed verification file are downloaded, the control unit 306 first verifies the integrity of the seed file whether or not it has been infected by malware before performing a download installation or update of a specific program using the seed file. do.

That is, the controller 306 first controls the digital signature checker 304 to check whether the digital signature for the seed verification file is valid, that is, whether the expiration date of the digital signature is valid (S504).

At this time, if the validity period of the digital signature has elapsed and it is checked that the expiration date of the digital signature is invalid (S506), the controller 306 determines that the seed file has failed to download (S508). Do not download, install or update specific programs.

On the other hand, if the validity period of the digital signature has not elapsed, and the expiration date of the digital signature is checked as valid (S506), the controller 306 checks the certificate issuer who issued the digital signature again by a valid certificate issuer. Check whether the digital signature is issued (S510). For example, if the seed file is a seed file for the distribution or update of the antivirus engine V3 program, and the company that develops and distributes the V3 program is "AhnLab," the proper certificate issuer is "AhnLab." In this case, if the certificate issuer of the digital signature is a subject other than "AhnLab," it may be determined that the certificate issuer is not a valid certificate issuer.

At this time, if the certificate issuer of the digital signature is not a valid issuer (S512), the controller 306 determines that the download of the seed file has failed (S508), and downloads, installs or updates a specific program using the seed file. Do not perform.

However, in contrast, if the certificate issuer of the digital signature is a legitimate issuer (S512), the controller 306 verifies that the digital description has been issued by a legitimate certificate issuer.

Subsequently, when verification is performed up to the issuer of the digital signature, the controller 306 examines the hash value of the seed verification file and checks whether it matches the hash value of the seed file (S514). The hash value check of the seed verification file is to verify whether the seed file is a seed file distributed from a valid server. When the seed file is generated, the same hash value is recorded in the seed file and the seed verification file. This is to verify the integrity of the seed file by checking.

At this time, if the hash value recorded in the seed verification file does not match the hash value recorded in the seed file (S516), the controller 306 determines that downloading of the seed file has failed (S508), Do not download, install or update specific programs.

However, in contrast, when the hash value recorded in the seed verification file coincides with the hash value recorded in the seed file (S516), the controller 306 determines that the seed file has been successfully downloaded, and downloads the file using the seed file. By performing the download installation or update of a specific program (S518).

Subsequently, the controller 306 terminates the torrent client program when the file download is completed and the download installation or update of the specific program is completed (S520).

As described above, according to the present invention, in the P2P-based file update or data transmission using the P2P communication protocol, the metadata file is generated when a meta data file is used as a standard for file transfer between users. Create and distribute additional metadata verification files with the same hash value to verify the integrity.Clients use the metadata verification files downloaded along with the metadata files to ensure the integrity of the metadata files. By verifying, it is possible to detect whether the meta data file has been tampered with in advance, thereby greatly improving the security of the P2P type file transfer protocol. In addition, due to the improved security, P2P communication protocols can be more easily applied to reliable data transmission in business environments.

While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention. Accordingly, the scope of the invention should not be limited by the described embodiments but should be defined by the appended claims.

100: seed file generation server 150: digital signature server
200: file server 300: client
102: seed file generation unit 104: seed verification file generation unit
106: communication unit 108: control unit
110: digital signature 112: seed verification file integrity checker
302: communication unit 304: digital signature inspection unit
306: control unit 308: seed verification file integrity check unit

Claims (19)

A metadata file generator for generating a metadata file;
A metadata verification file generation unit generating a metadata verification file for verifying the integrity of the metadata file;
An electronic signature unit for digitally signing the metadata verification file;
A metadata verification file integrity checker for checking the integrity of the digitally signed metadata verification file;
Controls the metadata verification file generation unit to generate a metadata verification file for verifying the integrity of the metadata file, and transmits the metadata file and the metadata verification file using a peer-to-peer based protocol. Control
Server device for verifying the integrity of the data in a P2P-based network comprising a.
The method of claim 1,
The metadata verification file generation unit,
And a hash value recorded in the metadata verification file to a same value as a hash value recorded in the metadata file.
The method of claim 1,
The metadata verification file integrity check unit,
A server for verifying the integrity of data in a P2P based network by verifying the validity of the digital signature of the metadata verification file and whether the issuer of the digital signature is valid. Device.
The method of claim 3, wherein
The metadata verification file integrity check unit,
When the validity of the digital signature is recognized and the certificate issuer is verified as valid, and the hash value recorded in the metadata verification file and the hash value recorded in the metadata file are the same, the integrity of the metadata verification file is verified. The server device for verifying the integrity of the data in the P2P-based network, characterized in that it is determined that.
The method of claim 1,
The P2P-
Server device for verifying the integrity of data in a P2P-based network, characterized in that the torrent protocol.
The method of claim 5, wherein
The metadata file includes:
Server device for verifying the integrity of data in a P2P-based network, characterized in that the seed file that has information about the file to be updated.
Metadata verification file integrity checker that checks whether the hash value recorded in the metadata file and the hash value recorded in the metadata verification file are the same when downloading the metadata file and the metadata verification file using a P2P based protocol. Wow,
An electronic signature checker that checks the validity of the digital signature digitally signed in the metadata verification file and whether the issuer of the digital signature is valid;
A control unit that verifies the integrity of the metadata file using the metadata verification file whose integrity is verified, and performs P2P based data transmission using the metadata file when the integrity of the metadata file is verified.
Client device for verifying the integrity of the data in a P2P-based network comprising a.
The method of claim 7, wherein
The P2P-
Client device for verifying the integrity of data in a P2P-based network, characterized in that the torrent protocol.
The method of claim 8,
The metadata file includes:
Client device for verifying the integrity of data in a P2P-based network, characterized in that the seed file having information about the file to be updated.
Creating a metadata file,
Generating a metadata verification file for verifying the integrity of the metadata file;
Digitally signing the metadata verification file;
Checking the integrity of the digitally signed metadata verification file;
If the integrity of the metadata verification file is verified, transmitting the metadata file and the metadata verification file using a P2P based protocol
Method of verifying the integrity of data in a P2P-based network comprising a.
11. The method of claim 10,
Generating the metadata verification file,
And setting the hash value recorded in the metadata verification file to the same value as the hash value recorded in the metadata file.
11. The method of claim 10,
Checking the integrity of the metadata verification file,
Validating the digital signature digitally signed in the metadata verification file;
If the digital signature is valid, checking whether the certificate issuer who issued the digital signature is valid
Integrity verification method of data in a P2P-based network comprising a.
13. The method of claim 12,
Checking the integrity of the metadata verification file,
If the digital signature is validated and the certificate issuer is verified to be valid, checking whether the hash value recorded in the metadata verification file and the hash value recorded in the metadata file are the same;
Determining that the integrity of the metadata verification file is verified when the hash value recorded in the metadata verification file and the hash value recorded in the metadata file are the same.
Integrity verification method of data in a P2P-based network, characterized in that it further comprises.
11. The method of claim 10,
The P2P-
Method of verifying the integrity of data in a P2P based network, characterized in that the torrent protocol.
15. The method of claim 14,
The metadata file includes:
Method for verifying the integrity of data in a P2P-based network, characterized in that the seed file having information about the file to be updated.
Downloading the metadata file and the metadata validation file using a P2P based protocol,
Checking the integrity of the metadata verification file;
When the integrity of the metadata verification file is verified, checking whether the hash value recorded in the metadata verification file whose integrity is verified and the hash value recorded in the metadata file are the same;
Performing P2P-based data transfer using the metadata file when the hash value recorded in the metadata verification file and the hash value recorded in the metadata file are the same.
Method of verifying the integrity of data in a P2P-based network comprising a.
17. The method of claim 16,
Checking the integrity of the metadata verification file,
Validating the digital signature digitally signed in the metadata verification file;
If the digital signature is valid, checking whether the certificate issuer who issued the digital signature is valid;
Determining that the integrity of the metadata verification file is verified if the certificate issuer is legitimate
Integrity verification method of a P2P-based update environment comprising a.
17. The method of claim 16,
The P2P-
Method of verifying the integrity of data in a P2P based network, characterized in that the torrent protocol.
The method of claim 17,
The metadata file includes:
Method for verifying the integrity of data in a P2P-based network, characterized in that the seed file having information about the file to be updated.

Images