2011 Workshop on Fault Diagnosis and Tolerance in Cryptography 2011
DOI: 10.1109/fdtc.2011.12
|View full text |Cite
|
Sign up to set email alerts
|

Practical Optical Fault Injection on Secure Microcontrollers

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
64
0

Year Published

2012
2012
2020
2020

Publication Types

Select...
4
4

Relationship

0
8

Authors

Journals

citations
Cited by 135 publications
(69 citation statements)
references
References 6 publications
0
64
0
Order By: Relevance
“…This would allow a block cipher to be implemented where no check is required to detect whether a fault has occurred since no information would be available to an attacker. This would prevent an attacker from implementing a multiple-fault attack that affects tests at the end of a block cipher [25,18].…”
Section: Further Strengthening the Countermeasurementioning
confidence: 99%
See 1 more Smart Citation
“…This would allow a block cipher to be implemented where no check is required to detect whether a fault has occurred since no information would be available to an attacker. This would prevent an attacker from implementing a multiple-fault attack that affects tests at the end of a block cipher [25,18].…”
Section: Further Strengthening the Countermeasurementioning
confidence: 99%
“…Kim and Quisquater demonstrated that one can attack a cryptographic algorithm and then inject a fault in the verification stage [17]. The natural response would be to make the verification itself redundant but van Woudenberg et al [18] have shown that three faults can be used to attack two tests after the execution of a cryptographic algorithm, i.e. inject one fault in the algorithm itself and use two faults to overcome the redundant verification.…”
Section: Introductionmentioning
confidence: 99%
“…However many of them involves unrealistic assumptions regarding environment and capabilities of the attackers For example, in chosen-cipher text attack, the attacker requires an impractical number of deliberately chosen plaintext-cipher text pairs. It may not be applied over all however the detail that some attack happens should be reason of fear mainly if the attack method has chances for development [16].…”
Section: Practicality Of Attacks-mentioning
confidence: 99%
“…Double fault attacks [9,10], require the attacker clear the difference of data between two encrypted paths during injecting errors. Since our infection countermeasure applies not the two encrypted paths, but the encryption/decryption circuit, so it can avoid suffer double error attacks.…”
Section: The Proposed Random Infection Countermeasurementioning
confidence: 99%
“…This is because the most commonly used infection mechanisms are based on the assumption of the signal fault [4,5,7]. What is worse, with the significantly improving accuracy of fault injections in recent years, it has become possible to carry on double fault attacks at a certain time [9,10].…”
Section: Introductionmentioning
confidence: 99%