How Secure is Deterministic Encryption?

Abstract

This paper presents three curious findings about deterministic public-key encryption (D-PKE) that further our understanding of its security, in particular because of the contrast with standard, randomized public-key encryption (R-PKE):• It would appear to be a triviality, for any primitive, that security in the standard model implies security in the random-oracle model, and it is certainly true, and easily proven, for R-PKE. For D-PKE it is not clear and depends on details of the definition. In particular we can show it in the non-uniform case but not in the uniform case.• The power of selective-opening attacks (SOA) comes from an adversary's ability, upon corrupting a sender, to learn not just the message but also the coins used for encryption. For R-PKE, security is achievable. For D-PKE, where there are no coins, one's first impression may be that SOAs are vacuous and security should be easily achievable. We show instead that SOA-security is impossible, meaning no D-PKE scheme can achieve it.• For R-PKE, single-user security implies multi-user security, but we show that there are D-PKE schemes secure for a single user and insecure with two users.

SoK: Privacy-Preserving Collaborative Tree-based Model Learning

“…Alternatively, parties offload deterministic encryption of their data, and the learning is done on the ciphertexts as new labels and feature values [147,152]. But this encryption technique is prone to frequency-analysis attacks [18,136].…”

Using Transposition Padding to Get CCA2 Security From Any Deterministic Encryption Schemes

“…Brakerski and Segev [17] formalized a framework that focuses on hard-to-invert auxiliary inputs to study what security level a deterministic public-key encryption scheme provides. A lot of researchers focused on constructing deterministic publickey encryption schemes, among which some schemes employ very novel methods, such as schemes proposed in [16]- [20].…”