Proceedings of the 5th Workshop on Embedded Systems Security 2010
DOI: 10.1145/1873548.1873555
|View full text |Cite
|
Sign up to set email alerts
|

Countermeasures against fault attacks on software implemented AES

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
72
0

Year Published

2014
2014
2024
2024

Publication Types

Select...
6

Relationship

0
6

Authors

Journals

citations
Cited by 77 publications
(72 citation statements)
references
References 11 publications
0
72
0
Order By: Relevance
“…Software countermeasures can be designed at different levels, such as at an algorithmic level [6], in a high-level programming language [7][8][9] or at assembly level [10][11][12]. While higher level countermeasures may be optimized away or altered by a compiler, low-level countermeasures are compatible with existing compilers and toolchains.…”
Section: Many Countermeasuresmentioning
confidence: 99%
See 4 more Smart Citations
“…Software countermeasures can be designed at different levels, such as at an algorithmic level [6], in a high-level programming language [7][8][9] or at assembly level [10][11][12]. While higher level countermeasures may be optimized away or altered by a compiler, low-level countermeasures are compatible with existing compilers and toolchains.…”
Section: Many Countermeasuresmentioning
confidence: 99%
“…Software countermeasures are often based on temporal redundancy (i.e. performing the same computation multiple times) to detect or tolerate errors during computations [10,12,8,11]. Control flow protection requires different mechanisms to detect a modification of the execution flow [7,14].…”
Section: Related Workmentioning
confidence: 99%
See 3 more Smart Citations