Thread replies: 10
Thread images: 3
Thread images: 3
Anonymous
Intel Management Engine 2017-09-10 08:16:09 Post No. 62354425
[Report] Image search: [Google]
Intel Management Engine 2017-09-10 08:16:09 Post No. 62354425
[Report] Image search: [Google]
File: nsaintel.png (8KB, 233x216px) Image search:
[Google]
8KB, 233x216px
What is this feature in my BIOS that seems to be forced in on CPUs newer than Core2? I hear about vulnerabilities constantly. Is this some kind of hardware backdoor? If this is some kind of business feature why would a business choose a hardware remote access that is exploitable over a system-agent like setup? I've looked around online but am having trouble finding just what IME is really supposed to do. Is there any way to remove or block it? Also when configuring the Linux kernel, what does enabling the IME module actually do?
>>
>>62354425
>Is this some kind of hardware backdoor?
Yes.
>>
Should i be concerned enough to disable it? If there is not a way to disable it does AMD RYZEN have something similar?
>>
>>62354902
Can't disable it. Yes.
>>
File: libre-enlightened.png (578KB, 612x1156px) Image search:
[Google]
578KB, 612x1156px
>>62354425
>>
there is a github project that strips it down to the minimally possible configuration that would still allow the processor to work, but throws away as much of the other code as possible.
Works.
But if intel decides to do another microcode update it may reinstall it. Just saying
>>
>>62354425
so how do i use this thing? it should be supported on this cpu but theres no way to access it?
>>
>>62356554
microcode updates are temporary so they cant really change anything. its gone when you remove power from the pc.
>>
File: 1352923472_148028060450a3f950bf6b2_992_11869.jpg (33KB, 680x463px) Image search:
[Google]
33KB, 680x463px
>>62356242
>templeOS in a VM
>>
>>62356554
Sauce of that project?
Thread posts: 10
Thread images: 3
Thread images: 3