On Tue, Aug 21, 2018 at 09:17:04AM +1000, wirelessduck@??? wrote:
>
>
> > On 21 Aug 2018, at 02:14, Hendrik Boom <hendrik@???> wrote:
> >
> >> On Mon, Aug 20, 2018 at 02:31:05PM +0100, leloft wrote:
> >>
> >> Tue, 14 Aug 2018 21:52:19 +0000
> >> [SECURITY] [DSA 4272-1] linux security update
> >> version 4.9.110-3+deb9u2
> >> Confirmed: ascii-proposed-updates
> >> Note: this update has been superseded by version 4.9.110-3+deb9u3
> >> confirmed present in ascii-security.
> >> Note: jessie-security contains version 4.9.110-3+deb9u2~deb8u1
> >>
> >> To fully resolve these vulnerabilities it is also necessary to install
> >> updated CPU microcode (only available in Debian non-free). Common server
> >> class CPUs are covered in the update released as DSA 4273-1 (see below).
> >
> > Any idea how the microcode updates work on a machine with a disabled
> > management engine?
> >
> > -- hendrik
>
> Microcode runs on the CPU
>
> https://superuser.com/questions/1283788/what-exactly-is-microcode-and-how-does-it-differ-from-firmware

True; but does it use the management engine to replace the microcode?
I've sen too many systems where you had to something bizarre like
running MSDOS to replace the microcode to be anything but worried.
It just seems like the management engine is tailor-made for this kind
of action.

-- hendrik