diff options
| author | Salim B <git@salim.space> | 2023-01-24 22:23:32 +0100 |
|---|---|---|
| committer | Daniel Micay <danielmicay@gmail.com> | 2023-01-24 16:44:24 -0500 |
| commit | 70dc38f1f6cb19e5e8fea116abacf2dfb4c94b09 (patch) | |
| tree | 21a6b354f42216e5fe34ab4f7ae2b7d571cbe4e1 /static/faq.html | |
| parent | 941db078de4a272dbc335da796c17e168a7366c7 (diff) | |
Fix sentence in FAQ
Diffstat (limited to 'static/faq.html')
| -rw-r--r-- | static/faq.html | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/static/faq.html b/static/faq.html index d83fed6e..34475dd9 100644 --- a/static/faq.html +++ b/static/faq.html @@ -1314,11 +1314,11 @@ supported devices.</p> <p>A component being on a separate chip is orthogonal to whether it's isolated. In - order to be isolated, the drivers need to treat it as untrusted. If it has DMA access + order to be isolated, the drivers need to treat it as untrusted. If it has DMA access, that needs to be contained via IOMMU and the driver needs to treat the shared memory - as untrusted, as it would data received another way. There's a lot of attack surface - between the baseband and the kernel/userspace software stack connected to it. OS - security is very relevant to containing hardware components including the radios and + as untrusted, as it would do with data received another way. There's a lot of attack + surface between the baseband and the kernel/userspace software stack connected to it. + OS security is very relevant to containing hardware components including the radios and the vast majority of the attack surface is in software. The OS relies upon the hardware and firmware to be able to contain components but ends up being primarily responsible for it due to control over the configuration of shared memory and the |