News for hackers. Stuff that matters.
Re:Disabling the Intel Management Engine by RetpolineDrama on Wednesday October 26, 2022 @11:45AM (#33345469)
It's absolutely insane that _this_ is what it takes to get IME fully disabled.
Re:Disabling the Intel Management Engine by RunSet on Wednesday October 26, 2022 @12:25PM (#33346005)
But according to Intel it exists to provide functionality that is desired by hardware owners.

Big "Look what you made me do" energy.

Re:Disabling the Intel Management Engine by nonrandomstring on Wednesday October 26, 2022 @12:43PM (#33346236)
> "functionality that is desired by hardware owners"

We hear this all the time don't we? Claims that something is;

"Because people want it".

"Markets demand it".

But we see absolutely no evidence of them whatsoever, this mythical mass of people clamouring for features that are strangely aligned with the things big-tech suppliers and manufacturers wish ti push and get to simply assert that "people want".

We like to think of ourselves as "evidence based, rational society" We'll happily hold governments, scientific and health research to a high standard of evidence. Even Wikipedia articles demand "citation needed".

Show us those people! Back up your claims Intel.

Re:Disabling the Intel Management Engine by iszomer on Wednesday October 26, 2022 @01:36PM (#33346881)
How is Intel ME any different in functionality than the Baseboard Management Controller usually found on servers (eg: Aspeed)? And what of those whom extend these feature sets with boards like the Raspberry Pi?
Re:Disabling the Intel Management Engine by UI_at_80x24 on Wednesday October 26, 2022 @01:53PM (#33347092)
Here's the real kick in the nuts that IME does compared to BMC or other 'Management ports'.

(1) It is not something that you can (easily) disable

(2) It uses the same Network port that your LAN NIC uses instead of a separate "I won't plug that in if I don't want it" NIC.

(3) Security/Patches? This is outside the control of the BIOS manufacturer, so how do you make sure it's patched and upto date? and

(4) It wasn't an option.

Re:Disabling the Intel Management Engine by gwillen on Wednesday October 26, 2022 @06:37PM (#33350550)
Note that the BMC does not always restrict itself to the BMC port. I've worked with machines that have a dedicated BMC port, but also have a BIOS-configurable option (on by default) to let it use whatever port is connected.
Re:Disabling the Intel Management Engine by UI_at_80x24 on Thursday October 27, 2022 @09:11PM (#33366263)
Ouch, atleast it's a BIOS option.
Re:Disabling the Intel Management Engine by wmf on Wednesday October 26, 2022 @02:00PM (#33347193)
That's a really low bar because (1) BMCs are a security nightmare because their firmware is garbage and (2) many PC owners do not need or want BMCs.

I think the ME hating is kinda strident but it has a bunch of undocumented firmware and your PC still works after you remove it so... what was that firmware doing?

Re:Disabling the Intel Management Engine by pexabit on Wednesday October 26, 2022 @01:19PM (#33346685)
The tell is that you cannot even pay more to buy ME-disabled hardware when it is obvious that there is plenty of money in it, at little additional cost to Intel. The workaround in me_cleaner was originally intended for government buyers that demanded it. And they probably had good reason to demand it.
Re:Disabling the Intel Management Engine by djbusby on Wednesday October 26, 2022 @01:50PM (#33347052)
This seems like the hardware owners are demanding the opposite of what Intel is delivering.
Re:Disabling the Intel Management Engine by Manu40 on Wednesday October 26, 2022 @03:17PM (#33348085)
Rather, it's both.

The government folk want it gone from theirs, but they want the rest of us to have it. Thus the claim "Our users want it" is true, in a tongue in cheek way.

Re:Disabling the Intel Management Engine by sidewndr46 on Wednesday October 26, 2022 @01:02PM (#33346492)
I feel similar with 5G. I don't know anyone who was actually demanding 5G speeds from their phone, or excited about it. Technically it's very cool, but I'm unsure it actually is enabling end users to do something they could not.

From my experience, I actually must disable 5G. The 4G network in my area actually works well enough in all circumstances. The 5G network is all-or-nothing. I either wind up with incredible speeds or completely unusable.

Re:Disabling the Intel Management Engine by generalizations on Wednesday October 26, 2022 @01:11PM (#33346602)
Is the end user actually the market this is aimed at? All we really know is that 5G and the Intel ME are endeavors that are expected to make a profit. But who wants this enough to pay for it? Someone does. If not the mass market consumer, then who?
Re:Disabling the Intel Management Engine by cedilla on Wednesday October 26, 2022 @02:49PM (#33347741)
In the case of 5G, telcos love it. It's vastly less expensive to run than any lower G, both in cities and the countryside. That interest even aligns with end users' interest.
Re:Disabling the Intel Management Engine by Manu40 on Wednesday October 26, 2022 @05:51PM (#33350039)
Except they still charge the same anyways, or more.

I'm with Telus up here in Canada. You pay the same old rates as per the usual for 5G speeds. If however you go with their subsidiary (Koodo) using the older infrastructure, you can pay a little less for similar packages.

Check it out yourself. Mind you, I use prepaid, cause I don't want to be on a contract, so I buy my own phone and use it. Koodo even charges more for bringing your own phone, since they aren't collecting on having leased one to you.

https://www.telus.com/en/mobility/prepaid/plans?linktype=sub... https://www.koodomobile.com/en/rate-plans?INTCMP=KMNew_NavMe...

Simply put, if I want to save money while still having enough data for what I actually need data for; I can either spend about 35-40$ with Koodo for 2-4GB of data at 3 & 4G speeds; or 40-50$ for 2.5-4.5GB at 4 & 5G speeds. I round things this way by the way, because of taxes. Also, auto-top up also tends to give some extra data too. 500MB more. So generous of them (/s).

And also, this is new packages. They just updated them with the new promo on Telus with that whole 1GB extra data and 10$ one time credit. I'm gonna have to call them and get that I guess. Unless they auto gave it to me? Who knows with them. Ultimately, I only need 500MB though, since I use Spotify in offline mode, and only download music via my wifi at home; and the only other thing I tend to use is Google Maps which can also be downloaded ahead of time to save on data.

Edit: I should also note that they do actually state 4G on the Telus website, but my phone says I am getting 5G speeds. Hence why I state 5G. I could care less what they claim on their website. End user experience is truth.

Re:Disabling the Intel Management Engine by sidewndr46 on Thursday October 27, 2022 @12:46PM (#33360328)
If it aligned with end-users why not just create a robust narrowband specification that attempts to guaranteed some minimum bandwidth between the device and tower in many different signal conditions? Or would we just call that 4G?
Re:Disabling the Intel Management Engine by Zigurd on Wednesday October 26, 2022 @01:12PM (#33346612)
Some aspects of 5G are sensible in that they take advantage of improving hardware to use spectrum more efficiently: denser encoding, full-duplex radios, etc.

Some of it, like beam steering that tracks moving devices, which is going to be challenging to make it work in real world cases, and using spectrum that makes it hard to penetrate inside cars and buildings, is a reach nobody asked for.

Some seems greed driven, like "If we can convince AWS customers they need to put computing at the network edge we (telcos) will capture some of the value AWS accumulates now."

As for your 4G network, that's what we call 5Ge now.

Re:Disabling the Intel Management Engine by sidewndr46 on Wednesday October 26, 2022 @02:14PM (#33347358)
I knew a guy who worked on cell phone beam forming from the tower 20 years ago. He said it worked flawlessly in Florida where the company was based. He also said every single deployment failed because no where in the US has such a flat terrain without reflections.

Is 5Ge some sort of joke? Or is that a real designation.

Re:Disabling the Intel Management Engine by colejohnson66 on Wednesday October 26, 2022 @08:19PM (#33351404)
> Is 5Ge some sort of joke? Or is that a real designation.

It’s real. My iPhone 13 says it right now. https://arstechnica.com/tech-policy/2020/05/att-still-refuse...

Re:Disabling the Intel Management Engine by kjs3 on Thursday October 27, 2022 @11:18AM (#33358860)
At least in the US, AT&T made the incredibly cynical move to rebrand their 4G service in areas where 5G was expected one day to be available as '5Ge' aka '5G Evolution'. That was so they could 'imply' in ads you were getting a 5G connection before, you know, there was a 5G network to connect to. Even changed the little icon on your phone from 4G to 5Ge.

Sprint sued for the blatant false advertising and AT&T unsurprisingly settled.

Re:Disabling the Intel Management Engine by sidewndr46 on Thursday October 27, 2022 @12:47PM (#33360348)
OK, thanks for clarifying that. I don't have AT&T so I hadn't heard of the term.
Re:Disabling the Intel Management Engine by Spooky23 on Wednesday October 26, 2022 @05:06PM (#33349454)
If you have Verizon, that’s a bad idea as they’ve bungled the rollout and LTE performs poorly in many areas.
Re:Disabling the Intel Management Engine by Mindwipe on Thursday October 27, 2022 @09:07AM (#33356896)
5G offers significant improvements in network congestion.

I want my phone to work in busy cell tower areas, so that is absolutely something I was demanding.

Re:Disabling the Intel Management Engine by dislikedtom2 on Wednesday October 26, 2022 @03:05PM (#33347926)
if someone wants and demands it, it's the nice people at cia and nsa
Re:Disabling the Intel Management Engine by GekkePrutser on Wednesday October 26, 2022 @12:49PM (#33346322)
As hardware owner I disagree.

Both personally and as part of the management team of 150.000 computers at work, we don't use this stuff there either.

Re:Disabling the Intel Management Engine by chasil on Wednesday October 26, 2022 @02:43PM (#33347678)
I can tell you that I have used HPE Integrated Lights Out (iLO) on Gen8/9/10 servers.

It is a great help for server lock-ups - it is able to force a full power-down of the main board and cold-boot.

The software behind iLO was also a presentation at BlackHat, so it's important to keep them patched (and I don't know anybody else that does).

https://www.blackhat.com/us-21/briefings/schedule/index.html...

Re:Disabling the Intel Management Engine by GekkePrutser on Wednesday October 26, 2022 @03:37PM (#33348308)
Yep we use that too but it has nothing to do with IME.

We also have Dells with iDRAC cards. But it's a nice thing with iLO that it's built-in, and it can be managed on a completely dedicated out-of-band network. Unlike the IME thing.

I understand there's a point to this in stuff like servers, but for workstations?

Re:Disabling the Intel Management Engine by Spooky23 on Wednesday October 26, 2022 @05:12PM (#33349524)
I use it to segment network access.

The devices are on an untrusted network and VPN into a LAN based on the device assignment. Things like printers are on a separate network, and there’s no cleartext on the network.

In the case of laptops, if they fall out of certain compliance baselines, they get remote wiped or bricked.

Re:Disabling the Intel Management Engine by GekkePrutser on Thursday October 27, 2022 @07:24AM (#33355987)
We do this too, but based on 802.1x certificates. Devices without this don't get access to the internet and are relegated to a closed VLAN.

But IME is not needed for this. The certs are issued through windows / mac management systems e.g. SCCM/Intune. They are also dependent on the current security state of the machine (e.g. no EDR installed -> only access to remediation network). Is IME really used in your case?

Re:Disabling the Intel Management Engine by Spooky23 on Thursday October 27, 2022 @11:11AM (#33358738)
Depends on the requirements. One I set this up years ago and it uses AMT - IME only provides a few functions although I don’t recall exactly what from memory.

The key difference is that you can provide a level of assurance and multi-tenant access without an OS. For example you can run a hypervisor on the PC and have a few OS instances running.

Re:Disabling the Intel Management Engine by everforward on Wednesday October 26, 2022 @03:27PM (#33348190)
I've used that and Dell's DRAC. They have their uses. We ran those on a separate network, and it was somewhat routine to use them to get into a host that was locked up or had disconnected from the network somehow.

It's definitely a security risk, but at a big company with a poorly managed IT department it wasn't the worst offender.

Re:Disabling the Intel Management Engine by criddell on Wednesday October 26, 2022 @01:36PM (#33346879)
Parts of it you want. The management engine does a lot of stuff and I don't think you can say all of it is good or bad. It would be nice if they would break it down area-by-area and give owners some controls to disable the unnecessary parts.
Re:Disabling the Intel Management Engine by qu4z-2 on Wednesday October 26, 2022 @04:54PM (#33349298)
What is a thing it does that a user may want?
Re:Disabling the Intel Management Engine by criddell on Thursday October 27, 2022 @07:03AM (#33355821)
CPU health monitoring and fan speed control. It’s in the Intel QST which is part of the management engine.
Re:Disabling the Intel Management Engine by qu4z-2 on Friday October 28, 2022 @06:04PM (#33378557)
Thanks :) I just wanted to get down to some concrete examples.
Re:Disabling the Intel Management Engine by flenserboy on Wednesday October 26, 2022 @02:03PM (#33347229)
It makes a body wonder just who Intel thinks the hardware owners are.
Re:Disabling the Intel Management Engine by ridgered4 on Wednesday October 26, 2022 @02:56PM (#33347828)
Knowing Intel, if this functionality was actually desired by hardware owners it would only be available on high end chipsets and i7+ processors.
Re:Disabling the Intel Management Engine by dottedmag on Wednesday October 26, 2022 @12:22PM (#33345973)
Well, it's a very detailed guide how to dump contents of flash device, update and put it back.

If the guide said "dump the flash" and "write back the flash" instead of the detailed instructions, and only described firmware manipulation steps in details it would be much shorter.

Re:Disabling the Intel Management Engine by intelVISA on Wednesday October 26, 2022 @12:25PM (#33346000)
Both absolutely insane and completely understandable.

...hopefully RISC-V will save us from this nightmare.

Re:Disabling the Intel Management Engine by gjsman-1000 on Wednesday October 26, 2022 @12:37PM (#33346154)
Ha - no. Absolutely not. I don't know where this total myth came from that RISC-V is open source therefore implementations will be better.

RISC-V is just an ISA (Instruction Set) that anyone can use, but what people use it in, and how they use it, is not specified and does not have to be open source. Apple could take RISC-V, plop it in their iPhone, and release it tomorrow in a processor that only boots Apple-signed code and requires proprietary firmware without any issue whatsoever. Intel could literally release a Core i5 with a RISC-V instruction set and an Intel ME built-in, no problem.

Where the hope mainly comes from is small chip developers like SiFive, who make many of their drivers and such open-source. But that's only if you buy from vendors like them - if you implement your own RISC-V core, there's no requirement that the drivers or firmware be open-source for it, in any way. You might say that's a missed opportunity. I say RISC-V wouldn't have caught on otherwise.

Re:Disabling the Intel Management Engine by intelVISA on Wednesday October 26, 2022 @12:42PM (#33346225)
Ofc, as you mentioned RISC-V is simply an open-source ISA; however, it is arguably the groundwork for chips independent of Intel/AMD.
Re:Disabling the Intel Management Engine by justinclift on Wednesday October 26, 2022 @12:55PM (#33346399)
> Where the hope mainly comes from is small chip developers like SiFive, who make many of their drivers and such open-source. But that's only if you buy from vendors like them ...

So, you're saying it is possible (or will be down the track...) as long as things are bought from SiFive or a similar OSS-friendly place.

That's still a large improvement over the current situation, even if other vendors take different, locked down approach.

Re:Disabling the Intel Management Engine by evilos on Wednesday October 26, 2022 @01:14PM (#33346631)
So... you're saying someone could (but not necessarily will) save us using RISC-V. Seems like a necessary precondition to it.
Re:Disabling the Intel Management Engine by smoldesu on Wednesday October 26, 2022 @01:32PM (#33346839)
> I don't know where this total myth came from that RISC-V is open source therefore implementations will be better.

The hope is that (unlike x86/ARM) you will be able to purchase core designs from people who aren't sockpuppets. RISC-V will at least let people choose between which backdoor they want installed, which is an upgrade from a status quo of "All Your TCP Traffic Belongs To U.S.".

It's not exactly Superman, descending from the skies to deliver us from dystopia. But it's certainly a better path than letting ARM dominate any more of our chip landscape.

Re:Disabling the Intel Management Engine by walterbell on Wednesday October 26, 2022 @05:03PM (#33349413)
> The hope is that (unlike x86/ARM) you will be able to purchase core designs from people who aren't sockpuppets.

It also lowers the barrier to entry for new/rebranded sockpuppets, but having choices is a step in the right direction.

Re:Disabling the Intel Management Engine by MisterTea on Wednesday October 26, 2022 @01:38PM (#33346896)
> Where the hope mainly comes from is small chip developers like SiFive, who make many of their drivers and such open-source.

But there are still roadblocks as they likely bought the memory controller from a 3rd party as an IP block they drop into their chip. This means the bring up procedure for the memory controller is proprietary and delivered in blob form to be loaded into the black box ip. Likely the same for other 3rd party ip blocks as developing this stuff from scratch is very difficult and time consuming. Especially for critical hardware like memory controllers. This makes opening the platforms firmware just as tricky as any other chip from $bigvendor. This makes full top to bottom security audits difficult or impossible.

Re:Disabling the Intel Management Engine by RobotToaster on Wednesday October 26, 2022 @02:03PM (#33347231)
It's still an improvement over x86, where anyone who manufactured an alternative would be sued into oblivion by intel for patent infringement.
Re:Disabling the Intel Management Engine by sprash on Wednesday October 26, 2022 @02:46PM (#33347705)
Next year all x86_64 patents will expire. From then on everybody can make a IME/PSP/Pluton-free x86_64 chip. This makes RISC V completely obsolete since the x86 ecosystem is obviously much more mature.
Re:Disabling the Intel Management Engine by tmtvl on Wednesday October 26, 2022 @04:58PM (#33349339)
X86 may be mature but I think the M1 has shown that there is plenty of potential for improvement. I know M1 is ARM instead of RISCV, but there may yet be ways to get better chips.

That said, the hardware we have is really good, it's just the software side that is a complete garbage heap.

Re:Disabling the Intel Management Engine by smoldesu on Wednesday October 26, 2022 @05:16PM (#33349592)
Apple Silicon was an interesting move when you look at it from a numbers perspective. The M1 is a really impressive chip, but AMD had competitive x86 hardware that was out on the 7nm node. It benchmarked ~10% slower (the 4800u did, at least), consumed more power (25w max vs 15w max) and ran equally as hot as M1, but it did make me wonder - could AMD have made an M1-class chip if TSMC sold them the 5nm silicon they needed? It's hard to say, and arguably the Zen process wasn't (and still isn't) competitive with Apple's process enhancement.

Still though, AMD seems convinced that x86 can compete against modern RISC ISAs. They aren't far away from proving themselves right, honestly.

Re:Disabling the Intel Management Engine by wmf on Thursday October 27, 2022 @12:43AM (#33353211)
M2 and Ryzen 7000U will both be on TSMC N5 with similar RAM, etc. It will be very interesting to see the comparisons.
Re:Disabling the Intel Management Engine by smoldesu on Wednesday October 26, 2022 @05:13PM (#33349548)
> This makes RISC V completely obsolete since the x86 ecosystem is obviously much more mature.

While I'd really love to agree with you, the IPC of a RISC-V chip can annihilate an x86 machine on equivalently advanced manufacturing node. It's performance-per-watt can reach up to 10x efficiency over x86 in the right situations, and pretty much all of the cool stuff we like in x86 can be added as an ISA extension.

If we're headed to a RISC/low-power computing future, RISC-V will be the future people's champion. x86 will be a legacy compatibility mode that we use for games and "retrocomputing", likely.

Re:Disabling the Intel Management Engine by midislack on Wednesday October 26, 2022 @02:49PM (#33347745)
In the future, buying Chinese designed and made RISV-V will be the way to assure yourself that there’s no extra NSA garbage in there.
Re:Disabling the Intel Management Engine by smolder on Wednesday October 26, 2022 @01:51PM (#33347065)
Depending on the motherboard it can be very hard, pretty easy, or very easy. For my one motherboard that isn't covered by me-cleaner due to the newness, I verifiably turned off ME the "pretty easy" way: By downloading the latest bios from gigabyte, opening it in Intel's CSME tools (there are download links on some forums geared towards bios modding), flipping the unlabeled "reserved bit" which turns on "high assurance platform mode", and then flashing that bios .bin, also with Intel's tools.

I believe some motherboards won't let you flash the modded bios if it's cryptographically unsigned or something like that, which is good for other reasons... but I haven't run into it myself.

I've disabled ME on a couple of supermicro boards too, using me-cleaner, since they were supported. (What I consider the "very easy" method.)

edit: Sibling poster is right that it can't be fully disabled. I do assume it's effectively disabled when it no longer appears in device manager and Intel's ME inspection tools show it as disabled.

Re:Disabling the Intel Management Engine by chasil on Wednesday October 26, 2022 @01:56PM (#33347147)
This does not and cannot "fully disable" the ME subsystem on modern CPUs.

A small remnant is left operational - without it, a PC shuts down after 30 minutes (this is well-known).

The Core 2 Duo/Quad architecture was the last iteration where the ME subsystem could be entirely removed.

I posted two BIOS images on this link for old HP machines. They can easily be flashed from within the booted bios without much hassle. Looking for the link...

Found it on Bing of all places!

https://github.com/corna/me_cleaner/issues/233

Re:Disabling the Intel Management Engine by tomxor on Wednesday October 26, 2022 @02:36PM (#33347600)
> The Core 2 Duo/Quad architecture was the last iteration where the ME subsystem could be entirely removed.

Yeah, but unfortunately intel also didn't bother providing microcode patches for meltdown on those chipsets "because to old" by some arbitrary definition of "old".

Re:Disabling the Intel Management Engine by chasil on Wednesday October 26, 2022 @02:50PM (#33347752)
These are vulnerable to Meltdown, and the page table isolation patches are required to secure kernel memory. These do involve a performance hit, so I'd recommend Core-2 Quad 9550s as an upgrade for a minimally-usable machine.

However, these are not SMT/hyperthreaded, so many of the Specter vulnerabilities do not apply.

OpenBSD runs well enough on them, and these machines are likely what I trust most with this OS.

Most Linux runs on these machines (RedHat 9 doesn't - requires an i3), but will pause on the mei_me module and look for a response from the ME that you have lobotomized; blacklist the related modules if you want to boot faster.

Re:Disabling the Intel Management Engine by chasil on Wednesday October 26, 2022 @06:34PM (#33350516)
The well-known spectre-meltdown check says that my Q9650 is not vulnerable to Meltdown or Spectre 1-3.

It is vulnerable to variant 3a, 4, Fallout, Zombieload, and and both RIDLs.

https://github.com/speed47/spectre-meltdown-checker

Re:Disabling the Intel Management Engine by etiam on Wednesday October 26, 2022 @07:12PM (#33350870)
Sadly I just learned that even the remnants seem to cause known harm

Neither of the two methods to disable the ME discovered so far turned out to be an effective countermeasure against the SA-00086 vulnerability. This is because the vulnerability is in an early-loaded ME module that is essential to boot the main CPU.

https://en.wikipedia.org/wiki/Intel_Management_Engine#Disabl...

Re:Disabling the Intel Management Engine by chasil on Wednesday October 26, 2022 @07:32PM (#33351045)
That is exactly why the Core 2 platform remains popular precisely for this purpose.

A 45nm platform that will do what you ask is far preferable to a 10nm platform that won't.

Re:Disabling the Intel Management Engine by RunSet on Wednesday October 26, 2022 @09:14PM (#33351781)
I observe that the end of the passage you quoted bears a "[citation needed]".
Re:Disabling the Intel Management Engine by chasil on Thursday October 27, 2022 @12:12AM (#33352988)
Will this do?

"Additional major security flaws in the ME affecting a very large number of computers incorporating ME, Trusted Execution Engine (TXE), and Server Platform Services (SPS) firmware, from Skylake in 2015 to Coffee Lake in 2017, were confirmed by Intel on 20 November 2017 (SA-00086).[39] Unlike SA-00075, this bug is even present if AMT is absent, not provisioned or if the ME was ‘disabled’ by any of the known unofficial methods.[40] In July 2018 another set of vulnerabilitites were disclosed (SA-00112).[41] In September 2018, yet another vulnerability was published (SA-00125).[42]"

https://njnewnjnew.medium.com/management-engine-interface-dr...

https://www.theregister.com/2017/12/06/intel_management_engi...

It does make me wonder what else has been missed.

Re:Disabling the Intel Management Engine by RunSet on Thursday October 27, 2022 @08:59AM (#33356805)
> Will this do?

Sorry to be a stickler, but not really.

The citation indexed [40] (that is, the relevant portion) in your quote points to the Register article you also linked, just as the Wikipedia entry does in support of the statement:

"Unlike SA-00075, this bug is even present if AMT is absent, not provisioned or if the ME was "disabled" by any of the known unofficial methods."

That being the case I would expect the Register article to contain something that bolsters the quote above but if it does, it is so subtle as to escape my repeated rereading.