41–50 of 93 posts
Hmm, I ensured the mei driver was loaded (lsmod confirms it), but I get: "Cannot open /dev/mei: No such file or directory" dmesg shows: "[ 18.233688] mei_me 0000:00:16.0: Device doesn't have valid ME Interface [ 18.233700] mei_me 0000:00:16.1: Device doesn't have valid ME Interface" So I'm guessing I'm not vulnerable. I suppose Supermicro replaced it with their own IPMI interface.
Earlier quoted context omitted.
I have no BIOS option at all for this, yet it’s enabled and provisioned. What do I do?
Well, firstly, don't connect your machine to networks you don't trust the members of :) If your machine's manufacturer still supports the device, check if they have any firmware updates available. Hopefully they will have recent updates that include a fix for the AMT authn issue. If you want to disable it, Intel has provided a mitigation guide which has instructions on disabling LMS (which AMT is part of): https://do…
I don’t run windows, though.
> Well, firstly, don't connect your machine to networks you don't trust the members of :)
I’ve already had issues with the intel card, so I’m running on a RealTek ethernet card for now anyway. But that’s no long term solution.
Why would Intel insist on being so secretive about their management engine? Is it some kind of competitive advantage for them? Supposedly, it's useful for management tasks in enterprise environments, but if I were CIO, I think I would ban VPro chips. Who wants ring -3 processes running on their network for which they have no information about?
Has anyone else checked their VMware box accordingly?
Hmm, I ensured the mei driver was loaded (lsmod confirms it), but I get: "Cannot open /dev/mei: No such file or directory" dmesg shows: "[ 18.233688] mei_me 0000:00:16.0: Device doesn't have valid ME Interface [ 18.233700] mei_me 0000:00:16.1: Device doesn't have valid ME Interface" So I'm guessing I'm not vulnerable. I suppose Supermicro replaced it with their own IPMI interface.
# git rev-parse HEAD
9aa755885093fc8ca8c822797a30ed98ffe2e166
# make
gcc mei-amt-check.c -o mei-amt-check
# modprobe mei-me
# ./mei-amt-check -v
Cannot open /dev/mei: No such file or directory
# l /dev/*mei*
/bin/ls: cannot access /dev/*mei*: No such file or directory
# dmesg |grep -i mei
#
Hmm, I ensured the mei driver was loaded (lsmod confirms it), but I get: "Cannot open /dev/mei: No such file or directory" dmesg shows: "[ 18.233688] mei_me 0000:00:16.0: Device doesn't have valid ME Interface [ 18.233700] mei_me 0000:00:16.1: Device doesn't have valid ME Interface" So I'm guessing I'm not vulnerable. I suppose Supermicro replaced it with their own IPMI interface.
Earlier quoted context omitted.
Is disabling always possible? I don’t find UI to disable in recent Lenovo ThinkStation BIOS even though I’ve seen such option previously in ThinkPad BIOS.
Intel has provided a mitigation guide that goes through how to disable LMS (local manageability services), which AMT is a part of. Take a look: https://downloadmirror.intel.com/26754/eng/Intel-SA-00075%20...
Earlier quoted context omitted.
Well, firstly, don't connect your machine to networks you don't trust the members of :) If your machine's manufacturer still supports the device, check if they have any firmware updates available. Hopefully they will have recent updates that include a fix for the AMT authn issue. If you want to disable it, Intel has provided a mitigation guide which has instructions on disabling LMS (which AMT is part of): https://do…
The machine is self-assembled, and the motherboard manufacturer doesn’t provide updates. I don’t run windows, though. > Well, firstly, don't connect your machine to networks you don't trust the members of :) I’ve already had issues with the intel card, so I’m running on a RealTek ethernet card for now anyway. But that’s no long term solution.