Where were you when x86 is kill?

>>52256176
What year is this?

>>52256176
This is really old, we had threads about this literally months ago.

>>52256176
Why do you care if you run Windows, you own a cell phone and you run non-free Javascript. If you want freedom in computing, you need to use free software.

>>52256176
Old news, OP


https://github.com/xoreaxeaxeax/sinkhole

>>52256176
Who is this 64 bit sex bit?

>>52256514
Dillion Harper

>>52256276
>>52256201
>>52256199

Uh...everywhere I check it says it's from fall 2015. Pretty new.

>>52258503
>august 2015
>pretty new
As I said in >>52256201 , it's LITERALLY months ago

>>52259715
Oh, so you did agree with me that it's new. I must've read your post wrong.

>>52256176

my name is chrome domus.

>>52259731
It's old. You missed the threads, numbnuts.

>>52259731
There are a bunch of threads about it in the /g/ archives.

>>52258503
It's 2016.

>>52260026
no its becky

>>52259805
It hasn't even been 6 months. It's pretty new.

>>52260981
It has been a few months. It's old.

>>52261016
Which is new

>>52260981
>>>52259805
>It hasn't even been 6 months. It's pretty new.

And for a month it was posted about at least a few times a week, and still averages a thread or two a month

It's old news, the only thing that is new here is you, friend

D E M E N S E M O N
E
M
E
N

S
E
M
O
N

Was this really discovered and reported here by anon? If so, bless him

Anyone wanna explain this to a baby?

>>52256176
Who is this Respectable Human Being?

>>52261578
Processor has thing installed on it to make it compatible with programs from 20 years ago. Still on processor 20 years later. Programmer finds exploit to install software that is undetectable by the OS or even kernel.

>>52261578

>>52261610
>undetectable by the OS or even kernel.
...

CPUs traditionally have a "normal" user mode for programs that limits them from fucking each other up and a kernel mode where trusted OS logic goes that can interfere with normal programs.

When system virtualization was created, a priority mode under (more privileged than) kernel mode was created, and a layer even beneath that was created for Trusted Platform garbage.

The ancient interrupt controller (used to preempt programs whenever a device needed the kernel to do stuff) logic needed to have the hardware memory address it "lived" at movable to prevent some customers' software from breaking, and it turns out there is a sneaky way for pre-Sandy Bridge CPUs to have a normal rootkit move this around and sneak a rootkit into the bottom-most privilege layer that kernels and the hypervisor can't even look at.

File: 37ddd2d62835efa790fd2633c15032d5.jpg (26KB, 322x330px) Image search: [Google]

26KB, 322x330px

>intel in charge of security
This is why I will always chose AMD over intel.

>>52262300
But muhh vPro

So you're going to eat shit if you have a pre sandy bridge processor and get an uber 1337 rootkit right?

Also what is the attack vectors for this vulnerability? Is it just by USB or could you attack your victim through the net?

Finally, this has already been patched on many new processors and AMD doesn't seem to have this problem so angry birds processors won't be replacing x86 anytime soon.

It was fixed by accident years ago, nothing is kill

>>52256176

Delusional RISCfag.

She looks like my sister but better. Wish my sister was this hot.

>>52256514

Seth MacFarlane.

So if im in haswell/devil canyon im fine?

>>52263644
pretty much. Even if you were a nehalemcuck, you'd need the rootkit to be installed by usb (not sure if you can use other attack vectors).

>>52262441
>angry birds processors
I gotta write this one down.

>>52261596
Dillion Harper

>>52256514
Donald Trump