oxeo0/blog-contributions
1
0
Fork 0
mirror of http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions.git synced 2025-07-02 11:56:40 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fixed typos and broken link

Browse source
This commit is contained in:
Zesc 2024-08-24 16:01:33 +02:00
parent 6eb68f0270
commit dcf265743e
38 changed files with 88 additions and 88 deletions
Download patch file Download diff file Expand all files Collapse all files

4
opsec/openhardware/index.html
View file

@ -87,10 +87,10 @@
</ol>
<p>The problem is, <b>if you have closed-source hardware (such as an Intel or AMD CPU, or a nvidia graphics card, or a msi motherboard)</b>, you can at most have open-source software and protocols all the way down to layer 2, <b>but not further below.</b> That's because you have hardware manufacturers creating products, but they are keeping the method as to how they create them a proprietary secret. Because you can't audit it yourself, you can't tell if there is any spyware baked into it or not. </p>
<img src="8.png" class="imgRz">
<p>Take for example AMD's <a href="https://en.wikipedia.org/wiki/AMD_Platform_Security_Processor">PSP</a> or Intel's <a href="https://en.wikipedia.org/wiki/Intel_Management_Engine">Management Engine</a>, which are both alleged backdoors implemented directly in consummers' CPUs. In the case of Intel's processor chipsets, <b>all CPUs since 2008 are to be considered backdoored by Intel ME, and there's nothing you can do about it, without knowing intel's secret way to disable it.</b><a href="https://www.intel.com/content/www/us/en/developer/articles/guide/getting-started-with-active-management-technology.html">[1]</a><a href="https://www.intel.com/content/www/us/en/support/articles/000005974/software/chipset-software.html">[2]</a><a href="https://www.eff.org/deeplinks/2017/05/intels-management-engine-security-hazard-and-users-need-way-disable-it">[3]</a> It is located in the Platform Controller Hub of modern Intel motherboards. </p>
<p>Take for example AMD's <a href="https://en.wikipedia.org/wiki/AMD_Platform_Security_Processor">PSP</a> or Intel's <a href="https://en.wikipedia.org/wiki/Intel_Management_Engine">Management Engine</a>, which are both alleged backdoors implemented directly in consumers' CPUs. In the case of Intel's processor chipsets, <b>all CPUs since 2008 are to be considered backdoored by Intel ME, and there's nothing you can do about it, without knowing intel's secret way to disable it.</b><a href="https://www.intel.com/content/www/us/en/developer/articles/guide/getting-started-with-active-management-technology.html">[1]</a><a href="https://www.intel.com/content/www/us/en/support/articles/000005974/software/chipset-software.html">[2]</a><a href="https://www.eff.org/deeplinks/2017/05/intels-management-engine-security-hazard-and-users-need-way-disable-it">[3]</a> It is located in the Platform Controller Hub of modern Intel motherboards. </p>
<p>check out <a href="https://iv.nowhere.moe/watch?v=0o8Co1ekemU&listen=false">this video</a> for a deep dive into Intel's Management Engine from 36c3 chaoswest 2019.</p>
<p>Regarding non-free firmware, even Debian has been forced to accept this reality in 2022 in their <a href="https://www.debian.org/vote/2022/vote_003">general resolution vote</a>. In short, they now ship non-free firmware by default because 99.999999% of the people out there are running closed-source hardware CPUs, or GPUs, etc.</p>
<p><u>TLDR:</u> if you use closed-source hardware, you won't be able to get open source firware for the CPU, GPU or motherboard. <b>You cannot ever be 100% sure that your hardware itself contains a spying mechanism, because you can't check it yourself, be it in your motherboard, CPU, GPU, or network interfaces.</b> </p>
<p><u>TLDR:</u> if you use closed-source hardware, you won't be able to get open source firmware for the CPU, GPU or motherboard. <b>You cannot ever be 100% sure that your hardware itself contains a spying mechanism, because you can't check it yourself, be it in your motherboard, CPU, GPU, or network interfaces.</b> </p>
</div>
</div><!-- /row -->
</div> <!-- /container -->