Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Information conflict with SEAL regarding size of ciphertext under different key mode #464

Open
ZiyueXu77 opened this issue Dec 20, 2023 · 0 comments
Labels
Type: Question ❔ Question about implementation or some technical aspect

Comments

@ZiyueXu77
Copy link

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.

@ZiyueXu77 ZiyueXu77 added the Type: Question ❔ Question about implementation or some technical aspect label Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Question ❔ Question about implementation or some technical aspect
Projects
None yet
Development

No branches or pull requests

1 participant