Live data from Hacker News

Hardware backdoors in some x86 CPUs

github.com

41–50 of 103 posts

Re: Hardware backdoors in some x86 CPUs

#43

Earlier quoted context omitted.

They should have mentioned that in the first line of the github readme, not burried deep down in the text.

Buried? Deep down? The fourth paragraph, clearly labeled "Affected Systems", a minute or two into the read.

We have shorter attention spans now.

Re: Hardware backdoors in some x86 CPUs

#44

Earlier quoted context omitted.

They should have mentioned that in the first line of the github readme, not burried deep down in the text.

Buried? Deep down? The fourth paragraph, clearly labeled "Affected Systems", a minute or two into the read.

Opening with the title "hardware backdoors in x86 CPUs" is quite misleading, though.

Re: Hardware backdoors in some x86 CPUs

#47

This shows that large companies making closed-source CPUs cannot be trusted. No doubt they would add whatever the government asks them to add. What can be done to mitigate this? One option would be to buy a large FPGA and flash it with an open-source CPU. Another would be to emulate a CPU, working with encrypted data and commands, so that even if the backdoor in a host CPU tries to overwrite memory, it would only cra…

Once you control the hosts CPU it's game over for the guest. The best you can do is to fetch old PPC G4 Apple computers or Thinkpads.

Re: Hardware backdoors in some x86 CPUs

#48
post #43

Earlier quoted context omitted.

Buried? Deep down? The fourth paragraph, clearly labeled "Affected Systems", a minute or two into the read.

We have shorter attention spans now.

Multiple things can be true at the same time. While we do have shorter attention spans, some (lots of?) developers absolutely suck at writing articles

Re: Hardware backdoors in some x86 CPUs

#49
post #43

Earlier quoted context omitted.

We have shorter attention spans now.

Multiple things can be true at the same time. While we do have shorter attention spans, some (lots of?) developers absolutely suck at writing articles

I fancy myself as a decent writer, but I suck at writing documentation. People describe reading my notes frustrating and incomprehensible. I find it much better to use AI to untangle my, admittedly, convoluted reasoning

Re: Hardware backdoors in some x86 CPUs

#50

This shows that large companies making closed-source CPUs cannot be trusted. No doubt they would add whatever the government asks them to add. What can be done to mitigate this? One option would be to buy a large FPGA and flash it with an open-source CPU. Another would be to emulate a CPU, working with encrypted data and commands, so that even if the backdoor in a host CPU tries to overwrite memory, it would only cra…

>What can be done to mitigate this?

Buy hardware used by government computers that are rivals to your country.

So if American, buy Chinese CPUs and install Chinese Linux or HarmoneyOS Assuming there is nothing you are doing of interest to them, as that will also have back doors

After Snowden, one can only imagine the worst and think everything has a backdoor.

But unless you are a high level terrorist or other person of interest, no state organization is going to target you at this level

P.s. you say no one can trust closed source, but a lot of open source is maintained by one or two people or a small group, just takes infiltration by one or two trusted contributors to push malicious code in and unless someone looks and finds that code amongst millions of lines of code, may never be discovered (more so as mainstream media won't publish any thing)

Post reply on HN