Trusted data witness method and system based on three-party TLS

Encrypted communication between users and trusted data sources through the tripartite TLS protocol, and data proof is formed using the private key signature of the witness server, which solves the problem of not being able to prove the data source and integrity in the existing technology, and realizes the data transmission process security and credibility.

CN118944870APending Publication Date: 2024-11-12SHANGHAI WANXIANG BLOCK CHAIN CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410974586.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-19
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The prior art cannot provide credible data witness to Internet communication content and cannot prove the source and integrity of the data.

Method used

Using the tripartite TLS protocol, the witness server and the user side calculate the session key shard by exchanging public keys, encrypting and decrypting the plain text request information, and forming data proof through the witness server's private key signature to ensure that the data is in transmission. security and integrity.

Benefits of technology

Through the trusted data witness service of the three-party TLS, users can obtain encrypted data proof from trusted data sources to ensure the security and reliability of the data source, and the original data has not been tampered with, ensuring the credibility of the data when using and sharing it.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118944870A_ABST
    Figure CN118944870A_ABST
Patent Text Reader

Abstract

The invention provides a trusted data witnessing method and system based on a three-party TLS, and the method comprises the steps: enabling a witnessing server side and a user side to exchange public keys with a trusted data source side in a handshake process between the witnessing server side and the trusted data source side and between the user side and the trusted data source side through a TLS protocol; session key fragments are respectively calculated by witnessing private keys of the server side and the user side; the witness server side and the user side are fragmented through respective session keys, encryption of plaintext request information of the user side is completed through two-party security cooperation calculation, and an encryption request is sent to the trusted data source side; the user side receives an encryption response returned by the credible data source side, decryption of the encryption response is completed through safe cooperative calculation of the user side and the witness server side, and responded plaintext information is obtained; and the witness server takes the original encrypted response and the related session data as a proof, and signs the proof by using a private key of the witness server to form an effective proof of the plaintext response.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of data witnessing technology, and in particular to a trusted data witnessing method and system based on three-party TLS. Background Art

[0002] TLS is an Internet security transmission protocol that provides authentication and encryption services between two communicating applications, such as web servers. However, it cannot prove the content of the communication.

[0003] Patent document CN108347429A (application number: 201711485141.7) discloses an information witness system, method and device, specifically: the client of the authoritative witness platform receives an information witness request; the client sends the information to be witnessed carried in the information witness request to the server of the authoritative witness platform; the server witnesses the information to be witnessed and obtains the witness result; the server returns the witness result to the client; the server sends an information write request to the blockchain system; the blockchain system writes the witness result carried in the information write request into the witness blockchain, wherein the witness blockchain is a data chain for storing the witness result. In this way, the information is witnessed by the authoritative witness platform, and the witness result is written into the witness blockchain by the blockchain system, which not only improves the credibility of the witness result, but also the witness result stored in the witness blockchain is not easy to be tampered with, thereby ensuring the accuracy and legitimacy of the witness result. Summary of the invention

[0004] In view of the defects in the prior art, the purpose of the present invention is to provide a trusted data witness method and system based on three-party TLS.

[0005] A trusted data witnessing method based on three-party TLS provided by the present invention includes:

[0006] Step S1: The witness server and the user end act as clients in the TLS protocol; in the process of completing the handshake between the witness server and the user end and the trusted data source end through the TLS protocol, the witness server and the user end exchange public keys with the trusted data source end respectively, and calculate the session key fragments respectively through the private keys of the witness server and the user end;

[0007] Step S2: The witness server and the user end use their own session key shards to encrypt the plaintext request information of the user end through two-party secure collaborative calculation, and send the encrypted request to the trusted data source end;

[0008] Step S3: The user receives the encrypted response returned by the trusted data source, and decrypts the encrypted response through secure collaborative calculation between the user and the witness server to obtain the plain text information of the response;

[0009] Step S4: The witness server uses the original encrypted response and related session data as proof, and signs the proof using the witness server's private key to form a valid proof of the plaintext response.

[0010] Preferably, the step S1 comprises:

[0011] Step S1.1: The witness server generates a random number as the shard private key, and calculates the witness server's shard public key Q based on the witness server's shard private key w =G*d w , where G represents the base point (constant point); the witness server sends the shard public key to the user;

[0012] Step S1.2: The user generates a random number d u As the shard private key, the user's shard public key Q is calculated based on the user's shard private key u =G*d u , where G represents the base point (constant point); the user end calculates the user end's public key Q based on the user end's shard public key c =Q w +Q u , and the client's public key Q c Send to the trusted data source;

[0013] Step S1.3: The trusted data source generates a random number d s As a random private key, the random public key Q of the trusted data source is calculated based on the random private key of the trusted data source. s =G*d s , the server certificate of the trusted data source and the random public key Q s The data signature is sent to the user end; the trusted data source end obtains the session key by calculating based on the random private key of the trusted data source end and the client public key;

[0014] PMS=d s *Q c =d s *(Q w +Q u ) = d s *Q w +d s Q u =Q s *d w +Q s d u ;

[0015] Step S1.4: The client receives the server certificate and random public key Q from the trusted data source sAnd data signature, verify the server certificate of the trusted data source and the corresponding data signature, and forward it to the witness server; the user end uses the shard private key d u and the random public key Q from the trusted data source s Calculate and obtain session key fragments;

[0016] PMS u =d u *Q s ;

[0017] Step S1.5: The witness server receives the server certificate and random public key Q forwarded by the client s And data signature, verify the certificate and corresponding signature of the trusted data source; the witness server uses the shard private key d w and the random public key Q from the trusted data source s Calculate and obtain session key fragments;

[0018] PMS w =d w *Q s

[0019] Step S1.6: Witness the session key fragment of the server and the session key fragment of the client, and obtain the complete session key through collaborative calculation;

[0020] PMS=PMS w +PMS u .

[0021] Preferably, the step S2 adopts:

[0022] Step S2.1: The user end splits the session key into PMS u and the request plaintext are submitted as private input to the two-party secure collaborative computing encryption module;

[0023] Step S2.2: The witness server splits the session key into PMS w Submitted as private input to the two-party secure collaborative computing encryption module;

[0024] Step S2.3: The two parties' secure collaborative computing encryption modules perform secure encryption computing to obtain the requested ciphertext;

[0025] Step S2.4: The user sends the request ciphertext to the trusted data source.

[0026] Preferably, the step S3 adopts:

[0027] Step S3.1: The user receives the response ciphertext CT from the trusted data source and sends the session key fragment PMS uAs private input, the response ciphertext CT is submitted to the two-party secure collaborative computing decryption module as public input;

[0028] Step S3.2: The witness server splits the session key into PMS w Submitted as private input to the two-party secure collaborative computation decryption module;

[0029] Step S3.3: The two-party secure collaborative computing decryption module performs secure decryption computing to obtain a response plaintext PT; and provides the response plaintext PT to the user end;

[0030] Step S3.4: The witness server obtains the response ciphertext.

[0031] Preferably, the step S4 adopts:

[0032] Step S4.1: The witness server uses the identity private key to sign the response ciphertext CT and the trusted data source certificate of the trusted data source;

[0033] Step S4.2: The witness server shards the signature information and session key into PMS w Send to the user end;

[0034] Step S4.3: The user end obtains the complete session key PMS=PMS by calculation w +PMS u

[0035] Step S4.4: The session key PMS, the response ciphertext CT, the trusted data source certificate, the response ciphertext and the witness service signature of the trusted data source certificate constitute data proof of the response plaintext PT.

[0036] A trusted data witness system based on three-party TLS provided by the present invention includes:

[0037] Module M1: The witness server and the user end act as clients in the TLS protocol; in the process of completing the handshake between the witness server and the user end and the trusted data source end through the TLS protocol, the witness server and the user end exchange public keys with the trusted data source end respectively, and calculate the session key fragments respectively through the private keys of the witness server and the user end;

[0038] Module M2: The witness server and the user end use their own session key shards to encrypt the user's plaintext request information through two-party secure collaborative calculations, and send the encrypted request to the trusted data source end;

[0039] Module M3: The user receives the encrypted response returned by the trusted data source, and decrypts the encrypted response through secure collaborative calculation between the user and the witness server to obtain the plaintext information of the response;

[0040] Module M4: The witness server uses the original encrypted response and related session data as proof, and signs the proof using the witness server's private key to form a valid proof of the plaintext response.

[0041] Preferably, the module M1 comprises:

[0042] Module M1.1: The witness server generates a random number as the shard private key, and calculates the witness server's shard public key Q based on the witness server's shard private key w =G*d w , where G represents the base point (constant point); the witness server sends the shard public key to the user;

[0043] Module M1.2: The user generates a random number d u As the shard private key, the user's shard public key Q is calculated based on the user's shard private key u =G*d u , where G represents the base point (constant point); the user end calculates the user end's public key Q based on the user end's shard public key c =Q w +Q u , and the client's public key Q c Send to the trusted data source;

[0044] Module M1.3: Generate a random number d at the trusted data source s As a random private key, the random public key Q of the trusted data source is calculated based on the random private key of the trusted data source. s =G*d s , the server certificate of the trusted data source and the random public key Q s The data signature is sent to the user end; the trusted data source end obtains the session key by calculating based on the random private key of the trusted data source end and the client public key;

[0045] PMS=d s *Q c =d s *(Q w +Q u ) = d s *Q w +d s Q u =Q s *d w +Q s d u ;

[0046] Module M1.4: The client receives the server certificate and random public key Q from the trusted data source sAnd data signature, verify the server certificate of the trusted data source and the corresponding data signature, and forward it to the witness server; the user end uses the shard private key d u and the random public key Q from the trusted data source s Calculate and obtain session key fragments;

[0047] PMS u =d u *Q s ;

[0048] Module M1.5: Witness server receives server certificate and random public key Q forwarded by client s And data signature, verify the certificate and corresponding signature of the trusted data source; the witness server uses the shard private key d w and the random public key Q from the trusted data source s Calculate and obtain session key fragments;

[0049] PMS w =d w *Q s

[0050] Module M1.6: Witness the session key shards of the server and the client, and obtain the complete session key through collaborative calculation;

[0051] PMS=PMS w +PMS u .

[0052] Preferably, the module M2 adopts:

[0053] Module M2.1: The user end splits the session key into PMS u and the request plaintext are submitted as private input to the two-party secure collaborative computing encryption module;

[0054] Module M2.2: Witness server splits session key into PMS w Submitted as private input to the two-party secure collaborative computing encryption module;

[0055] Module M2.3: The two-party secure collaborative computing encryption module performs secure encryption calculations to obtain the requested ciphertext;

[0056] Module M2.4: The user sends the request ciphertext to the trusted data source.

[0057] Preferably, the module M3 adopts:

[0058] Module M3.1: The user receives the response ciphertext CT from the trusted data source and sends the session key fragment PMS uAs private input, the response ciphertext CT is submitted to the two-party secure collaborative computing decryption module as public input;

[0059] Module M3.2: Witness server splits session key into PMS w Submitted as private input to the two-party secure collaborative computation decryption module;

[0060] Module M3.3: The two-party secure collaborative calculation decryption module performs secure decryption calculation to obtain a response plaintext PT; and provides the response plaintext PT to the user end;

[0061] Module M3.4: The witness server obtains the response ciphertext.

[0062] Preferably, the module M4 adopts:

[0063] Module M4.1: The witness server uses the identity private key to sign the response ciphertext CT and the trusted data source certificate of the trusted data source;

[0064] Module M4.2: The witness server shards the signature information and session key into PMS w Send to the user end;

[0065] Module M4.3: The user obtains the complete session key PMS=PMS by calculation w +PMS u

[0066] Module M4.4: The session key PMS, the response ciphertext CT, the trusted data source certificate, the response ciphertext and the witness service signature of the trusted data source certificate constitute the data proof of the response plaintext PT.

[0067] Compared with the prior art, the present invention has the following beneficial effects:

[0068] 1. Through the trusted data witness service of three-party TLS, users can use the third-party witness service to witness the data obtained by users from the trusted data source without leaking the plain text exchanged between the user and the trusted data source, thus solving the credibility of users obtaining data from the trusted data source and sharing it;

[0069] 2. Through the trusted witness service of three-party TLS, witness the secure communication between users and trusted data sources. Provide encrypted data proof for the data obtained by users from trusted data sources, ensure the security and reliability of the data source, and ensure that the original data has not been tampered with. Ensure the credibility of data when it is used and shared. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0071] Figure 1 The figure is a flow chart of the trusted data witness method based on three-party TLS.

[0072] Figure 2 This is a timing diagram of the trusted data witness handshake phase based on three-party TLS.

[0073] Figure 3 This is a timing diagram of the trusted data witness data communication phase based on three-party TLS. DETAILED DESCRIPTION

[0074] The present invention is described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those of ordinary skill in the art, several changes and improvements can also be made without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

[0075] Example 1

[0076] The present invention provides a trusted data witness method and system based on three-party TLS, which witnesses the secure communication between users and trusted data sources through the trusted witness service of three-party TLS. It provides encrypted data proof for the data obtained by users from trusted data sources, ensures the security and reliability of the data source, and ensures that the original data has not been tampered with. It ensures the credibility of data when it is used and shared.

[0077] Specifically, the trusted data witnessing method based on three-party TLS includes: when a user communicates and interacts with a trusted data source, the communication data and message content are encrypted and protected at the TLS layer. The present invention improves the two-party TLS protocol into a three-party TLS to witness the original information obtained by the user from the trusted data source.

[0078] Step 1: The witness service and the user play the role of ordinary clients in the TLS protocol, exchange public keys with the trusted data source, calculate the session key shards through their respective private keys, and complete the handshake with the trusted data source.

[0079] Step 2: The witness service and the user use their own private key shards, and through a two-party secure collaborative calculation, they encrypt the user's plaintext request information and send the encrypted request to the trusted data source.

[0080] Step 3: The user receives the encrypted response returned by the trusted data source, and through secure collaborative calculation between the two parties and the witness service, completes the decryption of the encrypted response to obtain the plaintext information of the response.

[0081] Step 4: The witness service uses the original encrypted response and related session data as proof and signs the proof using the witness service’s private key to form a valid proof of the plaintext response.

[0082] The step 1 comprises the following steps:

[0083] Step 1.1: The witness service generates a random number (d w ) as the shard private key, and calculate the shard public key Q of the witness service through the formula w =G*d w , the witness service will shard the public key (Q w ) is sent to the user.

[0084] Step 1.2: The user generates a random number (d u ) as the shard private key, and calculate the user's shard public key Q through the formula u =G*d u , the user obtains the client's public key Q through calculation c =Q w +Q u , and the client public key Q c Sent to the trusted data source for the handshake process.

[0085] Step 1.3: A trusted data source generates a random number (d s ) as a random private key, and obtain the random public key Q of the trusted data source through the formula calculation s =G*d s , the server certificate and random public key of the trusted data source and the data signature are sent to the user. The trusted data source is signed by the server through the random private key (d s ) and the client public key (Q c )calculate

[0086] The session key can be obtained:

[0087] PMS=d s *Q c =d s *(Q w +Q u ) = d s *Q w +d s Q u =Q s *d w +Q s d u

[0088] Step 1.4: The user receives the server certificate and random public key (Q s) and data signature, verify the certificate and the corresponding signature, and forward it to the witness service. u ) and a random public key (Q s ) Calculate the session key fragment:

[0089] PMS u =d u *Q s

[0090] Step 1.5: The witness service receives the server certificate and random public key (Q s ) and data signatures to verify the certificates and signatures of trusted data sources. w ) and a random public key (Q s ) Calculate the session key fragment: PMS w =d w *Q s

[0091] Step 1.6: The witness service session key shard and the user session key shard are used to collaboratively calculate the complete session key: PMS = PMS w +PMS u

[0092] The step 2 comprises the following steps:

[0093] Step 2.1: User splits the session key into pieces (PMS u ) and the request plaintext are submitted as private input to the two-party secure collaborative computing encryption module.

[0094] Step 2.2: The witness service shards the session key (PMS w ) is submitted as private input to the two-party secure collaborative computing encryption module.

[0095] Step 2.3: The two parties perform secure collaborative computing to perform secure encryption computing and obtain the request ciphertext. Both the user and the witness service can obtain the request ciphertext, and neither the witness service nor the user can decrypt the request ciphertext alone.

[0096] Step 2.4: The user sends the request ciphertext to the trusted data source.

[0097] The step 3 comprises the following steps:

[0098] Step 3.1: The user receives the response ciphertext (CT) from the trusted data source and splits the session key (PMS u ) as private input and the response ciphertext (CT) as public input are submitted to the two-party secure collaborative computing decryption module.

[0099] Step 3.2: The witness service shards the session key (PMS w ) is submitted as private input to the two-party secure collaborative computing decryption module.

[0100] Step 3.3: The two parties perform secure collaborative computing to perform secure decryption computing and obtain the response plaintext (PT). Only the response plaintext is provided to the user.

[0101] Step 3.4: The witness service obtains the response ciphertext.

[0102] The step 4 comprises the following steps:

[0103] Step 4.1: The witness service uses the identity private key to sign the response ciphertext and trusted data source certificate of the trusted data source.

[0104] Step 4.2: The witness service shards the signature information and session key (PMS w )Send to user

[0105] Step 4.3: The user obtains the complete session key PMS by calculation = PMS w +PMS u

[0106] Step 4.4: The session key PMS, the response ciphertext (CT), the trusted data source certificate, the response ciphertext and the witness service signature of the trusted data source certificate constitute the data proof of the response plaintext (PT)

[0107] The present invention also provides a trusted data witness system based on three-party TLS. The trusted data witness system based on three-party TLS can be implemented by executing the process steps of the trusted data witness method based on three-party TLS, that is, a person skilled in the art can understand the trusted data witness method based on three-party TLS as a preferred implementation of the trusted data witness system based on three-party TLS.

[0108] Specifically, the present invention can be applied to users obtaining transaction details through the website provided by ICBC. When the user shares the details with a third party, it is impossible to prove that the data he provided was obtained from ICBC and has not been tampered with. However, the trusted data witness method and system based on three-party TLS provided by the present invention can prove that the data shared by the user is obtained from the ICBC website and has not been tampered with through the data proof provided by the data witness service. At the same time, the witness service does not obtain the user's plaintext data.

[0109] Those skilled in the art know that, in addition to realizing the system and its various devices, modules, and units provided by the present invention in a purely computer-readable program code, it is entirely possible to realize the same functions in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, the system and its various devices, modules, and units provided by the present invention can be considered as a hardware component, and the devices, modules, and units included therein for realizing various functions can also be regarded as structures within the hardware component; the devices, modules, and units for realizing various functions can also be regarded as both software modules for realizing the method and structures within the hardware component.

[0110] The above describes the specific embodiments of the present invention. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims

1. A trusted data witness method based on three-party TLS, characterized in that: include: Step S1: Witness the server and the user as clients in the TLS protocol; In the process of completing the handshake between the witness server and the user end and the trusted data source end through the TLS protocol, the witness server and the user end exchange public keys with the trusted data source end respectively, and calculate the session key fragments respectively through the private keys of the witness server and the user end; Step S2: The witness server and the user end use their own session key shards to encrypt the plaintext request information of the user end through two-party secure collaborative calculation, and send the encrypted request to the trusted data source end; Step S3: The user receives the encrypted response returned by the trusted data source, and decrypts the encrypted response through secure collaborative calculation between the user and the witness server to obtain the plain text information of the response; Step S4: The witness server uses the original encrypted response and related session data as proof, and signs the proof using the witness server's private key to form a valid proof of the plaintext response.

2. The trusted data witness method based on three-party TLS according to claim 1 is characterized in that: The step S1 comprises: Step S1.1: The witness server generates a random number as the shard private key, and calculates the witness server's shard public key Q based on the witness server's shard private key w =G8d w , where G represents the base point; the witness server sends the shard public key to the user; Step S1.2: The user generates a random number d u As the shard private key, the user's shard public key Q is calculated based on the user's shard private key u =G8d u , where G represents the base point; the user end calculates the user end's public key Q based on the user end's shard public key c =Q w +Q u , and the client's public key Q c Send to the trusted data source; Step S1.3: The trusted data source generates a random number d s As a random private key, the random public key Q of the trusted data source is calculated based on the random private key of the trusted data source. s =G*d s , the server certificate of the trusted data source and the random public key Q s The data signature is sent to the user end; the trusted data source end obtains the session key by calculating based on the random private key of the trusted data source end and the client public key; PMS=d s 8Q c =d s *(Q w +Q u )=d s *Q w +d s Q u =Q s 8d w +Q s d u ; Step S1.4: The client receives the server certificate and random public key Q from the trusted data source s And data signature, verify the server certificate of the trusted data source and the corresponding data signature, and forward it to the witness server; the user end uses the shard private key d u and the random public key Q from the trusted data source s Calculate and obtain session key fragments; PMS u =d u 8Q s ; Step S1.5: The witness server receives the server certificate and random public key Q forwarded by the client s And data signature, verify the certificate and corresponding signature of the trusted data source; the witness server uses the shard private key d w and the random public key Q from the trusted data source s Calculate and obtain session key fragments; PMS w =d w *Q s Step S1.6: Witness the session key fragment of the server and the session key fragment of the client, and obtain the complete session key through collaborative calculation; PMS=PMS w +PMS u 。 3. The trusted data witness method based on three-party TLS according to claim 1 is characterized in that: The step S2 adopts: Step S2.1: The user end splits the session key into PMS u and the request plaintext are submitted as private input to the two-party secure collaborative computing encryption module; Step S2.2: The witness server splits the session key into PMS w Submitted as private input to the two-party secure collaborative computing encryption module; Step S2.3: The two parties' secure collaborative computing encryption modules perform secure encryption computing to obtain the requested ciphertext; Step S2.4: The user sends the request ciphertext to the trusted data source.

4. The trusted data witness method based on three-party TLS according to claim 1 is characterized in that: The step S3 adopts: Step S3.1: The user receives the response ciphertext CT from the trusted data source and sends the session key fragment PMS u Submitted as private input and the response ciphertext CT as public input to the two-party secure collaborative computing decryption module; Step S3.2: The witness server splits the session key into PMS w Submitted as private input to the two-party secure collaborative computation decryption module; Step S3.3: The two-party secure collaborative computing decryption module performs secure decryption computing to obtain a response plaintext PT; and provides the response plaintext PT to the user end; Step S3.4: The witness server obtains the response ciphertext.

5. The trusted data witness method based on three-party TLS according to claim 1 is characterized in that: The step S4 adopts: Step S4.1: The witness server uses the identity private key to sign the response ciphertext CT and the trusted data source certificate of the trusted data source; Step S4.2: The witness server shards the signature information and session key into PMS w Send to the user end; Step S4.3: The user end obtains the complete session key PMS=PMS by calculation w +PMS u Step S4.4: The session key PMS, the response ciphertext CT, the trusted data source certificate, the response ciphertext and the witness service signature of the trusted data source certificate constitute data proof of the response plaintext PT.

6. A trusted data witness system based on three-party TLS, characterized in that: include: Module M1: Witness the server and the user as clients in the TLS protocol; In the process of completing the handshake between the witness server and the user end and the trusted data source end through the TLS protocol, the witness server and the user end exchange public keys with the trusted data source end respectively, and calculate the session key fragments respectively through the private keys of the witness server and the user end; Module M2: The witness server and the user end use their own session key shards to encrypt the user's plaintext request information through two-party secure collaborative calculations, and send the encrypted request to the trusted data source end; Module M3: The user receives the encrypted response returned by the trusted data source, and decrypts the encrypted response through secure collaborative calculation between the user and the witness server to obtain the plaintext information of the response; Module M4: The witness server uses the original encrypted response and related session data as proof, and signs the proof using the witness server's private key to form a valid proof of the plaintext response.

7. The trusted data witness system based on three-party TLS according to claim 6 is characterized in that: The module M1 comprises: Module M1.1: The witness server generates a random number as the shard private key, and calculates the witness server's shard public key Q based on the witness server's shard private key w =G*d w , where G represents the base point; the witness server sends the shard public key to the user; Module M1.2: The user generates a random number d u As the shard private key, the user's shard public key Q is calculated based on the user's shard private key u =G*d u , where G represents the base point; the user end calculates the user end's public key Q based on the user end's shard public key c =Q w +Q u , and the client's public key Q c Send to the trusted data source; Module M1.3: Generate a random number d at the trusted data source s As a random private key, the random public key Q of the trusted data source is calculated based on the random private key of the trusted data source. s =G*d s , the server certificate of the trusted data source and the random public key Q s The data signature is sent to the user end; the trusted data source end obtains the session key by calculating based on the random private key of the trusted data source end and the client public key; PMS=d s 8Q c =d s 8(Q w +Q u )=d s 8Q w +d s Q u =Q s 8d w +Q s d u ; Module M1.4: The client receives the server certificate and random public key Q from the trusted data source s And data signature, verify the server certificate of the trusted data source and the corresponding data signature, and forward it to the witness server; the user end uses the shard private key d u and the random public key Q from the trusted data source s Calculate and obtain session key fragments; PMS u =d u *Q s ; Module M1.5: Witness server receives server certificate and random public key Q forwarded by client s And data signature, verify the certificate and corresponding signature of the trusted data source; the witness server uses the shard private key d w and the random public key Q from the trusted data source s Calculate and obtain session key fragments; PMS w =d w *Q s Module M1.6: Witness the session key shards of the server and the client, and obtain the complete session key through collaborative calculation; PMS=PMS w +PMS u 。 8. The trusted data witness system based on three-party TLS according to claim 6 is characterized in that: The module M2 adopts: Module M2.1: The user end splits the session key into PMS u and the request plaintext are submitted as private input to the two-party secure collaborative computing encryption module; Module M2.2: Witness server splits session key into PMS w Submitted as private input to the two-party secure collaborative computing encryption module; Module M2.3: The two-party secure collaborative computing encryption module performs secure encryption calculations to obtain the requested ciphertext; Module M2.4: The user sends the request ciphertext to the trusted data source.

9. The trusted data witness system based on three-party TLS according to claim 6, characterized in that: The module M3 adopts: Module M3.1: The user receives the response ciphertext CT from the trusted data source and sends the session key fragment PMS u Submitted as private input and the response ciphertext CT as public input to the two-party secure collaborative computing decryption module; Module M3.2: Witness server splits session key into PMS w Submitted as private input to the two-party secure collaborative computation decryption module; Module M3.3: The two-party secure collaborative calculation decryption module performs secure decryption calculation to obtain a response plaintext PT; and provides the response plaintext PT to the user end; Module M3.4: The witness server obtains the response ciphertext.

10. The trusted data witness system based on three-party TLS according to claim 6, characterized in that: The module M4 adopts: Module M4.1: The witness server uses the identity private key to sign the response ciphertext CT and the trusted data source certificate of the trusted data source; Module M4.2: The witness server shards the signature information and session key into PMS w Send to the user end; Module M4.3: The user obtains the complete session key PMS=PMS by calculation w +PMS u Module M4.4: The session key PMS, the response ciphertext CT, the trusted data source certificate, the response ciphertext and the witness service signature of the trusted data source certificate constitute the data proof of the response plaintext PT.