2006
DOI: 10.1007/11894063_16
|View full text |Cite
|
Sign up to set email alerts
|

Cache-Collision Timing Attacks Against AES

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
158
0
6

Year Published

2006
2006
2022
2022

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 256 publications
(164 citation statements)
references
References 20 publications
0
158
0
6
Order By: Relevance
“…We stress that MDATDCAs are resistant to Boolean masking of software AES implementations in the case where all S-Boxes share the same random mask, as detailed in [3]. When such a masking scheme is used, our attacks will outperform higher order DPAs or CPAs that typically require thousands of traces.…”
Section: Discussionmentioning
confidence: 94%
See 2 more Smart Citations
“…We stress that MDATDCAs are resistant to Boolean masking of software AES implementations in the case where all S-Boxes share the same random mask, as detailed in [3]. When such a masking scheme is used, our attacks will outperform higher order DPAs or CPAs that typically require thousands of traces.…”
Section: Discussionmentioning
confidence: 94%
“…Cache attacks demonstrated fall into three categories, depending on the channels used to collect the leakages. These channels are spy processes [1], timing information [2,3] and power/electromagnetic (EM) traces [4,5,6,7,8,9,10,11]. The focus of this paper is trace driven cache attack (TDCA), which exploits the power or electromagnetic traces.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…Subsequent research verified the correctness of the findings [11,10,9,15], improved the attack technically [14,3,8] or algorithmically [5], and devised and analysed countermeasures [6,4,16].…”
Section: Introductionmentioning
confidence: 95%
“…Unfortunately, many of the techniques are not designed for IFC scenarios. For example, modifying an algorithm implementation, as in the case of AES [7], does not naturally generalize to arbitrary untrusted code. Similarly, flushing or disabling the cache when switching protection domains, as suggested in [6,49], is prohibitively expensive in systems like Hails, where context switches occur hundreds of times per second.…”
Section: Introductionmentioning
confidence: 99%