You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to benchmark tutorial: "the symmetric/asymmetric encryption switch doesn't actually impact the size of the ciphertext, only of the context", but according to SEAL (https://github.com/microsoft/SEAL/blob/main/native/examples/7_serialization.cpp) "ciphertexts can be created in a seeded state in secret-key mode, providing a huge reduction in the data size upon serialization". I wonder if I have some misunderstanding? Or there are some deep reason for this descrepancy.
Further Information
Describe your question in greater length here.
Screenshots
If applicable, add screenshots to help explain your question.
Question
According to benchmark tutorial: "the symmetric/asymmetric encryption switch doesn't actually impact the size of the ciphertext, only of the context", but according to SEAL (https://github.com/microsoft/SEAL/blob/main/native/examples/7_serialization.cpp) "ciphertexts can be created in a seeded state in secret-key mode, providing a huge reduction in the data size upon serialization". I wonder if I have some misunderstanding? Or there are some deep reason for this descrepancy.
Further Information
Describe your question in greater length here.
Screenshots
If applicable, add screenshots to help explain your question.
System Information
Additional Context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: