Information conflict with SEAL regarding size of ciphertext under different key mode
Opened this issue · 0 comments
ZiyueXu77 commented
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
- OS: [e.g. iOS]
- OS Version: [e.g. 22]
- Language Version: [e.g. Python 3.7, Node 10.18.1]
- Package Manager Version: [e.g. Conda 4.6.1, NPM 6.14.1]
Additional Context
Add any other context about the problem here.