Hardware backdoors in x86

Small correction, turns out I fucked up and kernel actually runs at ring 0.

Regardless of why it's there, it's interesting that it is there, or more importantly, how someone stumbled upon it.
If this was just a mistake, it's useful to know how to detect these bugs BEFORE pushing to market.
If this is intentional, it's still useful to know how to detect one embodiment of this pattern.

Attached: Screenshot_2018-09-01 GOD MODE UNLOCKED - Hardware Backdoors in x86 CPUs - YouTube.png (1488x837, 157.53K)

I phrased my post not entirely correct. What I meant to say was
I agree they are not evil by design, and while you can be secure without, that path is largely unexplored.

Arm goes the other way, with 0 being least priviliged, and 2 and 3 being kernel and hypervisor. At least that way you avoid the negative level retardation we have now.

The process for this is brilliant. How it was continually reduced and automated. The correlations between experiment results and patent descriptions.

Attached: Screenshot_2018-09-01 GOD MODE UNLOCKED - Hardware Backdoors in x86 CPUs - YouTube.png (1488x837, 266.89K)

Do you jerk yourself off on online IQ tests as well pretentious bastard? No one likes what you described, non-spergs just watch the talk and go on with their life, you on the other hand are just utterly retarded.

Attached: 18bc531ceb0cd5ba06d96a5cfb900dc1d1c284140af534e62979e9f947689bf4.png (700x700, 186.66K)

On a few non-Intel and non-AMD CPUs, the instruction was documented clearly as being a debug feature (but docs were hard to find bc niche hardware), and even then the real issue was the products shipping with the debug flag turned on.


because you didn't watch the video


Intentionally giving the 3 letters a 50 years tech advantage is suicidal (they have infinitely better tools and far more experience), and so is isolating your project from the general public (nobody will help or give feedback for something they won't use).


Actions speak louder than words.

why is net wearing a party hat

Why the fuck would they put this in their patents?

in order to ensure those damned jews from RISC-V don't copy such vital features without any legal repercussions

Attached: african iq.png (1600x1757, 240.38K)

People could still use current hardware in the interim. Take, as an analogy, development of a new OS. A new OS is not self-hosting right away. That is no reason to abandon the project. Even once it is self-hosting some tasks cannot be done on the OS. Still not a reason to abandon it.
Debatable. Even if it were the case, governmental agencies only have as must expertise in technology as they can purchase. The experts in technology come up organically and are then conscripted by agencies. Agents are absolute mongoloids when it comes to technology, hence why they go into such jobs in the first place.
I proposed no such thing. On the contrary I specifically stated the need for open hardware. The inability of the average person to fully understand an idea, in this case a hardware design, must not be conflated with an attempt to obfuscate it.
The general public should not be involved in this process. Why would any project aimed at creating open hardware want to invite the general public into the development process? The general public does not have the knowledge necessary to meaningfully contribute and will only get in the way. The new trend of trying to empower the average person and invite him or her into areas he or she is not literate in is a mistake. So many projects are now trying to invite idiots into their ranks. All these new people do is slow down development by introducing more garbage code and features. Now, if a member of the general public is able to educate themselves up to the level necessary to meaningfully contribute, then by all means let them in.