On 11/23/2017 12:47 AM, R0b0t1 wrote:
I think the information I outlined is a pretty good argument for assuming the ME
can not be disabled.
Even if true, there's not much to be done about it anyway
Yeah it certainly can't be disabled (I argue this point on a regular
basis to no avail), as in
On Wed, Nov 22, 2017 at 10:36 PM, taii...@gmx.com wrote:
> On 11/22/2017 11:16 PM, R0b0t1 wrote:
>
>> Does anyone have more information on this? Has anything been
>> published? I'm interested in exploiting my own computers so I can
>> control the ME.
>
> It seems that it is the
On 11/22/2017 11:16 PM, R0b0t1 wrote:
Does anyone have more information on this? Has anything been
published? I'm interested in exploiting my own computers so I can
control the ME.
It seems that it is the same people who figured out HAP mode but they
haven't made a blog update I would ask on
On Wed, Nov 22, 2017 at 6:03 PM, taii...@gmx.com wrote:
> Using ME cleaner would also solve the issue and you wouldn't need any more
> firmware updates when the next "bug" comes around.
>
Intel ME has been found to remain active after being disabled, and
some motherboards that
On Tue, Nov 21, 2017 at 11:42 PM, Adam Carter wrote:
> I notice that an update for sys-firmware/intel-microcode just come through
> on ~amd64, does that address the ME issues?
>
No. As a sidenote, microcode updates can only remove or patch out
functionality. They can't
On 11/22/2017 12:42 AM, Adam Carter wrote:
I notice that an update for sys-firmware/intel-microcode just come through
on ~amd64, does that address the ME issues?
http://www.zdnet.com/article/intel-weve-found-severe-bugs-in-secretive-management-engine-affecting-millions/
Or will my NUC need a
I notice that an update for sys-firmware/intel-microcode just come through
on ~amd64, does that address the ME issues?
http://www.zdnet.com/article/intel-weve-found-severe-bugs-in-secretive-management-engine-affecting-millions/
Or will my NUC need a firmware update?
7 matches
Mail list logo