|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| David Naccache, "Finding Faults," IEEE Security & Privacy, vol. 3, no. 5, pp. 61-65, September/October, 2005. | |||
| BibTex | x | ||
| @article{ 10.1109/MSP.2005.122, author = {David Naccache}, title = {Finding Faults}, journal ={IEEE Security & Privacy}, volume = {3}, number = {5}, issn = {1540-7993}, year = {2005}, pages = {61-65}, doi = {http://doi.ieeecomputersociety.org/10.1109/MSP.2005.122}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Security & Privacy TI - Finding Faults IS - 5 SN - 1540-7993 SP61 EP65 EPD - 61-65 A1 - David Naccache, PY - 2005 KW - fault tolerance KW - fault injection KW - error VL - 3 JA - IEEE Security & Privacy ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MSP.2005.122
The injection of an error can, in fact, cause the leakage of confidential information. Often, the only way to attack strong cryptographic implementations is to attack the infrastructure upon which they are built. This infrastructure is most often the underlying operating system or middleware, but attacks can also be mounted directly against the hardware upon which the cryptographic implementation is being run. This issue's Crypto Corner describes some of the methods used to induce faults in systems and explains how such faults can be exploited to reveal secret information.
Index Terms:
fault tolerance, fault injection, error
Citation:
David Naccache, "Finding Faults," IEEE Security & Privacy, vol. 3, no. 5, pp. 61-65, Sept.-Oct. 2005, doi:10.1109/MSP.2005.122
Usage of this product signifies your acceptance of the Terms of Use.

