On 01/18/18 03:41, Pete Biggs wrote: > >> Look at: >> >> https://t.co/6fT61xgtGH >> >> Get the latest microcode.dat file from here: >> >> https://t.co/zPwagbeJFY >> >> See how to update the microcode from the links at the bottom of this page: >> >> https://t.co/EOgclWdHCw >> >> An before anyone asks .. I have no idea why Red Hat chose this path, >> they did. It doesn't matter if I (or anyone else) agrees with the >> decision. It is what it is. >> > **I'm not blaming you.** > > But can I just clarify. We have to *manually* install the microcode > update an EL7 in order to be protected against Spectre? EL6 as well? > > Presumably this is to remove RH from the loop and to stop people > blaming them - i.e. this is between Intel and the customer, it's > nothing to do with them. I bet you are right. I was going to rant about that... then it occurred to me that class action against Intel (didn't hear about AMD though) is quite likely, so, indeed, RedHat does not want to be even mentioned in it, which will be unfair, especially after RedHat putting effort into fixing somebody's else crap. Valeri > > What about future microcode updates? They come out reasonably regularly > (2 or 3 times a year) - are RH going to absolve themselves from all > future updates because presumably the next update will also contain the > Spectre fixes? > > So, before I re-invent the wheel, does anyone have automation scripts > to do the microcode update? I don't relish the prospect of doing this > manually on a couple of hundred machines. Is it reasonable to grab the > microcode_ctl SRPM and create my own updated RPM to do it? > > P. > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > -- ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++