The multi-party encryption problem is that all parties need to send the private key to the server for decryption, and the private key received by the server is a situation where the key is leaked. Is there a way to avoid this situation。
The typical solution to this is threshold FHE (another solution is multiparty FHE), where the secret key is secret-shared between multiple parties (and neither one has the full secret key). Please watch Homomorphic Encryption for OpenFHE Users – OpenFHE.org to learn more about this.
I have looked at the code from multiple parties and what I want to ask is that the server sends the ciphertext to each client in the end, and each client decrypts it with their own private key. Then, each client transmits the decrypted ciphertext with the private key to each other, and finally, each client aggregates the received ciphertext and obtains the result. I think this is the case, right.
I’m not sure if you’re being fast-and-loose with your terminology, but I don’t think that’s correct. The video does not mention sending secret keys to one another as part of the decryption. You should watch the video
What I’m talking about is that after the server operates on the ciphertext, it sends it to various clients. The clients partially decrypt it with their own private key, and then the clients share the partially decrypted information with each other. Then, each client concatenates the shared ciphertext to obtain the decryption result, right？Do I understand correctly？
I have already seen that ppt ,not video.I have a understand as follow.
Again, watch the video. Yuriy covers it in the video and walks through an example script.
This is a better understanding. The usage of “partial decryption” is better than “decryption” as in your previous comment. Note that partial decryption is also known as secret sharing.