-
Notifications
You must be signed in to change notification settings - Fork 53
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
11 changed files
with
96 additions
and
94 deletions.
There are no files selected for viewing
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -445,7 +445,7 @@ <h1 class="title">Low-Level Software Security for Compiler | |
Copyright 2023 Lucian Popescu <a href="mailto:[email protected]" class="email">[email protected]</a><br /> | ||
Copyright 2024 Anders Waldenborg <a href="mailto:[email protected]" class="email">[email protected]</a><br /> | ||
</p> | ||
<p>Version: 0-194-g05b0c3d</p> | ||
<p>Version: 0-196-g248bd20</p> | ||
</header> | ||
|
||
<main id="content"> | ||
|
@@ -2992,9 +2992,10 @@ <h3 data-number="7.3.1" id="common-forms-of-fault-injection-attacks"><span class | |
instruction execution level are often referred to as fault models, where | ||
one can say that a specific fault injection behaves as an instruction | ||
skip, etc. More details about the concept of fault models can be found | ||
in the paper “Fault Attacks on Secure Embedded Software: Threats, Design | ||
and Evaluation” (https://arxiv.org/pdf/2003.10513.pdf), where a good | ||
illustration of the concept is shown in figure 1 of that paper.</p> | ||
in the paper <a href="https://arxiv.org/pdf/2003.10513.pdf">“Fault | ||
Attacks on Secure Embedded Software: Threats, Design and | ||
Evaluation”</a>, where a good illustration of the concept is shown in | ||
figure 1 of that paper.</p> | ||
<span class="todo_ref" href="#todo_31"><sup>todo</sup></span> | ||
<span id="todo_31" class="todo">Make the above reference to a paper use | ||
bibtex. <a href="https://github.com/llsoftsec/llsoftsecbook/issues/159"><img src="data:image/svg+xml;charset=utf-8;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAwIiBoZWlnaHQ9IjIwIiByb2xlPSJpbWciIGFyaWEtbGFiZWw9Imlzc3VlIDE1OTogb3BlbiI+PHRpdGxlPmlzc3VlIDE1OTogb3BlbjwvdGl0bGU+PGxpbmVhckdyYWRpZW50IGlkPSJzIiB4Mj0iMCIgeTI9IjEwMCUiPjxzdG9wIG9mZnNldD0iMCIgc3RvcC1jb2xvcj0iI2JiYiIgc3RvcC1vcGFjaXR5PSIuMSIvPjxzdG9wIG9mZnNldD0iMSIgc3RvcC1vcGFjaXR5PSIuMSIvPjwvbGluZWFyR3JhZGllbnQ+PGNsaXBQYXRoIGlkPSJyIj48cmVjdCB3aWR0aD0iMTAwIiBoZWlnaHQ9IjIwIiByeD0iMyIgZmlsbD0iI2ZmZiIvPjwvY2xpcFBhdGg+PGcgY2xpcC1wYXRoPSJ1cmwoI3IpIj48cmVjdCB3aWR0aD0iNjMiIGhlaWdodD0iMjAiIGZpbGw9IiM1NTUiLz48cmVjdCB4PSI2MyIgd2lkdGg9IjM3IiBoZWlnaHQ9IjIwIiBmaWxsPSIjMmNiZTRlIi8+PHJlY3Qgd2lkdGg9IjEwMCIgaGVpZ2h0PSIyMCIgZmlsbD0idXJsKCNzKSIvPjwvZz48ZyBmaWxsPSIjZmZmIiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBmb250LWZhbWlseT0iVmVyZGFuYSxHZW5ldmEsRGVqYVZ1IFNhbnMsc2Fucy1zZXJpZiIgdGV4dC1yZW5kZXJpbmc9Imdlb21ldHJpY1ByZWNpc2lvbiIgZm9udC1zaXplPSIxMTAiPjx0ZXh0IGFyaWEtaGlkZGVuPSJ0cnVlIiB4PSIzMjUiIHk9IjE1MCIgZmlsbD0iIzAxMDEwMSIgZmlsbC1vcGFjaXR5PSIuMyIgdHJhbnNmb3JtPSJzY2FsZSguMSkiIHRleHRMZW5ndGg9IjUzMCI+aXNzdWUgMTU5PC90ZXh0Pjx0ZXh0IHg9IjMyNSIgeT0iMTQwIiB0cmFuc2Zvcm09InNjYWxlKC4xKSIgZmlsbD0iI2ZmZiIgdGV4dExlbmd0aD0iNTMwIj5pc3N1ZSAxNTk8L3RleHQ+PHRleHQgYXJpYS1oaWRkZW49InRydWUiIHg9IjgwNSIgeT0iMTUwIiBmaWxsPSIjMDEwMTAxIiBmaWxsLW9wYWNpdHk9Ii4zIiB0cmFuc2Zvcm09InNjYWxlKC4xKSIgdGV4dExlbmd0aD0iMjcwIj5vcGVuPC90ZXh0Pjx0ZXh0IHg9IjgwNSIgeT0iMTQwIiB0cmFuc2Zvcm09InNjYWxlKC4xKSIgZmlsbD0iI2ZmZiIgdGV4dExlbmd0aD0iMjcwIj5vcGVuPC90ZXh0PjwvZz48L3N2Zz4=" alt="#159" /></a></span> | ||
|
@@ -3011,8 +3012,8 @@ <h3 data-number="7.3.1" id="common-forms-of-fault-injection-attacks"><span class | |
E.g. When writing a crypto key to a crypto accelerator, forcing the key | ||
value written to be zero (caused to low voltage on bus hardware).</li> | ||
</ul> | ||
<p>Example: Attack on TrustZone for Armv8-M: | ||
https://www.youtube.com/watch?v=4u6BAH8mEDw</p> | ||
<p>Example: <a href="https://www.youtube.com/watch?v=4u6BAH8mEDw">Attack | ||
on TrustZone for Armv8-M</a></p> | ||
<p>There are other forms of physical attacks, but most of them requires | ||
significant effort or cost (e.g. cut open the chip package can carry out | ||
fault injection or readout secret data on chip).</p> | ||
|
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -445,7 +445,7 @@ <h1 class="title">Low-Level Software Security for Compiler | |
Copyright 2023 Lucian Popescu <a href="mailto:[email protected]" class="email">[email protected]</a><br /> | ||
Copyright 2024 Anders Waldenborg <a href="mailto:[email protected]" class="email">[email protected]</a><br /> | ||
</p> | ||
<p>Version: 0-194-g05b0c3d</p> | ||
<p>Version: 0-196-g248bd20</p> | ||
</header> | ||
|
||
<main id="content"> | ||
|
@@ -2992,9 +2992,10 @@ <h3 data-number="7.3.1" id="common-forms-of-fault-injection-attacks"><span class | |
instruction execution level are often referred to as fault models, where | ||
one can say that a specific fault injection behaves as an instruction | ||
skip, etc. More details about the concept of fault models can be found | ||
in the paper “Fault Attacks on Secure Embedded Software: Threats, Design | ||
and Evaluation” (https://arxiv.org/pdf/2003.10513.pdf), where a good | ||
illustration of the concept is shown in figure 1 of that paper.</p> | ||
in the paper <a href="https://arxiv.org/pdf/2003.10513.pdf">“Fault | ||
Attacks on Secure Embedded Software: Threats, Design and | ||
Evaluation”</a>, where a good illustration of the concept is shown in | ||
figure 1 of that paper.</p> | ||
<span class="todo_ref" href="#todo_31"><sup>todo</sup></span> | ||
<span id="todo_31" class="todo">Make the above reference to a paper use | ||
bibtex. <a href="https://github.com/llsoftsec/llsoftsecbook/issues/159"><img src="data:image/svg+xml;charset=utf-8;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB3aWR0aD0iMTAwIiBoZWlnaHQ9IjIwIiByb2xlPSJpbWciIGFyaWEtbGFiZWw9Imlzc3VlIDE1OTogb3BlbiI+PHRpdGxlPmlzc3VlIDE1OTogb3BlbjwvdGl0bGU+PGxpbmVhckdyYWRpZW50IGlkPSJzIiB4Mj0iMCIgeTI9IjEwMCUiPjxzdG9wIG9mZnNldD0iMCIgc3RvcC1jb2xvcj0iI2JiYiIgc3RvcC1vcGFjaXR5PSIuMSIvPjxzdG9wIG9mZnNldD0iMSIgc3RvcC1vcGFjaXR5PSIuMSIvPjwvbGluZWFyR3JhZGllbnQ+PGNsaXBQYXRoIGlkPSJyIj48cmVjdCB3aWR0aD0iMTAwIiBoZWlnaHQ9IjIwIiByeD0iMyIgZmlsbD0iI2ZmZiIvPjwvY2xpcFBhdGg+PGcgY2xpcC1wYXRoPSJ1cmwoI3IpIj48cmVjdCB3aWR0aD0iNjMiIGhlaWdodD0iMjAiIGZpbGw9IiM1NTUiLz48cmVjdCB4PSI2MyIgd2lkdGg9IjM3IiBoZWlnaHQ9IjIwIiBmaWxsPSIjMmNiZTRlIi8+PHJlY3Qgd2lkdGg9IjEwMCIgaGVpZ2h0PSIyMCIgZmlsbD0idXJsKCNzKSIvPjwvZz48ZyBmaWxsPSIjZmZmIiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBmb250LWZhbWlseT0iVmVyZGFuYSxHZW5ldmEsRGVqYVZ1IFNhbnMsc2Fucy1zZXJpZiIgdGV4dC1yZW5kZXJpbmc9Imdlb21ldHJpY1ByZWNpc2lvbiIgZm9udC1zaXplPSIxMTAiPjx0ZXh0IGFyaWEtaGlkZGVuPSJ0cnVlIiB4PSIzMjUiIHk9IjE1MCIgZmlsbD0iIzAxMDEwMSIgZmlsbC1vcGFjaXR5PSIuMyIgdHJhbnNmb3JtPSJzY2FsZSguMSkiIHRleHRMZW5ndGg9IjUzMCI+aXNzdWUgMTU5PC90ZXh0Pjx0ZXh0IHg9IjMyNSIgeT0iMTQwIiB0cmFuc2Zvcm09InNjYWxlKC4xKSIgZmlsbD0iI2ZmZiIgdGV4dExlbmd0aD0iNTMwIj5pc3N1ZSAxNTk8L3RleHQ+PHRleHQgYXJpYS1oaWRkZW49InRydWUiIHg9IjgwNSIgeT0iMTUwIiBmaWxsPSIjMDEwMTAxIiBmaWxsLW9wYWNpdHk9Ii4zIiB0cmFuc2Zvcm09InNjYWxlKC4xKSIgdGV4dExlbmd0aD0iMjcwIj5vcGVuPC90ZXh0Pjx0ZXh0IHg9IjgwNSIgeT0iMTQwIiB0cmFuc2Zvcm09InNjYWxlKC4xKSIgZmlsbD0iI2ZmZiIgdGV4dExlbmd0aD0iMjcwIj5vcGVuPC90ZXh0PjwvZz48L3N2Zz4=" alt="#159" /></a></span> | ||
|
@@ -3011,8 +3012,8 @@ <h3 data-number="7.3.1" id="common-forms-of-fault-injection-attacks"><span class | |
E.g. When writing a crypto key to a crypto accelerator, forcing the key | ||
value written to be zero (caused to low voltage on bus hardware).</li> | ||
</ul> | ||
<p>Example: Attack on TrustZone for Armv8-M: | ||
https://www.youtube.com/watch?v=4u6BAH8mEDw</p> | ||
<p>Example: <a href="https://www.youtube.com/watch?v=4u6BAH8mEDw">Attack | ||
on TrustZone for Armv8-M</a></p> | ||
<p>There are other forms of physical attacks, but most of them requires | ||
significant effort or cost (e.g. cut open the chip package can carry out | ||
fault injection or readout secret data on chip).</p> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -180,7 +180,7 @@ | |
Copyright 2024 Anders Waldenborg | ||
\href{mailto:[email protected]}{\nolinkurl{[email protected]}}\\ | ||
|
||
Version 0-194-g05b0c3d | ||
Version 0-196-g248bd20 | ||
\clearpage | ||
|
||
{ | ||
|
@@ -3625,8 +3625,8 @@ \subsection{Common forms of Fault injection | |
instruction execution level are often referred to as fault models, where | ||
one can say that a specific fault injection behaves as an instruction | ||
skip, etc. More details about the concept of fault models can be found | ||
in the paper ``Fault Attacks on Secure Embedded Software: Threats, | ||
Design and Evaluation'' (https://arxiv.org/pdf/2003.10513.pdf), where a | ||
in the paper \href{https://arxiv.org/pdf/2003.10513.pdf}{``Fault Attacks | ||
on Secure Embedded Software: Threats, Design and Evaluation''}, where a | ||
good illustration of the concept is shown in figure 1 of that paper. | ||
\tododiv{Make the above reference to a paper use bibtex. | ||
|
@@ -3651,8 +3651,8 @@ \subsection{Common forms of Fault injection | |
value written to be zero (caused to low voltage on bus hardware). | ||
\end{itemize} | ||
Example: Attack on TrustZone for Armv8-M: | ||
https://www.youtube.com/watch?v=4u6BAH8mEDw | ||
Example: \href{https://www.youtube.com/watch?v=4u6BAH8mEDw}{Attack on | ||
TrustZone for Armv8-M} | ||
There are other forms of physical attacks, but most of them requires | ||
significant effort or cost (e.g.~cut open the chip package can carry out | ||
|
Oops, something went wrong.