aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFrancis Rowe <info@gluglug.org.uk>2015-10-13 03:24:58 +0100
committerFrancis Rowe <info@gluglug.org.uk>2015-10-13 03:24:58 +0100
commitee3bf61c84440a59b6d576b38c9ed96b90ebaa19 (patch)
tree1b431fc02c89d63d5832c341023e3d7314a2a6dc
parentb523072656419b0fd540f8a65af2ae2100666573 (diff)
downloadlibrebootfr-ee3bf61c84440a59b6d576b38c9ed96b90ebaa19.tar.gz
librebootfr-ee3bf61c84440a59b6d576b38c9ed96b90ebaa19.zip
docs/hcl/c201.html: clarify which type of evil maid attack
-rw-r--r--docs/hcl/c201.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/hcl/c201.html b/docs/hcl/c201.html
index 1a6bbbc8..f58ca4af 100644
--- a/docs/hcl/c201.html
+++ b/docs/hcl/c201.html
@@ -78,7 +78,7 @@
</p>
<p>
Write protection is useful, because it prevents the firmware from being re-flashed by any malicious software that
- might become executed on your GNU/Linux system, as root. In other words, it can prevent an <i>evil maid</i> attack. It's
+ might become executed on your GNU/Linux system, as root. In other words, it can prevent a firmware-level <i>evil maid</i> attack. It's
possible to write protect on all current libreboot systems, but chromebooks make it easy. The screw is such a stupidly
simple idea, which all laptop designs should implement.
</p>