From 0e3520f74d25bc43572a1afeaa4439bfedcc0d78 Mon Sep 17 00:00:00 2001 From: Francis Rowe Date: Sat, 27 Jun 2015 21:20:19 -0400 Subject: s/machine/system It was annoying me. --- (limited to 'docs/security/t60_security.html') 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 @@

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.

@@ -157,7 +157,7 @@

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:
+ screw (a permanent marker pen will do), this is so that you have a point of reference when re-assembling the system:

@@ -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). In other words, - the machine could already be compromised from the factory. + the system could already be compromised from the factory.

-- cgit v0.9.1