2015
DOI: 10.1007/978-3-662-49096-9_13
|View full text |Cite
|
Sign up to set email alerts
|

Non-Malleable Encryption: Simpler, Shorter, Stronger

Abstract: In a seminal paper, Dolev et al. [15] introduced the notion of non-malleable encryption (NM-CPA). This notion is very intriguing since it suffices for many applications of chosen-ciphertext secure encryption (IND-CCA), and, yet, can be generically built from semantically secure (IND-CPA) encryption, as was shown in the seminal works by Pass et al. [29] and by Choi et al. [9], the latter of which provided a black-box construction. In this paper we investigate three questions related to NM-CPA security:1. Can … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
29
0

Year Published

2017
2017
2022
2022

Publication Types

Select...
6
1
1

Relationship

2
6

Authors

Journals

citations
Cited by 37 publications
(29 citation statements)
references
References 30 publications
0
29
0
Order By: Relevance
“…In this paper, we focus only on the "default flavor" of continuous non-malleability. This in contrast to previous work on continuously nonmalleable codes (except [20,19,28]), which instead by default considered continuous super non-malleability. While the notion we consider is strictly weaker than continuous strong or super non-malleability, to the best of our knowledge, it is sufficient for all known applications of continuously non-malleable codes, in particular [30,31,20,19,28].…”
Section: Continuous Non-malleabilitymentioning
confidence: 89%
See 2 more Smart Citations
“…In this paper, we focus only on the "default flavor" of continuous non-malleability. This in contrast to previous work on continuously nonmalleable codes (except [20,19,28]), which instead by default considered continuous super non-malleability. While the notion we consider is strictly weaker than continuous strong or super non-malleability, to the best of our knowledge, it is sufficient for all known applications of continuously non-malleable codes, in particular [30,31,20,19,28].…”
Section: Continuous Non-malleabilitymentioning
confidence: 89%
“…The more general case of continuous non-malleability was introduced by Faust et al [30], with the goal of guaranteeing non-malleability even after multiple (adaptively chosen) tampering attempts; that is, the adversary is allowed to choose the tampering functions to apply in the next round based on the answers obtained in the previous rounds. As pointed out also in [30], continuously non-malleable codes (CNMCs) are arguably the most natural generalization of standard NMCs, and allow to significantly strengthen their applications [31,20,19].…”
Section: Continuous Non-malleabilitymentioning
confidence: 99%
See 1 more Smart Citation
“…Several constructions of non-malleable codes in the split-state model appeared in the literature, both for the information-theoretic [32,31,3,20,4,2,14,5,48,49,17] and computational setting [50,36,24,1,46,52,23]. Non-malleable codes exist also for several other models besides split-state tampering, including bit-wise independent tampering and permutations [20,6,7,22,21], circuits of polynomial size [32,19,38,39], constant-state tampering [18], block-wise tampering [13], space-bounded algorithms [35,9], bounded-depth circuits [8,16], and partial functions [47].…”
Section: Further Related Workmentioning
confidence: 99%
“…Recently, they also found application to computational cryptography Full version of this paper available at http://eprint.iacr.org/2016/397 (e.g. construction of non-malleable commitments [AGM + 15b], domain extension for public-key encryption schemes [CMTV15,CDTV16]). Roughly speaking, a coding scheme (Enc, Dec) is non-malleable with respect to the tampering function f if decoding f (Enc(m)) produces the original message m or a value m (eventually ⊥) completely unrelated with m. Moreover, the probability of which one of these two events happens is also independent of m. As an illustration of the notion, consider a key that is stored in a device.…”
Section: Introductionmentioning
confidence: 99%