summaryrefslogtreecommitdiffstats
path: root/docs/security
diff options
context:
space:
mode:
Diffstat (limited to 'docs/security')
-rw-r--r--docs/security/t60_security.html6
-rw-r--r--docs/security/x60_security.html6
2 files changed, 6 insertions, 6 deletions
diff --git a/docs/security/t60_security.html b/docs/security/t60_security.html
index 03bb2a0..bb2f9bb 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>
diff --git a/docs/security/x60_security.html b/docs/security/x60_security.html
index bc2f36c..8e84ccb 100644
--- a/docs/security/x60_security.html
+++ b/docs/security/x60_security.html
@@ -56,7 +56,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>
<h1 id="procedure">Disassembly</h1>
@@ -104,7 +104,7 @@
</p>
<p>
- The following is a summary of what you will remove (already done to this machine):<br/>
+ The following is a summary of what you will remove (already done to this system):<br/>
<img src="../images/x60_security/0001_overview.jpg" alt="" /><br/>
Note: the blue lines represent antenna cables and modem cables. You don't need to remove these, but you can if you want
(to make it tidier after removing other parts). I removed the antenna wires, the modem jack, the modem cable and
@@ -119,7 +119,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>