2015
DOI: 10.1007/978-3-662-47989-6_26
|View full text |Cite
|
Sign up to set email alerts
|

Explicit Non-malleable Codes Against Bit-Wise Tampering and Permutations

Abstract: A non-malleable code protects messages against various classes of tampering. Informally, a code is non-malleable if the message contained in a tampered codeword is either the original message, or a completely unrelated one. Although existence of such codes for various rich classes of tampering functions is known, explicit constructions exist only for "compartmentalized" tampering functions: i.e. the codeword is partitioned into a priori fixed blocks and each block can only be tampered independently. The promin… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
65
0

Year Published

2015
2015
2019
2019

Publication Types

Select...
8

Relationship

1
7

Authors

Journals

citations
Cited by 41 publications
(66 citation statements)
references
References 32 publications
1
65
0
Order By: Relevance
“…Beyond the constructions of [23,9,25], non-malleable codes exists against block-wise tampering [11], against bit-wise tampering and permutations [5,4], against split-state tampering-both information-theoretic [22,2,7,3,1] and computational [38,18]-and in a setting where the computational complexity of the tampering functions is limited [8,27,34]. We stress that the typical application of non-malleable codes is to protect cryptographic schemes against memory tampering (see, e.g., [29,23,19,20]).…”
Section: More Details On Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Beyond the constructions of [23,9,25], non-malleable codes exists against block-wise tampering [11], against bit-wise tampering and permutations [5,4], against split-state tampering-both information-theoretic [22,2,7,3,1] and computational [38,18]-and in a setting where the computational complexity of the tampering functions is limited [8,27,34]. We stress that the typical application of non-malleable codes is to protect cryptographic schemes against memory tampering (see, e.g., [29,23,19,20]).…”
Section: More Details On Related Workmentioning
confidence: 99%
“…4 In other words, once the MBO is 1, it cannot return to 0. 5 Intuitively, this means that in order to distinguish the two systems, D has to provoke the MBO. 6 In less formal contexts, we sometimes drop the superscripts on ==⇒ .…”
Section: Public-key Encryption Schemesmentioning
confidence: 99%
“…Very recently, an explicit rate-0 code against a more powerful class of tampering functions, which in addition to tampering with each bit of the codeword independently can also permute the bits of the resulting codeword after tampering, was achieved in [4]. This was further improved to rate 1 by [5].…”
Section: Prior Workmentioning
confidence: 99%
“…Non-malleable codes have found interesting cryptographic applications like domain extension of self-destruct CCA-secure public-key encryption [13] and non-malleable commitments [4].…”
Section: Prior Workmentioning
confidence: 99%
“…However, a general impossibility result by Gennaro et al [27] shows that the above flavour of tamper resistance is unachievable without further assumptions. To overcome this impossibility one usually relies on self-destruct (e.g., [22,15,1,14,13,23,24,25,17,2,3,4,16,30]), or limits the power of the tampering function (e.g., [9,33,7,6,28,35,37,10,11,30,36]). …”
Section: Introductionmentioning
confidence: 99%