aboutsummaryrefslogtreecommitdiff
path: root/docs/security/t60_security.html
diff options
context:
space:
mode:
authorFrancis Rowe <info@gluglug.org.uk>2015-06-28 02:20:19 +0100
committerFrancis Rowe <info@gluglug.org.uk>2015-06-28 02:20:19 +0100
commit0e3520f74d25bc43572a1afeaa4439bfedcc0d78 (patch)
tree0a94f3f6574017e7bd0a8a03f6bd86dae5912db2 /docs/security/t60_security.html
parentd56f1258cc63b9981d29f37530fafd72b5acf904 (diff)
downloadlibrebootfr-0e3520f74d25bc43572a1afeaa4439bfedcc0d78.tar.gz
librebootfr-0e3520f74d25bc43572a1afeaa4439bfedcc0d78.zip
s/machine/system
It was annoying me.
Diffstat (limited to 'docs/security/t60_security.html')
-rw-r--r--docs/security/t60_security.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/security/t60_security.html b/docs/security/t60_security.html
index 03bb2a08..bb2f9bb7 100644
--- a/docs/security/t60_security.html
+++ b/docs/security/t60_security.html
@@ -50,7 +50,7 @@
<p>
This tutorial deals with reducing the number of devices that have direct memory access that
could communicate with inputs/outputs that could be used to remotely
- command the machine (or leak data). All of this is purely theoretical for the time being.
+ command the system (or leak data). All of this is purely theoretical for the time being.
</p>
</div>
@@ -157,7 +157,7 @@
<p>
Remove the shielding containing the motherboard, then flip it over. Remove these screws, placing them on a steady
surface in the same layout as they were in before you removed them. Also, you should mark each screw hole after removing the
- screw (a permanent marker pen will do), this is so that you have a point of reference when re-assembling the machine:<br/>
+ screw (a permanent marker pen will do), this is so that you have a point of reference when re-assembling the system:<br/>
<img src="../images/t60_dev/0027.JPG" alt="" /> <img src="../images/t60_dev/0028.JPG" alt="" /> <img src="../images/t60_dev/0029.JPG" alt="" />
<img src="../images/t60_dev/0031.JPG" alt="" /> <img src="../images/t60_dev/0032.JPG" alt="" /> <img src="../images/t60_dev/0033.JPG" alt="" />
</p>
@@ -170,7 +170,7 @@
record what you say, and use it to receive data from nearby devices if
they're compromised too. Also, we do not know what the built-in microcode (in the CPU) is doing; it could theoretically
be programmed to accept remote commands from some speaker somewhere (remote security hole). <b>In other words,
- the machine could already be compromised from the factory.</b>
+ the system could already be compromised from the factory.</b>
</p>
<p>