PrivSec-dev/privsec.dev
1
0
Fork 0
mirror of https://github.com/PrivSec-dev/privsec.dev synced 2024-11-09 08:21:32 -05:00
Code

Fix pictures

Browse Source 
Signed-off-by: Tommy <contact@tommytran.io>
This commit is contained in:
Tommy 2024-06-10 09:59:11 -07:00
parent 772ed6c82f
commit 39c4d15394
Signed by: Tomster
GPG Key ID: 555C902A34EC968F
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
content/posts/knowledge/Laptop Hardware Security/dell.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 1.7 MiB

After

Width:  |  Height:  |  Size: 1.1 MiB

4
content/posts/knowledge/Laptop Hardware Security/index.md
View File

@ -60,9 +60,9 @@ It is important to note that DRTM technologies can be bypassed via the System Ma
A very common misinformation among privacy communities is that the Intel Management Engine (ME), its sucessor - Intel Converged Security and Management Engine (CSME), and AMD Platform Security Processor (PSP) are some sort of evil backdoor. Some may go so far as to tell the user to "disable the ME", either out of [paranoia](https://www.whonix.org/wiki/System_Hardening_Checklist#Disable_Intel_ME_Functionality) or for ["attack surface reduction"](https://discuss.privacyguides.net/t/linux-laptops-system76-other-options/16557/19):
![Intel ME Misinformation](/images/intel-me-misinfo-1.png)
![Intel ME Misinformation](intel-me-misinfo-1.png)
![Intel ME Misinformation](/images/intel-me-misinfo-2.png)
![Intel ME Misinformation](intel-me-misinfo-2.png)
The problem with these recommendations are as follows: