From 0e3520f74d25bc43572a1afeaa4439bfedcc0d78 Mon Sep 17 00:00:00 2001 From: Francis Rowe Date: Sun, 28 Jun 2015 02:20:19 +0100 Subject: s/machine/system It was annoying me. --- docs/security/x60_security.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/security/x60_security.html') diff --git a/docs/security/x60_security.html b/docs/security/x60_security.html index bc2f36ce..8e84ccbc 100644 --- a/docs/security/x60_security.html +++ b/docs/security/x60_security.html @@ -56,7 +56,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.

Disassembly

@@ -104,7 +104,7 @@

- The following is a summary of what you will remove (already done to this machine):
+ The following is a summary of what you will remove (already done to this system):

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

-- cgit v1.2.3-70-g09d2