summaryrefslogtreecommitdiffstats
path: root/site/faq
diff options
context:
space:
mode:
authorFrancis Rowe <info@gluglug.org.uk>2015-09-18 14:37:16 (EDT)
committer Francis Rowe <info@gluglug.org.uk>2015-09-18 14:37:16 (EDT)
commit3d9dee496085e73604c9bd8d8785a5e4997a1f85 (patch)
tree5f9547b3dd325271edf48939792c384c4812716d /site/faq
parenta4f80720358dca47030fbd7c726eb5f2fa67c04c (diff)
downloadlibreboot.org-3d9dee496085e73604c9bd8d8785a5e4997a1f85.zip
libreboot.org-3d9dee496085e73604c9bd8d8785a5e4997a1f85.tar.gz
libreboot.org-3d9dee496085e73604c9bd8d8785a5e4997a1f85.tar.bz2
FAQ: fix wrong info
Diffstat (limited to 'site/faq')
-rw-r--r--site/faq/index.php2
1 files changed, 1 insertions, 1 deletions
diff --git a/site/faq/index.php b/site/faq/index.php
index dada502..19b593e 100644
--- a/site/faq/index.php
+++ b/site/faq/index.php
@@ -604,7 +604,7 @@
</p>
<p>
Example attack that malicious firmware could do: substitute your SSH keys, allowing unauthorized remote access by an unknown
- adversary. Or maybe substitute your GPG keys. AHCI (SATA) drives also will have DMA, which means that they could read
+ adversary. Or maybe substitute your GPG keys. SATA drives can also have DMA (through the controller), which means that they could read
from system memory; the drive can have its own hidden storage, theoretically, where it could read your LUKS keys and store them
unencrypted for future retrieval by an adversary.
</p>